OpenSRS System Status » .cn

Online

James Koole — Sun, 25 Dec 2011 02:00:28 +0000

The .CN maintenance is complete.

In Maintenance

James Koole — Sat, 24 Dec 2011 15:50:16 +0000

The .CN registry has a 10 hour scheduled maintenance period beginning now. Management of .CN names won't be possible during this time.

Online

James Koole — Sat, 12 Nov 2011 14:00:31 +0000

The .BIZ, .CO and .CN registry maintenance is complete.

In Maintenance

James Koole — Sat, 12 Nov 2011 12:50:58 +0000

The .BIZ, .CO and .CN registries have a 1 hour maintenance window beginning now. During this window, it won't be possible to make changes to existing .BIZ, .CO and .CN domains or to register new .BIZ, .CO and .CN domains.

Online

BenLucier — Sun, 18 Sep 2011 10:28:51 +0000

Our monitoring systems confirmed this TLD is back online. The Registry operator also confirmed the earlier trouble has been resolved.

Offline

BenLucier — Sun, 18 Sep 2011 09:23:56 +0000

We are seeing connectivity issues with this TLD, which is preventing new registrations. Neustar has confirmed the issue is at their end and they are currently working on it. There is no ETA at the moment, but we'll provide updates as they become available.

Online

amccallum — Sat, 20 Aug 2011 16:00:34 +0000

The .CN registry maintenance has completed.

In Maintenance

amccallum — Sat, 20 Aug 2011 11:45:33 +0000

The .CN registry has a scheduled maintenance on Saturday, August 20, 2011 UTC.

Service Impact for Resellers:
Domain renewals and transfers to .CN domains will not be possible. Customers who have enabled provisioning queuing will have their orders queued until this complete.

Service Impact for End-users:
Domains will continue to resolve.

Date: Saturday, August 20, 2011 UTC
Time: 12:00 - 16:00 UTC
Duration: 6 hours

Online

amccallum — Sun, 27 Feb 2011 06:00:38 +0000

The .BIZ, .US, .CO, .TEL, and .CN Registry maintenance has completed.

Online

James Koole — Fri, 07 Jan 2011 17:35:33 +0000

Our connection to Neustar has been restored.

We don't have anything official to provide in terms of an explanation or incident report just yet, but we'll provide more information about what happened in the next couple of days. That summary will be published at the bottom of this status update once it's available.

Our apologies for any inconvenience that this may have caused.