Network · data from 2026-11-12
AS41124 BTcom Infocommunications
Registry name: BTCOM BTcom Infocommunications Ltd., KZ · PeeringDB
54IPv4 routes
100.0% RPKI valid · 70.4% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
16 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
9Route objects not announced
registered with origin AS41124, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS41124, 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.
| 31.148.208.0/24 | Valid | Nonecovered by 31.148.208.0/22 | 673 100% |
| 31.148.210.0/24 | Valid | Nonecovered by 31.148.208.0/22 | 673 100% |
| 31.148.211.0/24 | Valid | Nonecovered by 31.148.208.0/22 | 673 100% |
| 95.47.32.0/24 | Valid | Nonecovered by 95.47.32.0/22 | 673 100% |
| 95.47.33.0/24 | Valid | Nonecovered by 95.47.32.0/22 | 673 100% |
| 95.47.34.0/24 | Valid | Nonecovered by 95.47.32.0/22 | 673 100% |
| 95.47.35.0/24 | Valid | Nonecovered by 95.47.32.0/22 | 673 100% |
| 95.47.192.0/24 | Valid | Nonecovered by 95.47.192.0/22 | 673 100% |
| 95.47.193.0/24 | Valid | Nonecovered by 95.47.192.0/22 | 673 100% |
| 95.47.194.0/24 | Valid | Nonecovered by 95.47.192.0/22 | 673 100% |
| 95.47.195.0/24 | Valid | Nonecovered by 95.47.192.0/22 | 673 100% |
| 146.120.176.0/24 | Valid | Nonecovered by 146.120.176.0/22 | 673 100% |
| 146.120.177.0/24 | Valid | Nonecovered by 146.120.176.0/22 | 673 100% |
| 146.120.178.0/24 | Valid | Nonecovered by 146.120.176.0/22 | 673 100% |
| 146.120.179.0/24 | Valid | Nonecovered by 146.120.176.0/22 | 673 100% |
| 31.148.209.0/24 | Valid | Nonecovered by 31.148.208.0/22 | 671 100% |
| 89.107.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.107.97.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.107.98.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.107.99.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.107.100.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.107.101.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.107.102.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.107.103.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.171.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.171.65.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.171.66.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.171.67.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.171.228.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.171.229.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.120.124.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.120.125.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.120.126.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.120.127.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.120.152.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.120.153.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.120.154.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.120.155.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.158.24.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.158.25.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.158.26.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.158.27.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.158.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.158.65.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.158.66.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.158.67.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.27.68.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.27.69.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.27.70.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.27.71.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.171.68.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 93.171.69.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 93.171.70.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 93.171.71.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS41124's PeeringDB record names no 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 25 are in fix.csv.
- Route object: none16
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 31.148.208.0/24 | No route object for it. A route object for 31.148.208.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 31.148.210.0/24 | No route object for it. A route object for 31.148.208.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 31.148.211.0/24 | No route object for it. A route object for 31.148.208.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 95.47.32.0/24 | No route object for it. A route object for 95.47.32.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 95.47.33.0/24 | No route object for it. A route object for 95.47.32.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 95.47.34.0/24 | No route object for it. A route object for 95.47.32.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 95.47.35.0/24 | No route object for it. A route object for 95.47.32.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 95.47.192.0/24 | No route object for it. A route object for 95.47.192.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 95.47.193.0/24 | No route object for it. A route object for 95.47.192.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 95.47.194.0/24 | No route object for it. A route object for 95.47.192.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 95.47.195.0/24 | No route object for it. A route object for 95.47.192.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 146.120.176.0/24 | No route object for it. A route object for 146.120.176.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 146.120.177.0/24 | No route object for it. A route object for 146.120.176.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 146.120.178.0/24 | No route object for it. A route object for 146.120.176.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 146.120.179.0/24 | No route object for it. A route object for 146.120.176.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
| Route object: none | 31.148.209.0/24 | No route object for it. A route object for 31.148.208.0/22 with origin AS41124 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41124 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS41124 whose prefix no peer sees AS41124 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.148.208.0/22 | RIPE | Valid |
| 89.107.96.0/21 | RIPE | No ROA |
| 93.171.64.0/21 | RIPE | Valid |
| 93.171.228.0/23 | RIPE | Valid |
| 95.47.32.0/22 | RIPE | Valid |
| 95.47.192.0/22 | RIPE | Valid |
| 146.120.176.0/22 | RIPE | Valid |
| 146.158.64.0/22 | RIPE | Valid |
| 185.27.68.0/22 | 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.