154.94.12.0/22
AS401322 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/22 block
Visibility
1 of 76 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 Oregon, US.
Seen from Oregon, US
- Peer of AS19318seen on 4,652 paths from 127 vantage points
- Peer of AS3257seen on 66,134 paths from 17 vantage points
- Peer of AS6762seen on 33,086 paths from 1 vantage point
- Peer of AS1680seen on 35,424 paths from 1 vantage point
US
IT
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.
Route visibility
1%
Seen by 1 of 76 full-feed vantage points
Seen by few vantage pointsObserved at 1 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 | 76/76 |
| 154.92.0.0/14 | 262k | AS35916MULTACOM CORPORATION | 76/76 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 154.94.12.0/24 | 256 | AS17561LARUS Limited | 1/76 |
| 154.94.13.0/24 | 256 | AS17561LARUS Limited | 1/76 |
| 154.94.14.0/24 | 256 | AS17561LARUS Limited | 1/76 |
| 154.94.15.0/24 | 256 | AS17561LARUS Limited | 1/76 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 154.94.8.0/22 | 1k | AS11427Charter Communications Inc | 76/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 154.94.12.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.