Cloud Port SLAs Sample Clauses

Cloud Port SLAs. Service Level commitment for availability of the LightEdge Cloud Port Service: ● CLOUD PORTS Service Level Service Level Agreement SLA Credit DESCRIPTION: LightEdge maintains peering routers which connect to a variety of private network connectivity providers. Cloud Ports are a LightEdge managed connection of these network circuits into Customer collocation or cloud services from LightEdge. MEASURED BY: Cloud Port availability is measured every 5 minutes via remote monitoring system that monitors network path between each LightEdge backbone network and Customer Cloud Port. CLOUD PORT AVAILABILITY 99.99% Service Failure occurs when Customer is unable to utilize LightEdge Cloud Port to pass network traffic from the Customer environment at LightEdge to the LightEdge side of the Cloud Port. Measurement is to the specific Cloud Port used by Customer but does not cover availability of the network providers network. For example, a failure of the LightEdge backbone network that results in Customer being unable to pass traffic across their Cloud Port connected to a Level 3 MPLS network would constitute a Service Failure. A failure of Level 3, within their own network and outside of LightEdge direct control, would not constitute a Service Failure of LightEdge’s Cloud Port service. 5% for each 30 minutes of Service Failure in excess of SLA Service Failure begins when the monitoring system detects a complete loss of ICMP traffic or loss of network traffic to Cloud Port that results in an inability by Customer to substantially utilize Cloud Port service. Service Failure ends when the monitoring system detects a return to normal conditions. THIS SPACE INTENTIONALLY LEFT BLANK
AutoNDA by SimpleDocs

Related to Cloud Port SLAs

  • Conversion of Live Telephone Exchange Service to Analog 2W Loops The following coordination procedures shall apply to “live” cutovers of VERIZON Customers who are converting their Telephone Exchange Services to SPRINT Telephone Exchange Services provisioned over Analog 2W unbundled Local Loops (“Analog 2W Loops”) to be provided by VERIZON to SPRINT.

  • Air Transport Services 1. For the purposes of this Article:

  • Cloud storage DSHS Confidential Information requires protections equal to or greater than those specified elsewhere within this exhibit. Cloud storage of Data is problematic as neither DSHS nor the Contractor has control of the environment in which the Data is stored. For this reason:

  • Local Number Portability Database 10.6.1 The Permanent Number Portability (PNP) database supplies routing numbers for calls involving numbers that have been ported from one local service provider to another. BellSouth agrees to provide access to the PNP database at rates, terms and conditions as set forth by BellSouth and in accordance with an effective FCC or Commission directive.

  • Unbundled Voice Loop – SL2 (UVL-SL2 Loops may be 2-wire or 4-wire circuits, shall have remote access test points, and will be designed with a DLR provided to NewPhone. SL2 circuits can be provisioned with loop start, ground start or reverse battery signaling. OC is provided as a standard feature on XX0 Xxxxx. The OC feature will allow NewPhone to coordinate the installation of the Loop with the disconnect of an existing customer’s service and/or number portability service. In these cases, BellSouth will perform the order conversion with standard order coordination at its discretion during normal work hours.

  • Shipping must be Freight On Board Destination to the delivery location designated on the Customer purchase order The Contractor will retain title and control of all goods until delivery is completed and the Customer has accepted the delivery. All risk of transportation and all related charges are the responsibility of the Contractor. The Customer will notify the Contractor and H-GAC promptly of any damaged goods and will assist the Contractor in arranging for inspection. The Contractor must file all claims for visible or concealed damage. Unless otherwise stated in the Agreement, deliveries must consist only of new and unused merchandise.

  • Harvest Share Use Section 7.2 is administrative except to the extent that it applies to the 17 Sector managers ability to impose and utilize legal means to recover Liquated damages as 18 authorized in section §10.10 of this agreement, in which case NMFS enforcement procedures 19 may apply.

  • Contract Migration Authorized Users holding individual Contracts with a Contractor at the time that Contractor is awarded a Centralized Contract for the same Products or services shall be permitted to migrate to that Centralized Contract effective with its commencement date. Such migration shall not operate to diminish, alter or eliminate any right that the Authorized User otherwise had under the terms and conditions of their individual Contract.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

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