2801:94::/32
At a glance
Subnets
/32 block
Visibility
24 of 62 vantage points
RPKI
Registry
BRAllocated 31st January 2011
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS52958seen on 52 paths from 38 vantage points
- Peer of AS273490seen on 105 paths from 27 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 Paulo5295827349032590This path
- Amsterdam529582734906939213151Shown above
- Singapore529582734906939132337This path
- London, UK529582734906939419133428851907This 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
39%
Seen by 24 of 62 full-feed vantage points
Seen by few vantage pointsObserved 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 January 2011
- Allocation block
- 2801:94::/32
- Status
- assigned
- 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 |
|---|---|---|---|
| 2801:94::/48 | 65.5k × /64 | AS52958Empr.Tec.Inform.Comun. Mun.SP-PRODAM-SP S/A | 61/62 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS5295812th 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.