Network · data from 2026-11-12
AS61367 ASBALKHASH TOO "B-TEL"
Registry name: ASBALKHASH TOO "B-TEL", KZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61367, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 5.59.40.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.59.57.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 5.59.58.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 5.59.208.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.59.216.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 5.59.242.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.31.200.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 45.132.160.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.132.162.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.141.248.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.141.250.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.143.240.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.143.242.0/23 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS61367 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.
- ROA: none7
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 5.59.40.0/22 | No ROA covers it. Add a ROA for AS61367, maxLength 22. |
| ROA: none | 5.59.57.0/24 | No ROA covers it. Add a ROA for AS61367, maxLength 24. |
| ROA: none | 5.59.58.0/23 | No ROA covers it. Add a ROA for AS61367, maxLength 23. |
| ROA: none | 5.59.208.0/22 | No ROA covers it. Add a ROA for AS61367, maxLength 22. |
| ROA: none | 5.59.216.0/22 | No ROA covers it. Add a ROA for AS61367, maxLength 22. |
| ROA: none | 5.59.242.0/24 | No ROA covers it. Add a ROA for AS61367, maxLength 24. |
| ROA: none | 193.31.200.0/21 | No ROA covers it. Add a ROA for AS61367, maxLength 21. |
Route objects not announced
Route objects with origin AS61367 whose prefix no peer sees AS61367 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.59.196.0/23 | RIPE | No ROA |
| 5.59.220.0/24 | RIPE | No ROA |
| 45.132.160.0/22 | RIPE | No ROA |
| 45.141.248.0/22 | RIPE | No ROA |
| 45.143.240.0/22 | RIPE | No ROA |
| 2001:67c:14a8::/48 | RIPE | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.