Network · data from 2026-11-12
AS196797 CityTeleNet Joint Stock Company TransTeleCom
Registry name: CityTeleNet Joint Stock Company TransTeleCom, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS196797, 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.
| 164.138.32.0/21 | Valid | None | 673 100% |
| 91.222.28.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.222.29.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.222.30.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.222.31.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.125.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.125.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.125.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.125.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.125.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.125.94.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.125.95.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.233.168.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.233.169.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.233.170.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.233.171.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 164.138.32.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 164.138.33.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 164.138.34.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 164.138.35.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 164.138.36.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 164.138.37.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 164.138.38.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 164.138.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.115.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.115.89.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.115.90.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.115.91.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.115.92.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.115.93.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.115.94.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.115.95.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.151.24.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.151.25.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.151.26.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.151.27.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.69.168.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.69.169.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.69.170.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.69.171.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.69.236.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.69.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.69.238.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.69.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.30.48.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.30.49.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.30.50.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.30.51.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.30.52.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.30.54.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.30.55.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.30.56.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.30.59.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.30.60.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.30.61.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.30.62.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.30.63.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS196797 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 8 are in fix.csv.
- Route object: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 164.138.32.0/21 | No route object for it. Add a route object with origin AS196797 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS196797 whose prefix no peer sees AS196797 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.222.28.0/22 | RIPE | Valid |
| 109.233.168.0/21 | RIPE | No ROA |
| 109.233.168.0/22 | RIPE | Valid |
| 176.115.88.0/21 | RIPE | Valid |
| 193.151.24.0/22 | RIPE | Valid |
| 195.69.168.0/22 | RIPE | Valid |
| 195.69.236.0/22 | 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.