24.166.176.0/20
At a glance
Addresses
/20 block
Visibility
76 of 76 vantage points
RPKI
Registry
USAllocated 9th June 2000
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS20231seen on 810 paths from 110 vantage points
- Peer of AS11427seen on 43,667 paths from 139 vantage points
- Peer of AS7843seen on 191,641 paths from 102 vantage points
- Peer of AS6939seen on 131,487 paths from 2 vantage points
CHOne path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.
Every path we see
- Sao Paulo2023111427784335280This path
- Amsterdam2023111427784369398298Shown above
- London, UK2023111427784312998529This path
- Singapore20231114277843693923673This path
- Oregon, US202311142778431299855142013This path
Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.
Route visibility
100%
Seen by 76 of 76 full-feed vantage points
Globally propagatedObserved at 5 of our collectors.
What this percentage counts
The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.
It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.
Registry and RPKI
- RIR
- ARIN — North America
- Country
- United States
- Allocated
- 9th June 2000
- Allocation block
- 24.160.0.0/13
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 24.166.160.0/19 | 8.2k | AS10796Charter Communications Inc | 76/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
Why these dates start where they do
A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.
Open 24.166.176.0/20 in the calculator/20 reference
Routing data derived from RouteViews MRT archives and public registry data.