Live  /  OpenSRS  /  Incident

OpenSRS: Degraded performance on Database

OpenSRS · opensrs.comMajor incidentResolved2026-10-01 17:51 UTC
Public — what happened

Summary

OpenSRS reported a major incident involving slower-than-normal performance of its database, beginning at 17:04 UTC on 2026-10-01. The company said orders for new registrations and renewals might go through without customers receiving a notification or being billed, and that some customers could see delays or errors when placing orders. In an update at 17:51 UTC, OpenSRS said its engineers were still working on the problem; no cause had been named and the status remained under investigation.

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 41, 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.