2804:80bc::/32
At a glance
Subnets
/32 block
Visibility
60 of 62 vantage points
RPKI
Registry
BRAllocated 31st May 2021
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS271770seen on 367 paths from 123 vantage points
- Peer of AS28598seen on 9,372 paths from 140 vantage points
- Peer of AS61832seen on 3,708 paths from 142 vantage points
- Peer of AS264409seen on 14,035 paths from 134 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 320,794 paths from 2 vantage points
US
SGOne 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
- London, UK271770266156762900251907This path
- Sao Paulo271770285986183226440932590This path
- Amsterdam271770285986183226440913786223566939213151This path
- Singapore271770285986183226440913786223566939132337Shown 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
- 31st May 2021
- Allocation block
- 2804:80bc::/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
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2804:80bc::/33 | 2.1B × /64 | AS271770PINGUIM TELECOM E TECNOLOGIA EIRELI | 60/62 |
| 2804:80bc:8000::/33 | 2.1B × /64 | AS271770PINGUIM TELECOM E TECNOLOGIA EIRELI | 60/62 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS27177012th 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.