172.93.131.0/24
At a glance
Addresses
/24 block
Visibility
67 of 76 vantage points
RPKI
Registry
USAllocated 1st June 2015
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS27176seen on 4,427 paths from 138 vantage points
- Peer of AS20278seen on 8,079 paths from 133 vantage points
- Peer of AS174seen on 178,349 paths from 22 vantage points
- Peer of AS6762seen on 251,398 paths from 5 vantage points
- Peer of AS25091seen on 663,280 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
- London, UK2027869398529This path
- Singapore2027869393862323673This path
- Sao Paulo2717620278174645335280This path
- Oregon, US2717620278174855142013This path
- Amsterdam27176202781746762250918298Shown 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
88%
Seen by 67 of 76 full-feed vantage points
Partially 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
- 1st June 2015
- Allocation block
- 172.93.128.0/17
- 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 |
|---|---|---|---|
| 172.93.128.0/17 | 32.8k | AS20278Nexeon Technologies, Inc. | 76/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 172.93.130.0/24 | 256 | AS20278Nexeon Technologies, Inc. | 34/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 172.93.131.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.