2804:4bb8:8000::/33
At a glance
Subnets
/33 block
Visibility
60 of 62 vantage points
RPKI
Registry
Allocated 27th March 2018
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS267326seen on 726 paths from 138 vantage points
- Peer of AS265038seen on 2,947 paths from 131 vantage points
- Peer of AS61832seen on 28,505 paths from 135 vantage points
- Peer of AS13786seen on 151,942 paths from 82 vantage points
- Peer of AS22356seen on 79,498 paths from 65 vantage points
- Peer of AS6939seen on 309,709 paths from 2 vantage points
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
- Sao Paulo26732626503832590This path
- Singapore26732626503837468132337This path
- London, UK26732626503837468900251907This path
- Amsterdam2673262650386183213786223566939213151Shown 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 60 of 62 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
- 27th March 2018
- Allocation block
- 2804:4bb8::/32
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 2804:4bb8::/32 | AS267326 | /48 |
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:4bb8::/32 | 4.3B × /64 | AS267326MICROLINK INFORMATICA COMERCIO E SERVICOS LTDA ME | 60/62 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2804:4bb8::/33 | 2.1B × /64 | AS267326MICROLINK INFORMATICA COMERCIO E SERVICOS LTDA ME | 60/62 |
History
- AS26732612th 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.