2a09:5302:ffff::/48
At a glance
Subnets
/48 block
Visibility
57 of 62 vantage points
RPKI
Registry
VGAllocated 15th November 2018
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS205090seen on 4,745 paths from 142 vantage points
- Peer of AS35196seen on 4,636 paths from 126 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
- London, UK205090351963559851907This path
- Amsterdam205090351963559820485213151Shown above
- Sao Paulo2050903519635598719532590This path
- Singapore20509035196355986939132337This 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
92%
Seen by 57 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
- 15th November 2018
- Allocation block
- 2a09:5300::/29
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a09:5302::/32 | 4.3B × /64 | AS35196FIRST SERVER LIMITED | 5/62 |
| 2a09:5302::/32 | 4.3B × /64 | AS205090FIRST SERVER LIMITED | 57/62 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
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.