AS35104Jusan Mobile JSC
As of 26th September 2026, AS35104 (Jusan Mobile JSC), an access network registered in Kazakhstan with RIPE NCC, originates 168 IPv4 prefixes covering 47.1k addresses and 10 IPv6 prefixes. By IPv4 address space that makes it the 4,579th-largest of the 79,516 networks we see originating IPv4, and the 10th-largest of 212 in Kazakhstan. It is seen behind 21 upstream networks, most often AS43727 (JSC KVANT-TELEKOM) and AS3216 (Vimpelcom PJSC), and in front of 45 downstream networks. 96% of its announcements have a valid RPKI ROA; 1 is RPKI-invalid. Over 99% of its routes reach at least 90% of full-feed peers.
At a glance
IPv4 prefixes
IPv6 prefixes
IPv4 addresses
IPv6 /64s
Upstream graph
The networks AS35104 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS35104 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.
Neighbouring networks
170
adjacent networks
- Upstreams
- 2112%
- Peers
- 10461%
- Downstreams
- 4526%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS43727JSC KVANT-TELEKOM | Peer | 15,026 | 145 | |
| AS3216Vimpelcom PJSC | Peer | 8,208 | 107 | |
| AS35168TNS-Plus LLP | Peer | 4,912 | 81 | |
| AS6453TATA Communications (America) Inc | Peer | 3,233 | 75 | |
| AS31133MegaFon PJSC | Peer | 2,152 | 81 | |
| AS12389Rostelecom PJSC | Peer | 1,948 | 141 | |
| AS41798JSC Transtelecom | Peer | 1,892 | 144 | |
| AS31253Sovemennye Telekommunikatsionnye Sistemy LLP | Peer | 1,620 | 81 | |
| AS9002RETN Limited | Peer | 1,440 | 114 | |
| AS8359MTS PJSC | Peer | 1,020 | 55 |
Prefixes
All 178The largest blocks AS35104 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 93.185.72.0/21 | 2k | 81/81 |
| 77.245.104.0/22 | 1k | 81/81 |
| 95.141.136.0/22 | 1k | 81/81 |
| 77.245.108.0/23 | 512 | 81/81 |
| 185.48.148.0/23 | 512 | 81/81 |
| 217.196.26.0/23 | 512 | 81/81 |
| 37.228.64.0/24 | 256 | 81/81 |
| 37.228.65.0/24 | 256 | 81/81 |
| 37.228.66.0/24 | 256 | 81/81 |
| 37.228.67.0/24 | 256 | 81/81 |
Routing health
How AS35104's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.
RPKI origin validation
- Valid95.5%170
- Invalid0.6%1
- No ROA3.9%7
Propagation
- Globally propagated90% of full-feed peers or more99.4%177
- Partially propagated40% to 90%0.0%0
- Seen by few peersUnder 40%0.6%1
Prefix sizes
IPv4 — 168 prefixes
IPv6 — 10 prefixes
- /324.3B × /6410.0%1
- /36268M × /6420.0%2
- /424.2M × /6410.0%1
- /441M × /6410.0%1
- /4865.5k × /6450.0%5
Recent changes
Announcements that started or stopped since 28th Aug 2026.
No announcement by AS35104 started or stopped in this period.
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.