Emergency Escalation. 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 Escalation. Registry Operator and ICANN shall provide the contact information of their respective emergency operations departments to the other party for the purposes of this Section and such contact information shall be maintained and kept current at all times by both Registry Operator and ICANN. ICANN shall issue an emergency escalation notice informing Registry Operator of any possible or potential issues in relation to the monitored RDAP-RDDS service. Upon the issuance of an emergency escalation notice, Registry Operator and ICANN shall cooperate and use commercially reasonably efforts to diagnose and/or resolve the identified issue(s), including through the sharing of appropriate measurement data. The initiation of any emergency escalation and the subsequent cooperation to diagnose and/or resolve the identified issue(s) do not in themselves imply or otherwise establish that the monitored RDAP-RDDS service has failed the applicable Service Level Requirements set forth in Section 3.1 above.
Emergency Escalation. 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.
Emergency Escalation. 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 Escalation initiated by ICANN Upon reaching 10% of the Emergency thresholds as described in Section 6 of this Specification, ICANN’s emergency operations will initiate an Emergency Escalation with the relevant Registry Operator. An Emergency Escalation consists of the following minimum elements: electronic (i.e., email or SMS) and/or voice contact notification to the Registry Operator’s emergency operations department with detailed information concerning the issue being escalated, including evidence of monitoring failures, cooperative trouble-shooting of the monitoring failure between ICANN staff and the Registry Operator, and the commitment to begin the process of rectifying issues with either the monitoring service or the service being monitoring. Emergency Escalation initiated by Registrars Registry Operator will maintain an emergency operations department prepared to handle emergency requests from registrars. In the event that a registrar is unable to conduct EPP transactions with the registry for the TLD because of a fault with the Registry Service and is unable to either contact (through ICANN mandated methods of communication) the Registry Operator, or the Registry Operator is unable or unwilling to address the fault, the registrar may initiate an emergency escalation to the emergency operations department of ICANN. ICANN then may initiate an emergency escalation with the Registry Operator as explained above. Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note plann...
Emergency Escalation. If Data Correction and Restore Workaround Techniques prove unsuccessful in Purchaser’s sole discretion, Vendor will perform emergency maintenance to Resolve the Severity 2 Error within forty-eight (48) hours of Purchaser’s request for emergency escalation to Resolve the Severity 2 Error. The greater of: (1) 8% of the amounts paid or payable by Purchaser for Maintenance and Support Services in such month will be imposed on Vendor or (2) $800.00.
