Latency Sample Clauses

Latency. For purposes of measuring Windstream’s MPLS Networking Services performance under this SLA, latency is defined as the round trip delay (in milliseconds) of packets transported across the Windstream core network, between the points specified in Section 1.1. Latency shall be calculated based on an aggregate monthly measurement average between the previously specified points. The following outlines the latency targets and Service credits, depending on the class selected by Customer, in any given Calendar Month. Current QoS Service Level Name Former QoS Service Level Name Latency Target Credit (Provided as a fraction of the MRC for the affected service) Expedited Forwarding Real Time ≤ 40ms (Roundtrip) 1/30 MRC for each day (any 24-hour period) Windstream fails to meet the latency SLA for Expedited Forwarding QoS in a Calendar Month Assured Forwarding 4 ≤ 40ms (Roundtrip) 1/30 MRC for each day (any 24-hour period) Windstream fails to meet the latency SLA for Assured Forwarding 4 QoS in a Calendar Month Assured Forwarding 3 Mission Critical Data ≤ 45 ms (Roundtrip) 1/30 MRC for each day (any 24-hour period) Windstream fails to meet the latency SLA for Assured Forwarding 3 QoS during any Calendar Month Assured Forwarding 2 ≤ 45 ms (Roundtrip) 1/30 MRC for each day (any 24-hour period) Windstream fails to meet the latency SLA for Assured Forwarding 2 QoS in a Calendar Month Assured Forwarding 1 Business Critical Data ≤ 48 ms (Roundtrip) 1/30 MRC for each day (any 24-hour period) Windstream fails to meet the latency SLA for Assured Forwarding 1 QoS during any Calendar Month. Best Effort Standard Data (Internet) N/A N/A

Latency. SLA • For “Local Market” distances of ≤ 75 miles = 10 ms • For “Inter-Market” distances of between 76 – 750 miles = 20 ms • For “Long-Haul” distances of > 750 miles = 50 ms

Latency. Masergy will meet or be less than 5ms average roundtrip latency time as measured between the DCC Partner’s peering location and Masergy’s closest hub. Customer will be eligible to receive a credit equal to one week of its affected site's monthly recurring Masergy Service fees (excluding local access circuit charges) for the month in which the average latency target is not met. In order to be eligible for the Direct Cloud Connect Latency credit, Customer must notify Masergy of the latency failure within thirty (30) business days of the end of the month in which the failure occurred. Customer should open a trouble ticket and make claims via the Masergy Portal application, which can be accessed by clicking on the Log In link located on the Masergy website ▇▇▇.▇▇▇▇▇▇▇.▇▇▇; claims may also be submitted via electronic mail sent to ▇▇▇▇▇▇▇▇▇▇▇▇▇@▇▇▇▇▇▇▇.▇▇▇. Latency failures caused by Force Majeure events do not apply and any resulting latency data will not be used in the calculation of the monthly latency measurement.

Latency. Latency, Frame Transfer Delay (FTD), is the maximum packet delivery time measured round-trip between Customer’s A and Z locations at the Committed Information Rate (CIR). Latency is measured across On-Net Service paths between ingress and egress NIDs. Measurements are taken at one-hour intervals over a one month period. Credits are based on round-trip latency of 95th percentile packet. Customer must meet the following criteria to qualify for Service credits on the E-LINE Latency SLA outlined in Table 1D:  Access loops at Customer locations A and Z may be fiber or copper connectivity from the Serving Wire Center to the NIDs at each premise to qualify for the circuit SLA.  Each SLA guarantee is associated with ONLY one QoS Level. Frontier will honor the Service credit associated with the QoS level ordered for On-Net Services. Customer will be entitled to Service credits if the Service fails to meet applicable Performance Objective as outlined in Table 1D subject to Sections 3 and 4 below Silver [Standard Data Service] ≤ 56 ms ≤ 100 ms ≤ 250 ms 10%

