.name Status Archive

.name is In Maintenance

Updated Tuesday, May 3rd, 2011 at 7:00 PM ET
2011-05-03 at 23:00 UTC - Other time zones

The .NAME registry has scheduled maintenance on Tuesday, May 3, 2011 UTC to Wednesday, May 4, 2011 UTC.

Service Impact for Resellers:
The registry has indicated that there will be brief, intermittent outages during the 1 hour of maintenance. Domain provisioning, renewals, transfers, availability checks and modifications to .NAME domains may not be possible for brief periods of time. 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: Tuesday, May 3, 2011 UTC to Wednesday, May 4, 2011 UTC
Time: 23:15 on Tuesday, May 3, 2011 UTC to 00:15 on Wednesday, May 4, 2011 UTC
Duration: 1 hour

.name is Online

Updated Saturday, April 2nd, 2011 at 11:00 PM ET
2011-04-03 at 3:00 UTC - Other time zones

The .NAME registry maintenance has completed.

.name is In Maintenance

Updated Saturday, April 2nd, 2011 at 8:45 PM ET
2011-04-03 at 0:45 UTC - Other time zones

The .NAME registry has a scheduled maintenance on Sunday, April 3, 2011 UTC.

Service Impact for Resellers:

The .NAME registry has indicated they may have brief interruptions in connections to their system, but connections will resume activity within a few minutes. These connection losses would affect domain provisioning, renewals, transfers, availability checks and modifications to .NAME domains. Except for availability checks to domain names which require a response back from the registry, 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: Sunday, April 3, 2011 UTC.
Time: 1:00 - 3:00 UTC
Duration: 2 hours

.name is Online

Updated Sunday, January 23rd, 2011 at 1:00 AM ET
2011-01-23 at 5:00 UTC - Other time zones

The .INFO registry maintenance is complete.

.name is In Maintenance

Updated Saturday, January 22nd, 2011 at 8:45 PM ET
2011-01-23 at 0:45 UTC - Other time zones

The .NAME registry has a scheduled maintenance on Sunday, January 23, 2011 UTC.

Service Impact for Resellers:
Domain provisioning, renewals, transfers, availability checks and modifications to .NAME 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: Sunday, January 23, 2011 UTC.
Time:1:00 - 5:00 UTC
Duration: 4 hours

.name is Online

Updated Wednesday, January 19th, 2011 at 1:41 PM ET
2011-01-19 at 17:41 UTC - Other time zones

Our monitoring shows our connection to .NAME is working as expected again. We'll update this post if and when we get some info on what the cause of the interruption was.

.name is Offline

Updated Wednesday, January 19th, 2011 at 1:33 PM ET
2011-01-19 at 17:33 UTC - Other time zones

We've noticed a connection issue with the .NAME registry that started about 12:15pm EST (17:15 UTC). We're working with the registry to figure out what's causing the problem and we'll get you an update as soon as we can.

.name is Online

Updated Sunday, December 5th, 2010 at 5:00 AM ET
2010-12-05 at 9:00 UTC - Other time zones

The .NAME registry maintenance is complete.

.name is In Maintenance

Updated Saturday, December 4th, 2010 at 8:45 PM ET
2010-12-05 at 0:45 UTC - Other time zones

The .NAME registry has a scheduled maintenance on Sunday December 5, 2010 UTC.

Service Impact for Resellers:
Domain provisioning, renewals, transfers, availability checks and modifications to 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: Sunday December 5, 2010 UTC.
Time: 01:00 - 09:00 UTC
Duration: 8 hours

.name is Online

Updated Sunday, November 7th, 2010 at 1:23 AM ET
2010-11-07 at 5:23 UTC - Other time zones

The problem has been identified and corrected. The cause of the event was related to the routing tables of a layer 2/3 network switch during an earlier upgrade. Everything appears to be back to normal and we're keeping an eye on things and will post updates if we notice anything else.

This update is related to