Metronet Downtime Report
How often our home internet connection has dropped, measured once a minute from Aug 1, 2026 to Oct 14, 2026 at 2:04 PM (Central time).
88outages
14h 31mtotal time down
1h 28mlongest outage (Sep 1)
99.19%uptime
Summary by month
| Month | Total | 1 min or less | Longer than 1 min | Average outage | Reliability |
|---|---|---|---|---|---|
| Aug | 32 (5h 42m) | 2 (2 min) | 30 (5h 40m) | 10.7 min | 99.23% |
| Sep | 25 (3h 34m) | 9 (9 min) | 16 (3h 25m) | 8.6 min | 99.50% |
| Oct (1–14) | 31 (5h 15m) | 4 (4 min) | 27 (5h 11m) | 10.2 min | 98.39% |
| Total | 88 (14h 31m) | 15 (15 min) | 73 (14h 16m) | 9.9 min | 99.19% |
Each cell shows the number of outages and the total time down. Average outage is total time divided by the number of outages. Reliability is the share of the month the connection was up while it was being monitored.
Charts
Internet downtime per day
Minutes down each day. Each section is one outage, stacked in the order they happened. The line is the trailing 7-day average.
Longer than 1 min1 min or less7-day average
Outages per day
Number of separate outages each day, with the trailing 7-day average.
Longer than 1 min1 min or less7-day average
When outages start
Number of outages by the hour of day they began.
Longer than 1 min1 min or less
How this is measured
- An Uptime Kuma monitor on a Raspberry Pi pings a public address (8.8.4.4) once a minute. A failed ping marks the internet as down until the next successful one, so each start and end time can be off by up to about a minute.
- A second monitor pings our own router. Outages where our router was also down within 3 minutes are left out, since those point to a problem inside the house rather than with Metronet.
- Outages of 1 minute or less are a single failed check and could be a dropped ping rather than a real outage, so they are shown separately.