SUBNET.IM

201.71.56.0/22

Jds Telecomunicação MeAS270763

At a glance

Addresses

1,024

/22 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 29th May 2020

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: 5 observed paths to 201.71.56.0/22, fanning out from AS270763 toward the vantage points that see it. Each path is written out in full beneath the graph.AS270763Jds Telecomunicaç…OriginAS11432Telium Telecomuni…AS266213PLANETCLICK TELEC…AS132337AxclusiveAS137409GSL Networks Pty …AS8529Zain Omantel Inte…AS52320V.tal (GlobeNet)AS6939Hurricane Electri…AS213151Christian ElsenAS20130Depaul University
  1. Sao Paulo27076311432266213This path
  2. Singapore27076311432132337This path
  3. London, UK270763114321374098529This path
  4. Amsterdam27076311432523206939213151This path
  5. Oregon, US2707631143252320693920130This 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
29th May 2020
Allocation block
201.71.56.0/22
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 201.71.56.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.201.71.56.0/22AS270763This prefix201.71.56.0/23AS270763201.71.58.0/23AS270763201.71.56.0/24AS270763201.71.57.0/24AS270763201.71.58.0/24AS270763+1 more

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

No less specific announcement covers this prefix.

Sibling prefixes

Prefixes of the same length sharing a parent block with 201.71.56.0/22
PrefixAddressesOriginVisibility
201.71.60.0/221kAS263073DTEL TELECOM80/80

History

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

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