Internet quality by location

Measured period 2026-10-13 09:36 to 10:36 EDT · one measurement per second per location

At a glance

✓now  As of 10:21–10:35 EDT, ending 2 minutes ago, all 10 locations were clean.

355 clean125 clean212 clean255 clean371 clean629 clean630 clean729 clean76 cleanCONTROL clean

▲last 24h  4 location(s) went over the 1.0% threshold at some point in the last 24 hours: 255 (1h), 125 (1h), 371 (1h), 355 (1h). Worst single hour 1.34% at 255.

Location Each hour, oldest to newestHours over thresholdLast lost packet Independent view
629050 minutes agooutside 0.033% - agrees within 1.0 point
630023 minutes agono outside data
729050 minutes agooutside 0.004% - agrees within 1.0 point
35515 minutes agooutside 0.318% - agrees within 1.0 point
125123.3 hours agooutside 0.007% - agrees within 1.0 point
21203.2 hours agooutside 0.009% - agrees within 1.0 point
255187 minutes agooutside 0.212% - agrees within 1.0 point
371183 minutes agooutside 0.252% - agrees within 1.0 point
7603.4 hours agooutside 0.0% - agrees within 1.0 point

One block per hour from 11: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 — 10:21–10:35 EDT

✓clean  As of 10:21–10:35 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
355✓clean0.11%18.911/88515
125✓clean0.0%20.020/75315
212✓clean0.0%4.760/80015
255✓clean0.0%19.70/84115
371✓clean0.0%19.150/90015
629✓clean0.0%21.780/89915
630✓clean0.0%22.510/89915
729✓clean0.0%18.320/90015
76✓clean0.0%18.070/90015
CONTROL✓clean0.0%1.220/89915

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

▲watch  During 09:36–10:36 EDT on 2026-10-13, 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 09:36–10:36 EDT on 2026-10-13

SeverityWhereWhat it means
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
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-13 04:37 to 2026-10-13 10:37 Eastern, across every measurement run in that window. 99.4% 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.

62916–43 ms · 0% of the window unmeasured
63017–45 ms · 0% of the window unmeasured
72914–23 ms · 0% of the window unmeasured
35513–20 ms · 0% of the window unmeasured
12514–34 ms · 0% of the window unmeasured
2124–5 ms · 0% of the window unmeasured
25513–21 ms · 0% of the window unmeasured
37114–23 ms · 0% of the window unmeasured
7613–21 ms · 0% of the window unmeasured

Each location during 09:36–10:36 EDT on 2026-10-13

LocationState LossWorst 5 min Typical msSlowest 1 in 20 Worst ms
629✓clean0.9%10.67%22.5546.85191.5
630✓clean0.73%8.33%23.1444.87161.96
729✓clean0.14%1.67%18.4325.3280.74
355✓clean0.11%0.33%18.7124.7759.64
125✓clean0.0%0.0%19.7327.6792.95
212✓clean0.0%0.0%4.765.9311.44
255✓clean0.0%0.0%19.3924.38269.21
371✓clean0.0%0.0%19.123.750.19
76✓clean0.0%0.0%18.0721.0734.49

Every interruption during 09:36–10:36 EDT on 2026-10-13

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

TimeLocationKindSeconds
09:43:50630MICRO_DROP2
09:43:56629SHORT_FAILURE5
09:43:56630SHORT_FAILURE5
09:43:58729MICRO_DROP1
09:44:02630MICRO_DROP1
09:44:05630MICRO_DROP1
09:44:06629MICRO_DROP2
09:44:08729MICRO_DROP1
09:44:09629MICRO_DROP2
09:44:13630MICRO_DROP1
09:44:23629MICRO_DROP1
09:44:25630MICRO_DROP1
09:44:31629MICRO_DROP1
09:44:34629MICRO_DROP1
09:44:44630MICRO_DROP1
09:44:55629MICRO_DROP1
09:44:55630MICRO_DROP1
09:45:02630MICRO_DROP1
09:45:07629MICRO_DROP1
09:45:22629SHORT_FAILURE3
09:45:23630MICRO_DROP1
09:45:23729MICRO_DROP1
09:45:24355MICRO_DROP1
09:45:33630MICRO_DROP1
09:45:39630MICRO_DROP1
09:45:44630MICRO_DROP1
09:45:45629MICRO_DROP1
09:45:46630MICRO_DROP1
09:45:47629MICRO_DROP1
09:45:49629MICRO_DROP1
09:45:56629MICRO_DROP1
09:45:59629MICRO_DROP1
09:46:01629MICRO_DROP2
09:46:07630MICRO_DROP1
09:46:11629MICRO_DROP1
09:46:11630MICRO_DROP1
09:46:29629MICRO_DROP2
09:46:32630MICRO_DROP1
09:46:46729MICRO_DROP1
09:46:49629MICRO_DROP1
09:46:49630MICRO_DROP1
09:47:06629MICRO_DROP2
09:47:14729MICRO_DROP1
09:47:18630MICRO_DROP1
09:47:34629MICRO_DROP1
09:47:34630MICRO_DROP1
09:47:37629MICRO_DROP1
09:55:25355MICRO_DROP1
10:09:09355MICRO_DROP1
10:14:53630MICRO_DROP1
10:17:49255SLOWDOWN10
10:32:41355MICRO_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.