Internet quality by location

Measured period 2026-10-23 06:18 to 07:18 EDT · one measurement per second per location

At a glance

✓now  As of 07:03–07:17 EDT, ending 2 minutes ago, all 10 locations were clean.

125 clean212 clean255 clean355 clean371 clean629 clean630 clean729 clean76 cleanCONTROL clean

▲last 24h  7 location(s) went over the 1.0% threshold at some point in the last 24 hours: 630 (2h), 629 (2h), 125 (1h), 729 (2h). Worst single hour 3.59% at 630.

Location Each hour, oldest to newestHours over thresholdLast lost packet Independent view
125154 minutes agooutside 0.556% - agrees within 1.0 point
629254 minutes agooutside 0.721% - agrees within 1.0 point
729254 minutes agooutside 0.559% - agrees within 1.0 point
630254 minutes agono outside data
371124 minutes agooutside 0.41% - agrees within 1.0 point
255322 minutes agooutside 0.658% - agrees within 1.0 point
355222 minutes agooutside 0.47% - agrees within 1.0 point
21205.3 hours agooutside 0.013% - agrees within 1.0 point
7602.8 hours agooutside 0.228% - agrees within 1.0 point

One block per hour from 08:00 EDT onwards. Green is at or below 1.0% loss, amber above it, orange above 5.0%, red above 10.0%, grey is unmeasured. Hover a block for its figure.
Independent view is the same window measured from a machine on an unrelated datacentre connection, which pings each location from the public internet instead of asking that location's own equipment to send the test. It shares none of the main monitor's machinery, so it is a running check on it. A slightly higher figure there is expected, because that path is longer. A materially LOWER figure would mean the loss is being produced at or near the measurement rather than on the line.

Current conditions — 07:03–07:17 EDT

✓clean  As of 07:03–07:17 EDT, ending 2 minutes ago, all 10 locations were clean.

The most recent measured minutes on record. This answers "what is it doing now", as distinct from the measurement period summarised below.

LocationStateLossTypical msLost / sentMinutes of data
125✓clean0.0%15.830/65813
212✓clean0.0%4.680/74813
255✓clean0.0%13.490/71514
355✓clean0.0%14.10/80014
371✓clean0.0%13.910/78314
629✓clean0.0%17.490/80915
630✓clean0.0%18.430/89115
729✓clean0.0%14.10/89915
76✓clean0.0%13.270/90015
CONTROL✓clean0.0%1.210/89915

Measurement runs continuously, one sample per second per location, and this page is republished every 5 minutes. Page built 07:18 EDT. Newest measured minute on record: 07:17 EDT, 2 minutes ago. The measurement period summarised below runs up to 07:18 EDT and is still going - that is its latest sample, less than a minute ago, not an end. This page reloads itself every 10 minutes.

The measurement period — 06:18–07:18 EDT on 2026-10-23

▲degraded  During 06:18–07:18 EDT on 2026-10-23, 1 of 9 locations lost more packets than the threshold allows: 125.

Each location's internet connection is tested once per second by sending a small packet to a public internet address and waiting for the reply. A missing reply means a packet was lost somewhere between that location and the internet.

Measured period: 3600 seconds, one sample per second per location. A single lost second moves a location's loss figure by 0.028 percentage points, so small percentages rest on few events. Graphs below cover a longer window and are labelled separately.

Problems found during 06:18–07:18 EDT on 2026-10-23

SeverityWhereWhat it means
MEDIUM125dropped more packets over the measured period than the threshold allows
MEDIUM125loss was concentrated in one five-minute stretch
MEDIUM629loss was concentrated in one five-minute stretch
MEDIUM729loss was concentrated in one five-minute stretch
MEDIUMshared carrier equipment, group Aseveral locations sharing one piece of carrier equipment lost packets in the same seconds, so the fault is upstream of all of them
10 note(s) about the measurement itself, not problems with any location
SeverityWhereWhat it means
INFOindependent referencethe independent reference also lost packets, so some loss belongs to the wider internet
INFO125not enough history yet to compare this location against its own normal
INFO212not enough history yet to compare this location against its own normal
INFO255not enough history yet to compare this location against its own normal
INFO355not enough history yet to compare this location against its own normal
INFO371not enough history yet to compare this location against its own normal
INFO629not enough history yet to compare this location against its own normal
INFO630not enough history yet to compare this location against its own normal
INFO729not enough history yet to compare this location against its own normal
INFO76not enough history yet to compare this location against its own normal

Each location over the last 6 hours

One panel per location. The line is the median response time in each slice; rising means slower. The strip underneath marks slices in which packets were lost. Breaks in the line are periods with no measurement, never drawn across. Each panel is scaled to its own range, printed beside its name.

Covers the last 6 hours, 2026-10-23 01:18 to 2026-10-23 07:18 Eastern, across every measurement run in that window. 99.7% of those hours carry data. Measurement is continuous now, so that figure climbs towards 100% as the day goes on; the gaps are earlier periods when measurement ran in short scheduled sessions instead. An unmeasured period is not a quiet period.

