Testsigma Outage History
8 incidents recorded over the last 365 days, 8 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 Testsigma Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 23, 2026 | PHP Vulnerabilities (CVE-2026-109618 & CVE-2026-109619) - ResolvedOn October 21, 2026, the PHP project disclosed two critical vulnerabilities in the PHP runtime (CVE-2026-109618 and CVE-2026-109619, also known as "PHP2Shell"). PHP is not used in the Testsigma platform, including the… | -3518 min | Resolved |
| Oct 23, 2026 | Degraded performance in the US region: slowness and intermittent errorsThis incident has been resolved. The fix has been deployed, the affected data has been cleaned up, and the platform has remained stable since. We apologise for the disruption and thank you for your patience. | 44h 38m | Resolved |
| Oct 15, 2026 | Degraded availability of the Testsigma Web App, US region## Summary On 14 October 2026, between 09:00 and 09:06 IST \(03:30 to 03:36 UTC\), the Testsigma web application in the US region was unavailable for approximately six minutes. A routine cleanup job caused one database… | -2042 min | Resolved |
| Oct 3, 2026 | Degraded availability of the Testsigma Web App, US region## Summary On 1 October 2026, between 13:27 and 13:31 IST \(07:57 to 08:01 UTC\), the Testsigma web application in the US region was unavailable for approximately four minutes. A burst of requests from a single API… | -2909 min | Resolved |
| May 25, 2026 | Some Customers Experienced Testsigma Terminal Connection Issues Due to Configuration Problem### **Incident Summary** On **May 22nd**, **some customers** faced issues with their local **Testsigma Terminal** connections. The incident was caused by a configuration problem that affected the terminal’s ability to… | -4286 min | Resolved |
| Mar 19, 2026 | Application Availability Issue – US RegionWe experienced an issue affecting application availability in the US region, where some users may have faced difficulty accessing the platform or experienced degraded performance. Initial investigation indicated that… | -109 min | Resolved |
| Dec 16, 2025 | Application Not Accessible - EU Region# **Root Cause Analysis \(RCA\) – Database Service Disruption** ## **Incident Summary** On **16th December, 2025**, the database service experienced an unexpected outage caused by **heavy load generated from an… | 6h 9m | Resolved |
| Dec 11, 2025 | Application Not Accessible - EU RegionWe have resolved the database server incident that impacted customers in the Europe region. Services have been restored, and we are closely monitoring the system for any further issues. | 6h 27m | 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 Testsigma 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 Testsigma 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 Testsigma 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 Testsigma outage in this window ran 1d 20h, against a mean recovery of 19h 5m. If you depend on Testsigma 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.