Network · data from 2026-11-12
AS4821 Sinergi Semesta Telematika
Registry name: SINERGINET-AS-ID - PT Sinergi Semesta Telematika, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS4821, 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.
| 223.25.105.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
| 223.25.108.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 672 100% |
AS-SET
AS4821's PeeringDB record names no 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 11 are in fix.csv.
- Route object: RIR2
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 223.25.105.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 223.25.108.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS4821 whose prefix no peer sees AS4821 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 223.25.96.0/20 | NTTCOM, RADB | No ROA |
| 223.25.104.0/21 | APNIC, NTTCOM, RADB | No ROA |
| 223.25.104.0/22 | NTTCOM, RADB | No ROA |
| 223.25.104.0/23 | NTTCOM, RADB | No ROA |
| 223.25.106.0/23 | NTTCOM, RADB | No ROA |
| 223.25.108.0/22 | NTTCOM, RADB | No ROA |
| 223.25.108.0/23 | NTTCOM, RADB | No ROA |
| 223.25.110.0/23 | NTTCOM, RADB | No ROA |
| 2402:a500::/32 | APNIC | 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.