Latency. 2.1 The Allstream Network will have an average round trip packet transit time (latency) for those packets with a QoS label of voiceover a calendar month of: 2.2 Credit 2.2.1 In the event of excess latency, as determined at the sole discretion of Allstream, Allstream will credit Customer’s Monthly Recurring Charges (“MRC”) solely for that Service experiencing the excess latency at the Service location. If duly approved by Allstream, the Credits will be applied to Customer’s account to offset invoiced MRC. The Credits apply only to the invoiced MRC for that month for the affected Service, and not to taxes, surcharges, or other charges and fees, which will be charged to Customer’s invoice and must be paid monthly in full. 2.2.2 If the latency guarantee is not met in a calendar month, the customer may receive a service credit of 1/30th of the MRC for that month for each full 1 ms above the average maximum based on distance, up to 15 ms above the latency guarantee.

Latency. PacketFabric is committed to delivering a reliable, low-latency service, with guaranteed and predictable performance. To that end, and to accommodate PacketFabric's ongoing market expansion, PacketFabric maintains a Round-Trip Latency Metric Table on its website, that is incorporated by reference into this SLA. In the event that these performance metrics cannot be met, the following table(s) shall define the amount of SLA Credit the Customer is entitled to receive: 10% 10% of MRC 20% 20% of MRC 30% 30% of MRC 50% 40% of MRC 75% 50% of MRC 100% 60% of MRC

Latency. 2.2.1 For Latency measurement purposes, Metrotech divides the network into zones, namely the Access Zone, the Metrotech Zone (Metrotech’s national IP network) and the 3nd zone called the “Public Internet Zone”. If the Access Zone is terminated at the Service Demarcation Point with a Metrotech Network Interface Device (as identified on the SOF) then Metrotech guarantees that the round trip Latency between the Service Demarcation Point and a Metrotech Network Core Internet Router will be no greater than the target identified on the SOF. If no such device is provided, (as identified on the SOF) then Metrotech guarantees that the round trip Latency between the Metrotech Network PoP and a Metrotech Network Core Internet Router will be no greater than the target identified on the SOF. If the Latency so identified is greater than the target, the Customer may claim re-imbursement up to 10% of the monthly rental for the relevant Connection, PROVIDED THAT in calculating the average round trip Latency there shall be deducted from such calculation any increase in the Latency as a result of the Customer’s breach of this Agreement, or a disruption to the power supply to the Equipment, or a disruption to the Internet Services caused by the Customer or the Customer’s own equipment, or a failure by the Customer to provide access to the Site and/or the Premises or as a result of an event of Force Majeure PROVIDED ALWAYS THAT Metrotech’s total aggregate liability to the Customer under this Service Level Agreement shall not exceed the sum of one year’s Annual Rental for the relevant Connection. 2.2.2 The Latency between the Metrotech Network PoP (or the Service Demarcation Point if a Network Interface Device is provided) and the designated Core Internet Router will be monitored and reported to the Customer only if the Customer so requests, and Metrotech agrees to such monitoring taking place. Metrotech will agree to such a request once a Quarter, if necessary. The Latency will be calculated by averaging the Latency measurements recorded over a 60 minute period. Any compensation awarded to the Customer pursuant to this Agreement will be credited by Metrotech against the next following payment due from the Customer or if no payment is due it will be payable by Metrotech by cheque to the Customer at the end of the relevant monitoring Quarter. 2.2.3 Latency on access ports below 10Mbps will be guaranteed for the target Latency for 64 byte frames only. 2.2.4 In respect of a 3rd pa...

Latency. For purposes of this SLA latency shall be defined to mean the elapsed time interval between the transmission and reception of a packet of data from one point to another. FirstDigital’s latency assumption is data should be transmitted instantly between one point and another, there are however several contributing factors to consider when calculating latency. These are:

Latency a maximum one-way trip transmission delay of ten milliseconds between intra-regional points-of- presence (PoPs) of the Supplier;