subnet.im

2804:5fbc::/33

Internet FacilAS269120

At a glance

Subnets

2,147,483,648 × /64

/33 block

Visibility

98%

61 of 62 vantage points

RPKI

No ROA

Registry

LACNICBR

Allocated 5th July 2019

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 2804:5fbc::/33 as seen from Singapore, read outward from the origin: AS269120 → AS265290 → AS61832 → AS37468 → AS132337. Each hop is listed with its network name beneath the graph.AS269120Internet FacilOriginAS265290Uplink TelecomAS61832Giga+ EmpresasAS37468Angola CablesAS132337Axclusive

Seen from Singapore

  1. 1AS269120Internet FacilBROrigin
    Peer of AS269120seen on 198 paths from 137 vantage points
  2. 2AS265290Uplink TelecomBR
    Peer of AS265290seen on 4,840 paths from 138 vantage points
  3. 3AS61832Giga+ EmpresasBR
    Peer of AS61832seen on 64,760 paths from 137 vantage points
  4. 4AS37468Angola CablesAO
    Peer of AS37468seen on 4,887 paths from 2 vantage points
  5. 5AS132337AxclusiveSGVantage 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 Paulo2691202652906183232590This path
  2. Singapore2691202652906183237468132337Shown above
  3. London, UK2691202652906183237468900251907This path
  4. Amsterdam2691202652905308713786223566939213151This 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
5th July 2019
Allocation block
2804:5fbc::/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:5fbc::/33
PrefixAddressesOriginVisibility
2804:5fbc:8000::/332.1B × /64AS269120Internet Facil61/62

History

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