SUBNET.IM

186.211.136.0/21

At a glance

Addresses

2,048

/21 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 17th June 2010

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 186.211.136.0/21 as seen from Amsterdam, read outward from the origin: AS14840 → AS213151. Each hop is listed with its network name beneath the graph.AS14840BR.DIGITALOriginAS213151Christian Elsen

Seen from Amsterdam

  1. Peer of AS14840seen on 5,199 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. Amsterdam14840213151Shown above
  2. London, UK148408529This path
  3. Sao Paulo14840266213This path
  4. Singapore14840132337This path
  5. Oregon, US14840693920130This 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

99%

Seen by 79 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
LACNIC — Latin America and the Caribbean
Country
Brazil
Allocated
17th June 2010
Allocation block
186.211.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 186.211.136.0/21
ROA prefixAuthorised originMax length
186.211.128.0/17AS14840/32

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 186.211.136.0/21
PrefixAddressesOriginVisibility
186.211.128.0/212kAS14840BR.DIGITAL 79/80

History

  1. AS1484012th 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 186.211.136.0/21 in the calculator/21 reference

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