2a03:32c0:2e::/47
At a glance
Subnets
/47 block
Visibility
61 of 62 vantage points
RPKI
Registry
KZAllocated 26th October 2012
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 AS48503seen on 30,272 paths from 141 vantage points
- Peer of AS9198seen on 114,191 paths from 138 vantage points
- Peer of AS12389seen on 526,463 paths from 116 vantage points
- Peer of AS6939seen on 132,979 paths from 2 vantage points
RU
US
CHOne 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
- Amsterdam485039198123896939213151This path
- London, UK48503919812389693951907Shown above
- Sao Paulo48503919812389676232590This path
- Singapore485039198123896939132337This 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
98%
Seen by 61 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
- Kazakhstan
- Allocated
- 26th October 2012
- Allocation block
- 2a03:32c0::/32
- 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 |
|---|---|---|
| 2a03:32c0:2e::/47 | AS48503 | /47 |
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
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a03:32c0:2e::/48 | 65.5k × /64 | AS29555Mobile Telecom-Service LLP | 62/62 |
| 2a03:32c0:2f::/48 | 65.5k × /64 | AS29555Mobile Telecom-Service LLP | 62/62 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a03:32c0:2c::/47 | 131k × /64 | AS48503Mobile Telecom-Service LLP | 61/62 |
History
- AS4850312th August 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.