subnet.im

151.158.136.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICMM

Allocated 4th February 2026

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 151.158.136.0/24 as seen from London, UK, read outward from the origin: AS151965 → AS136255 → AS4229 → AS6453 → AS8529. Each hop is listed with its network name beneath the graph.AS151965Hepta Alliance Te…OriginAS136255Mytel MyanmarAS4229Zenlayer IncAS6453TATA Communicatio…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS151965seen on 112 paths from 50 vantage points
  2. Peer of AS136255seen on 6,222 paths from 107 vantage points
  3. Peer of AS4229seen on 49,534 paths from 109 vantage points
  4. Peer of AS6453seen on 89,408 paths from 35 vantage points

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. Singapore1519651362554229132337This path
  2. London, UK151965136255422964538529Shown above
  3. Amsterdam1519651335241369751375576939213151This path
  4. Sao Paulo1519651335241369751375576939266213This path
  5. Oregon, US151965133524136975137557693920130This 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
Myanmar (Burma)
Allocated
4th February 2026
Allocation block
151.158.136.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.136.0/24
ROA prefixAuthorised originMax length
151.158.136.0/24AS151965/24
151.158.136.0/23AS151965/23

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

Prefixes of the same length sharing a parent block with 151.158.136.0/24
PrefixAddressesOriginVisibility
151.158.137.0/24256AS151965Hepta Alliance Technology Group80/80

History

  1. AS15196512th 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.136.0/24 in the calculator/24 reference

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