Network · data from 2026-11-12
AS58172 Freedom Telecom AS58172
Registry name: FreedomTelecom-AS Freedom Telecom Operations LLP, KZ · PeeringDB
77IPv4 routes
100.0% RPKI valid · 97.4% with a route object
27IPv6 routes
88.9% RPKI valid · 92.6% with a route object
2RPKI invalid
0 origin · 2 maxLength
1No ROA
4 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
27Route objects not announced
registered with origin AS58172, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS58172, 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.
| 2a04:3b00:8800::/41 | Invalid: maxLength | Nonecovered by 2a04:3b00:8800::/37 | 66 10% |
| 2a04:3b00:8900::/41 | Invalid: maxLength | Nonecovered by 2a04:3b00:8800::/37 | 66 10% |
| 2a04:3b01:8800::/44 | No ROA | RIR databaseRIPE | 636 100% |
| 94.131.226.0/24 | Valid | Nonecovered by 94.131.226.0/23 | 673 100% |
| 94.131.227.0/24 | Valid | Nonecovered by 94.131.226.0/23 | 673 100% |
| 45.133.232.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 45.135.131.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 80.173.160.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 80.173.162.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 80.173.163.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 80.173.164.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.178.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.179.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.180.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.181.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.183.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.184.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.185.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.186.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.188.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.188.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.189.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.190.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.116.191.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.132.148.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.132.149.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.132.150.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.132.151.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.213.49.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.239.101.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.60.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.61.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.62.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.63.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.224.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.225.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.228.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.229.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.230.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.231.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.232.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.233.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.234.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.235.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.236.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.127.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.127.97.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.127.98.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.127.99.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.127.100.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.127.101.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.127.102.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 128.127.103.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 153.56.200.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 153.56.201.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 153.56.202.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 153.56.203.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 153.56.204.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 157.22.232.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 157.22.234.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 157.22.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 157.22.238.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 157.22.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.20.176.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.20.177.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.20.178.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.20.179.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.20.180.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.20.181.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.20.182.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.20.183.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.191.212.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.210.139.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.148.60.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.35.124.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.232.206.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 157.22.233.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a04:3b00::/36 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b00:100::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b00:1000::/37 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b00:1800::/37 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b00:3000::/37 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b00:4000::/37 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b00:5000::/37 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b00:6000::/37 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b00:8000::/37 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b00:a000::/37 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b01::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b01:810::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b01:2800::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b01:3800::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b01:4800::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b01:5800::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b01:6000::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b01:8000::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b02:c20::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b02:5c20::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b02:8420::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a04:3b01:800::/44 | Valid | RIR databaseRIPE | 635 100% |
| 2a04:3b00:2800::/37 | Valid | RIR databaseRIPE | 3 0%low visibility |
| 2a04:3b01:1800::/44 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 153.56.205.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS58172'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 34 are in fix.csv.
- ROA: maxLength2
- ROA: none1
- Route object: none4
- Route object: not announced27
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2a04:3b00:8800::/41 | ROA 2a04:3b00:8800::/37 AS58172 has maxLength 37; the route is a /41. Raise the maxLength, or add a ROA for 2a04:3b00:8800::/41. |
| Route object: none | 2a04:3b00:8800::/41 | No route object for it. A route object for 2a04:3b00:8800::/37 with origin AS58172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58172 in the RIR database for the space. |
| ROA: maxLength | 2a04:3b00:8900::/41 | ROA 2a04:3b00:8800::/37 AS58172 has maxLength 37; the route is a /41. Raise the maxLength, or add a ROA for 2a04:3b00:8900::/41. |
| Route object: none | 2a04:3b00:8900::/41 | No route object for it. A route object for 2a04:3b00:8800::/37 with origin AS58172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58172 in the RIR database for the space. |
| ROA: none | 2a04:3b01:8800::/44 | No ROA covers it. Add a ROA for AS58172, maxLength 44. |
| Route object: none | 94.131.226.0/24 | No route object for it. A route object for 94.131.226.0/23 with origin AS58172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58172 in the RIR database for the space. |
| Route object: none | 94.131.227.0/24 | No route object for it. A route object for 94.131.226.0/23 with origin AS58172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58172 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS58172 whose prefix no peer sees AS58172 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.173.161.0/32 | RIPE | Invalid: maxLength |
| 80.173.165.0/24 | RIPE | Valid |
| 80.173.166.0/24 | RIPE | Valid |
| 85.116.176.0/24 | RIPE | Valid |
| 85.116.177.0/24 | RIPE | Valid |
| 94.131.226.0/23 | RIPE | Valid |
| 94.131.236.0/23 | RIPE | Valid |
| 141.133.144.0/24 | RIPE | Valid |
| 141.133.145.0/24 | RIPE | Valid |
| 141.133.146.0/24 | RIPE | Valid |
| 141.133.147.0/24 | RIPE | Valid |
| 2a04:3b00:2000::/37 | RIPE | Valid |
| 2a04:3b00:3800::/37 | RIPE | Valid |
| 2a04:3b00:4800::/37 | RIPE | Valid |
| 2a04:3b00:5800::/37 | RIPE | Valid |
| 2a04:3b00:6800::/37 | RIPE | Valid |
| 2a04:3b00:7000::/37 | RIPE | Valid |
| 2a04:3b00:7800::/37 | RIPE | Valid |
| 2a04:3b00:8800::/37 | RIPE | Valid |
| 2a04:3b00:9000::/37 | RIPE | Valid |
| 2a04:3b00:9800::/37 | RIPE | Valid |
| 2a04:3b01:7800::/44 | RIPE | No ROA |
| 2a04:3b02:420::/44 | RIPE | Valid |
| 2a04:3b02:1c20::/44 | RIPE | Valid |
| 2a04:3b02:2c20::/44 | RIPE | Valid |
| 2a04:3b02:3c20::/44 | RIPE | Valid |
| 2a04:3b02:6420::/44 | RIPE | Valid |
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.