Live / OpenSRS / Incident
OpenSRS: Issues with .ES Domain Registration Orders
OpenSRS · opensrs.comMinor incidentResolved2026-11-12 22:03 UTC
Public — what happened
Summary
OpenSRS said that starting at 13:27 UTC on 2026-11-12, new orders to register .ES domain names were affected, with customers possibly seeing delays, failed orders or errors. The company said its engineers worked with the registry on the problem, and by 19:56 UTC it reported that only certain .ES domains tied to specific contact identification types were still hitting validation errors while other registrations went through normally. OpenSRS said engineers had confirmed the root cause and were finalizing a fix, and the incident was marked resolved at 22:03 UTC.
Affected
Core ccTLDs
Timeline
- Started — 2026-11-12 13:27 UTC
- Investigating — 2026-11-12 13:27 UTC (2 updates)
- Identified — 2026-11-12 19:56 UTC
- Resolved — 2026-11-12 22:03 UTC · 8h 36m 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 47, 2026, our weekly internet health report.