2a01:4b40:3000::/37
At a glance
Subnets
/37 block
Visibility
62 of 63 vantage points
RPKI
Registry
KZAllocated 29th May 2012
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS21299seen on 64,311 paths from 139 vantage points
- Peer of AS35168seen on 6,735 paths from 138 vantage points
- Peer of AS43727seen on 113 paths from 39 vantage points
- Peer of AS31133seen on 72,046 paths from 101 vantage points
- Peer of AS1299seen on 428,523 paths from 30 vantage points
- Peer of AS6453seen on 653,228 paths from 6 vantage points
RU
SE
US
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
- Amsterdam2129935168437278298This path
- London, UK21299351684372735280This path
- Singapore21299351686939132337This path
- Sao Paulo212993516843727311331299645335280Shown 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
98%
Seen by 62 of 63 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
- Kazakhstan
- Allocated
- 29th May 2012
- Allocation block
- 2a01:4b40::/32
- Status
- allocated
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
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 |
|---|---|---|---|
| 2a01:4b40:3800::/37 | 134M × /64 | AS21299Kar-Tel LLC | 62/63 |
History
- AS2129922nd September 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.