OpenSRS Status

Services are online. VeriSign addressed the issue which was causing intermittent connection issues for OpenSRS resellers. We will provide more details once VeriSign provides follow-up on the root cause.

Update: (February 2, 2010 : 22:52 UTC /17:52 ET):

The VeriSign registry had an problem which resulted in high connection issues for the OpenSRS API. Services were degraded from 12:15 ET/17:15 UTC until 13:48 ET/18:48 UTC.

During the incident, our technical teams worked to isolate the cause. At 12:15 ET/17:15 UTC, we noted alerts for an intermittent connection issue for Resellers using the OpenSRS API. We tested and restarted our services and determined that the API was affected by a registry issue. We were already in contact with VeriSign for .com/.net and .cc/.tv. VeriSign addressed the cause, and the intermittent connection issues experienced by OpenSRS resellers cleared by 13:48 ET/18:48 UTC.

We are following up with the Registry for more root cause analysis. They advised that cause seems to have been network-related.

This update is related to Incident 10338

Services are online. VeriSign addressed the issue which was causing intermittent connection issues for OpenSRS resellers. We will provide more details once VeriSign provides follow-up on the root cause.

Update: (February 2, 2010 : 22:52 UTC /17:52 ET):

The VeriSign registry had an problem which resulted in high connection issues for the OpenSRS API. Services were degraded from 12:15 ET/17:15 UTC until 13:48 ET/18:48 UTC.

During the incident, our technical teams worked to isolate the cause. At 12:15 ET/17:15 UTC, we noted alerts for an intermittent connection issue for Resellers using the OpenSRS API. We tested and restarted our services and determined that the API was affected by a registry issue. We were already in contact with VeriSign for .com/.net and .cc/.tv. VeriSign addressed the cause, and the intermittent connection issues experienced by OpenSRS resellers cleared by 13:48 ET/18:48 UTC.

We are following up with the Registry for more root cause analysis. They advised that cause seems to have been network-related.

This update is related to Incident 10338

Services are online. VeriSign addressed the issue which was causing intermittent connection issues for OpenSRS resellers.

Update: (February 2, 2010 : 22:52 UTC /17:52 ET):

The VeriSign registry had an problem which resulted in high connection issues for the OpenSRS API. Services were degraded from 12:15 ET/17:15 UTC until 13:48 ET/18:48 UTC.

During the incident, our technical teams worked to isolate the cause. At 12:15 ET/17:15 UTC, we noted alerts for an intermittent connection issue for Resellers using the OpenSRS API. We tested and restarted our services and determined that the API was affected by a registry issue. We were already in contact with VeriSign for .com/.net and .cc/.tv. VeriSign addressed the cause, and the intermittent connection issues experienced by OpenSRS resellers cleared by 13:48 ET/18:48 UTC.

We are following up with the Registry for more root cause analysis. They advised that cause seems to have been network-related.

This update is related to Incident 10338

Services are online. VeriSign addressed the issue which was causing intermittent connection issues for OpenSRS resellers. We will provide more details once VeriSign provides follow-up on the root cause.

Update: (February 2, 2010 : 22:52 UTC /17:52 ET):

The VeriSign registry had an problem which resulted in high connection issues for the OpenSRS API. Services were degraded from 12:15 ET/17:15 UTC until 13:48 ET/18:48 UTC.

During the incident, our technical teams worked to isolate the cause. At 12:15 ET/17:15 UTC, we noted alerts for an intermittent connection issue for Resellers using the OpenSRS API. We tested and restarted our services and determined that the API was affected by a registry issue. We were already in contact with VeriSign for .com/.net and .cc/.tv. VeriSign addressed the cause, and the intermittent connection issues experienced by OpenSRS resellers cleared by 13:48 ET/18:48 UTC.

We are following up with the Registry for more root cause analysis. They advised that cause seems to have been network-related.

This update is related to Incident 10338

We have worked with the registry and determined that the intermittent connection issues for Storefront customers is applicable for .com/.net and .cc/.tv.
Storefront services are available.

We will be degrading the individual TLD services while we continue our investigation.

Update: (February 2, 2010 : 22:52 UTC /17:52 ET):

The VeriSign registry had an problem which resulted in high connection issues for the Storefront customers. Services were degraded from 12:15 ET/17:15 UTC until 13:48 ET/18:48 UTC.

During the incident, our technical teams worked to isolate the cause. At 12:15 ET/17:15 UTC, we noted alerts for an intermittent connection issue for Resellers and your customers using Storefront. We tested and restarted our services and determined that the API was affected by a registry issue. We were already in contact with VeriSign for .com/.net and .cc/.tv. VeriSign addressed the cause, and the intermittent connection issues experienced by OpenSRS resellers cleared by 13:48 ET/18:48 UTC.

We are following up with the Registry for more root cause analysis. They advised that cause seems to have been network-related.

This update is related to Incident 10338

We have worked with the registry and determined that the intermittent connection issues for OpenSRS API customers is for .com/.net and .cc/.tv. Our OpenSRS API is available.

We will be degrading the individual TLD services while we continue our investigation.

Update: (February 2, 2010 : 22:52 UTC /17:52 ET):

The VeriSign registry had an problem which resulted in high connection issues for the OpenSRS API. Services were degraded from 12:15 ET/17:15 UTC until 13:48 ET/18:48 UTC.

During the incident, our technical teams worked to isolate the cause. At 12:15 ET/17:15 UTC, we noted alerts for an intermittent connection issue for Resellers using the OpenSRS API. We tested and restarted our services and determined that the API was affected by a registry issue. We were already in contact with VeriSign for .com/.net and .cc/.tv. VeriSign addressed the cause, and the intermittent connection issues experienced by OpenSRS resellers cleared by 13:48 ET/18:48 UTC.

We are following up with the Registry for more root cause analysis. They advised that cause seems to have been network-related.

This update is related to Incident 10338