Live / OpenSRS / Incident
OpenSRS: API Timeouts
OpenSRS · opensrs.comMajor incidentResolved2026-10-01 12:53 UTC
Public — what happened
Summary
OpenSRS reported a major incident beginning at 07:53 UTC on October 1, 2026, in which customers could see sluggish responses or failed connections when using its API. As the day went on, the company said the problems also reached the reseller control panel, including both the Classic Interface and the New Reseller Interface. OpenSRS said at 09:39 UTC that its engineers had found the underlying cause, though it did not describe it, and by 10:34 UTC it reported that systems were gradually coming back. After saying services had held steady for roughly an hour, the company marked the incident resolved at 12:53 UTC.
Timeline
- Started — 2026-10-01 07:53 UTC
- Investigating — 2026-10-01 07:53 UTC (2 updates)
- Identified — 2026-10-01 09:39 UTC
- Monitoring — 2026-10-01 10:34 UTC (2 updates)
- Resolved — 2026-10-01 12:53 UTC · 5h after it started
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 →
More from OpenSRS
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.