2a14:7581:5070::/44
At a glance
Subnets
/44 block
Visibility
42 of 63 vantage points
RPKI
Registry
USAllocated 12th January 2024
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS218471seen on 75 paths from 20 vantage points
- Peer of AS204464seen on 590 paths from 138 vantage points
- Peer of AS205941seen on 517 paths from 56 vantage points
- Peer of AS400587seen on 239 paths from 20 vantage points
- Peer of AS35133seen on 3,684 paths from 68 vantage points
- Peer of AS6939seen on 478,416 paths from 2 vantage points
DE
GB
RO
NL
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
- Amsterdam2044642158288298This path
- London, UK204464215828693935280This path
- Sao Paulo204464215828693935280This path
- Singapore218471204464205941400587351336939132337Shown 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
67%
Seen by 42 of 63 full-feed vantage points
Partially propagatedObserved 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
- United States
- Allocated
- 12th January 2024
- Allocation block
- 2a14:7580::/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.
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 |
|---|---|---|---|
| 2a14:7581:5060::/44 | 1M × /64 | AS204464SharedServ Ltd | 42/63 |
| 2a14:7581:5060::/44 | 1M × /64 | AS218470Franke Capital GmbH | 20/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.