subnet.im

103.151.83.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICAU

Allocated 13th May 2020

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 103.151.83.0/24 as seen from Oregon, US, read outward from the origin: AS140643 → AS9507 → AS7474 → AS7473 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS140643NetbrightOriginAS9507NextHop Pty LtdAS7474SingTel Optus Pty…AS7473Singapore Telecom…AS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. Peer of AS140643seen on 130 paths from 76 vantage points
  2. Peer of AS9507seen on 11,195 paths from 92 vantage points
  3. Peer of AS7474seen on 90,136 paths from 136 vantage points
  4. Peer of AS7473seen on 38,994 paths from 66 vantage points
  5. Peer of AS6939seen on 975,334 paths from 1 vantage point
  6. 6AS20130Depaul 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. Singapore14064338195132337This path
  2. London, UK1406439507122146378529This path
  3. Sao Paulo1406439507122146373356266213This path
  4. Oregon, US140643950774747473693920130Shown above
  5. Amsterdam140643950774747473646134549213151This 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
Australia
Allocated
13th May 2020
Allocation block
103.151.83.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 103.151.83.0/24
ROA prefixAuthorised originMax length
103.151.83.0/24AS140643/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. AS14064312th 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 103.151.83.0/24 in the calculator/24 reference

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