Network · data from 2026-11-12
AS43197 TT mobile
Registry name: TT-Mobile-AS Closed Joint Stock Company TT mobile, TJ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43197, 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.
| 109.68.236.0/24 | Valid | Nonecovered by 109.68.236.0/22 | 671 100% |
| 45.81.37.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 62.89.208.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 62.89.220.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.68.232.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.105.228.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 62.89.208.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.89.223.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 109.68.232.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 109.68.233.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 109.68.239.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.105.229.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.105.231.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.89.209.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 62.89.210.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 62.89.211.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.68.234.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.68.238.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.105.230.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.68.237.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.105.228.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a0b:6bc0::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:6bc0::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:6bc0:1::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:6bc0:1::/64 | Valid | RIR databaseRIPE | 7 1%low visibility |
| 62.89.221.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
| 109.68.235.0/24 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS43197'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 5 are in fix.csv.
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 109.68.236.0/24 | No route object for it. A route object for 109.68.236.0/22 with origin AS43197 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43197 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS43197 whose prefix no peer sees AS43197 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 62.89.220.0/22 | RIPE | Valid |
| 62.89.222.0/24 | RIPE | Valid |
| 109.68.236.0/22 | RIPE | Invalid: maxLength |
| 2a0b:6bc0::/29 | 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.