SUBNET.IM

2804:6334:8000::/33

SPACY NETAS269345

At a glance

Subnets

2,147,483,648 × /64

/33 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 17th September 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 2804:6334:8000::/33, fanning out from AS269345 toward the vantage points that see it. Each path is written out in full beneath the graph.AS269345SPACY NETOriginAS262476BRCENTRAL TELECOMAS32590Valve CorporationAS14840BR.DIGITALAS213151Christian ElsenAS51907Kanton ZugAS132337Axclusive
  1. Sao Paulo26934526247632590This path
  2. Amsterdam26934526247614840213151This path
  3. London, UK2693452624761484051907This path
  4. Singapore26934526247614840132337This 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

98%

Seen by 61 of 62 full-feed vantage points

Globally 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 September 2019
Allocation block
2804:6334::/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

Prefixes of the same length sharing a parent block with 2804:6334:8000::/33
PrefixAddressesOriginVisibility
2804:6334::/332.1B × /64AS269345SPACY NET61/62

History

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