SUBNET.IM

202.186.0.0/15

At a glance

Addresses

131,072

/15 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

APNICMY

Allocated 29th October 1996

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 202.186.0.0/15 as seen from Amsterdam, read outward from the origin: AS9930 → AS213151. Each hop is listed with its network name beneath the graph.AS9930TIME dotCom BhdOriginAS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS9930seen on 364 paths from 2 vantage points
  2. 2AS213151Christian 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. Amsterdam9930213151Shown above
  2. London, UK99308529This path
  3. Singapore9930132337This path
  4. Oregon, US9930693920130This path
  5. Sao Paulo993029143356266213This 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
Malaysia
Allocated
29th October 1996
Allocation block
202.186.0.0/15
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 202.186.0.0/15
ROA prefixAuthorised originMax length
202.186.0.0/15AS9930/15

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 202.186.0.0/15
PrefixAddressesOriginVisibility
202.184.0.0/15131kAS9930TIME dotCom Bhd80/80

History

  1. AS993012th 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 202.186.0.0/15 in the calculator/15 reference

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