subnet.im

45.180.35.0/24

AD TELECOMAS265080

RCS NET PROVEDOR DE INTERNETAS269162

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

13%

10 of 80 vantage points

RPKI

Invalid

Registry

LACNICBR

Allocated 23rd July 2019

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 45.180.35.0/24, fanning out from AS269162 toward the vantage points that see it. Each path is written out in full beneath the graph.AS269162RCS NET PROVEDOR …OriginAS265080AD TELECOMAS262355VSX NetworksAS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS132337AxclusiveAS20130Depaul UniversityAS58299Openfactory GmbH …AS41051Freetransit Proje…AS213151Christian Elsen
  1. Sao Paulo269162265080262355266213This path
  2. Singapore2691622650806939132337This path
  3. Oregon, US269162265080693920130This path
  4. Amsterdam26916226508069395829941051213151This 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

13%

Seen by 10 of 80 full-feed vantage points

Seen by few vantage points

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
23rd July 2019
Allocation block
45.180.32.0/22
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 45.180.35.0/24
ROA prefixAuthorised originMax length
45.180.32.0/22AS269162/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 45.180.35.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.45.180.34.0/23AS26916245.180.32.0/22AS26916245.180.35.0/24AS265080This prefix45.180.34.0/24AS269162

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 45.180.35.0/24
PrefixAddressesOriginVisibility
45.180.34.0/23512AS269162RCS NET PROVEDOR DE INTERNET80/80
45.180.32.0/221kAS269162RCS NET PROVEDOR DE INTERNET80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 45.180.35.0/24
PrefixAddressesOriginVisibility
45.180.34.0/24256AS269162RCS NET PROVEDOR DE INTERNET80/80

History

  1. AS26916212th August 2026 — present
  2. AS26508012th 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 45.180.35.0/24 in the calculator/24 reference

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