Availability Exclusions Sample Clauses

Availability Exclusions. In addition to the General Exclusions, Availability Service Level Standard measurements do not include periods of Dedicated E-Line Outage resulting in whole or in part from one or more of the following causes: ● For on-net circuits, any act or omission on the part of any third party including but not limited to any Local Access provider other than any third-party over which Verizon exercises control; ● For off-net circuits, any act or omission on the part of any third party (other than a local access provider) over which Verizon exercises control; ● Periods of Service degradation where Customer has not released its Service for immediate testing.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Availability Exclusions. The Service Commitment and the calculation of Unavailability shall not apply to (therefore no Service Credits will be issued as a result of) any unavailability, suspension, downtime or termination of the Workspot Hosted Virtual Desktop Service or any performance issues with respect to Workspot DaaS Services, attributable to: (i) scheduled or critical systems maintenance activities (whether by Workspot or its IaaS provider); (ii) suspension, termination or expiration of a Subscription Term or the Agreement or Company’s right to use Workspot DaaS Services under the Agreement; (iii) activation of the Workspot DaaS Disaster Recovery Services; (iv) factors beyond Workspot’s reasonable control, including any force majeure event (as provided in the Agreement) or other Internet access or related problems beyond the demarcation point of Workspot DaaS Services; (v) any actions or inactions of Company, its Affiliates or End Users, including a failure to comply with, or perform their respective obligations in accordance with, the Agreement, Microsoft Customer Agreement or End User Terms (including, by way of example, any failure to use the Online Product Services in accordance with the applicable Documentation); (vi) External Software or other Company equipment, software or other technology; or (vii) third party services equipment, software or other technology (other than third party services, equipment, software or technology within Workspot’s direct control); or (viii) the Inactive status of a Workspot Hosted Virtual Desktop (collectively, the “Availability Exclusions”).
Sample 1
Availability Exclusions. All Broadsign sandbox, beta, evaluation and testing environments are expressly excluded from this Service Level Agreement.
Sample 1
Availability Exclusions. In addition to the general exclusions found in Appendix A, the following exclusions apply to the Availability SLA: 4.1.4.1 A site is not considered unavailable during periods of Soft Outage. 4.1.4.2 The Availability SLA does not apply to sites installed for less than one full calendar month. 4.1.4.3 A site is not considered unavailable during interruptions not reported by Customer, or for which no trouble ticket was opened. 4.1.4.4 A site is not considered unavailable during any Hard Outage caused in whole or part by the failure of CPE not under 24 x 7 maintenance coverage with a 4 hour response time with Verizon or a Verizon approved 3rd Party Maintenance provider. 4.2 Time to Repair (“TTR”) SLA
Sample 1
Availability Exclusions. Loss of Service Availability caused by (i) issues beyond Sellers’ reasonable control, including, without limitation, denial of service or similar attacks, mail bombs, DNS resolution, domain name expiration, hardware failure, Internet availability, Purchaser portion of the network, IP transit provider issues, SYN attacks or any other Force Majeure Event; or (ii) any loss of Services related to periods of time where customer premises equipment is being replaced or repaired; or (iii) any issues related to the Services due to number porting, whether inbound or outbound; or (iv) Loss of Service Availability lasting less than 24 hours, (v) other issues addressed in this SLA, will be excluded from Service Availability calculations.
Sample 1
Availability Exclusions i. Availability measurements do not include periods of Network Outage resulting in whole or in part from one or more of the following causes: 1. Periods of service degradation, such as slow data transmission. 2. “Customer Time,” the time identified on the trouble ticket (if any) attributable to or caused by, through no fault of Verizon, the following: 3. Incorrect or incomplete callout information provided by Customer which prevents Verizon from completing the trouble diagnosis and service restoration; 4. Verizon being denied access to network components at the Customer location when access is required to complete trouble shooting, repair, diagnosis, or acceptance testing; 5. The CPE Maintenance Provider must have access to the CPE to restore and fix; 6. Customer’s failure or refusal to release the circuit for testing; 7. Verizon calling Customer to close a trouble ticket, but Customer being unavailable, or Verizon being unable to verify service restoration with a Customer; 8. Any other act or omission on the part of Customer, or ii. Schedule Maintenance iii. Force Majeure events beyond Verizon’s reasonable control, including but not limited to Acts of God, government regulation, labor strikes natural disaster, and national emergency. iv. Interruptions not reported by Customer, or for which no trouble ticket was opened. v. Trouble tickets associated with new installations (before Customer accepts a new service) or opened for circuit monitoring purposes only. vi. All routers not under 24x7 Maintenance through Verizon or another vendor. vii. Unavailability continuing for [**] or less which Customer fails to report to Verizon within [**] from the date the SLA was not met, or any unavailability resulting from: • Verizon Network maintenance; • any Customer-ordered telephone company circuits; • Customer’s applications, equipment, or facilities;
Sample 1
Availability Exclusions. In measuring availability of the eArcu Application, downtime relating to the following causes shall be excluded from the calculation:
Sample 1
AutoNDA by SimpleDocs

Related to Availability Exclusions

  • General Availability The commitment to availability specified in the letter of appointment shall be subject to mutually acceptable revision. Such revision will occur once per year, or, if mutually agreed between the Employer and the employee, on a more frequent basis. The Employer will issue a revised letter of appointment to reflect approved changes to employee’s general availability.

  • Warranty Exclusions The Limited Warranty in clauses 1.2 and 1.3 does not apply: a) if the Product was not purchased and installed in Australia; b) if You do not grant BYD or BYD Partner access to the performance data of the Product over the Internet upon request after reporting the warranty claim and/or manipulate such data; c) to wear and tear in the appearance of the Product (including but not limited to any scratches, stains, mechanical wear, rust or mould) which does not impair its function; d) to any damage to property or personal injury arising from any defect if the state of scientific and technical knowledge at the time when the Product is sold to Original Buyer was not such as to enable the defect to be discovered; e) if the invoice for the Product and the information listed in clause 4 below is not provided with the warranty claim; or f) if the serial number on the Product can no longer be identified or has been modified.

  • Availability Subject to the terms and conditions of this Agreement, Bank shall make Advances not exceeding the Availability Amount. Amounts borrowed under the Revolving Line may be repaid and, prior to the Revolving Line Maturity Date, reborrowed, subject to the applicable terms and conditions precedent herein.

  • GENERAL EXCLUSIONS We do not insure for loss caused directly or indirectly by any of the following. Such loss is excluded regardless of any other cause or event contributing concurrently or in any sequence to the loss. These exclusions apply whether or not the loss event results in widespread damage or affects a substantial area.

  • High Availability Registry Operator will conduct its operations using network and geographically diverse, redundant servers (including network-­‐level redundancy, end-­‐node level redundancy and the implementation of a load balancing scheme where applicable) to ensure continued operation in the case of technical failure (widespread or local), or an extraordinary occurrence or circumstance beyond the control of the Registry Operator. Registry Operator’s emergency operations department shall be available at all times to respond to extraordinary occurrences.

  • RDDS availability Refers to the ability of all the RDDS services for the TLD, to respond to queries from an Internet user with appropriate data from the relevant Registry System. If 51% or more of the RDDS testing probes see any of the RDDS services as unavailable during a given time, the RDDS will be considered unavailable.

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