subnet.im

151.158.42.0/23

At a glance

Addresses

512

/23 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

APNICID

Allocated 18th January 2026

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 151.158.42.0/23 as seen from Singapore, read outward from the origin: AS154495 → AS24534 → AS63516 → AS132337. Each hop is listed with its network name beneath the graph.AS154495PT Sterlink Perma…OriginAS24534PT Trans Hybrid C…AS63516Transhybrid Inter…AS132337Axclusive

Seen from Singapore

  1. Peer of AS154495seen on 79 paths from 79 vantage points
  2. Peer of AS24534seen on 2,550 paths from 56 vantage points
  3. Peer of AS63516seen on 100 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage point

One 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

  1. London, UK1544952453464538529This path
  2. Singapore1544952453463516132337Shown above
  3. Amsterdam15449524534645334549213151This path
  4. Sao Paulo1544952453464533356266213This path
  5. Oregon, US154495245346453693920130This 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 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
18th January 2026
Allocation block
151.158.42.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

Route Origin Authorisations covering 151.158.42.0/23
ROA prefixAuthorised originMax length
151.158.42.0/23AS154495/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

No prefix of the same length in the same parent block is announced.

History

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

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