Network Latency Sample Clauses

Network Latency. The network latency will average less than 25 ms per element averaged across all elements on the local portion of SI&T’s network. After being notified by Customer of network latency in excess of the limit specified above, SI&T will use commercially reasonable efforts to determine the source of such excess network latency and to correct such problem to the extent that the source of the problem is on SI&T’s Network. If SI&T fails to remedy such network latency within four (4) hours of verification and if the average network latency for the preceding 30 days has exceeded the rates specified above, Customer may request a one (1) day Service Credit for that particular event. Customer may not request network latency service credit more than once for any given calendar day. Network Latency across an element is defined as the average time taken for data to make a round trip across such element. Elements in the transport circuit include routers, switches, circuits and other components. Test points for latency are designated solely by SI&T. Testing must be done during a period in which the only traffic on the circuit is the test traffic. Average latency is not measured when a circuit is experiencing a service outage. In the case of continuous high latency exceeding the limits of this SLA, SI&T reserves the right to recommend the disconnection of the affected circuit without penalty of breach.

Network Latency. Network Latency is defined as the round-trip delay (in milliseconds) of packets transported between specific WIN POP locations across the WIN Data Network and does not apply to Third Party Provider local access circuits. Network Latency is calculated based on an aggregate monthly measurement average between specific WIN PoP endpoints.

Network Latency. As the primary locus of data moves from disk to flash or even DRAM, the network is becoming the primary source of latency in remote data accesses. Network latency is an expression of how much time it takes for a packet of data to get from one point to another. Several factors contribute to latency, including not only the time it takes for a packet to travel in the cable, but the equipment/switch used to transmit/receive and forward the packet. Total packet latency is the sum of all of the path latencies and all of the switch latencies encountered along the route (e.g, RTT, Round Trip Time). A packet that travels over N paths will pass through N −1 switches. The value of N for any given packet will vary depending on the amount of locality that can be exploited in an application’s communication pattern, the topology of the network, the routing algorithm, and the size of the network. However, when it comes to typical case latency in a big-scale data centre network, path latency is a very small part of total latency. Total latency is dominated by the switch latency which includes delays due to buffering, routing algorithm complexity, arbitration, flow control, switch traversal, and the load congestion for a particular switch egress port. Note that these delays are incurred at every switch in the network and hence these delays are multiplied by the hop count. One of the suitable ways to reduce hop-count is to increase the radix of the switches. Increased switch radix means fewer switches for a network of a given size and therefore a reduced CapEx cost. Reduced hop-count and fewer switches also lead to reduced power consumption as well as reduced latency. For all-electrical switches, there is a fundamental trade-off due to the poor scaling of both signal pins and per pin bandwidth. Namely one could choose to utilize more pins per port which results in a lower radix but with higher bandwidth per port. The other option is to use fewer pins per port which would increase the switch radix but the bandwidth of each port would suffer. Photonics may lead to a better option, namely the bandwidth advantage due to spatial/spectrum division multiplexing, and the tighter signal packaging density of optics means that high-radix switches are feasible without a corresponding degradation of port bandwidth.

Network Latency. Masergy will meet or be less than the average roundtrip latency times between Masergy hubs shown below on Table 1 (Network Latency). Latency is calculated by averaging five (5) minute latency measurements between ▇▇▇▇▇▇▇'s inter-city transit backbone routers monthly. In the event that Masergy fails to meet the latency measurement set forth in Table 1 (Network Latency) in any given calendar month during the term of Masergy's agreement with Customer, and Customer has Service between the affected hubs, 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 measurement is not met. In order to be eligible for the Network 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.

Network Latency. Real Time – 10 milliseconds or less Priority Data – 10 milliseconds or less Basic – 100 milliseconds or less 3.3.1 Latency is the average time for a packet to make a trip between network terminations on the METROFIBRE Network (Gauteng only). Aggregate latency will be monitored by monitoring trip times between NNI to UNI and/or UNI to UNI on an ongoing basis. 3.3.2 After notification of Network Latency being in excess of rates applicable as stated above, METROFIBRE will use commercially reasonable efforts to determine the source of such excessive latency and to correct such problem. If METROFIBRE fails to remedy such Network Latency within two (2) hours of being notified of any excessive Network Latency and average Network Latency for the preceding 30 days has exceeded the rates specified above, Customer will receive, at Customer’s request, a Service Credit for the period from the time of notification by the Customer until the average Network Latency for the preceding 30 days is less than the rates specified above. Customer may obtain no more than 20% of one (1) month Service Credit for any given month.

Network Latency. The average network transit delay (“Latency”) will be measured via roundtrip pings on an ongoing basis every five minutes to determine a consistent average monthly performance level for Latency between edge. Edge locations are defined at Customer sites, trading partner locations, or Exchange locations. Latency is calculated as follows: Region Minimum Latency Per Mile Latency If Goal Exceeded By (c) Packet Delivery. Packet Delivery will be measured on an ongoing basis every five minutes to determine a consistent average monthly performance level for packets actually delivered between the POPs. Region Goal Remedy (Credit is applied as a % of the Lumen Financial Connect Port MRC for the Affected Service)*

Network Latency. BANDWIDTH

Network Latency. Jitter <= 30ms: 2.1 Nova Broadband aims to provide a maximum average network latency from the CPE to INEX of 30ms. This latency is calculated by sending ping packets from the Nova NOC to the Customer’s CPE and recording the response times. 2.2 Nova Broadband aims to provide a maximum average network jitter from the CPE to INEX of 30ms. This jitter is calculated by sending ping packets from the Nova NOC to the Customer’s CPE and recording the response times. 2.3 If one or both of the latency or jitter figures exceeds their above specified values, Nova Broadband will be liable to credit the account of the Customer with a penalty charge equivalent to two days’ Service fee.

Network Latency. 3.4.1 ▇▇▇ agrees to provide the Service with target latency of 20 milliseconds or less. 3.4.2 Latency will be determined by ▇▇▇ as measured from our core network calculating the average of round-trip transmission measurements taken in ten-minute intervals during a calendar month. 3.4.3 All suspected latency issues should be reported in the first instance to Ogi by telephone to ▇▇▇ ▇▇▇▇ ▇▇▇▇ or ▇▇▇▇▇▇▇▇.▇▇▇▇@▇▇▇.▇▇▇▇▇.