SUBNET.IM

59.153.106.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICSG

Allocated 20th October 2015

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 59.153.106.0/24 as seen from Oregon, US, read outward from the origin: AS64049 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS64049Reliance Jio Info…OriginAS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. Peer of AS64049seen on 7,263 paths from 7 vantage points
  2. Peer of AS6939seen on 975,334 paths from 1 vantage point
  3. 3AS20130Depaul 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. Amsterdam6404934549213151This path
  2. London, UK640491374098529This path
  3. Oregon, US64049693920130Shown above
  4. Sao Paulo6404929143356266213This path
  5. Singapore6404929148966132337This 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
Singapore
Allocated
20th October 2015
Allocation block
59.153.104.0/22
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 59.153.106.0/24
ROA prefixAuthorised originMax length
59.153.106.0/24AS64049/24
59.153.104.0/22AS64049/22

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 59.153.106.0/24
PrefixAddressesOriginVisibility
59.153.107.0/24256AS64049Reliance Jio Infocomm Pte. Ltd.80/80

History

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

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