testRigor Outage History
12 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 testRigor Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 16, 2026 | Scheduled maintenanceMaintenance has been concluded, test cases can be executed as usual. | 17 min | Resolved |
| Sep 11, 2026 | Test cases stuck in queueThe issue has been fixed, and test cases should be executing as expected. | 5h 0m | Resolved |
| Jul 13, 2026 | We're currently experiencing issues with email functionality.This incident has been resolved. | 4h 1m | Resolved |
| Jun 1, 2026 | Ubuntu/external infrastructure devices are partially downThis incident has been resolved. | 3h 31m | Resolved |
| May 16, 2026 | Android Testing agents maintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Apr 28, 2026 | Test cases are getting stuck in queueIssue has been fixed. All is back to normal. | 11h 23m | Resolved |
| Apr 24, 2026 | Intermitent failures on test cases due to networking issues on AzureThis incident has been resolved. | 23h 36m | Resolved |
| Mar 7, 2026 | Previous scheduled maintenance extendedThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Mar 7, 2026 | Testing agents infra maintenanceThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Dec 15, 2025 | Problems processing queue of testsThis incident has been resolved. | 46h 35m | Resolved |
| Nov 18, 2025 | testRigor is not accessible due to cloudflare error code 500This incident has been resolved. | 4h 33m | Resolved |
| Nov 10, 2025 | Android Test Execution StuckThis incident has been resolved. | 9h 1m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next testRigor incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This testRigor 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 testRigor 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 testRigor outage in this window ran 1d 22h, against a mean recovery of 9h 35m. If you depend on testRigor 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.