subnet.im

190.186.176.0/20

COTAS LTDA.AS25620

At a glance

Addresses

4,096

/20 block

Visibility

72%

55 of 76 vantage points

RPKI

Valid

Registry

LACNICBO

Allocated 17th April 2009

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 4 observed paths to 190.186.176.0/20, fanning out from AS25620 toward the vantage points that see it. Each path is written out in full beneath the graph.AS25620COTAS LTDA.OriginAS12956Telxius (Telefoni…AS35280F5 Networks SARLAS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…AS6762Telecom Italia Sp…AS25091IP-Max SAAS8298IPng Networks GmbHAS8551Bezeq Internation…AS42013Together Communic…
  1. Sao Paulo256201295635280This path
  2. London, UK256201295612998529This path
  3. Amsterdam25620129566762250918298This path
  4. Oregon, US25620129561299855142013This 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

72%

Seen by 55 of 76 full-feed vantage points

Partially 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
Bolivia
Allocated
17th April 2009
Allocation block
190.186.128.0/18
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 190.186.176.0/20
ROA prefixAuthorised originMax length
190.186.0.0/16AS25620/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 190.186.176.0/20: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.190.186.160.0/19AS25620190.186.128.0/17AS25620190.186.176.0/20AS25620This prefix190.186.160.0/20AS25620190.186.189.0/24AS25620

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 190.186.176.0/20
PrefixAddressesOriginVisibility
190.186.160.0/198.2kAS25620COTAS LTDA.75/76
190.186.128.0/1732.8kAS25620COTAS LTDA.75/76

More specific announcements

Announcements contained within 190.186.176.0/20
PrefixAddressesOriginVisibility
190.186.189.0/24256AS25620COTAS LTDA.75/76

Sibling prefixes

Prefixes of the same length sharing a parent block with 190.186.176.0/20
PrefixAddressesOriginVisibility
190.186.160.0/204.1kAS25620COTAS LTDA.55/76

History

  1. AS2562031st October 2026 — present
  2. AS2562031st October 2026 — 31st October 2026
  3. AS2562030th October 2026 — 30th October 2026
  4. AS2562029th October 2026 — 29th October 2026
  5. AS2562020th October 2026 — 27th October 2026
  6. AS2562018th October 2026 — 19th October 2026
  7. AS2562024th September 2026 — 17th October 2026
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 190.186.176.0/20 in the calculator/20 reference

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