Network · data from 2026-11-12
AS48716 PS Internet Company Network
Registry name: PSKZ-ALA PS Internet Company LLP, KZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48716, 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.
| 46.8.254.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.238.43.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 212.116.235.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 87.199.128.0/23 | No ROA | RIR databaseRIPE | 670 100% |
| 87.199.128.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 87.199.129.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 195.49.210.0/23 | Valid | Nonecovered by 195.49.208.0/21 | 673 100% |
| 195.49.212.0/22 | Valid | Nonecovered by 195.49.208.0/21 | 673 100% |
| 2a00:5da0:1000::/48 | Valid | Nonecovered by 2a00:5da0:1000::/36 | 636 100% |
| 31.3.209.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.247.40.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 46.247.40.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 46.247.41.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 77.240.38.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 77.240.38.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 77.240.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 77.243.80.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 77.243.80.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 77.243.81.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.108.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.108.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 78.40.109.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.115.40.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 82.115.40.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.115.41.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.115.42.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.115.43.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 83.97.77.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.202.194.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 85.202.194.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.202.195.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.219.32.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.219.32.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.219.33.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.219.34.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.219.35.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.147.92.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 91.147.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.147.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.147.94.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.147.95.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.147.104.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 91.147.104.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.147.105.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.147.106.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.147.107.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.201.214.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 91.201.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.201.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.215.136.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 91.215.136.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.215.137.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.215.139.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.247.128.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.247.128.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.247.129.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.247.130.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.247.131.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.247.132.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.247.133.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.247.134.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.247.135.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.233.108.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 109.233.108.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.233.109.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.233.110.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.233.111.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.4.180.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.4.180.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.4.181.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.4.182.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.4.183.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.22.64.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.22.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.22.65.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.22.66.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.22.67.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.35.222.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.35.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.35.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.102.72.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.102.72.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.102.73.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.102.74.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.102.75.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.146.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.146.1.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.146.2.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.146.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.253.8.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.32.140.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.32.140.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.32.141.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.32.142.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.32.143.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.39.64.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.39.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.39.65.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.39.66.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.39.67.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.110.54.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.110.54.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.110.55.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.238.40.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.238.40.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.238.41.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.49.209.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.49.210.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.49.211.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.49.212.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.49.213.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.49.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.49.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.93.152.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.93.152.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.93.153.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.210.46.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 195.210.46.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.210.47.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.116.232.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 212.116.232.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.116.233.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.155.20.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 213.155.20.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.155.21.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.146.0.0/24 | Valid | RIR databaseRIPE | 652 97% |
| 2a00:5da0::/36 | Valid | RIR databaseRIPE | 636 100% |
| 2a00:5da0:1000::/36 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS48716'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 19 are in fix.csv.
- ROA: none6
- Route object: none3
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 46.8.254.0/24 | No ROA covers it. Add a ROA for AS48716, maxLength 24. |
| ROA: none | 194.238.43.0/24 | No ROA covers it. Add a ROA for AS48716, maxLength 24. |
| ROA: none | 212.116.235.0/24 | No ROA covers it. Add a ROA for AS48716, maxLength 24. |
| ROA: none | 87.199.128.0/23 | No ROA covers it. Add a ROA for AS48716, maxLength 23. |
| ROA: none | 87.199.128.0/24 | No ROA covers it. Add a ROA for AS48716, maxLength 24. |
| ROA: none | 87.199.129.0/24 | No ROA covers it. Add a ROA for AS48716, maxLength 24. |
| Route object: none | 195.49.210.0/23 | No route object for it. A route object for 195.49.208.0/21 with origin AS48716 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48716 in the RIR database for the space. |
| Route object: none | 195.49.212.0/22 | No route object for it. A route object for 195.49.208.0/21 with origin AS48716 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48716 in the RIR database for the space. |
| Route object: none | 2a00:5da0:1000::/48 | No route object for it. A route object for 2a00:5da0:1000::/36 with origin AS48716 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48716 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS48716 whose prefix no peer sees AS48716 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.90.180.0/22 | RIPE | Invalid: origin |
| 91.147.119.0/24 | RADB, RIPE | Valid |
| 91.147.123.0/24 | RADB, RIPE | Valid |
| 91.147.126.0/23 | RADB, RIPE | Valid |
| 91.215.136.0/22 | RIPE | Valid |
| 94.198.220.0/23 | RIPE | Valid |
| 94.247.128.0/22 | RIPE | Valid |
| 94.247.132.0/22 | RIPE | Valid |
| 195.49.208.0/21 | RIPE | Valid |
| 2a03:6f06::/36 | RIPE | Invalid: maxLength |
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.