Network · data from 2026-11-12
AS393770 BICOM-US - Bicom Systems
Registry name: BICOM-US - Bicom Systems, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS393770, 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.
| 192.151.130.0/23 | No ROA | RIR databaseARIN | 573 85% |
| 161.129.56.0/24 | Valid | Nonecovered by 161.129.56.0/23 | 673 100% |
| 161.129.57.0/24 | Valid | Nonecovered by 161.129.56.0/23 | 673 100% |
| 161.129.58.0/24 | Valid | Nonecovered by 161.129.58.0/23 | 673 100% |
| 161.129.59.0/24 | Valid | Nonecovered by 161.129.58.0/23 | 673 100% |
| 2607:e4c0::/48 | Valid | RIR databaseARIN | 605 95% |
| 2607:e4c0:1::/48 | Valid | RIR databaseARIN | 605 95% |
AS-SET
AS393770 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 9 are in fix.csv.
- ROA: none1
- Route object: none4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 192.151.130.0/23 | No ROA covers it. Add a ROA for AS393770, maxLength 23. |
| Route object: none | 161.129.56.0/24 | No route object for it. A route object for 161.129.56.0/23 with origin AS393770 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393770 in the RIR database for the space. |
| Route object: none | 161.129.57.0/24 | No route object for it. A route object for 161.129.56.0/23 with origin AS393770 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393770 in the RIR database for the space. |
| Route object: none | 161.129.58.0/24 | No route object for it. A route object for 161.129.58.0/23 with origin AS393770 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393770 in the RIR database for the space. |
| Route object: none | 161.129.59.0/24 | No route object for it. A route object for 161.129.58.0/23 with origin AS393770 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393770 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS393770 whose prefix no peer sees AS393770 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 161.129.56.0/22 | ARIN | Valid |
| 161.129.56.0/23 | ARIN | Valid |
| 161.129.58.0/23 | ARIN | Valid |
| 2607:e4c0::/32 | ARIN | 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.