Demo data. Everything here is synthetic and read-only: it shows how isitmyisp reports a real network.

Incidents in the last 30 days

StartEndDurationWhereEvidence
2026-11-17 20:592026-11-17 21:02 2 min 30 s branch-office · Tunnel down: configuration (path was clean) through the tunnel (10.10.0.1): 100.0% loss (15/15)
outside the tunnel (198.51.100.20): OK
2026-11-17 20:54ongoing 15 min Internet · Loop or broadcast storm on your network gateway ping: 10 duplicate replies (DUP) out of 30
broadcast on your network card: 6084 packets/s (usual 6)
home router 192.168.1.1: 26.7% loss (4/15)
2026-11-17 19:092026-11-17 19:11 2 min 30 s branch-office · Tunnel down: configuration (path was clean) through the tunnel (10.10.0.1): 100.0% loss (15/15)
outside the tunnel (198.51.100.20): OK
2026-11-17 17:472026-11-17 19:43 1 h 55 min Internet · ISP backbone / upstream problem 1.1.1.1: 33.3% loss (5/15)
8.8.8.8: 33.3% loss (5/15)
9.9.9.9: 33.3% loss (5/15)
What the evidence rules out
Your router and local network answered normally at the same time
Real TCP connections were affected too (not just ping being deprioritized)
Several independent networks were affected at once (not one website)
Your link was not full (read from your router: ↓ 179 Mbps (60%) · ↑ 32 Mbps (32%))
Your router's CPU was not overloaded (10.8%)
No sign of a loop or broadcast storm on your network (no duplicate replies, normal broadcast)
What it can't rule out
That the fault is in your ISP's own upstream providers; towards you, it is still your ISP's service
2026-11-17 17:092026-11-17 17:11 2 min 30 s branch-office · Tunnel down: configuration (path was clean) through the tunnel (10.10.0.1): 100.0% loss (15/15)
outside the tunnel (198.51.100.20): OK
2026-11-17 16:072026-11-17 16:36 28 min Card terminal, till 1 · Device not answering (your network is fine) 192.168.1.60 (ping): no reply to ping (3/3 checks failed)
your network: OK at the same time (your router answered)
2026-11-17 15:092026-11-17 15:11 2 min 30 s branch-office · Tunnel down: configuration (path was clean) through the tunnel (10.10.0.1): 100.0% loss (15/15)
outside the tunnel (198.51.100.20): OK
2026-11-17 14:262026-11-17 15:09 43 min ERP · Service unreachable (your internet is fine) erp.example:443: timeout (3/3 checks failed)
your internet: OK at the same time
2026-11-17 13:092026-11-17 13:11 2 min 30 s branch-office · Tunnel down: configuration (path was clean) through the tunnel (10.10.0.1): 100.0% loss (15/15)
outside the tunnel (198.51.100.20): OK
2026-11-17 11:092026-11-17 11:11 2 min 30 s branch-office · Tunnel down: configuration (path was clean) through the tunnel (10.10.0.1): 100.0% loss (15/15)
outside the tunnel (198.51.100.20): OK
2026-11-17 11:042026-11-17 12:59 1 h 55 min Internet · ISP backbone / upstream problem 1.1.1.1: 40.0% loss (6/15)
8.8.8.8: 40.0% loss (6/15)
9.9.9.9: 40.0% loss (6/15)
What the evidence rules out
Your router and local network answered normally at the same time
Real TCP connections were affected too (not just ping being deprioritized)
Several independent networks were affected at once (not one website)
Your router's CPU was not overloaded (20.1%)
No sign of a loop or broadcast storm on your network (no duplicate replies, normal broadcast)
What it can't rule out
That the fault is in your ISP's own upstream providers; towards you, it is still your ISP's service
Saturation by your own traffic (downloads, backups): connect isitmyisp to your router (SNMP) to rule it out
2026-11-17 09:092026-11-17 09:11 2 min 30 s branch-office · Tunnel down: configuration (path was clean) through the tunnel (10.10.0.1): 100.0% loss (15/15)
outside the tunnel (198.51.100.20): OK
2026-11-17 08:262026-11-17 10:21 1 h 55 min failover · Running on the backup link provider: Example ISP S.A. -> Backup Wireless S.R.L.
ISP first hop: ? -> ?
2026-11-17 06:452026-11-17 07:14 29 min branch-office · Tunnel down: far site or the path to it through the tunnel (10.10.0.1): 53.3% loss (8/15)
outside the tunnel (198.51.100.20): 53.3% loss (8/15)
2026-11-17 05:092026-11-17 05:11 2 min 30 s branch-office · Tunnel down: configuration (path was clean) through the tunnel (10.10.0.1): 100.0% loss (15/15)
outside the tunnel (198.51.100.20): OK
2026-11-17 03:232026-11-17 03:59 36 min Internet · Problem on your side home router 192.168.1.1: 33.3% loss (5/15)
1.1.1.1: 33.3% loss (5/15)
8.8.8.8: 33.3% loss (5/15)
2026-11-17 03:092026-11-17 03:11 2 min 30 s branch-office · Tunnel down: configuration (path was clean) through the tunnel (10.10.0.1): 100.0% loss (15/15)
outside the tunnel (198.51.100.20): OK
2026-11-17 01:092026-11-17 01:11 2 min 30 s branch-office · Tunnel down: configuration (path was clean) through the tunnel (10.10.0.1): 100.0% loss (15/15)
outside the tunnel (198.51.100.20): OK
2026-11-17 00:032026-11-17 00:30 27 min Internet · ISP backbone / upstream problem
comes and goes (19 drops)
1.1.1.1: 40.0% loss (6/15)
8.8.8.8: 40.0% loss (6/15)
9.9.9.9: 40.0% loss (6/15)
What the evidence rules out
Your router and local network answered normally at the same time
Real TCP connections were affected too (not just ping being deprioritized)
Several independent networks were affected at once (not one website)
Your link was not full (read from your router: ↓ 43 Mbps (14%) · ↑ 8 Mbps (8%))
Your router's CPU was not overloaded (10.8%)
No sign of a loop or broadcast storm on your network (no duplicate replies, normal broadcast)
What it can't rule out
That the fault is in your ISP's own upstream providers; towards you, it is still your ISP's service
2026-11-16 23:092026-11-16 23:11 2 min 30 s branch-office · Tunnel down: configuration (path was clean) through the tunnel (10.10.0.1): 100.0% loss (15/15)
outside the tunnel (198.51.100.20): OK