Internet quality by location

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

At a glance

✓now  As of 06:20–06:34 EDT, ending 2 minutes ago, all 10 locations were clean.

255 clean630 clean629 clean125 clean212 clean355 clean371 clean729 clean76 cleanCONTROL clean

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

Location Each hour, oldest to newestHours over thresholdLast lost packet Independent view
2551114 minutes agooutside 2.253%, higher than inside by 1.77 points - expected direction, the outside path is longer
630911 minutes agono outside data
629910 minutes agooutside 0.095% - agrees within 1.0 point
371233 minutes agooutside 0.773% - agrees within 1.0 point
355537 minutes agooutside 0.902% - agrees within 1.0 point
729836 minutes agooutside 0.009% - agrees within 1.0 point
125862 minutes agooutside 0.013% - agrees within 1.0 point
212021.2 hours agooutside 0.0% - agrees within 1.0 point
7609.5 hours agooutside 0.0% - agrees within 1.0 point

One block per hour from 07: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 — 06:20–06:34 EDT

✓clean  As of 06:20–06:34 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
255✓clean0.22%14.012/89915
630✓clean0.22%17.222/90015
629✓clean0.11%16.821/89915
125✓clean0.0%15.770/90015
212✓clean0.0%4.720/90015
355✓clean0.0%14.590/90015
371✓clean0.0%13.990/89915
729✓clean0.0%14.660/89915
76✓clean0.0%12.40/90015
CONTROL✓clean0.0%1.210/89815

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

▲watch  During 05:35–06:35 EDT on 2026-10-07, no location breached a threshold; some showed minor loss.

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 05:35–06:35 EDT on 2026-10-07

SeverityWhereWhat it means
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
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-07 00:35 to 2026-10-07 06:35 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.

25513–31 ms · 0% of the window unmeasured
63015–41 ms · 0% of the window unmeasured
62914–37 ms · 0% of the window unmeasured
37113–19 ms · 0% of the window unmeasured
35514–37 ms · 0% of the window unmeasured
72913–18 ms · 0% of the window unmeasured
12513–33 ms · 0% of the window unmeasured
2124–5 ms · 0% of the window unmeasured
7612–15 ms · 0% of the window unmeasured

Each location during 05:35–06:35 EDT on 2026-10-07

LocationState LossWorst 5 min Typical msSlowest 1 in 20 Worst ms
255✓clean0.48%3.33%14.119.6444.21
630✓clean0.25%1.0%17.8436.91142.81
629✓clean0.11%0.67%17.1737.9885.21
371✓clean0.08%0.67%14.1219.6854.32
355✓clean0.06%0.33%20.0543.3991.66
729✓clean0.06%0.33%14.3321.3265.27
125✓clean0.0%0.0%15.7522.7547.51
212✓clean0.0%0.0%4.615.8313.91
76✓clean0.0%0.0%12.4315.1135.94

Every interruption during 05:35–06:35 EDT on 2026-10-07

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

TimeLocationKindSeconds
05:36:52255MICRO_DROP1
05:39:07355SLOWDOWN11
05:40:34255MICRO_DROP1
05:41:01255MICRO_DROP1
05:41:44255MICRO_DROP1
05:41:54255MICRO_DROP1
05:41:57255MICRO_DROP1
05:42:04255MICRO_DROP1
05:42:09255MICRO_DROP1
05:42:23255MICRO_DROP1
05:43:11255MICRO_DROP1
05:43:51371MICRO_DROP1
05:45:01255MICRO_DROP1
05:45:47371MICRO_DROP1
05:47:44629MICRO_DROP1
05:48:13629MICRO_DROP1
05:48:13630MICRO_DROP2
05:48:14729MICRO_DROP1
05:48:18630MICRO_DROP1
05:49:05355MICRO_DROP1
05:49:26255MICRO_DROP1
05:53:48255MICRO_DROP1
05:56:13255MICRO_DROP1
05:56:14629SLOWDOWN11
05:56:53629SLOWDOWN33
05:58:59355MICRO_DROP1
06:00:15255MICRO_DROP1
06:00:21630MICRO_DROP1
06:00:46629MICRO_DROP1
06:00:46729MICRO_DROP1
06:03:23371MICRO_DROP1
06:12:23630MICRO_DROP1
06:13:02630MICRO_DROP1
06:13:08630MICRO_DROP1
06:21:33255MICRO_DROP1
06:22:23255MICRO_DROP1
06:25:21630MICRO_DROP1
06:25:42630MICRO_DROP1
06:26:22629MICRO_DROP1
06:33:24630SLOWDOWN17
06:34:44630SLOWDOWN13

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.