Emergency Downtime Sample Clauses

Emergency Downtime. With respect to emergency downtime, Docebo shall provide the Company with as much notice as practical under the circumstances and strives for a minimum of seventy- two
Sample 1
AutoNDA by SimpleDocs
Emergency Downtime. SOFTWARE PROVIDER shall use commercially reasonable efforts to conduct Emergency Maintenance requiring downtime for any Module during Off-Peak Hours (as defined above) upon providing the Merchant with reasonable prior notice by email, if feasible, to one of the following contacts:
Sample 1
Emergency Downtime. Emergency Downtime means any emergency suspension of access or use of the Service required as a result of conditions or circumstances which may pose immediate danger to any component of the Service, including its infrastructure, and requires an immediate response, as determined by DigitalEd, acting reasonably and in good faith.
Sample 1
Emergency Downtime. Emergency downtime (“Emergency Downtime”) for the GSDS shall not exceed two (2) hours per month. Supplier shall give Company at least 24 hours’ advance notice by telephone. If practicable, Emergency Downtime should be scheduled during 11 PM-4 AM HST. Emergency Downtime will not be deducted from minutes GSDS is available to dispatch or schedule Grid Service Capability. Emergency Downtime shall be indicated as appropriate in Supplier’s Operational Forecast and updated to the Company in accordance with Exhibit F (Operational Forecast).
Sample 1
Emergency Downtime. Unplanned maintenance requirements that arise from unforeseen equipment malfunctions, accidents or problems must be minimized through equipment redundancy, switching, etc. When unplanned equipment problems force removal of the facilities from service, the Contractor personnel shall (1) notify Intelsat immediately.
Sample 1
Emergency Downtime. EHS reserves the right to perform emergency maintenance services at any time and without prior notice to Customer (“Emergency Maintenance”); provided that, EHS will use commercially reasonable efforts to provide prior notice to Customer.
Sample 1
Emergency Downtime. Word-Tech reserves the right to perform emergency maintenance services at any time and without prior notice to Customer (“Emergency Maintenance”); provided that, Word-Tech will use commercially reasonable efforts to provide prior notice to Customer.
Sample 1
AutoNDA by SimpleDocs
Emergency Downtime c. Any downtime during the Period which is not caused by any act or omission of Licensor, such as downtime caused by Force Majeure or caused by GGO or external vendor. d. Any downtime caused by the disconnection or suspension of the Game Platform (or any part of the Game Platform) by AIL pursuant to a right to do so under the Agreement. Defect any degradation of the functionality or content provided by the Game Platform or operational failure of the Game Platform. Emergency Downtime means the period of Downtime to enable Licensor to carry out urgent maintenance on the Game Platform which was not reasonably foreseeable and where GGO is notified less than seven (7) days before the downtime (unless otherwise agreed) and which could not have been communicated to GGO prior to this due to the exceptional nature of the emergency. Final Resolution Period(s) means the elapsed time between the initial report of a incident until that incident has been resolved in accordance with paragraph 3.1 of this SLA.
Sample 1

Related to Emergency Downtime

  • Emergency Situation In the event of an emergency situation beyond our reasonable control, such as an "act of God," war, fire, or natural disaster, services involving your account could be available only in a modified or reduced form or could be entirely unavailable. Unless expressly prohibited by applicable law, you agree that we will have no liability to you for such modification, reduction, or unavailability of services caused by an emergency situation.

  • Emergency Situations If the condition is an emergency, this will be communicated to the Contractor with the request that corrections are to be accomplished immediately. The Contractor shall respond to the notice in emergency situations within twenty-four hours. If the Contractor fails to respond within this time limit, the Owner may correct the defect and charge the Contractor for the Work. If it is determined the complaint is not the responsibility of the Contractor, the Contractor shall be promptly paid for the cost of the corrective work. The Contractor shall give notice in writing to the Owner when corrections have been completed.

  • Emergency Operator Access Registry Operator shall provide bulk access to the zone files for the TLD to the Emergency Operators designated by ICANN on a continuous basis in the manner ICANN may reasonably specify from time to time.

  • 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.

  • Emergencies 10.3.1 In any emergency affecting the safety of persons or property, the Contractor shall act to prevent threatened damage, injury or loss. Any additional compensation or extension of time claimed by the Contractor on account of emergency work shall be determined as provided in Article 12 for Changes in the Work.

Time is Money Join Law Insider Premium to draft better contracts faster.