Events Beyond Our Control If an Event Beyond Our Control occurs and prevents Us from performing any of Our obligations under this Contract to any extent, then We are not required to perform that obligation to the extent and for as long as We are prevented by that Event Beyond Our Control. If such an Event Beyond Our Control occurs and We consider it appropriate to do so, We may notify You of the Event Beyond Our Control by any reasonable means, including by a public announcement.
No-‐Activation Period Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-‐Activation Period ends.
EVENTS OUTSIDE OUR CONTROL 7.1 We will not be liable or responsible for any failure to perform, or delay in performance of, any of Our obligations under these Terms that is caused by an Event Outside Our Control.
Extraordinary Event Registry Operator will use commercially reasonable efforts to restore the critical functions of the registry within twenty-‐four (24) hours after the termination of an extraordinary event beyond the control of the Registry Operator and restore full system functionality within a maximum of forty-‐eight (48) hours following such event, depending on the type of critical function involved. Outages due to such an event will not be considered a lack of service availability.
Direct Trunked Transport 7.3.2.1 Either Party may elect to purchase direct trunked transport from the other Party.
