2a11:840:77::/48
At a glance
Subnets
/48 block
Visibility
6 of 63 vantage points
RPKI
Registry
CAAllocated 2nd July 2021
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS136258seen on 82 paths from 82 vantage points
- Peer of AS152734seen on 386 paths from 82 vantage points
- Peer of AS55808seen on 1,224 paths from 138 vantage points
- Peer of AS45758seen on 24 paths from 6 vantage points
- Peer of AS63529seen on 877 paths from 66 vantage points
- Peer of AS23764seen on 101,136 paths from 70 vantage points
- Peer of AS7713seen on 102,149 paths from 6 vantage points
TH
HK
ID
FROne 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, UK13625815273455808457586352923764771335280Shown above
- Sao Paulo13625815273455808457586352923764771335280This 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
10%
Seen by 6 of 63 full-feed vantage points
Seen by few vantage pointsObserved at 3 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
- Canada
- Allocated
- 2nd July 2021
- Allocation block
- 2a11:840::/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 |
|---|---|---|
| 2a11:840:77::/48 | AS136258 | /48 |
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 |
|---|---|---|---|
| 2a11:840:76::/48 | 65.5k × /64 | AS136258BrainStorm Network, Inc | 56/63 |
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.