12514–38 ms · 1% of the window unmeasured
62915–39 ms · 0% of the window unmeasured
72913–26 ms · 0% of the window unmeasured
63016–39 ms · 0% of the window unmeasured
37113–18 ms · 0% of the window unmeasured
25513–16 ms · 0% of the window unmeasured
35513–39 ms · 0% of the window unmeasured
2124–5 ms · 1% of the window unmeasured
7612–17 ms · 0% of the window unmeasured

Each location during 06:18–07:18 EDT on 2026-10-23

LocationState LossWorst 5 min Typical msSlowest 1 in 20 Worst ms
125▲watch1.03%7.0%15.7425.6857.04
629✓clean0.82%5.33%17.6235.0265.91
729✓clean0.81%6.0%13.9520.8258.81
630✓clean0.62%5.0%18.2933.2561.51
371✓clean0.23%2.33%14.0219.8166.38
255✓clean0.17%1.67%13.418.5273.37
355✓clean0.06%0.33%13.9120.3657.26
212✓clean0.0%0.0%4.75.8613.95
76✓clean0.0%0.0%13.3116.8535.55

Every interruption during 06:18–07:18 EDT on 2026-10-23

Includes one-second blips, which are harmless alone but indicate an unsteady connection. Times are Eastern.

TimeLocationKindSeconds
06:18:40630SHORT_FAILURE5
06:18:41729MICRO_DROP2
06:18:43729SLOWDOWN10
06:18:44729MICRO_DROP1
06:18:46630MICRO_DROP1
06:18:46729MICRO_DROP2
06:18:49729SHORT_FAILURE6
06:18:50630MICRO_DROP1
06:19:00125MICRO_DROP1
06:19:01125SLOWDOWN23
06:19:01629SHORT_FAILURE3
06:19:03125MICRO_DROP2
06:19:05629SLOWDOWN10
06:19:07125SHORT_FAILURE7
06:19:07629MICRO_DROP2
06:19:10629MICRO_DROP1
06:19:12629MICRO_DROP1
06:19:15629SHORT_FAILURE5
06:19:16125MICRO_DROP1
06:19:19125MICRO_DROP1
06:19:21125MICRO_DROP2
06:19:23629MICRO_DROP1
06:25:13630MICRO_DROP1
06:25:16630MICRO_DROP1
06:25:17729MICRO_DROP1
06:25:20729MICRO_DROP1
06:25:21630MICRO_DROP1
06:25:22729MICRO_DROP1
06:25:26729MICRO_DROP1
06:25:30630MICRO_DROP1
06:25:32630MICRO_DROP2
06:25:35630MICRO_DROP2
06:25:36729MICRO_DROP1
06:25:38630SHORT_FAILURE5
06:25:39729SHORT_FAILURE4
06:25:41125MICRO_DROP1
06:25:42629MICRO_DROP1
06:25:44729MICRO_DROP1
06:25:47630MICRO_DROP1
06:25:47729MICRO_DROP1
06:25:50729MICRO_DROP1
06:25:52125SHORT_FAILURE3
06:25:52729SHORT_FAILURE3
06:25:54629MICRO_DROP1
06:25:57630MICRO_DROP1
06:26:02729SHORT_FAILURE3
06:26:05629SHORT_FAILURE3
06:26:07125SHORT_FAILURE3
06:26:10629SLOWDOWN10
06:26:11125MICRO_DROP2
06:26:12629MICRO_DROP2
06:26:14125SHORT_FAILURE8
06:26:15629SHORT_FAILURE3
06:26:22629MICRO_DROP1
06:26:24629SHORT_FAILURE4
06:26:25125SHORT_FAILURE3
06:26:29125MICRO_DROP1
06:26:29629MICRO_DROP1
06:32:17125SLOWDOWN43
06:35:21630SLOWDOWN33
06:37:03355MICRO_DROP1
06:47:25629SLOWDOWN18
06:47:54629SLOWDOWN22
06:51:11255MICRO_DROP1
06:51:23255MICRO_DROP1
06:51:50371MICRO_DROP1
06:52:16255MICRO_DROP1
06:52:36371MICRO_DROP1
06:52:42371MICRO_DROP1
06:53:17371MICRO_DROP1
06:53:34255MICRO_DROP1
06:54:02371MICRO_DROP1
06:54:26255MICRO_DROP1
06:55:26371MICRO_DROP1
06:55:52371MICRO_DROP1
06:57:04371MICRO_DROP1
06:57:05355MICRO_DROP1
06:57:10255MICRO_DROP1

Terms

clean means loss at or below 1 per cent, watch above 1 and up to 5, degraded above 5 and up to 10, failing above 10. Minutes of data is how many one-minute summaries a current-conditions row is computed from, out of the 15 most recent available - 10 means the figure rests on 600 tests, 1 means it rests on 60. Loss is the share of once-per-second tests that got no reply. Typical ms is the middle response time. Slowest 1 in 20 is the 95th percentile. Worst 5 min is the highest loss over any five consecutive minutes in the period, which catches loss that is concentrated rather than spread evenly. The independent reference is a machine on an unrelated datacentre connection running the same test, so a bad moment at the address being pinged is not mistaken for a fault at these locations. MICRO_DROP is one or two lost seconds, SHORT_FAILURE three to twenty-nine, OUTAGE thirty or more, and SLOWDOWN is at least ten seconds much slower than that location's own median for the measured period - not against its long-run history.