154.7.2.0/24
At a glance
Addresses
/24 block
Visibility
79 of 80 vantage points
RPKI
Registry
USAllocated 5th February 1992
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS204902seen on 535 paths from 140 vantage points
- Peer of AS202753seen on 397 paths from 91 vantage points
- Peer of AS52025seen on 807 paths from 71 vantage points
- Peer of AS64289seen on 1,519 paths from 67 vantage points
- Peer of AS214565seen on 1,519 paths from 67 vantage points
- Peer of AS6461seen on 62,575 paths from 3 vantage points
- Peer of AS34549seen on 716,762 paths from 2 vantage points
FR
GB
DEOne 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, UK20490220275339417712998529This path
- Sao Paulo2049022027533941773356266213This path
- Singapore204902202753520251299132337This path
- Oregon, US204902202753394177693920130This path
- Amsterdam2049022027535202564289214565646134549213151Shown 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
99%
Seen by 79 of 80 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
- 5th February 1992
- Allocation block
- 154.7.0.0/16
- 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.
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 |
|---|---|---|---|
| 154.7.0.0/22 | 1k | AS204902XIWO CLOUD SAS | 79/80 |
| 154.7.0.0/16 | 65.5k | AS174Cogent Communications, LLC | 79/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 154.7.3.0/24 | 256 | AS204902XIWO CLOUD SAS | 79/80 |
History
- AS20490212th August 2026 — present
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 154.7.2.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.