Internet quality by location

Measured period 2026-10-03 22:40 to 23:10 EDT · one measurement per second per location

At a glance

▲now  As of 22:54–23:08 EDT, ending 1 minute ago, 2 of 10 locations were over the 1.0% loss threshold: 629, 630.

629 watch630 watch76 clean125 clean729 clean355 clean255 clean212 clean371 cleanCONTROL clean

▲last 24h  5 location(s) went over the 1.0% threshold at some point in the last 24 hours: 255 (5h), 629 (4h), 630 (3h), 125 (1h). Worst single hour 11.22% at 255.

Location Each hour, oldest to newestHours over thresholdLast lost packet Independent view
62945 minutes agooutside 1.139% - agrees within 1.0 point
63035 minutes agono outside data
7601 minute agooutside 0.199% - agrees within 1.0 point
12515 minutes agooutside 0.326% - agrees within 1.0 point
72915 minutes agooutside 0.307% - agrees within 1.0 point
212036 minutes agooutside 0.0% - agrees within 1.0 point
255534 minutes agooutside 0.09% - agrees within 1.0 point
355035 minutes agooutside 0.344% - agrees within 1.0 point
371020 minutes agooutside 0.344% - agrees within 1.0 point

One block per hour from 00: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 — 22:54–23:08 EDT

▲degraded  As of 22:54–23:08 EDT, ending 1 minute ago, 2 of 10 locations were over the 1.0% loss threshold: 629, 630.

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
629▲watch1.92%17.0623/120020
630▲watch1.67%17.220/120020
76✓clean0.75%12.969/120020
125✓clean0.42%16.565/120020
729✓clean0.25%14.533/120020
355✓clean0.0%28.410/120020
255✓clean0.0%15.050/120020
212✓clean0.0%4.530/120020
371✓clean0.0%13.870/120020
CONTROL✓clean0.0%1.190/120020

Measurement runs continuously, one sample per second per location, and this page is republished every 5 minutes. Page built 23:10 EDT. Newest measured minute on record: 23:08 EDT, 1 minute ago. The measurement period summarised below runs up to 23:10 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 — 22:40–23:10 EDT on 2026-10-03

▲degraded  During 22:40–23:10 EDT on 2026-10-03, 2 of 9 locations lost more packets than the threshold allows: 629, 630.

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: 1755 seconds, one sample per second per location. A single lost second moves a location's loss figure by 0.057 percentage points, so small percentages rest on few events. Graphs below cover a longer window and are labelled separately.

Problems found during 22:40–23:10 EDT on 2026-10-03

SeverityWhereWhat it means
MEDIUM629dropped more packets over the measured period than the threshold allows
MEDIUM630dropped more packets over the measured period than the threshold allows
MEDIUM629loss was concentrated in one five-minute stretch
MEDIUM630loss 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-03 17:10 to 2026-10-03 23:10 Eastern, across every measurement run in that window. 137.5% 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.

62914–39 ms · 3% of the window unmeasured
63016–42 ms · 3% of the window unmeasured
7612–15 ms · 3% of the window unmeasured
12514–28 ms · 3% of the window unmeasured
72913–22 ms · 3% of the window unmeasured
2124–5 ms · 3% of the window unmeasured
25514–35 ms · 3% of the window unmeasured
35514–35 ms · 3% of the window unmeasured
37113–22 ms · 3% of the window unmeasured

Each location during 22:40–23:10 EDT on 2026-10-03

LocationState LossWorst 5 min Typical msSlowest 1 in 20 Worst ms
629▲watch1.31%7.67%16.9538.34119.03
630▲watch1.08%6.33%17.1136.9177.69
76✓clean0.46%1.67%12.9718.1857.89
125✓clean0.34%1.67%16.426.068.6
729✓clean0.17%1.0%14.521.9658.35
212✓clean0.0%0.0%4.565.8117.96
255✓clean0.0%0.0%14.6920.4129.11
355✓clean0.0%0.0%28.3139.3557.15
371✓clean0.0%0.0%13.9420.62121.66

Every interruption during 22:40–23:10 EDT on 2026-10-03

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

TimeLocationKindSeconds
22:47:18125MICRO_DROP1
22:50:0476MICRO_DROP1
22:51:40630SLOWDOWN21
22:52:02630SLOWDOWN49
22:54:3376MICRO_DROP1
22:56:0776MICRO_DROP1
22:58:3976MICRO_DROP1
23:00:0176MICRO_DROP1
23:00:0876MICRO_DROP1
23:00:1076MICRO_DROP1
23:03:35629MICRO_DROP1
23:03:39630MICRO_DROP1
23:03:43630MICRO_DROP2
23:03:52629SLOWDOWN10
23:03:55629MICRO_DROP2
23:03:55630MICRO_DROP1
23:03:58629MICRO_DROP1
23:04:02630MICRO_DROP1
23:04:05629MICRO_DROP1
23:04:11629MICRO_DROP1
23:04:13630MICRO_DROP1
23:04:15629MICRO_DROP1
23:04:17630MICRO_DROP1
23:04:22629MICRO_DROP2
23:04:23125MICRO_DROP1
23:04:29125MICRO_DROP1
23:04:29629MICRO_DROP2
23:04:31125MICRO_DROP2
23:04:31729MICRO_DROP1
23:04:32630MICRO_DROP1
23:04:34630MICRO_DROP1
23:04:47629MICRO_DROP1
23:04:49630MICRO_DROP1
23:04:53629MICRO_DROP1
23:04:54729MICRO_DROP1
23:05:00630MICRO_DROP1
23:05:02630MICRO_DROP1
23:05:07630SLOWDOWN14
23:05:09629SHORT_FAILURE6
23:05:10630MICRO_DROP1
23:05:14630MICRO_DROP1
23:05:19630MICRO_DROP1
23:05:21125MICRO_DROP1
23:05:26629MICRO_DROP1
23:05:28630MICRO_DROP2
23:05:32629MICRO_DROP1
23:05:34629MICRO_DROP1
23:05:36630MICRO_DROP2
23:05:41729MICRO_DROP1
23:05:43629MICRO_DROP1
23:09:2476MICRO_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.