Network · data from 2026-11-12
AS43533 Gals Telecom
Registry name: ASGALSTELECOM OOO "Gals Telecom", UZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43533, 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.
| 91.231.56.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 31.148.100.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 31.148.144.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 92.38.16.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 92.38.24.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 92.38.52.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 92.253.196.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 93.170.16.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 93.170.168.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 93.170.208.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 93.171.210.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 146.158.20.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 146.158.28.0/23 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS43533'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 1 are in fix.csv.
- ROA: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.231.56.0/22 | No ROA covers it. Add a ROA for AS43533, maxLength 22. |
Route objects not announced
Every route object with origin AS43533 is announced.
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.