Network · data from 2026-11-12
AS55696 SCOM-AS-ID - Starcom Solusindo PT.
Registry name: SCOM-AS-ID - Starcom Solusindo PT., ID · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55696, 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.50.201.0/24 | Valid | Nonecovered by 202.50.200.0/22 | 35 5%low visibility |
| 202.50.202.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.50.203.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 202.50.200.0/24 | Valid | Other IRR onlyRADB | 672 100% |
AS-SET
AS55696 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 8 are in fix.csv.
- Route object: none1
- Route object: RIR3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 202.50.201.0/24 | No route object for it. A route object for 202.50.200.0/22 with origin AS55696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55696 in the RIR database for the space. |
| Route object: RIR | 202.50.202.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.50.203.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.50.200.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS55696 whose prefix no peer sees AS55696 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 121.50.128.0/20 | APNIC | No ROA |
| 202.50.200.0/22 | APNIC | No ROA |
| 203.190.184.0/21 | APNIC | No ROA |
| 2400:c900::/32 | 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.