eco Domain Registry Status Page

Mar 12, 2026 · resolved Mar 25

We have been monitoring EPP latency for the last 14 hours and are content that the performance issue has been resolved.

Jul 30, 2025 · resolved Jul 30

Resolved as of 2025-07-31 15:50 UTC

Feb 4, 2025 · resolved Feb 4

The .eco registry web portal was unavailable between 19:06 - 19:17 UTC on February 4 due to a system failure in the firewall used to protect the service. This issue was identical to the incident that impacted the primary firewall on January 21. The firewall vendor supplied a patch to address the issue and the patch was applied on February 4 at 20:30. EPP access to the .eco registry was not impacted by this incident.

Jan 21, 2025 · resolved Jan 21

The .eco registry web portal was unavailable between 17:21 - 17:37 UTC on January 21 due to a system failure in the firewall used to protect the service. Access was restored after failing over to the backup firewall. Our registry systems partner is working with the firewall vendor to diagnose the cause of the failure. EPP access to the .eco registry was not impacted by this incident.

Feb 5, 2024 · resolved Feb 5

# Incident report - b.ns.nic.eco transit outage A transit provider used by _b.ns.nic.eco_, one of the authoritative DNS nameserver clouds used to serve .eco domains, suffered an outage. The outage affected internet connectivity to some of the data centers serving traffic for this NS record. As the data centers have multiple transit providers, only requests reaching the data centers via this transit provider were impacted.This outage did not impact the redundant authoritative nameservers at _a.ns.nic.eco_. Any failing lookups requests for .eco domains would have automatically failed over to use these nameservers. Other than a slight increase in latency, there was no visible impact to visitors of .eco domains affected by this incident. ## Timeline All times are given in UTC. * 2024-02-05 20:53: Incident started * 2024-02-05 21:29: Incident was resolved * 2024-02-05 21:46: ICANN confirmed resolution of incident \***Duration of incident**: 34 minutes ## Root cause analysis One of the transit providers suffered an outage. The transit provider quickly addressed the outage without requiring action from the registry or registry service provider. ## Incident Impact No impact to visitors of .eco domains. This was a regional event that only impacted a proportion of DNS requests within those regions. The redundancy inherent in the authoritative DNS system for .eco domains ensured that there was no visible impact in this brief incident.