subnet.im

61.15.236.0/24

At a glance

Addresses

256

/24 block

Visibility

73%

57 of 78 vantage points

RPKI

Valid

Registry

APNICHK

Allocated 7th September 2001

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 61.15.236.0/24 as seen from Amsterdam, read outward from the origin: AS56683 → AS15830 → AS4637 → AS6762 → AS25091 → AS8298. Each hop is listed with its network name beneath the graph.AS56683EXNESS LIMITEDOriginAS15830Equinix, Inc.AS4637Telstra Internati…AS6762Telecom Italia Sp…AS25091IP-Max SAAS8298IPng Networks GmbH

Seen from Amsterdam

  1. Peer of AS56683seen on 129 paths from 74 vantage points
  2. Peer of AS15830seen on 9,758 paths from 127 vantage points
  3. Peer of AS4637seen on 18,987 paths from 21 vantage points
  4. Peer of AS6762seen on 250,457 paths from 5 vantage points
  5. Peer of AS25091seen on 663,434 paths from 2 vantage points
  6. 6AS8298IPng Networks GmbHCHVantage 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, UK566831583046378529This path
  2. Sao Paulo5668315830463735280This path
  3. Oregon, US56683158304637855142013This path
  4. Amsterdam566831583046376762250918298Shown 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

73%

Seen by 57 of 78 full-feed vantage points

Partially propagated

Observed at 4 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
Hong Kong SAR China
Allocated
7th September 2001
Allocation block
61.15.128.0/17
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 61.15.236.0/24
ROA prefixAuthorised originMax length
61.15.236.0/24AS56683/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 61.15.236.0/24
PrefixAddressesOriginVisibility
61.15.237.0/24256AS9304HGC Global Communications Limited78/78

History

  1. AS566837th November 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 61.15.236.0/24 in the calculator/24 reference

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