2a0d:3341:bc00::/41
At a glance
Subnets
/41 block
Visibility
62 of 64 vantage points
RPKI
Registry
USAllocated 28th July 2020
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS14593seen on 847 paths from 81 vantage points
- Peer of AS36926seen on 15,139 paths from 141 vantage points
- Peer of AS327708seen on 19,169 paths from 141 vantage points
- Peer of AS37662seen on 105,794 paths from 140 vantage points
- Peer of AS6939seen on 437,007 paths from 2 vantage points
KE
RW
MU
SGOne 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
- Amsterdam14593369263277083766232590This path
- London, UK14593369263277083766235280This path
- Sao Paulo145933692632770837662693935280This path
- Singapore1459336926327708376626939132337Shown 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 62 of 64 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
- United States
- Allocated
- 28th July 2020
- Allocation block
- 2a0d:3340::/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 |
|---|---|---|
| 2a0d:3340::/29 | AS14593 | /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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a0d:3341:bc00::/40 | 16.8M × /64 | AS14593SpaceX Starlink | 64/64 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a0d:3341:bc80::/41 | 8.4M × /64 | AS14593SpaceX Starlink | 64/64 |
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.