95.141.136.0/22
At a glance
Addresses
/22 block
Visibility
80 of 80 vantage points
RPKI
Registry
KZAllocated 5th June 2009
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 AS35104seen on 3,391 paths from 80 vantage points
- Peer of AS35168seen on 673 paths from 2 vantage points
AEOne 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
- Amsterdam3510435168213151This path
- London, UK35104351688529Shown above
- Singapore3510435168132337This path
- Oregon, US3510435168693920130This path
- Sao Paulo351043516832163356266213This 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
100%
Seen by 80 of 80 full-feed vantage points
Globally propagatedObserved at 5 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
- 5th June 2009
- Allocation block
- 95.141.128.0/20
- 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.
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 |
|---|---|---|---|
| 95.141.136.0/24 | 256 | AS35104Jusan Mobile JSC | 80/80 |
| 95.141.137.0/24 | 256 | AS35104Jusan Mobile JSC | 80/80 |
| 95.141.138.0/24 | 256 | AS35104Jusan Mobile JSC | 80/80 |
| 95.141.139.0/24 | 256 | AS35104Jusan Mobile JSC | 80/80 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS3510412th 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.
Open 95.141.136.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.