216.24.221.0/24
At a glance
Addresses
/24 block
Visibility
53 of 76 vantage points
RPKI
Registry
USAllocated 22nd January 2021
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Oregon, US.
Seen from Oregon, US
- Peer of AS53356seen on 938 paths from 38 vantage points
- Peer of AS6424seen on 55,796 paths from 115 vantage points
- Peer of AS6461seen on 81,633 paths from 1 vantage point
- Peer of AS8551seen on 1,076,486 paths from 1 vantage point
CA
PT
IL
PSOne 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
- Amsterdam5335669398298This path
- London, UK5335669398529This path
- Sao Paulo53356693935280This path
- Singapore350390091299335623673This path
- Oregon, US5335664246461855142013Shown above
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
70%
Seen by 53 of 76 full-feed vantage points
Partially propagatedObserved at 4 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
- 22nd January 2021
- Allocation block
- 216.24.208.0/20
- Status
- allocated
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 216.24.220.0/24 | 256 | AS3503WebNet LLC | 75/76 |
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 216.24.221.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.