Responding devices, whole network
RespondingExpectedIncident
Address blocks
OperationalDegradedOutageNo responding devices
Incidents Last 30 days
How this works
This is a community project. It is not operated by or affiliated with Ashland Fiber Network or the City of Ashland. For service issues, contact AFN directly.
- Every minute, a monitor pings each device that normally answers in the address space AFN routes (AS14188).
- An incident opens when an address block suddenly loses at least 30% of its normally responding devices, and closes once they return.
- The monitor also checks well-known public servers, so its own connection problems are never recorded as AFN outages.
- Route visibility is checked against RIPE's global BGP collectors to spot network-wide routing problems.
- Many home routers ignore pings, so this shows the health of the network as a whole, not every household.
Look up an address
Network time-lapse
Each tile is one /24 address block. Press play to replay how reachability or latency changed. Outages that start in one block and spread to its neighbors usually share equipment; ones that hit everything at once are usually upstream.
Latency right now Median round-trip vs. each block's 24h typical
Reliability Last 30 days
Incident timeline Last 30 days
Address space ARIN registrations vs. BGP routing
Admin sign-in
Stored in this browser only. Set with AFN_ADMIN_TOKEN on the server.
Address map
Every address AFN routes: one square per IP, one 16×16 grid per /24. Replay to see which addresses dropped together. A contiguous run usually means a shared DHCP pool or PON segment. Click a square for its history.
UpDown (was up)Never answeredJust changed