Excused Outage Sample Clauses

Excused Outage. The time taken to restore a Fault is measured from the time a Fault is recorded on Our fault management system until the time We notify You that Service has been restored or in the event that We are unable to contact You, the time recorded on Our fault management system that Service has been restored.
AutoNDA by SimpleDocs
Excused Outage. Availability shall be measured only for the resources fully and directly under DCLUX’ management and control and which are required by the Managed IP Services. The Customer understands and agrees therefore that DCLUX non-essential resources are expressly excluded from the scope of this SLA. (an “Excused Outage”). An Excused Outage is an outage: (a) caused by the acts or omissions of Customer and/or its End User or agents; (b) due to failure of power at the Customer or End User Premises; (c) caused by the failure or malfunction of non-DCLUX equipment or systems, including off-net local loops; (d) related to a Force Majeure Event; (e) during any period in which DCLUX is not given access to the Customer Hardware; or (f) caused by maintenance.
Excused Outage. An "Excused Outage" is an outage: (i) caused by the acts or omissions of Customer and/or its End User or agents; (ii) due to failure of power at the Customer or End User Premises; (iii) caused by the failure or malfunction of non-XO equipment or systems, including off-net local loops; (iv) related to a Force Majeure Event; (v) during any period in which XO is not given access to the Premises; or (vi) caused by maintenance.
Excused Outage. Availability shall be measured only for the resources fully and directly under DCLUX’ management and control and which are required by the Colocation Services. The Customer understands and agrees therefore that DCLUX non-essential resources are expressly excluded from the scope of this SLA. (an “Excused Outage”). An Excused Outage is an outage: (a) caused by the acts or omissions of Customer and/or its End User or agents; (b) due to failure of the Customer Hardware; (c) caused by the failure or malfunction of non-DCLUX equipment or systems; (d) related to a Force Majeure Event; (e) during any period in which DCLUX is not given access to the Customer Hardware; or (f) caused by maintenance.
Excused Outage. Availability shall be measured only for the resources fully and directly under MIXvoip’s management and control and which are required by the MIXvoip Services. The Customer understands and agrees therefore that MIXvoip non- essential resources are expressly excluded from the scope of this SLA. (an “Excused Outage”). An Excused Outage is an outage: (a) caused by the acts or omissions of Customer and/or its End User or agents; (b) due to failure of power at the Customer or End User Premises; (c) caused by the failure or malfunction of non-MIXvoip equipment or systems; (d) related to a Force Majeure Event; or (e) caused by maintenance.
Excused Outage. Any outage, unavailability, delay or other degradation of Service related to, associated with or caused by Planned System Maintenance, Customer actions or inactions, Customer provided power or equipment, any third party other than a third party directly involved in the operation and maintenance of the Seller network, including, without limitation, Customer’s end users, third party network providers, traffic exchange points controlled by third parties, or any power, equipment or services provided by third parties, or a Force Majeure Event;
Excused Outage. Orbital Net shall not be liable to pay Service Credits, where such failure is due to any of the following which each and all shall be an Excused Outage: • A Force Majeure event; • Scheduled or Emergency Maintenance; • Any Service-affecting fault that is not classified by Orbital Net as a loss of Service; • Failure because Customer has not provided suitable customer premise equipment or configuration to take advantage of a backup circuit that forms part of the Service availability; • Actions or inactions of the Customer and/or landlord of the building; • Works carried out by anyone other than Orbital Net; • Failure by the Customer to provide prompt assistance and information including first line checks, as requested by Orbital Net; • Any network incident that is raised by the Customer which is subject to inaccurate or incomplete information; • Failure by the Customer to respond to an enquiry from Orbital Net or any third party acting on its behalf which delays, hinders or prevents Orbital Net from performing its obligations; • Faults, delays, and failures by Orbital Net to meet any Service Levels which are caused by denial-of-service attacks; • Where the Fault is proven to be caused by the Customer; and/or the landlord of the building; • Faults which are associated with physical cable breaks or vandalism within the network. Estimated restoration of Service will be communicated to the Customer via Orbital Net; • Any problems caused by power disruption or environmental conditions at the Customer’s premises, the Customer’s router and/or associated cabling and/or any other hardware, software, materials, or services not provided by Orbital Net; • A misconfiguration or omission of a requested bolt-on configuration element; and • Any failure of the Customer premise equipment, such as routers, firewall hardware (but not any Orbital Net Equipment). For the avoidance of doubt, this does not form part of the Service availability target and no Service Credits are paid against these. Maintenance
AutoNDA by SimpleDocs

