2804:12fc:c000::/36
At a glance
Subnets
/36 block
Visibility
61 of 63 vantage points
RPKI
Registry
BRAllocated 30th December 2013
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS263508seen on 300 paths from 137 vantage points
- Peer of AS266181seen on 4,811 paths from 95 vantage points
- Peer of AS28283seen on 20,012 paths from 58 vantage points
- Peer of AS8167seen on 102,372 paths from 138 vantage points
- Peer of AS52320seen on 187,368 paths from 82 vantage points
- Peer of AS6461seen on 238,363 paths from 7 vantage points
CO
USOne 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 Paulo26350826618135280This path
- London, UK263508266181335635280This path
- Singapore263508266181264963615686939132337This path
- Amsterdam26350826618128283816752320646132590Shown 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
- 30th December 2013
- Allocation block
- 2804:12fc::/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:12fc:d000::/36 | 268M × /64 | AS263508SIMNET TELECOMUNICACOES LTDA | 62/63 |
History
- AS26350812th 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.