2804:238c::/36
At a glance
Subnets
/36 block
Visibility
47 of 62 vantage points
RPKI
Registry
BRAllocated 23rd March 2015
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS264169seen on 1,243 paths from 140 vantage points
- Peer of AS266445seen on 8,195 paths from 142 vantage points
- Peer of AS7738seen on 121,785 paths from 141 vantage points
- Peer of AS52320seen on 12,702 paths from 89 vantage points
- Peer of AS12956seen on 108,862 paths from 43 vantage points
- Peer of AS6453seen on 82,525 paths from 3 vantage points
- Peer of AS34549seen on 716,762 paths from 2 vantage points
CO
ES
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
- London, UK26416926644577385232051907This path
- Amsterdam26416926644577385232012956645334549213151Shown above
- Singapore2641692664457738523201295664534229132337This 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
76%
Seen by 47 of 62 full-feed vantage points
Partially 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
- 23rd March 2015
- Allocation block
- 2804:238c::/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:238c::/32 | AS264169 | /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
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2804:238c:100::/40 | 16.8M × /64 | AS264169WNP INTERNET | 47/62 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2804:238c:1000::/36 | 268M × /64 | AS264169WNP INTERNET | 61/62 |
History
- AS26416912th 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.