SUBNET.IM

2804:56cc:c000::/40

OK NET INFOR LTDAAS268037

TURBONET CAXIASAS268024

Announced by more than one origin AS (MOAS).

At a glance

Subnets

16,777,216 × /64

/40 block

Visibility

92%

57 of 62 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 28th November 2018

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:56cc:c000::/40, fanning out from AS268024, AS268037 toward the vantage points that see it. Each path is written out in full beneath the graph.AS268024TURBONET CAXIASOriginAS268037OK NET INFOR LTDAAS52995TEN INTERNET LtdaAS32590Valve CorporationAS268037OK NET INFOR LTDAOriginAS263880WANTEL TECNOLOGIA…AS61568ALOO TELECOM - FS…AS6939Hurricane Electri…AS213151Christian ElsenAS51907Kanton ZugAS132337Axclusive
  1. Sao Paulo2680242680375299532590This path
  2. Amsterdam268037263880615686939213151This path
  3. London, UK26803726388061568693951907This path
  4. Singapore268037263880615686939132337This 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

92%

Seen by 57 of 62 full-feed vantage points

Globally propagated

Observed at 3 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 November 2018
Allocation block
2804:56cc::/32
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.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS26802412th August 2026 — present
  2. AS26803712th 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.