SUBNET.IM

201.77.158.0/23

Sergio Barrios Noviaky MEAS270302

At a glance

Addresses

512

/23 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 31st January 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.77.158.0/23, fanning out from AS270302 toward the vantage points that see it. Each path is written out in full beneath the graph.AS270302Sergio Barrios No…OriginAS52688TELENET TELECOMUN…AS271253LINK BRASIL TELEC…AS266213PLANETCLICK TELEC…AS1031PEER 1031 LLCAS132337AxclusiveAS6453TATA Communicatio…AS8529Zain Omantel Inte…AS34549meerfarbig GmbH &…AS213151Christian ElsenAS3356Lumen (Level 3)AS6939Hurricane Electri…AS20130Depaul University
  1. Sao Paulo27030252688271253266213This path
  2. Singapore270302526881031132337This path
  3. London, UK2703025268827125364538529This path
  4. Amsterdam27030252688271253645334549213151This path
  5. Oregon, US270302526882712533356693920130This 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
Brazil
Allocated
31st January 2020
Allocation block
201.77.156.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.77.158.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.201.77.156.0/22AS270302201.77.158.0/23AS270302This prefix201.77.156.0/23AS270302201.77.158.0/24AS270302201.77.159.0/24AS270302

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 201.77.158.0/23
PrefixAddressesOriginVisibility
201.77.156.0/221kAS270302Sergio Barrios Noviaky ME80/80

More specific announcements

Announcements contained within 201.77.158.0/23
PrefixAddressesOriginVisibility
201.77.158.0/24256AS270302Sergio Barrios Noviaky ME80/80
201.77.159.0/24256AS270302Sergio Barrios Noviaky ME80/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 201.77.158.0/23
PrefixAddressesOriginVisibility
201.77.156.0/23512AS270302Sergio Barrios Noviaky ME80/80

History

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

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