Network · data from 2026-11-12
AS55667 IPTELECOM-AS-ID - PT IP Telecom Multimedia Indonesia
Registry name: IPTELECOM-AS-ID - PT IP Telecom Multimedia Indonesia, ID · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55667, 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.
| 49.156.56.0/23 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 49.156.56.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 49.156.57.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 49.156.60.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
AS-SET
AS55667 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: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 49.156.56.0/23 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 49.156.56.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 49.156.57.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 49.156.60.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 AS55667 whose prefix no peer sees AS55667 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 49.156.56.0/21 | NTTCOM, RADB | No ROA |
| 49.156.56.0/22 | NTTCOM, RADB | No ROA |
| 49.156.60.0/22 | NTTCOM, RADB | No ROA |
| 49.156.60.0/23 | 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.