subnet.im

151.158.49.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICBD

Allocated 19th January 2026

AS paths to this prefix

All paths

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

OriginVantage point · Amsterdam
One AS path to 151.158.49.0/24 as seen from Amsterdam, read outward from the origin: AS131192 → AS151967 → AS137425 → AS58945 → AS6939 → AS213151. Each hop is listed with its network name beneath the graph.AS131192BD WEBS DOT COMOriginAS151967DLITSAS137425INCOMIT SOLUTIONAS58945Virgo Communicati…AS6939Hurricane Electri…AS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS131192seen on 160 paths from 80 vantage points
  2. Peer of AS151967seen on 130 paths from 80 vantage points
  3. Peer of AS137425seen on 444 paths from 140 vantage points
  4. Peer of AS58945seen on 5,577 paths from 127 vantage points
  5. Peer of AS6939seen on 309,709 paths from 2 vantage points
  6. 6AS213151Christian ElsenDEVantage 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. Singapore13119215196713742510075132337This path
  2. Amsterdam131192151967137425589456939213151Shown above
  3. London, UK1311921519671374255871764538529This path
  4. Sao Paulo131192151967137425100759498266213This path
  5. Oregon, US13119215196713742558945693920130This 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
Bangladesh
Allocated
19th January 2026
Allocation block
151.158.48.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.49.0/24
ROA prefixAuthorised originMax length
151.158.48.0/23AS131192/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

Prefixes of the same length sharing a parent block with 151.158.49.0/24
PrefixAddressesOriginVisibility
151.158.48.0/24256AS131192BD WEBS DOT COM80/80

History

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

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