subnet.im

2804:469c:8000::/33

META-CTi Tecnologia da Informacao LTDA.AS267000

At a glance

Subnets

2,147,483,648 × /64

/33 block

Visibility

98%

62 of 63 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 9th November 2017

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Amsterdam.

OriginVantage point · Amsterdam
One AS path to 2804:469c:8000::/33 as seen from Amsterdam, read outward from the origin: AS267000 → AS396356 → AS262287 → AS52468 → AS25091 → AS8298. Each hop is listed with its network name beneath the graph.AS267000META-CTi Tecnolog…OriginAS396356Latitude.shAS262287Latitude.sh LTDAAS52468UFINET PANAMA S.A.AS25091IP-Max SAAS8298IPng Networks GmbH

Seen from Amsterdam

  1. 1AS267000META-CTi Tecnologia da Informacao LTDA.BROrigin
    Peer of AS267000seen on 212 paths from 137 vantage points
  2. 2AS396356Latitude.shUS
    Peer of AS396356seen on 765 paths from 82 vantage points
  3. 3AS262287Latitude.sh LTDABR
    Peer of AS262287seen on 1,675 paths from 51 vantage points
  4. 4AS52468UFINET PANAMA S.A.PA
    Peer of AS52468seen on 2,094 paths from 5 vantage points
  5. 5AS25091IP-Max SACH
    Peer of AS25091seen on 664,395 paths from 2 vantage points
  6. 6AS8298IPng Networks GmbHCHVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. London, UK267000396356335635280This path
  2. Sao Paulo2670003963561673535280This path
  3. Singapore26700039635633566939132337This path
  4. Amsterdam26700039635626228752468250918298Shown above

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 62 of 63 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
9th November 2017
Allocation block
2804:469c::/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:469c:8000::/33
PrefixAddressesOriginVisibility
2804:469c::/332.1B × /64AS262287Latitude.sh LTDA17/63
2804:469c::/332.1B × /64AS267000META-CTi Tecnologia da Informacao LTDA.45/63

History

  1. AS26700026th October 2026 — present
  2. AS26700012th August 2026 — 24th October 2026
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.