Network · data from 2026-11-12
AS25896 IPC-NETWORK-SERVICES-INC - IPC Network Services Inc.
Registry name: IPC-NETWORK-SERVICES-INC - IPC Network Services Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS25896, 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.
| 104.254.177.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 104.254.178.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 122.128.88.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 195.189.12.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 195.189.13.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.202.210.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 103.202.211.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 104.254.179.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 65.244.37.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
AS-SET
AS25896 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: none8
- Route object: RIR8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 104.254.177.0/24 | No ROA covers it. Add a ROA for AS25896, maxLength 24. |
| Route object: RIR | 104.254.177.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 104.254.178.0/24 | No ROA covers it. Add a ROA for AS25896, maxLength 24. |
| Route object: RIR | 104.254.178.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 122.128.88.0/24 | No ROA covers it. Add a ROA for AS25896, maxLength 24. |
| Route object: RIR | 122.128.88.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 195.189.12.0/24 | No ROA covers it. Add a ROA for AS25896, maxLength 24. |
| Route object: RIR | 195.189.12.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 195.189.13.0/24 | No ROA covers it. Add a ROA for AS25896, maxLength 24. |
| Route object: RIR | 195.189.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.202.210.0/24 | No ROA covers it. Add a ROA for AS25896, maxLength 24. |
| Route object: RIR | 103.202.210.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.202.211.0/24 | No ROA covers it. Add a ROA for AS25896, maxLength 24. |
| Route object: RIR | 103.202.211.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 104.254.179.0/24 | No ROA covers it. Add a ROA for AS25896, maxLength 24. |
| Route object: RIR | 104.254.179.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS25896 whose prefix no peer sees AS25896 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.119.211.0/24 | ARIN | Valid |
| 76.8.65.0/24 | 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.