subnet.im

160.25.162.0/23

At a glance

Addresses

512

/23 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICID

Allocated 11th July 2024

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 160.25.162.0/23, fanning out from AS149662 toward the vantage points that see it. Each path is written out in full beneath the graph.AS149662PT Hostnet Data G…OriginAS45147PT NAP Info Linta…AS6939Hurricane Electri…AS213151Christian ElsenAS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS55818Matrix Cable Inte…AS132337AxclusiveAS20130Depaul University
  1. Amsterdam149662451476939213151This path
  2. London, UK1496624514712998529This path
  3. Sao Paulo149662451476939266213This path
  4. Singapore1496624514755818132337This path
  5. Oregon, US14966245147693920130This 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 propagated

Observed 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
11th July 2024
Allocation block
160.25.162.0/23
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 160.25.162.0/23
ROA prefixAuthorised originMax length
160.25.162.0/23AS149662/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 160.25.162.0/23: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.160.25.162.0/23AS149662This prefix160.25.162.0/24AS149662160.25.163.0/24AS149662

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 160.25.162.0/23
PrefixAddressesOriginVisibility
160.25.162.0/24256AS149662PT Hostnet Data Global80/80
160.25.163.0/24256AS149662PT Hostnet Data Global80/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 160.25.162.0/23
PrefixAddressesOriginVisibility
160.25.160.0/23512AS153160C2A Internet Pty Ltd80/80

History

  1. AS14966212th 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.162.0/23 in the calculator/23 reference

Routing data derived from RouteViews MRT archives and public registry data.