Status archive for February, 2010
.org is Online
The .ORG maintenance is complete.
.org is In Maintenance
The .ORG registry has a 4-hour maintenance starting now (15:00 UTC).
Service Impact for Resellers:
Domain provisioning and Whois will be unavailable. Customers who have enabled provisioning queuing will have their orders queued until this complete.
Service Impact for End-users:
Domains will continue to resolve.
.es is In Maintenance
The .ES registry has an extended 24-hour maintenance starting now (23:00 UTC).
Service Impact for Resellers:
Domain provisioning and Whois will be unavailable. Customers who have enabled provisioning queuing will have their orders queued until this complete.
Service Impact for End-users:
Domains will continue to resolve.
.es is Online
.es is online.All services are available.
This update is related to Incident 10615
.es is Offline
We are experiencing connection issues with the .ES registry. All .ES services including domain look-ups, changes and renewals are unavailable. Our Technical teams continue to investigate.
We contacted the registry. (Please note that it is after .ES business hours and the response may be delayed.)
Domains continue to resolve.
This update is related to Incident 10615
.es is Degraded
We are experiencing intermittent connection issues with the .ES registry. Resellers may experience intermittent connection or timeout issues for .ES domain look-ups.
We contacted the registry to investigate. (Please note that it is after .ES business hours and the response may be delayed.)
This update is related to Incident 10615
.es is Online
.ES services are online. There were high connections with the .ES registry resulting in timeouts.
This update is related to Incident 10603
.es is Offline
.ES services are unavailable. Our technical teams are investigating and our NOC team is contacting the registry.
This update is related to Incident 10603
Storefront is Online
All Storefront services are online. We addressed the issue which was causing domain look-up/name suggestion errors.
Incident Summary (Updated:February 17, 2010: 16:17 ET/21:17 UTC):
The incident was caused by a name resolution timeout error on a database component, part of the name suggestion service. The result was that Storefront domain look-ups were intermittently unavailable. We advised customers at 16:22 ET/21:22 UTC. Our technical teams quickly identified and addressed it. A minor authorized change to our internal DNS service implemented a number of hours prior to the Incident has been determined as being the root cause for those errors. We advised customers that it was resolved at 16:44ET/ 21:44 UTC.
This update is related to Incident 10593
Domain Service is Online
All Domains services are online. We addressed the issue which was causing domain look-up/name suggestion errors.
Incident summary (Updated: February 17, 2010 16:17ET / 21:17 UTC):
The incident was caused by a name resolution timeout error on a database component, part of the name suggestion service. The result was that domain look-ups were intermittently unavailable. We advised customers at 16:22 ET/21:22 UTC. Our technical teams quickly identified and addressed it. A minor authorized change to our internal DNS service implemented a number of hours prior to the Incident has been determined as being the root cause for those errors. We advised customers that it was resolved at 16:44ET/ 21:44 UTC.
This update is related to Incident 10593