Related to Excused Outage

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Forced Outages During any forced outage, the NYISO or Connecting Transmission Owner may suspend interconnection service to the Interconnection Customer to effect immediate repairs on the New York State Transmission System or the Distribution System. The NYISO shall use Reasonable Efforts to provide the Interconnection Customer with prior notice. If prior notice is not given, the NYISO shall, upon request, provide the Interconnection Customer written documentation after the fact explaining the circumstances of the disconnection.

  • CLEC OUTAGE For a problem limited to one CLEC (or a building with multiple CLECs), BellSouth has several options available for restoring service quickly. For those CLECs that have agreements with other CLECs, BellSouth can immediately start directing traffic to a provisional CLEC for completion. This alternative is dependent upon BellSouth having concurrence from the affected CLECs. Whether or not the affected CLECs have requested a traffic transfer to another CLEC will not impact BellSouth's resolve to re-establish traffic to the original destination as quickly as possible.

  • Scheduled Outages (a) Commencing at least sixty (60) days before Initial Synchronization and throughout the Delivery Term, Seller shall, no later than January 1, April 1, July 1 and October 1 of each year, submit to SCE, using the Web Client, Seller’s schedule of proposed planned outages (“Outage Schedule”) for the subsequent twenty-four month period. (b) Seller shall provide the following information for each proposed planned outage: (i) Start date and time; (ii) End date and time; and (iii) Capacity online, in MW, during the planned outage. (c) Within thirty (30) days after SCE’s receipt of an Outage Schedule, SCE shall notify Seller in writing of any reasonable request for changes to the Outage Schedule, and Seller shall, consistent with Prudent Electrical Practices, accommodate SCE’s requests regarding the timing of any planned outage. (d) Seller shall cooperate with SCE to arrange and coordinate all Outage Schedules with the CAISO. (e) If a condition occurs at the Generating Facility which causes Seller to revise its planned outages, Seller shall promptly provide Notice to SCE, using the Web Client, of such change (including an estimate of the length of such planned outage) as required in the CAISO Tariff after the condition causing the change becomes known to Seller. (f) Seller shall promptly prepare and provide to SCE upon request, using the Web Client, all reports of actual or forecasted outages that SCE may reasonably require for the purpose of enabling SCE to comply with Section 761.3 of the California Public Utilities Code or any Applicable Law mandating the reporting by investor owned utilities of expected or experienced outages by electric energy generating facilities under contract to supply electric energy.

  • Termination Due to Force Majeure Event If the period of Force Majeure continues or is in the reasonable judgment of the Parties likely to continue beyond a period of 120 (one hundred and twenty) Days, the Parties may mutually decide to terminate this Agreement or continue this Agreement on mutually agreed revised terms. If the Parties are unable to reach an agreement in this regard, the Affected Party shall after the expiry of the said period of 120 (one hundred and twenty ) Days be entitled to terminate the Agreement in which event, the provisions of Articles 16 and 17 shall, to the extent expressly made applicable, apply.

  • Force Majeure Delays In any case where either party hereto is required to do any act (other than the payment of money), delays caused by or resulting from Acts of God or Nature, war, civil commotion, fire, flood or other casualty, labor difficulties, shortages of labor or materials or equipment, government regulations, delay by government or regulatory agencies with respect to approval or permit process, unusually severe weather, or other causes beyond such party’s reasonable control the time during which act shall be completed, shall be deemed to be extended by the period of such delay, whether such time be designated by a fixed date, a fixed time or “a reasonable time.”

  • Force Majeure Event 16.1 If a Force Majeure Event gives rise to a failure or delay in either party performing any obligation under this Agreement (other than any obligation to make a payment), that obligation will be suspended for the duration of the Force Majeure Event. 16.2 A party that becomes aware of a Force Majeure Event which gives rise to, or which is likely to give rise to, any failure or delay in that party performing any obligation under this Agreement, must: (a) promptly notify the other; and (b) inform the other of the period for which it is estimated that such failure or delay will continue. 16.3 A party whose performance of its obligations under this Agreement is affected by a Force Majeure Event must take reasonable steps to mitigate the effects of the Force Majeure Event.

  • Termination due to Force Majeure 13.5.1 If the Force Majeure Event or its effects continue to be present beyond the period as specified in Article 4.5.3, either Party shall have the right to cause termination of the Agreement. In such an event, this Agreement shall terminate on the date of such Termination Notice.

  • Force Majeure If by reason of Force Majeure, either party hereto shall be rendered unable wholly or in part to carry out its obligations under this Agreement through no fault of its own then such party shall give notice and full particulars of Force Majeure in writing to the other party within a reasonable time after occurrence of the event or cause relied upon. Upon delivering such notice, the obligation of the affected party, so far as it is affected by such Force Majeure as described, shall be suspended during the continuance of the inability then claimed but for no longer period, and such party shall endeavor to remove or overcome such inability with all reasonable dispatch. In the event that Vendor’s obligations are suspended by reason of Force Majeure, all TIPS Sales accepted prior to the Force Majeure event shall be the legal responsibility of Vendor and the terms of the TIPS Sale Supplemental Agreement shall control Vendor’s failure to fulfill for a Force Majeure event.

  • Force Majeur In case the Show Facility is damaged or destroyed, or in case of war, government regulations or any other circumstances whatsoever which will make it impossible or impractical for Show Management to permit Exhibitor to occupy the exhibit space described in this Agreement, this Agreement will terminate and Exhibitor will waive any claim for damages for compensation except the pro rata return of the amount paid for space rented, diminished only by a pro rata portion of the amounts expended to produce the Show.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!