2a04:5200::/32
At a glance
Subnets
/32 block
Visibility
60 of 62 vantage points
RPKI
Registry
VGAllocated 23rd July 2013
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS50113seen on 2,841 paths from 127 vantage points
- Peer of AS35598seen on 8,340 paths from 130 vantage points
- Peer of AS20485seen on 4,730 paths from 2 vantage points
GB
RU
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 Paulo50113693932590This path
- Amsterdam501133559820485213151Shown above
- London, UK50113355982048551907This path
- Singapore501133559820485132337This 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
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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- British Virgin Islands
- Allocated
- 23rd July 2013
- Allocation block
- 2a04:5200::/29
- 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 |
|---|---|---|
| 2a04:5200::/32 | AS50113 | /32 |
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 |
|---|---|---|---|
| 2a04:5200:1::/48 | 65.5k × /64 | AS50113FIRST SERVER LIMITED | 62/62 |
| 2a04:5200:3::/48 | 65.5k × /64 | AS50113FIRST SERVER LIMITED | 60/62 |
| 2a04:5200:4::/48 | 65.5k × /64 | AS50113FIRST SERVER LIMITED | 60/62 |
| 2a04:5200:7::/48 | 65.5k × /64 | AS50113FIRST SERVER LIMITED | 60/62 |
| 2a04:5200:9::/48 | 65.5k × /64 | AS50113FIRST SERVER LIMITED | 60/62 |
| 2a04:5200:50::/48 | 65.5k × /64 | AS50113FIRST SERVER LIMITED | 60/62 |
| 2a04:5200:68::/48 | 65.5k × /64 | AS204339FIRST SERVER LIMITED | 62/62 |
| 2a04:5200:121::/48 | 65.5k × /64 | AS50113FIRST SERVER LIMITED | 60/62 |
| 2a04:5200:20a::/48 | 65.5k × /64 | AS50113FIRST SERVER LIMITED | 60/62 |
| 2a04:5200:d21::/48 | 65.5k × /64 | AS50113FIRST SERVER LIMITED | 60/62 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS5011312th 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.