158.105.167.0/24
At a glance
Addresses
/24 block
Visibility
65 of 80 vantage points
RPKI
Registry
SEAllocated 25th February 1992
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS57208seen on 2,629 paths from 142 vantage points
- Peer of AS58343seen on 2,856 paths from 142 vantage points
- Peer of AS57208seen on 1,447 paths from 94 vantage points
- Peer of AS1257seen on 5,149 paths from 31 vantage points
- Peer of AS174seen on 74,525 paths from 2 vantage points
EU
US
SGOne 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, US5834357208693920130This path
- Amsterdam572085834357208129934549213151This path
- London, UK572085834357208125764538529This path
- Sao Paulo57208583435720812993356266213This path
- Singapore5720858343572081257174132337Shown 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
81%
Seen by 65 of 80 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Sweden
- Allocated
- 25th February 1992
- Allocation block
- 158.105.0.0/16
- Status
- assigned
- 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 158.105.167.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.