subnet.im

128.201.212.0/23

VLZ TECNOLOGIAS EIRELIAS265902

At a glance

Addresses

512

/23 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 28th June 2017

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 128.201.212.0/23, fanning out from AS265902 toward the vantage points that see it. Each path is written out in full beneath the graph.AS265902VLZ TECNOLOGIAS E…OriginAS14840BR.DIGITALAS213151Christian ElsenAS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul University
  1. Amsterdam26590214840213151This path
  2. London, UK265902148408529This path
  3. Sao Paulo26590214840266213This path
  4. Singapore26590214840132337This path
  5. Oregon, US26590214840693920130This 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
28th June 2017
Allocation block
128.201.212.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 128.201.212.0/23: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.128.201.212.0/22AS265902128.201.212.0/23AS265902This prefix128.201.214.0/23AS265902

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 128.201.212.0/23
PrefixAddressesOriginVisibility
128.201.212.0/221kAS265902VLZ TECNOLOGIAS EIRELI79/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 128.201.212.0/23
PrefixAddressesOriginVisibility
128.201.214.0/23512AS265902VLZ TECNOLOGIAS EIRELI79/80

History

  1. AS26590212th 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 128.201.212.0/23 in the calculator/23 reference

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