kz.kaztranscom
Jusan Mobile JSC
KZ
RIPE LIR — 14 IPv4 + 1 IPv6 allocations · BGP overlay from RIPE RIS RRC00
thank you!
KZ
| Date | Prefix | Status | Total | Announced | Coverage |
|---|---|---|---|---|---|
| 2012-04-10 | 37.228.64.0/21 RIPE DB ↗RADAR ↗ | ALLOCATED PA | 2 048 addr | 2 048 addr | Full 100% |
|
|||||
| 2011-02-10 | 46.235.80.0/21 RIPE DB ↗RADAR ↗ | ALLOCATED PA | 2 048 addr | 2 048 addr | Full 100% |
|
|||||
| 2007-04-24 | 77.245.96.0/20 RIPE DB ↗RADAR ↗ | ALLOCATED PA | 4 096 addr | 4 096 addr | Full 100% |
|
|||||
| 2009-09-16 | 80.242.208.0/20 RIPE DB ↗RADAR ↗ | ALLOCATED PA | 4 096 addr | 4 096 addr | Full 100% |
|
|||||
| 2006-07-05 | 89.219.24.0/23 RIPE DB ↗RADAR ↗ | ALLOCATED PA | 512 addr | 512 addr | Full 100% |
| 2006-07-05 | 89.219.27.0/24 RIPE DB ↗RADAR ↗ ↳AS35104RIPE DB ↗RADAR ↗ | ALLOCATED PA | 256 addr | 256 addr | Full 100% |
| 2008-06-06 | 93.185.64.0/20 RIPE DB ↗RADAR ↗ | ALLOCATED PA | 4 096 addr | 4 096 addr | Full 100% |
|
|||||
| 2009-06-05 | 95.141.128.0/20 RIPE DB ↗RADAR ↗ | ALLOCATED PA | 4 096 addr | 4 096 addr | Full 100% |
|
|||||
| 2013-03-06 | 185.20.124.0/22 RIPE DB ↗RADAR ↗ | ALLOCATED PA | 1 024 addr | 1 024 addr | Full 100% |
| 2011-05-24 | 188.0.128.0/19 RIPE DB ↗RADAR ↗ | ALLOCATED PA | 8 192 addr | 7 936 addr | Partial 96.88% |
|
Announced sub-prefixes
|
|||||
| 2009-07-27 | 188.127.32.0/19 RIPE DB ↗RADAR ↗ | ALLOCATED PA | 8 192 addr | 5 632 addr | Partial 68.75% |
|
Announced sub-prefixes
|
|||||
| 2004-03-31 | 193.29.53.0/24 RIPE DB ↗RADAR ↗ ↳AS35104RIPE DB ↗RADAR ↗ | ALLOCATED PA | 256 addr | 256 addr | Full 100% |
| 2006-05-19 | 195.189.28.0/22 RIPE DB ↗RADAR ↗ | ALLOCATED PA | 1 024 addr | 1 024 addr | Full 100% |
| 2004-10-07 | 217.196.16.0/20 RIPE DB ↗RADAR ↗ | ALLOCATED PA | 4 096 addr | 3 840 addr | Partial 93.75% |
|
Announced sub-prefixes
|
|||||
| Date | Prefix | Status | Total | Announced | Coverage |
|---|---|---|---|---|---|
| 2011-04-12 | 2a03:a300::/32 RIPE DB ↗RADAR ↗ | — | 65 536 /48 | 65 536 /48 | Full 100% |
|
|||||
Coverage = how much of an allocation is reachable via BGP. Full: every /24 (or /48) inside the block has a covering BGP route. Partial: some /24s announced, others unannounced — see the breakdown for the actual announced sub-prefixes. Not announced: no BGP route covers any /24 of the block.