Network · data from 2026-11-12
AS20720 TOL-AS LLC Tatarstan-On-Line
Registry name: TOL-AS LLC Tatarstan-On-Line, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20720, 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.
| 217.198.0.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.198.1.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.198.3.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.198.4.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.198.8.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 85.233.80.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.81.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.82.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.83.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.84.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.85.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.86.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.87.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.88.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.89.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.90.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.91.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.92.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.93.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.94.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 85.233.95.0/24 | No ROA | RIR databaseRIPE | 672 100% |
AS-SET
AS20720 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 23 are in fix.csv.
- ROA: none21
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 217.198.0.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 217.198.1.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 217.198.3.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 217.198.4.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 217.198.8.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.80.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.81.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.82.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.83.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.84.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.85.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.86.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.87.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.88.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.89.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.90.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.91.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.92.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.93.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.94.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
| ROA: none | 85.233.95.0/24 | No ROA covers it. Add a ROA for AS20720, maxLength 24. |
Route objects not announced
Route objects with origin AS20720 whose prefix no peer sees AS20720 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 217.198.2.0/24 | RIPE | No ROA |
| 217.198.7.0/24 | 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.