Network · data from 2026-11-12
AS9656 T-SYSTEMS-SG - T-SYSTEMS SINGAPORE PTE LTD
Registry name: T-SYSTEMS-SG - T-SYSTEMS SINGAPORE PTE LTD, SG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9656, 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.
| 202.56.144.0/20 | No ROA | Nonecovered by 202.56.128.0/19 | 673 100% |
| 202.136.0.0/21 | No ROA | Other origin onlycovered by 202.136.0.0/20 | 673 100% |
| 202.136.8.0/21 | No ROA | Nonecovered by 202.136.0.0/20 | 673 100% |
| 202.56.128.0/19 | No ROA | Other IRR onlyRADB | 673 100% |
| 202.136.0.0/20 | No ROA | Other IRR onlyRADB | 673 100% |
| 202.56.128.0/20 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 202.56.143.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
AS-SET
AS9656 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 18 are in fix.csv.
- ROA: none7
- Route object: none3
- Route object: RIR2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 202.56.144.0/20 | No ROA covers it. Add a ROA for AS9656, maxLength 20. |
| Route object: none | 202.56.144.0/20 | No route object for it. A route object for 202.56.128.0/19 with origin AS9656 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9656 in the RIR database for the space. |
| ROA: none | 202.136.0.0/21 | No ROA covers it. Add a ROA for AS9656, maxLength 21. |
| Route object: none | 202.136.0.0/21 | Route objects for it name AS4628. A route object for 202.136.0.0/20 with origin AS9656 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9656 in the RIR database for the space. |
| ROA: none | 202.136.8.0/21 | No ROA covers it. Add a ROA for AS9656, maxLength 21. |
| Route object: none | 202.136.8.0/21 | No route object for it. A route object for 202.136.0.0/20 with origin AS9656 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9656 in the RIR database for the space. |
| ROA: none | 202.56.128.0/19 | No ROA covers it. Add a ROA for AS9656, maxLength 19. |
| Route object: RIR | 202.56.128.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.136.0.0/20 | No ROA covers it. Add a ROA for AS9656, maxLength 20. |
| Route object: RIR | 202.136.0.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 202.56.128.0/20 | No ROA covers it. Add a ROA for AS9656, maxLength 20. |
| ROA: none | 202.56.143.0/24 | No ROA covers it. Add a ROA for AS9656, maxLength 24. |
Route objects not announced
Route objects with origin AS9656 whose prefix no peer sees AS9656 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.56.144.0/21 | RADB | No ROA |
| 202.56.144.0/22 | APNIC | No ROA |
| 202.56.148.0/22 | APNIC | No ROA |
| 202.136.0.0/22 | APNIC | No ROA |
| 202.136.4.0/22 | APNIC | No ROA |
| 202.136.8.0/22 | APNIC, 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.