Network · data from 2026-11-12
AS400684 ZOOMFIBER-01 - Zoom Fiber
Registry name: ZOOMFIBER-01 - Zoom Fiber, US · not in PeeringDB
13IPv4 routes
30.8% RPKI valid · 7.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
9No ROA
12 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
5Route objects not announced
registered with origin AS400684, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS400684, 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.
| 38.100.184.0/21 | No ROA | None | 673 100% |
| 38.100.184.0/24 | No ROA | Nonecovered by 38.100.184.0/22 | 671 100% |
| 38.100.190.0/24 | No ROA | Nonecovered by 38.100.190.0/23 | 671 100% |
| 38.100.191.0/24 | No ROA | Nonecovered by 38.100.190.0/23 | 671 100% |
| 38.100.185.0/24 | No ROA | Nonecovered by 38.100.184.0/22 | 669 99% |
| 38.100.186.0/24 | No ROA | Nonecovered by 38.100.184.0/22 | 669 99% |
| 38.100.187.0/24 | No ROA | Nonecovered by 38.100.184.0/22 | 669 99% |
| 38.100.188.0/24 | No ROA | Nonecovered by 38.100.188.0/23 | 669 99% |
| 38.100.189.0/24 | No ROA | Nonecovered by 38.100.188.0/23 | 669 99% |
| 208.75.96.0/22 | Valid | Nonecovered by 208.75.96.0/21 | 671 100% |
| 208.75.97.0/24 | Valid | Nonecovered by 208.75.96.0/21 | 671 100% |
| 208.75.100.0/22 | Valid | Nonecovered by 208.75.96.0/21 | 671 100% |
| 208.75.96.0/21 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS400684 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: none9
- Route object: none12
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.100.184.0/21 | No ROA covers it. Add a ROA for AS400684, maxLength 21. |
| Route object: none | 38.100.184.0/21 | No route object for it. Add a route object with origin AS400684 in the RIR database for the space. |
| ROA: none | 38.100.184.0/24 | No ROA covers it. Add a ROA for AS400684, maxLength 24. |
| Route object: none | 38.100.184.0/24 | No route object for it. A route object for 38.100.184.0/22 with origin AS400684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400684 in the RIR database for the space. |
| ROA: none | 38.100.190.0/24 | No ROA covers it. Add a ROA for AS400684, maxLength 24. |
| Route object: none | 38.100.190.0/24 | No route object for it. A route object for 38.100.190.0/23 with origin AS400684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400684 in the RIR database for the space. |
| ROA: none | 38.100.191.0/24 | No ROA covers it. Add a ROA for AS400684, maxLength 24. |
| Route object: none | 38.100.191.0/24 | No route object for it. A route object for 38.100.190.0/23 with origin AS400684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400684 in the RIR database for the space. |
| ROA: none | 38.100.185.0/24 | No ROA covers it. Add a ROA for AS400684, maxLength 24. |
| Route object: none | 38.100.185.0/24 | No route object for it. A route object for 38.100.184.0/22 with origin AS400684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400684 in the RIR database for the space. |
| ROA: none | 38.100.186.0/24 | No ROA covers it. Add a ROA for AS400684, maxLength 24. |
| Route object: none | 38.100.186.0/24 | No route object for it. A route object for 38.100.184.0/22 with origin AS400684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400684 in the RIR database for the space. |
| ROA: none | 38.100.187.0/24 | No ROA covers it. Add a ROA for AS400684, maxLength 24. |
| Route object: none | 38.100.187.0/24 | No route object for it. A route object for 38.100.184.0/22 with origin AS400684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400684 in the RIR database for the space. |
| ROA: none | 38.100.188.0/24 | No ROA covers it. Add a ROA for AS400684, maxLength 24. |
| Route object: none | 38.100.188.0/24 | No route object for it. A route object for 38.100.188.0/23 with origin AS400684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400684 in the RIR database for the space. |
| ROA: none | 38.100.189.0/24 | No ROA covers it. Add a ROA for AS400684, maxLength 24. |
| Route object: none | 38.100.189.0/24 | No route object for it. A route object for 38.100.188.0/23 with origin AS400684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400684 in the RIR database for the space. |
| Route object: none | 208.75.96.0/22 | No route object for it. A route object for 208.75.96.0/21 with origin AS400684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400684 in the RIR database for the space. |
| Route object: none | 208.75.97.0/24 | No route object for it. A route object for 208.75.96.0/21 with origin AS400684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400684 in the RIR database for the space. |
| Route object: none | 208.75.100.0/22 | No route object for it. A route object for 208.75.96.0/21 with origin AS400684 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400684 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS400684 whose prefix no peer sees AS400684 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.130.244.0/24 | ARIN | Valid |
| 38.100.184.0/22 | ARIN | No ROA |
| 38.100.188.0/23 | ARIN | No ROA |
| 38.100.190.0/23 | ARIN | No ROA |
| 2605:5ec0::/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.