154.94.12.0/22
At a glance
Addresses
/22 block
Visibility
18 of 77 vantage points
RPKI
Registry
SCAllocated 24th July 2013
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS401650seen on 2,529 paths from 76 vantage points
- Peer of AS62610seen on 52,850 paths from 139 vantage points
- Peer of AS29752seen on 22,510 paths from 126 vantage points
- Peer of AS4229seen on 18 paths from 18 vantage points
- Peer of AS20326seen on 759 paths from 6 vantage points
US
FROne 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
- Oregon, US1931832576762168042013This path
- Amsterdam40165062610297524229203268298This path
- Sao Paulo401650626102975242292032635280Shown above
- London, UK401650626102975242292032669398529This 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
23%
Seen by 18 of 77 full-feed vantage points
Seen by few vantage pointsObserved 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
- AFRINIC — Africa
- Country
- Seychelles
- Allocated
- 24th July 2013
- Allocation block
- 154.80.0.0/12
- 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.94.0.0/17 | 32.8k | AS35916MULTACOM CORPORATION | 77/77 |
| 154.92.0.0/14 | 262k | AS35916MULTACOM CORPORATION | 77/77 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 154.94.12.0/24 | 256 | AS17561LARUS Limited | 1/77 |
| 154.94.13.0/24 | 256 | AS17561LARUS Limited | 1/77 |
| 154.94.14.0/24 | 256 | AS401650888 Ventures LLC | 56/77 |
| 154.94.15.0/24 | 256 | AS401650888 Ventures LLC | 56/77 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 154.94.8.0/22 | 1k | AS11427Charter Communications Inc | 77/77 |
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 154.94.12.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.