Emergency Escalation Sample Clauses

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 providesaid 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.7.1. Emergency Escalation initiated by ICANNUpon 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, cooperativetrouble-­‐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.7.2. Emergency Escalation initiated by RegistrarsRegistry 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.7.3. Notifications of Outages and MaintenanceIn 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 ...
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.7.1 Emergency Escalation initiated by cxDAUpon reaching 10% of the Emergency thresholds as described in Section 6 of this Specification, cxDA’s emergency operations will initiate an Emergency Escalation with the relevant contact. An Emergency Escalation consists of the following minimum elements: electronic (i.e., email or SMS) and/or voice contact notification to CoCCA ’s emergency operations department with detailed information concerning the issue beingescalated, including evidence of monitoring failures, cooperative trouble-shooting of the monitoring failure between cxDA staff and CoCCA , and the commitment to begin the process of rectifying issues with either the monitoring service or the service being monitoring.If CoCCA declares an outage, as per its contractual obligations with cxDA, on services under a service level agreement and performance requirements, it will notify the cxDA emergency operations department.