Status archive for March, 2010
.org is Online
The .ORG registry maintenance is complete.
.asia is Online
The .ASIA registry maintenance is complete.
.org is In Maintenance
There is a 4-hour .ORG registry 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.
.asia is In Maintenance
The .ASIA registry has a 4-hour scheduled 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.
.info is In Maintenance
The .INFO 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.
.eu is Online
The .EU registry maintenance is complete.
.eu is In Maintenance
There is a 2-hour .EU registry maintenance starting now (05: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.
Storefront is Online
All Storefront services are online. Our technical teams fully tested and confirm all services are available.
Incident Summary: (Updated: March 24, 2010: 20:53 UTC/16:53 ET)
Our OpenSRS Storefront service began receiving a spike of connections outside of our acceptable use limits. Resellers may have encountered connection issues or timeouts for Storefront. We notified resellers that services were degraded. There was an approximate 6-10% failure rate for domain look-ups, domain registrations and changes. Our technical teams identified and addressed the source. We restarted services, tested and confirmed all were fully available.
To improve our early detection processes, we are implementing further improvements to our Nagios monitoring. We are also adding a rate-limit rule for one component of our services. The amount is well-over the expected use and is a preventative measure.
This update is related to Incident 11426
Domain Service is Online
All Domains services are online. Our technical teams fully tested and confirm all services are available.
Incident Summary: (Updated: March 24, 2010: 20:53 UTC/16:53 ET)
OpenSRS Services began receiving a spike of connections outside of our acceptable use limits. Resellers may have encountered connection issues or timeouts for OpenSRS services. We notified resellers that services were degraded. There was an approximate 6-10% failure rate for domain look-ups, domain registrations and changes. Our technical teams identified and addressed the source. We restarted services, tested and confirmed all were fully available.
To improve our early detection processes, we are implementing further improvements to our Nagios monitoring. We are also adding a rate-limit rule for one component of our services. The amount is well-over the expected use and is a preventative measure.
This update is related to Incident 11426
Storefront is Degraded
We are investigating degraded services for Storefront services. Customers may encounter connection issues or timeouts. Our technical teams will be providing more information on the symptoms shortly.
Update: 18:12 UTC
We are testing domain look-ups, new registrations and other changes for your services.
Update: 18:13 UTC
We are restarting services services and continue to closely monitor. Services appear to be working better. We will keep you posted.
Update: 18:19 UTC
Services are available. Our NOC team is closely monitoring and testing services. We are leaving the status as degraded while we confirm that the issue is resolved.
This update is related to Incident 11426