SUBNET.IM

200.71.92.0/22

At a glance

Addresses

1,024

/22 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

LACNICAR

Allocated 11th September 2008

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.

  1. London, UK27996229271295612998529This path
  2. Sao Paulo2799622927129563356266213This path
  3. Singapore2799622927129566939132337This path
  4. Oregon, US279962292712956693920130This path
  5. Amsterdam279962292712956291434549213151This 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
LACNIC — Latin America and the Caribbean
Country
Argentina
Allocated
11th September 2008
Allocation block
200.71.88.0/21
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 200.71.92.0/22
ROA prefixAuthorised originMax length
200.71.88.0/21AS27996/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 200.71.92.0/22: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.200.71.88.0/21AS27996200.71.92.0/22AS27996This prefix200.71.88.0/22AS27996200.71.92.0/24AS27996200.71.93.0/24AS27996200.71.94.0/24AS27996200.71.95.0/24AS27996

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 200.71.92.0/22
PrefixAddressesOriginVisibility
200.71.88.0/212kAS27996Cooperativa Electrica de Colon (BA) LTDA80/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 200.71.92.0/22
PrefixAddressesOriginVisibility
200.71.88.0/221kAS27996Cooperativa Electrica de Colon (BA) LTDA80/80

History

  1. AS2799612th 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 200.71.92.0/22 in the calculator/22 reference

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