160.25.67.0/24
At a glance
Addresses
/24 block
Visibility
79 of 80 vantage points
RPKI
Registry
AUAllocated 2nd July 2024
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS153049seen on 79 paths from 79 vantage points
- Peer of AS9738seen on 9,241 paths from 102 vantage points
- Peer of AS17898seen on 7,797 paths from 79 vantage points
- Peer of AS7474seen on 90,136 paths from 136 vantage points
- Peer of AS7473seen on 1,188 paths from 3 vantage points
- Peer of AS4229seen on 13,937 paths from 2 vantage points
SG
USOne 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, UK1530499738178987474747364618529This path
- Singapore153049973817898747474734229132337Shown above
- Oregon, US15304997381789874747473693920130This path
- Amsterdam15304997381789874747473646134549213151This path
- Sao Paulo1530499738178987474747364613356266213This 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
99%
Seen by 79 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
- Australia
- Allocated
- 2nd July 2024
- Allocation block
- 160.25.66.0/23
- 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.66.0/23 | AS153049 | /24 |
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 |
|---|---|---|---|
| 160.25.66.0/23 | 512 | AS153049Scope Aust Ltd | 79/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 160.25.66.0/24 | 256 | AS153049Scope Aust Ltd | 79/80 |
History
- AS15304912th 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.67.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.