Live / Incidents / OpenSRS
OpenSRS: Degraded API performance
OpenSRS · opensrs.comImpact: majorResolved2026-10-04 11:05 UTC
Public — what happened
Summary
OpenSRS reported a major incident on October 4, 2026, starting at 09:20 UTC, in which its API was failing to accept connections. The company said customers could see slow responses or failed requests when calling the API. By 09:26 UTC, OpenSRS said its engineers had put a fix in place and services were back to normal, though it did not name a cause. The incident remains open while the company watches to make sure things stay stable.
Timeline
- Started — 2026-10-04 09:20 UTC
- Last update — 2026-10-04 11:05 UTC
- Resolved — 2026-10-04 11:05 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach OpenSRS against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for OpenSRS: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the OpenSRS report →