Summary
- The way into ICANN's emergency registry regime is a printed number: Specification 10 §6, as replaced by the 7 August 2023 global amendment, sets DNS and DNSSEC at four hours of total downtime per week and EPP and RDAP-RDDS at 24.
- Inside, the Common Transition Process Manual's Stabilized State cancels creates, renewals, transfers and deletes, forbids expiry and auto-renewal, and preserves only registrant, contact, name server and DS updates.
- §2.13 of the base Registry Agreement says ICANN may designate an emergency operator; the return runs on the operator's demonstration and the operator's money, while ICANN pays the provider under a published schedule.
- No clause imposing a notice duty to the registrant was located in the three instruments read for that question on 19 November 2026, and the only public-information commitment found is a 2013-labelled FAQ saying ICANN posts status updates on its website.
Start with the renewal. In the Stabilized State, the Common Transition Process Manual says, the registry operates with limited changes: no domain transfers, no domain deletes, no domain renewals, no domain creates. Domain names must not be allowed to expire while an event is under way, and the emergency Shared Registration System must not auto-renew them either. What keeps working is the record — registrant, contact, name server and DS updates over EPP — and the manual says other EPP updates are rejected, with create, delete, renew, transfer and restore reachable only through an ICANN-approved web interface in limited circumstances.
That is a peculiar kind of liferaft. The name still resolves; the registration underneath it stops being a thing you can buy, sell, move or end on schedule. A registrant who wanted to renew in March, or transfer in April, is not looking at an outage. They are looking at a queue with no closing time printed on it.
The way in has a number. Specification 10 §6 of the base Registry Agreement, deleted in its entirety and replaced by the global amendment of 7 August 2023, sets the emergency thresholds: DNS service at four hours of total downtime per week, DNSSEC proper resolution at four hours per week, EPP at 24 hours per week, and RDAP-RDDS at 24 hours per week once the RDAP ramp-up has expired — with WHOIS-RDDS at 24 hours per week before it. Data Escrow is the outlier: its threshold is reaching any of the release criteria in Specification 2, Part B, §§6.2 to 6.6, which is a condition rather than a stopwatch.
Four hours is four hours inside a 168-hour week, and I report it the way the instrument prints it, in hours per week, without converting it into a percentage. The amendment says reaching any of these would cause the emergency transition of the registry for the TLD as specified in Section 2.13.
Section 2.13 is where the consequence stops being automatic. The base agreement provides that if any of those thresholds is reached, ICANN may designate an emergency interim registry operator of the registry for the TLD. May. The designation continues until the operator has demonstrated to ICANN's reasonable satisfaction that it can resume operation of the registry without recurrence of the failure — a standard written in one party's judgement — and the operator may transition back afterwards, provided it pays all reasonable costs incurred by ICANN as a result of the designation and by the Emergency Operator in connection with running the registry, documented in reasonable detail. Handing over all registry data, including escrow under §2.3, sits in the same clause; so does ICANN's latitude to make whatever changes it deems necessary to the IANA database.
Two trigger formulas are printed, and they are not the same formula. ICANN's Registry Transition Processes page describes the temporary transition for new gTLDs as applying primarily when two conditions are met — the registry is in breach of its agreement, and a Critical Function is being performed below the Emergency Thresholds, resulting in a situation of unacceptable risk — and it adds a second route: the operator itself may request a transition if it is aware of or anticipates an inability to provide the Critical Functions. The same page records the pre-authorisation that makes speed possible, changes to the IANA database for DNS and RDDS records in case of emergency, and the funding line: each case draws on the registry's Continued Operations Instrument under Specification 8. During emergency operation, the Emergency Operator will not bill SRS operations from registrars.
The current program page uses a third formulation still, describing activation when an operator is at risk of failing to sustain any of the five critical registry functions — DNS resolution, the Shared Registration System, Registration Data Directory Services, registry data escrow deposits and a properly signed DNSSEC zone — and noting that providers are confined to those functions and will not supply web hosting or network analytics, that the contracted providers are CIRA, CNNIC and Nominet, and that EBERO does not cover some legacy gTLDs. Three documents, three tenses of failure: at risk, is reached, in breach and below threshold at once.
Somebody signs the order and somebody ends it. The manual puts the emergency decisions in a named ICANN role: the Event Director confirms that an event is under way and whether an emergency transition is required, authorises IANA changes including root zone updates, and declares the end of the event, which terminates EBERO activities. It is ICANN's responsibility to identify the method to end the event, and successor selection begins after Transition-In. The 2025 agreement with the Canadian Internet Registration Authority turns that into a service order: the provider serves under an Event Activation Order until the earliest of ICANN's notice that the failed TLD will cease operations and not be transitioned, a transition to a successor operator — including the original registry operator — cancellation of the event, or ICANN's own termination of the order. Transition-out needs a plan approved by ICANN and IANA before execution. If the TLD is not transitioned, it may be removed from the root zone and the provider may decommission. ICANN can terminate the agreement on 270 days' notice, or any activation order on 90 days', for convenience. The term runs to 30 November 2027 and extends itself while an order is active.
The program FAQ, labelled 2 April 2013 and edited since, adds the aspiration and the parity: resolution as soon as possible, preferably within 12 months, sustainable as long as necessary, and emergency access to the same data the original operator had for the critical functions.
The money sits on two stages and must not be netted. ICANN pays the provider: under the 2025 CIRA schedule, a $10,000 Standard Emergency Event Fee per failed TLD, half within 30 days of the order's acceptance and completion of the Exhibit D requirements and half within six months, plus a quarterly ongoing fee driven by the number of domain names under management, a Difficult Emergency Event Fee capped at $30,000, and a $20,000 Transition-Out Fee. Those figures belong to that agreement; the earlier arrangement with CORE ran a standby fee and a different event fee, and the CNNIC and Nominet schedules were not read here, so none of these numbers travel. Behind the payment sits the Continued Operations Instrument: under Specification 8, a new gTLD operator must maintain a letter of credit or cash escrow sufficient to cover the five critical functions for a defined period, with ICANN or its designee as beneficiary. The failed operator's separate duty — reimbursing ICANN and the Emergency Operator as the price of coming back — is a different party paying a different instrument.
Now the part I went looking for and did not find. Across the three instruments read for that question on 19 November 2026 — the manual's Stabilized State, §2.13 of the 21 January 2024 base agreement and the 2025 CIRA agreement — no clause imposes a notice duty to the registrant, and the only public-information commitment located is the FAQ's line that ICANN posts status updates on its website. That is a statement about what the documents I read contain, on the day I read them; it is not a claim that no such duty exists anywhere, and it is not an allegation against any registry, provider or official.
What the documents do show is where information could be printed and is not: the manual already names the decision-maker, the agreement already prices the return, and neither attaches an addressee for the domain holder.
This is where the piece has to say what it adds. A literal search for "Emergency Back-End Registry Operator" on 19 November 2026 returned four published articles on this desk: one on the mechanism and who holds the record, dated 17 November 2026; one on three exercise results and the board's "fully implemented" verdict, dated 3 November 2026; one concluding the mechanism was documented but not proven invocable, dated 18 October 2026; and one on the .WED custody case, dated 31 July 2026. None of them inventories the suspension matrix against the update types the manual preserves, none puts the numeric entrance beside the provider fee schedule and the return condition, and none reads the 2023 replacement of Specification 10 §6 as the operative entrance. That inventory is the claim here, and it sits in the BTW directory entry for the program.
One historical note, because the design intent was never hidden: a 2010 explanatory memorandum already said the emergency operator would accept no billable new domains, renewals or transfers, and that there would be no automatic expirations. Its thresholds — five-day SRS downtime, seven-day WHOIS — do not match the matrix that binds today, so it belongs in the file as drafting history, not as current rule.
Two addresses could not be read on 19 November 2026, and the negative is bounded to them: the legacy EBERO resource page and the June 2012 base agreement PDF both returned nothing readable. ICANN keeps its agreements in a repository of base agreements that reproduces no emergency term itself. Whether the 2013 wording differed from today's, and whether the June 2012 numbering matches, is therefore unverified rather than settled.
Which leaves the finding where it belongs. The entrance to this regime is measured in hours per week, the exit in money and in one party's satisfaction, and the middle in the operations a registrant cannot perform. If ICANN wants the last gap closed, the tools are already in its hands, because the manual is incorporated by every provider agreement and ICANN may amend it. A notice duty with a named addressee and a stated clock would cost a paragraph. A published per-event record — one identifier, the TLD, the date the Event Director confirmed the event and the date the event ended — would cost a table. The numbers exist.
The sentence about who tells the domain holder does not.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






