2804:9968:8000::/33
At a glance
Subnets
/33 block
Visibility
61 of 63 vantage points
RPKI
Registry
BRAllocated 23rd June 2026
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS275777seen on 205 paths from 83 vantage points
- Peer of AS269553seen on 338 paths from 56 vantage points
- Peer of AS28260seen on 8,048 paths from 139 vantage points
- Peer of AS53181seen on 12,761 paths from 130 vantage points
- Peer of AS37468seen on 6,720 paths from 5 vantage points
- Peer of AS25091seen on 663,280 paths from 2 vantage points
AO
CHOne 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
- Sao Paulo27577726955335280This path
- Singapore275777269553282606939132337This path
- London, UK2757772695532826052468335635280This path
- Amsterdam275777269553282605318137468250918298Shown 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
97%
Seen by 61 of 63 full-feed vantage points
Globally propagatedObserved 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
- 23rd June 2026
- Allocation block
- 2804:9968::/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.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2804:9968::/32 | 4.3B × /64 | AS275777AAVG TELECOMUNICACOES LTDA | 61/63 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2804:9968::/33 | 2.1B × /64 | AS275777AAVG TELECOMUNICACOES LTDA | 61/63 |
History
- AS2757774th October 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.