Updates related to Incident 5331
.es is Online
.ES is online.
Incident summary:
The .ES registry experienced latency issues resulting connection timeouts for the past few weeks. OpenSRS consistently tested the service availability during peak and non-peak hours on a daily basis. Our tests identified ongoing issues. We communicated with the .ES registry on a regular basis advising that we could not provide .ES services to our customers. The .ES registry technical department was able to isolate the latency issue to one of their servers. They addressed this issue. Testing by the registry and our NOC/Ops departments showed that response times improved significantly. The .ES services were returned online.
This update is related to Incident 5331
.es is Offline
The .ES services are offline. We were noticing longer and longer response times and contacted the registry, who advised that they have been experiencing a recurrence of the issues which previously took them offline. We will continue to follow-up and advise you of any changes.
This update is related to Incident 5331
.es is Online
.ES is online. We monitored service availability through European peak hours.We confirm that the registry latency issues which were causing connection timeouts has reduced significantly and service is available.
This update is related to Incident 5331
.es is Offline
The .ES services are offline. We were noticing longer and longer response times and contacted the registry, who advised that they have been experiencing a recurrence of the issues which previously took them offline. We will continue to follow-up and advise you of any changes.
This update is related to Incident 5331
.es is Online
.ES is online. We monitored service availability through European peak hours.We confirm that the registry latency issues which were causing connection timeouts has reduced significantly and service is available.
This update is related to Incident 5331
.es is Offline
Our NOC and OPs team are closely monitoring the .ES services. The latency and timeout issue which the registry experienced over the past few days has decreased. Once we reach peak hours, we will determine if we can confirm the status back as available.
This update is related to Incident 5331
.es is Offline
We have been in contact with the .ES registry. Our NOC and Ops teams have tested and still note that the connection times to the registry are still not at the optimum rates. We will continue to work with the registry and closely monitor the service availability.
This update is related to Incident 5331
.es is Offline
.ES services remain offline. The .ES registry advised that they are experiencing latency issues with their database which is causing high connection/timeout issues for this service. If we are advised that the services are restored, we will fully test availability of .ES services and advise accordingly.
This update is related to Incident 5331
.es is Offline
The .ES registry has confirmed latency problems on their end. Their technical department is investigating. Services for .ES continue to be offline.
This update is related to Incident 5331
.es is Offline
The .ES services are unavailable. Our NOC and Ops testing and monitoring observed that the .ES connections were timing out.
We will be contacting the registry to investigate.
This update is related to Incident 5331