Network · data from 2026-11-12
AS20570 ASN-TSI-IPLS Telekom Deutschland GmbH
Registry name: ASN-TSI-IPLS Telekom Deutschland GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20570, 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.209.160.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 141.78.100.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.200.56.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 193.96.128.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 194.55.48.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 194.55.63.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.76.160.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.121.2.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 195.114.22.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 209.206.38.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2001:678:8ac::/48 | No ROA | RIR databaseRIPE | 627 99% |
| 193.105.147.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.93.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2001:67c:d70::/48 | Valid | RIR databaseRIPE | 627 99% |
AS-SET
AS20570 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 19 are in fix.csv.
- ROA: none11
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.209.160.0/24 | No ROA covers it. Add a ROA for AS20570, maxLength 24. |
| ROA: none | 141.78.100.0/22 | No ROA covers it. Add a ROA for AS20570, maxLength 22. |
| ROA: none | 185.200.56.0/22 | No ROA covers it. Add a ROA for AS20570, maxLength 22. |
| ROA: none | 193.96.128.0/20 | No ROA covers it. Add a ROA for AS20570, maxLength 20. |
| ROA: none | 194.55.48.0/20 | No ROA covers it. Add a ROA for AS20570, maxLength 20. |
| ROA: none | 194.55.63.0/24 | No ROA covers it. Add a ROA for AS20570, maxLength 24. |
| ROA: none | 194.76.160.0/24 | No ROA covers it. Add a ROA for AS20570, maxLength 24. |
| ROA: none | 194.121.2.0/24 | No ROA covers it. Add a ROA for AS20570, maxLength 24. |
| ROA: none | 195.114.22.0/23 | No ROA covers it. Add a ROA for AS20570, maxLength 23. |
| ROA: none | 209.206.38.0/24 | No ROA covers it. Add a ROA for AS20570, maxLength 24. |
| ROA: none | 2001:678:8ac::/48 | No ROA covers it. Add a ROA for AS20570, maxLength 48. |
Route objects not announced
Route objects with origin AS20570 whose prefix no peer sees AS20570 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 161.145.171.0/24 | RIPE | Valid |
| 185.149.164.0/22 | RIPE | Invalid: origin |
| 193.29.196.0/22 | RIPE | No ROA |
| 194.35.59.0/24 | RIPE | No ROA |
| 194.41.39.0/24 | RIPE | Invalid: origin |
| 194.93.96.0/23 | RIPE | No ROA |
| 194.93.97.0/24 | RIPE | Invalid: origin |
| 194.127.208.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.