Emergency Thresholds Clause Samples
The Emergency Thresholds clause establishes specific criteria or limits that must be met before certain emergency measures or responses are triggered within an agreement. Typically, this clause defines quantitative or qualitative benchmarks—such as financial losses, safety incidents, or operational disruptions—that, once reached, allow parties to take predefined actions like invoking force majeure, suspending obligations, or activating contingency plans. By clearly outlining when an emergency is recognized, the clause ensures all parties have a mutual understanding of what constitutes an emergency, thereby reducing ambiguity and facilitating prompt, coordinated responses to critical situations.
Emergency Thresholds. The following matrix presents the emergency thresholds that, if reached by any of the services mentioned above for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. DNS Service (all servers) 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDDS (WHOIS/Web-based WHOIS) 24-hour total downtime / week Data Escrow Breach of the Registry Agreement as described in Specification 2, Part B, Section 6.
Emergency Thresholds. 6.1. The following matrix presents the emergency thresholds that, if reached by any of the services related to DNS, EPP, RDAP-RDDS* and Data Escrow for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. DNS Service 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDAP-RDDS* 24-hour total downtime / week Data Escrow Reaching any of the criteria for the release of deposits described in Specification 2, Part B, Section 6.2 through Section 6.6. *The RDAP-RDDS emergency threshold becomes effective upon expiration of the RDAP Ramp-Up Period.
6.2. The following matrix presents the emergency thresholds that, if reached by any of the services related to WHOIS-RDDS for a TLD prior to the expiration of the RDAP Ramp-Up Period would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement WHOIS-RDDS 24-hour total downtime / week
Emergency Thresholds. Critical Function Emergency Thresholds
Emergency Thresholds. The following matrix presents the emergency thresholds that, if reached by any of the services mentioned above for the TLD, may (at ICANN’s discretion) cause the emergency transition of the TLD as specified in Section 3.6 of this Agreement . DNS Service (all servers) 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDDS (WHOIS/Web- based WHOIS) 24-hour total downtime / week Data Escrow Breach of the Registry Agreement caused by data escrow.
Emergency Thresholds. The following matrix presents the emergency thresholds that, if reached by any of the services mentioned above for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. DNS Service (all servers) 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDDS (WHOIS/Web-based WHOIS) 24-hour total downtime / week Data Escrow Breach of the Registry Agreement asReaching any of the criteria for the release of deposits described in Specification 2, Part B, Section 66.2 through Section 6.6.
Emergency Thresholds. The following matrix presents the Emergency Thresholds that, if reached by any of the services mentioned above for a TLD, would cause the Emergency Transition of the Critical Functions as specified in Section 2.13. of this Agreement. DNS service (all servers) 4-hour downtime / week DNSSEC proper resolution 4-hour downtime / week EPP 24-hour downtime / week RDDS (WHOIS/Web-based WHOIS) 24-hour downtime / week Data Escrow Breach of the Registry Agreement caused by missing escrow deposits as described in Specification 2, Part B, Section 6.
Emergency Thresholds. The following matrix presents the emergency thresholds that, if reached by any of the services related to DNS, EPP, RDAP-RDDS* and Data Escrow for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. DNS Service 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDAP-RDDS* 24-hour total downtime / week Data Escrow Reaching any of the criteria for the release of deposits described in Specification 2, Part B, Section 6.2 through Section 6.6. *The RDAP-RDDS emergency threshold becomes effective upon expiration of the RDAP Ramp-Up Period. The following matrix presents the emergency thresholds that, if reached by any of the services related to WHOIS-RDDS for a TLD prior to the expiration of the RDAP Ramp-Up Period would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement WHOIS-RDDS 24-hour total downtime / week Escalation is strictly for purposes of notifying and investigating possible or potential issues in relation to monitored services. The initiation of any escalation and the subsequent cooperative investigations do not in themselves imply that a monitored service has failed its performance requirements. Escalations shall be carried out between ICANN and Registry Operators, Registrars and Registry Operator, and Registrars and ICANN. Registry Operators and ICANN must provide said emergency operations departments. Current contacts must be maintained between ICANN and Registry Operators and published to Registrars, where relevant to their role in escalations, prior to any processing of an Emergency Escalation by all related parties, and kept current at all times.
Emergency Thresholds. 6.1. The following matrix presents the emergency thresholds that, if reached by any of the services mentioned aboverelated to DNS, EPP, RDAP-RDDS* and Data Escrow for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. DNS Service 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDDSRDAP-RDDS* 24-hour total downtime / week Data Escrow Reaching any of the criteria for the release of deposits described in Specification 2, Part B, Section 6.2 through Section 6.6.
6.2. The following matrix presents the emergency thresholds that, if reached by any of the services related to WHOIS-RDDS for a TLD prior to the expiration of the RDAP Ramp-Up Period would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement.
Emergency Thresholds. The following matrix presents the emergency thresholds that, if reached by any of the services mentioned above for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 3.1(dc)(iiix) of this Agreement. DNS Service (all servers) 4-‐‐hour total downtime / week DNSSEC proper resolution 4-‐‐hour total downtime / week EPP 24-‐‐hour total downtime / week RDDS (WHOIS/Web‐‐‐ based WHOIS) 24-‐‐hour total downtime / week Data Escrow Breach of the Registry Agreement asReaching any of the criteria for the release of deposits described in AppendixSpecification 2, Part B, Section 66.2 through Section 6.6.
Emergency Thresholds. The following matrix presents the emergency thresholds that, if reached by any of the services mentioned above for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. DNS Service DNSSEC proper resolution EPP RDDS Data Escrow