SUBNET.IM

2804:565c::/33

ALPHA FIBRA SERVICOS DE COMUNICACAO MULTIMIDIA SCMAS267993

At a glance

Subnets

2,147,483,648 × /64

/33 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 21st November 2018

AS paths to this prefix

All paths

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

OriginVantage point · London, UK
One AS path to 2804:565c::/33 as seen from London, UK, read outward from the origin: AS267993 → AS11432 → AS174 → AS15576 → AS51907. Each hop is listed with its network name beneath the graph.AS267993ALPHA FIBRA SERVI…OriginAS11432Telium Telecomuni…AS174Cogent Communicat…AS15576NTS workspace AGAS51907Kanton Zug

Seen from London, UK

  1. 1AS267993ALPHA FIBRA SERVICOS DE COMUNICACAO MULTIMIDIA SCMBROrigin
    Peer of AS267993seen on 427 paths from 127 vantage points
  2. 2AS11432Telium Telecomunicações LtdaBR
    Peer of AS11432seen on 8,707 paths from 103 vantage points
  3. 3AS174Cogent Communications, LLCUS
    Peer of AS174seen on 147,033 paths from 3 vantage points
  4. 4AS15576NTS workspace AGCH
    Peer of AS15576seen on 442,038 paths from 2 vantage points
  5. 5AS51907Kanton ZugCHVantage 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. Sao Paulo26799332590This path
  2. Singapore2679936939132337This path
  3. Amsterdam267993114327195213151This path
  4. London, UK267993114321741557651907Shown 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 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
21st November 2018
Allocation block
2804:565c::/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.

CoveringMore specific
Prefix hierarchy for 2804:565c::/33: 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:565c::/33AS267993This prefix2804:565c:7ffe::…AS267993

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 2804:565c::/33
PrefixAddressesOriginVisibility
2804:565c:7ffe::/4865.5k × /64AS267993ALPHA FIBRA SERVICOS DE COMUNICACAO MULTIMIDIA SCM61/62

Sibling prefixes

Prefixes of the same length sharing a parent block with 2804:565c::/33
PrefixAddressesOriginVisibility
2804:565c:8000::/332.1B × /64AS267993ALPHA FIBRA SERVICOS DE COMUNICACAO MULTIMIDIA SCM61/62

History

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