Status archive for August, 2009
.net is Online
The .NET maintenance is complete.
.com is Online
The .COM maintenance is complete.
.com is In Maintenance
The .COM registry has a scheduled maintenance starting now (01:00 UTC).
Service impact:
Domain provisioning and Whois will be unavailable. Customers who have enabled provisioning queuing will have their orders queued until this complete. Domains will continue to resolve.
.net is In Maintenance
The .NET registry has a scheduled maintenance starting now (01:00 UTC).
Service impact:
Domain provisioning and Whois will be unavailable. Customers who have enabled provisioning queuing will have their orders queued until this complete. Domains will continue to resolve.
.tv is Online
.TV is online. Our network monitoring alerts have cleared and we have tested our connection with the registry. We confirm that all services are working well.
We will provide an incident summary later today.
.cc is Online
.CC is back online. Our network monitoring alerts have cleared and we have tested our connection with the registry. We confirm that all services are working well. We will provide an incident summary later today.
.tv is Offline
We contacted the .TV registry after receiving alerts on our networking monitoring. They are investigating a connection issue. Provisioning requests are not available at this time.
Domains continue to resolve.
.cc is Offline
We contacted the .CC registry after receiving alerts on our networking monitoring. They are investigating a connection issue. Provisioning requests are not available at this time.
Domains continue to resolve.
.de is Online
The .DE registry maintenance is complete.
.de is In Maintenance
There is a 1-hour maintenance ending at 16:30 UTC. We just contacted the registry and confirmed the window. Unfortunately, we also had no advance notice.
Service Impact: Domain provisioning and Whois will be unavailable. Customers who have queuing enabled will have their orders queued until this is complete.
Domains will continue to resolve.
This update is related to Incident 7929

