Network · data from 2026-11-12
AS18704 T-SYSTEMS-NA - T-Systems North America, Inc.
Registry name: T-SYSTEMS-NA - T-Systems North America, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS18704, 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.
| 64.43.224.0/20 | No ROA | Nonecovered by 64.43.224.0/19 | 673 100% |
| 64.43.240.0/20 | No ROA | Nonecovered by 64.43.224.0/19 | 673 100% |
| 206.195.113.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 673 100% |
| 64.43.224.0/19 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 64.43.225.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 64.43.245.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 64.43.251.0/24 | No ROA | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS18704 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: none7
- Route object: none2
- Route object: RIR1
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.43.224.0/20 | No ROA covers it. Add a ROA for AS18704, maxLength 20. |
| Route object: none | 64.43.224.0/20 | No route object for it. A route object for 64.43.224.0/19 with origin AS18704 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18704 in the RIR database for the space. |
| ROA: none | 64.43.240.0/20 | No ROA covers it. Add a ROA for AS18704, maxLength 20. |
| Route object: none | 64.43.240.0/20 | No route object for it. A route object for 64.43.224.0/19 with origin AS18704 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18704 in the RIR database for the space. |
| ROA: none | 206.195.113.0/24 | No ROA covers it. Add a ROA for AS18704, maxLength 24. |
| Route object: RIR | 206.195.113.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| ROA: none | 64.43.224.0/19 | No ROA covers it. Add a ROA for AS18704, maxLength 19. |
| ROA: none | 64.43.225.0/24 | No ROA covers it. Add a ROA for AS18704, maxLength 24. |
| ROA: none | 64.43.245.0/24 | No ROA covers it. Add a ROA for AS18704, maxLength 24. |
| ROA: none | 64.43.251.0/24 | No ROA covers it. Add a ROA for AS18704, maxLength 24. |
Route objects not announced
Route objects with origin AS18704 whose prefix no peer sees AS18704 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.43.228.0/24 | ARIN | No ROA |
| 64.43.236.0/23 | ARIN | No ROA |
| 64.43.238.0/24 | ARIN | No ROA |
| 64.43.239.0/24 | ARIN | No ROA |
| 64.43.240.0/24 | ARIN | No ROA |
| 64.43.241.0/24 | ARIN | No ROA |
| 64.43.242.0/24 | ARIN | No ROA |
| 64.43.243.0/24 | ARIN | No ROA |
| 64.43.246.0/24 | ARIN | No ROA |
| 64.43.247.0/24 | ARIN | No ROA |
| 64.43.248.0/24 | ARIN | No ROA |
| 64.43.249.0/24 | ARIN | No ROA |
| 206.195.100.0/24 | NTTCOM, RADB | 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.