Internet quality by location

Measured period 2026-10-04 23:10 to 00:10 EDT · one measurement per second per location

At a glance

✓now  As of 23:55–00:09 EDT, ending 1 minute ago, all 10 locations were clean.

76 clean125 clean212 clean255 clean355 clean371 clean629 clean630 clean729 cleanCONTROL clean

▲last 24h  6 location(s) went over the 1.0% threshold at some point in the last 24 hours: 630 (11h), 629 (9h), 125 (6h), 729 (6h). Worst single hour 8.12% at 630.

Location Each hour, oldest to newestHours over thresholdLast lost packet Independent view
76010 minutes agooutside 0.212% - agrees within 1.0 point
212030 minutes agooutside 0.056% - agrees within 1.0 point
125681 minutes agooutside 0.034% - agrees within 1.0 point
255077 minutes agooutside 0.145% - agrees within 1.0 point
355178 minutes agooutside 0.145% - agrees within 1.0 point
371176 minutes agooutside 1.935%, higher than inside by 1.94 points - expected direction, the outside path is longer
62994.3 hours agooutside 0.0% - agrees within 1.0 point
630113.0 hours agono outside data
72964.6 hours agooutside 0.0% - agrees within 1.0 point

One block per hour from 01: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 — 23:55–00:09 EDT

✓clean  As of 23:55–00:09 EDT, ending 1 minute 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
76✓clean0.44%12.54/90015
125✓clean0.0%16.270/90015
212✓clean0.0%4.640/90015
255✓clean0.0%14.520/89915
355✓clean0.0%27.00/89915
371✓clean0.0%13.750/89915
629✓clean0.0%17.580/89915
630✓clean0.0%18.020/89915
729✓clean0.0%14.70/90015
CONTROL✓clean0.0%1.20/89915

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

✓clean  During 23:10–00:10 EDT on 2026-10-04, all 9 locations stayed within thresholds.

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 23:10–00:10 EDT on 2026-10-04

No problem found in this period - no location over a threshold and no shared fault detected.

9 note(s) about the measurement itself, not problems with any location
SeverityWhereWhat it means
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-04 18:10 to 2026-10-05 00:10 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.

7612–16 ms
2124–5 ms
12514–34 ms
25514–16 ms
35513–35 ms
37113–17 ms · 0% of the window unmeasured
62915–42 ms
63015–39 ms
72914–35 ms

Each location during 23:10–00:10 EDT on 2026-10-04

LocationState LossWorst 5 min Typical msSlowest 1 in 20 Worst ms
76✓clean0.31%1.33%12.8218.5261.92
212✓clean0.03%0.33%4.615.8415.97
125✓clean0.0%0.0%16.0125.4243.83
255✓clean0.0%0.0%14.5520.0652.98
355✓clean0.0%0.0%27.5946.8656.28
371✓clean0.0%0.0%13.7717.2392.51
629✓clean0.0%0.0%17.4436.9854.29
630✓clean0.0%0.0%18.5840.5566.76
729✓clean0.0%0.0%14.7221.8442.56

Every interruption during 23:10–00:10 EDT on 2026-10-04

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

TimeLocationKindSeconds
00:00:0876MICRO_DROP1
00:00:1276MICRO_DROP1
00:00:27629SLOWDOWN10
00:00:42629SLOWDOWN13
00:01:51629SLOWDOWN18
00:03:32629SLOWDOWN51
23:13:1876MICRO_DROP1
23:14:1276MICRO_DROP1
23:18:5976MICRO_DROP2
23:25:2976MICRO_DROP1
23:25:4376MICRO_DROP2
23:30:06629SLOWDOWN32
23:30:39629SLOWDOWN13
23:31:38125SLOWDOWN18
23:31:43630SLOWDOWN10
23:32:19630SLOWDOWN27
23:32:50630SLOWDOWN18
23:33:14630SLOWDOWN14
23:35:08630SLOWDOWN12
23:36:01630SLOWDOWN14
23:40:22212MICRO_DROP1
23:51:48630SLOWDOWN12
23:51:58125SLOWDOWN24
23:52:03630SLOWDOWN27
23:56:4676MICRO_DROP1
23:59:1876MICRO_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.