Latency Sample Clauses

The Latency clause defines the acceptable delay or response time for a service or system to perform its functions. It typically sets specific time thresholds within which actions, data transfers, or responses must occur, and may outline procedures or remedies if these thresholds are exceeded. By establishing clear expectations for performance speed, this clause helps ensure reliable service delivery and addresses potential issues caused by slow or delayed operations.
POPULAR SAMPLE Copied 12 times
Latency. If the actual monthly average Latency exceeds the number of milliseconds set forth in the table below and such failure is quality-impacting, Licensee shall be entitled to a Product Credit equal to the percentage of the applicable MRC set forth in the following table: 45ms or less No Credit >45ms 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. 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. The latency of the Service for each language will be [* *] seconds or less for [* *] of the page views from anywhere within the primary country or countries that such localized Service serves.
Latency a maximum one-way trip transmission delay of ten milliseconds between intra-regional points-of-presence (POPs) of the Supplier;
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. 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. Latency is measured as the one-way trip time; averaged over a one-month (720 hour) period, required for a data packet (100 bytes) to travel between the two end locations of the loop. Latency for Mediacom’s network shall be a maximum of fifty (50) milliseconds.
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. 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. Ziply Fiber 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 Standard [Standard Data Service] ≤ 56 ms ≤ 100 ms ≤ 250 ms 10% Platinum [Real Time Data Service] ≤ 14 ms ≤ 36 ms ≤ 140 ms 20%