103.91.146.0/24
At a glance
Addresses
/24 block
Visibility
1 of 76 vantage points
RPKI
Registry
SCAllocated 27th April 2017
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 AS213755seen on 78 paths from 76 vantage points
- Peer of AS30058seen on 22,878 paths from 116 vantage points
- Peer of AS3257seen on 66,143 paths from 17 vantage points
- Peer of AS6762seen on 32,980 paths from 1 vantage point
- Peer of AS1680seen on 35,288 paths from 1 vantage point
GB
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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Seychelles
- Allocated
- 27th April 2017
- Allocation block
- 103.91.146.0/23
- 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.
Covering announcements
No less specific announcement covers this prefix.
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 103.91.146.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.