subnet.im

157.10.97.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICID

Allocated 10th January 2024

AS paths to this prefix

All paths

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

OriginVantage point · Oregon, US
One AS path to 157.10.97.0/24 as seen from Oregon, US, read outward from the origin: AS58821 → AS136106 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS58821PT Lintas Jaringa…OriginAS136106PT Mega Akses Per…AS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. Peer of AS58821seen on 133 paths from 65 vantage points
  2. Peer of AS136106seen on 23,561 paths from 100 vantage points
  3. Peer of AS6939seen on 975,334 paths from 1 vantage point
  4. 4AS20130Depaul UniversityUSVantage 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, UK58821643158529This path
  2. Singapore58821136106132337This path
  3. Amsterdam588211361066939213151This path
  4. Sao Paulo588211361063356266213This path
  5. Oregon, US58821136106693920130Shown above

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
10th January 2024
Allocation block
157.10.97.0/24
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 157.10.97.0/24
ROA prefixAuthorised originMax length
157.10.97.0/24AS58821/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 157.10.97.0/24
PrefixAddressesOriginVisibility
157.10.96.0/24256AS146918Cablecom Network Private Limited80/80

History

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

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