Network · data from 2026-11-12
AS398156 ACE-FIBER-01 - ACE Fiber
Registry name: ACE-FIBER-01 - ACE Fiber, US · not in PeeringDB
29IPv4 routes
100.0% RPKI valid · 24.1% with a route object
1IPv6 routes
0.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
1No ROA
22 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
3Route objects not announced
registered with origin AS398156, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS398156, 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.
| 2605:87c0::/32 | No ROA | RIR databaseARIN | 605 95% |
| 158.120.208.0/23 | Valid | Nonecovered by 158.120.192.0/19 | 673 100% |
| 158.120.210.0/23 | Valid | Nonecovered by 158.120.192.0/19 | 673 100% |
| 158.120.212.0/23 | Valid | Nonecovered by 158.120.192.0/19 | 673 100% |
| 158.120.214.0/23 | Valid | Nonecovered by 158.120.192.0/19 | 673 100% |
| 158.120.216.0/23 | Valid | Nonecovered by 158.120.192.0/19 | 673 100% |
| 158.120.218.0/23 | Valid | Nonecovered by 158.120.192.0/19 | 673 100% |
| 158.120.220.0/23 | Valid | Nonecovered by 158.120.192.0/19 | 673 100% |
| 168.220.192.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.194.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.196.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.198.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.200.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.202.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.204.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.206.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.208.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.210.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.212.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.214.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.216.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.218.0/23 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 168.220.222.0/24 | Valid | Nonecovered by 168.220.192.0/19 | 673 100% |
| 158.120.192.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 158.120.196.0/23 | Valid | RIR databaseARIN | 673 100% |
| 158.120.198.0/23 | Valid | RIR databaseARIN | 673 100% |
| 158.120.200.0/23 | Valid | RIR databaseARIN | 673 100% |
| 158.120.202.0/23 | Valid | RIR databaseARIN | 673 100% |
| 168.220.192.0/19 | Valid | RIR databaseARIN, RADB | 673 100% |
| 198.48.96.0/19 | Valid | RIR databaseARIN | 672 100% |
AS-SET
AS398156 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 26 are in fix.csv.
- ROA: none1
- Route object: none22
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2605:87c0::/32 | No ROA covers it. Add a ROA for AS398156, maxLength 32. |
| Route object: none | 158.120.208.0/23 | No route object for it. A route object for 158.120.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 158.120.210.0/23 | No route object for it. A route object for 158.120.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 158.120.212.0/23 | No route object for it. A route object for 158.120.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 158.120.214.0/23 | No route object for it. A route object for 158.120.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 158.120.216.0/23 | No route object for it. A route object for 158.120.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 158.120.218.0/23 | No route object for it. A route object for 158.120.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 158.120.220.0/23 | No route object for it. A route object for 158.120.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.192.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.194.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.196.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.198.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.200.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.202.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.204.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.206.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.208.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.210.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.212.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.214.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.216.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.218.0/23 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
| Route object: none | 168.220.222.0/24 | No route object for it. A route object for 168.220.192.0/19 with origin AS398156 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398156 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS398156 whose prefix no peer sees AS398156 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 158.120.194.0/23 | ARIN | Valid |
| 158.120.204.0/23 | ARIN | Valid |
| 158.120.206.0/23 | 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.