64.205.96.0/24
At a glance
Addresses
/24 block
Visibility
80 of 81 vantage points
RPKI
Registry
USAllocated 16th May 2000
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS401362seen on 3,998 paths from 80 vantage points
- Peer of AS63199seen on 14,853 paths from 127 vantage points
- Peer of AS174seen on 163,856 paths from 28 vantage points
- Peer of AS6762seen on 255,350 paths from 5 vantage points
- Peer of AS25091seen on 666,530 paths from 2 vantage points
IT
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
- Singapore40136263199174132337This path
- London, UK40136263199174335635280This path
- Sao Paulo40136263199174645335280This path
- Amsterdam401362631991746762250918298Shown above
- Oregon, US4013626319917432572335220130This 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
99%
Seen by 80 of 81 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
- 16th May 2000
- Allocation block
- 64.204.0.0/15
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 64.205.96.0/24 | AS401362 | /24 |
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 |
|---|---|---|---|
| 64.204.0.0/15 | 131k | AS3257GTT Communications Inc. | 80/81 |
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 64.205.96.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.