Report period
Service profile
ISP details appear here.
At a glance
AnalyzingConnection overview
Disconnect history and recent latency readings.
- Disconnects · ICM
- —
- Downtime · ICM
- —
- Median latency
- —
- Packet loss
- —
- Router response
- —
- Availability · latency monitor
- —
All time
Service reliability
Work Hour Impact
—Disconnects
—Work downtime
—Total downtime
—Availability
—Longest outage
—Monitoring coverage and availability basis loading…
Trend
Daily availability
Availability99.9% reference
Pattern
Outage timing
Local time
By hour
Day and hourRecurring patternShow pattern
Recent activity
Connection history
Median latency
—Worst 15-min p95
—Jitter
—Packet loss
—Router latency
—Latency disconnects
—Availability
—Monitoring coverage loading…
CloudflareGoogleRouterICMP packet lossLatency outageICM status50 / 100 / 200 ms bands
Download redacted sample logs
Full-resolution 5-second samples. Local machine names, IP fields, and address are omitted.
- No published sample files listed.
Connection event timeline
ICM and latency events are separate observations. Matching times can describe the same outage.
| Time | Source | Duration | State |
|---|
Private evidence · this computer
Incident captures
These versioned captures and raw network diagnostics stay in your local profile folder and are not part of the published snapshot.
Plain-English diagnostic glossary
- DOCSIS
- Cable modem communication standard; these probes do not verify provider-side DOCSIS state.
- CMTS
- Provider equipment that connects cable modems to the provider network.
- T3/T4
- Modem timeout event labels, when a gateway exposes them; their presence needs timestamp and context.
- SNR / MER
- Signal quality measurements, when available from owner-accessible modem status.
- Ingress
- Unwanted signal entering a cable system; this monitor cannot locate or prove it.
- First hop
- The first network device reached beyond this computer, often the local gateway.
- Latency
- Time for a probe response, measured in milliseconds.
- Packet loss
- Probe attempts without a response; one lost ping alone is not a confirmed outage.
- Coverage
- Time with valid samples compared with the time expected to be monitored.
Latency data loading…
How these measurements work
Every 5 seconds, the collector pings the detected router and two internet targets: Cloudflare (1.1.1.1) and Google (8.8.8.8). Latency uses the fastest successful internet response; router latency is reported separately.
A sample is a confirmed-outage candidate only when both internet IP probes and HTTPS fail. A confirmed disconnect requires two consecutive candidate samples. A single failed probe or candidate sample is an impairment observation, not a confirmed outage. Consecutive confirmed samples count as one episode. These observations identify reachability, not who caused the fault.
Latency traces draw every available published 5-second sample when the redacted sample files are available. Packet-loss bars aggregate those raw requests into smaller time bins for short windows, while longer windows use wider bins; if raw files are unavailable, they fall back to 15-minute published summaries. This keeps individual 0/50/100% ping results from merging into a misleading solid block at dashboard width. Hover summaries and “Worst 15-min p95” use 15-minute buckets. Jitter is the average change between successive successful internet responses. Packet loss is the share of individual ICMP requests that failed; a disconnect requires two consecutive failed cycles with no HTTPS response.
Samples normally cover time until the next sample. Long gaps are unmonitored time, not evidence of uptime or an outage, and are excluded from availability. Coverage is shown separately from availability. ICM and latency records stay separately attributed; overlapping household downtime is also reported as a union measure.
Daily reliability
| Date | Availability | Downtime | Disconnects |
|---|