160.25.212.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
IDAllocated 16th July 2024
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS59142seen on 80 paths from 80 vantage points
- Peer of AS139382seen on 109 paths from 80 vantage points
- Peer of AS58553seen on 400 paths from 80 vantage points
- Peer of AS153068seen on 1,217 paths from 67 vantage points
- Peer of AS24534seen on 4,642 paths from 134 vantage points
- Peer of AS174seen on 181,897 paths from 3 vantage points
- Peer of AS34549seen on 716,762 paths from 2 vantage points
US
DEOne 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
- London, UK5914213938258553153068239478529This path
- Singapore591421393825855315306823947132337This path
- Oregon, US5914213938258553153068693920130This path
- Amsterdam59142139382585531530682453417434549213151Shown above
- Sao Paulo5914213938258553153068245341743356266213This 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
100%
Seen by 80 of 80 full-feed vantage points
Globally 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
- APNIC — Asia-Pacific
- Country
- Indonesia
- Allocated
- 16th July 2024
- Allocation block
- 160.25.212.0/24
- 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 |
|---|---|---|
| 160.25.212.0/24 | AS59142 | /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 |
|---|---|---|---|
| 160.25.213.0/24 | 256 | AS153173Information Technology Consultants Limited | 79/80 |
History
- AS5914212th August 2026 — present
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 160.25.212.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.