SUBNET.IM

2804:40a8:200::/41

R7 TELECOMUNICAÇÕES EIRELI MEAS265973

At a glance

Subnets

8,388,608 × /64

/41 block

Visibility

61%

38 of 62 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 17th July 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: 4 observed paths to 2804:40a8:200::/41, fanning out from AS265973 toward the vantage points that see it. Each path is written out in full beneath the graph.AS265973R7 TELECOMUNICAÇÕ…OriginAS28173Dinamica Telecomu…AS32590Valve CorporationAS1031PEER 1031 LLCAS51907Kanton ZugAS132337AxclusiveAS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. Sao Paulo2659732817332590This path
  2. London, UK26597328173103151907This path
  3. Singapore265973281731031132337This path
  4. Amsterdam26597328173103134549213151This 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

61%

Seen by 38 of 62 full-feed vantage points

Partially propagated

Observed at 4 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
17th July 2017
Allocation block
2804:40a8::/32
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 2804:40a8:200::/41
ROA prefixAuthorised originMax length
2804:40a8::/32AS265973/48

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2804:40a8:200::/41: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2804:40a8::/32AS2659732804:40a8:200::/…AS265973This prefix2804:40a8:280::/…AS265973

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 2804:40a8:200::/41
PrefixAddressesOriginVisibility
2804:40a8::/324.3B × /64AS265973R7 TELECOMUNICAÇÕES EIRELI ME62/62

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 2804:40a8:200::/41
PrefixAddressesOriginVisibility
2804:40a8:280::/418.4M × /64AS265973R7 TELECOMUNICAÇÕES EIRELI ME38/62

History

  1. AS26597312th 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.

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