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.
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.
Termination by Xxxxxx Xilinx may terminate this Agreement for material breach by Licensee, provided that Xilinx has given written notice to Licensee of such breach and Licensee fails to cure such breach within thirty (30) days thereof; provided, however, in the event of a breach of confidentiality under Section 7 whereby unauthorized disclosure and/or dissemination by electronic or other means is likely to cause undue harm to Xilinx, then Xilinx may, at its discretion, immediately terminate this Agreement and seek other appropriate equitable and legal remedies as deemed necessary to protect its interests hereunder.
Termination by Xxxxx Subject to Section 5.2, the CAISO may terminate this Agreement by giving written notice of termination in the event that the Participating Load commits any material default under this Agreement and/or the CAISO Tariff which, if capable of being remedied, is not remedied within thirty (30) days after the CAISO has given, to the Participating Load, written notice of the default, unless excused by reason of Uncontrollable Forces in accordance with Article X of this Agreement. With respect to any notice of termination given pursuant to this Section, the CAISO must file a timely notice of termination with FERC, if this Agreement was filed with FERC, or must otherwise comply with the requirements of FERC Order No. 2001 and related FERC orders. The filing of the notice of termination by the CAISO with FERC will be considered timely if: (1) the filing of the notice of termination is made after the preconditions for termination have been met, and the CAISO files the notice of termination within sixty (60) days after issuance of the notice of default; or (2) the CAISO files the notice of termination in accordance with the requirements of FERC Order No. 2001. This Agreement shall terminate upon acceptance by FERC of such a notice of termination, if filed with FERC, or thirty (30) days after the date of the CAISO’s notice of default, if terminated in accordance with the requirements of FERC Order No. 2001 and related FERC orders.
Termination by Supplier Termination by Supplier will not be considered.
Termination by Contractor Contractor may, at its option, terminate this Contract upon the failure of MPS to pay any amount, which may become due hereunder for a period of sixty (60) days following submission of appropriate billing and supporting documentation. Upon said termination, Contractor shall be paid the compensation due for all services rendered through the date of termination including any retainage.
Termination by Xxxxxxx (a) SORACOM may terminate the Agreement in the following situations, in which case SORACOM will give the Subscriber reasonable notice of such termination.
Termination by Owner The Owner may terminate this Agreement in whole or in part, for the failure of the Consultant to:
Termination by City Notwithstanding any other term, provision or conditions of this Agreement, subject only to prior written notification to Licensee or its successor-in- interest, this Agreement is revocable by the City if:
