ICANN has a process when a TLD hits an operational fail state, which is called "Emergency Back-End Registry Operations" or EBERO.
Basically, EBERO kicks in to continue to operate for registrations within a given TLD.
For almost a decade, the only EBERO TLD has been .wed, but more are joining that list.
The ICANN json resource and our automation process that syncs to it may or may not include these correctly, and we will want to ensure that we have a handler for them as the list may grow or shrink, so that registrants (if any) in those namespaces have their adverse impacts reduced.
ICANN has a process when a TLD hits an operational fail state, which is called "Emergency Back-End Registry Operations" or EBERO.
Basically, EBERO kicks in to continue to operate for registrations within a given TLD.
For almost a decade, the only EBERO TLD has been .wed, but more are joining that list.
The ICANN json resource and our automation process that syncs to it may or may not include these correctly, and we will want to ensure that we have a handler for them as the list may grow or shrink, so that registrants (if any) in those namespaces have their adverse impacts reduced.