2804:2f8::/40
At a glance
Subnets
/40 block
Visibility
62 of 62 vantage points
RPKI
Registry
BRAllocated 7th December 2010
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS28188seen on 144 paths from 40 vantage points
- Peer of AS274514seen on 216 paths from 70 vantage points
- Peer of AS262753seen on 2,403 paths from 117 vantage points
- Peer of AS267613seen on 32,165 paths from 107 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
US
DEOne 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 Paulo2818827451426275332590This path
- London, UK281882748394230900251907This path
- Amsterdam2818827451426275326761313786223566939213151Shown above
- Singapore2818827451426275326761313786223566939132337This 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
100%
Seen by 62 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
- 7th December 2010
- Allocation block
- 2804:2f8::/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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2804:2f8:100::/40 | 16.8M × /64 | AS28188Pronto Net Ltda. | 62/62 |
History
- AS2818812th 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.