169.40.58.0/24
At a glance
Addresses
/24 block
Visibility
17 of 76 vantage points
RPKI
Registry
DEAllocated 1st September 1993
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS30042seen on 111 paths from 76 vantage points
- Peer of AS49581seen on 41,823 paths from 126 vantage points
- Adjacentseen on 4 paths from 1 vantage point
- Peer of AS45899seen on 1,857 paths from 2 vantage points
- Peer of AS55329seen on 11,345 paths from 2 vantage points
US
NL
VN
KHOne 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
- Amsterdam40309321463939208298This path
- London, UK40309321463939208529This path
- Sao Paulo403093214639392035280This path
- Singapore300424958144592458995532923673Shown 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
22%
Seen by 17 of 76 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Germany
- Allocated
- 1st September 1993
- Allocation block
- 169.40.32.0/19
- Status
- assigned
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 169.40.58.0/24 | AS403093 | /24 |
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 169.40.59.0/24 | 256 | AS218515Shenfeng Chen | 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 169.40.58.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.