Runscope Outage History
17 incidents recorded over the last 365 days, 9 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Runscope Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| May 26, 2026 | Capacity Issues with Google Public LocationsThis incident has been resolved. | 144h 34m | Resolved |
| May 7, 2026 | New User Registrations are currently brokenThe incident with new user registration has been resolved | 13h 37m | Resolved |
| Mar 30, 2026 | Issue with JMeter Plugins Repository CertificateOur tests are continuing to run as expected and we have received confirmation from other sources as well. At this time, we are resolving the incident. | 3h 38m | Resolved |
| Feb 22, 2026 | Scheduled Platform Maintenance on Sunday, February 22nd (2am-4am EST)The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jan 21, 2026 | Some Dedicated IPs Encountering Issues when Running TestsThe fixes that have been applied are working as expected and teams should be able to use their Dedicated IPs again without issue. We are resolving the incident at this time | 1h 14m | Resolved |
| Jan 4, 2026 | Scheduled Platform Maintenance on Sunday, January 4th (5am-9am EST)The scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Dec 19, 2025 | Platform Maintenance on Thursday, December 18th - Friday, December 19th (10pm-2am EST)The scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Dec 14, 2025 | Scheduled Platform Maintenance on Sunday, December 14th (2am-6am EST)The scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Nov 30, 2025 | Scheduled Platform Maintenance on Sunday, November 30th (2am-6am EST)The scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Nov 9, 2025 | Scheduled Platform Maintenance on Sunday, November 9th (2am-6am EST)The scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Oct 26, 2025 | Scheduled Platform Maintenance on Sunday, October 26th (3am–5am EST)The scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Oct 15, 2025 | Issues with Starting or Stopping Tests due to database maintenance.This incident has been resolved. | 1h 30m | Resolved |
| Oct 7, 2025 | mock.blazemeter.com was briefly displaying a 404 when navigating to it.We are resolving the incident now as the issue has been fixed for some time and we have given time for users to see the message. As a reminder, if you Services are in Failed state then you just need to restart them and… | 1h 16m | Resolved |
| Oct 3, 2025 | The US Illinois Location for API Monitoring is offlineOur tests have continued to run successfully from the US Illinois location. At this time you may resume utilizing the US Illinois location in your tests if you would like. We are closing the incident now. | 1h 35m | Resolved |
| Sep 28, 2025 | Scheduled Platform Maintenance on Sunday, September 28th (2am-6am EDT)The scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Sep 24, 2025 | DATA Processing delays in BlazemeterWe are no longer seeing the data processing delays with our tests at this time. We are resolving the incident now, but will continue to monitor for any potentially lingering issues. | 4h 58m | Resolved |
| Sep 11, 2025 | Data Processing Delays Causing Long Test Shutdown TimesThe fix for the data processing issue has been deployed now and we are seeing improvement in our tests as well. At this time we are resolving the incident. | 1h 46m | Resolved |
How to Read This Runscope Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Runscope acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Runscope outage in this window ran 6d, against a mean recovery of 11h 43m. If you depend on Runscope in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.