Live  /  OpenSRS  /  Incident

OpenSRS: API timeouts

OpenSRS · opensrs.comMinor incidentResolved2026-10-07 19:02 UTC
Public — what happened

Summary

OpenSRS said it was looking into a problem with its API starting at 16:57 UTC on October 7, 2026, which it rated as minor. According to the company, resellers could run into sluggish responses, timed-out calls or occasional failures when sending API requests. By 17:13 UTC OpenSRS reported that performance was getting better and service was recovering, and it kept watching the system before marking the issue resolved at 19:02. The company did not say what caused the problem.

Affected

OpenSRS API

As listed on OpenSRS’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 42, 2026, our weekly internet health report.

The full archive is on the OpenSRS status & history page.

Related: OpenSRS status & history. SquidGrid is not affiliated with OpenSRS.