Network · data from 2026-11-12
AS393792 2600HZ-AS - 2600hz, Inc
Registry name: 2600HZ-AS - 2600hz, Inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS393792, 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.
| 161.38.208.0/23 | No ROA | Nonecovered by 161.38.208.0/21 | 673 100% |
| 161.38.210.0/23 | No ROA | Nonecovered by 161.38.208.0/21 | 673 100% |
| 161.38.212.0/23 | No ROA | Nonecovered by 161.38.208.0/21 | 673 100% |
| 161.38.214.0/23 | No ROA | Nonecovered by 161.38.208.0/21 | 673 100% |
| 8.45.131.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 8.30.173.0/24 | No ROA | RIR databaseARIN | 668 99% |
| 8.36.70.0/24 | No ROA | RIR databaseARIN | 668 99% |
| 204.141.37.0/24 | Valid | None | 673 100% |
| 204.141.41.0/24 | Valid | None | 673 100% |
| 204.141.97.0/24 | Valid | None | 673 100% |
AS-SET
AS393792 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 17 are in fix.csv.
- ROA: none7
- Route object: none7
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 161.38.208.0/23 | No ROA covers it. Add a ROA for AS393792, maxLength 23. |
| Route object: none | 161.38.208.0/23 | No route object for it. A route object for 161.38.208.0/21 with origin AS393792 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393792 in the RIR database for the space. |
| ROA: none | 161.38.210.0/23 | No ROA covers it. Add a ROA for AS393792, maxLength 23. |
| Route object: none | 161.38.210.0/23 | No route object for it. A route object for 161.38.208.0/21 with origin AS393792 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393792 in the RIR database for the space. |
| ROA: none | 161.38.212.0/23 | No ROA covers it. Add a ROA for AS393792, maxLength 23. |
| Route object: none | 161.38.212.0/23 | No route object for it. A route object for 161.38.208.0/21 with origin AS393792 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393792 in the RIR database for the space. |
| ROA: none | 161.38.214.0/23 | No ROA covers it. Add a ROA for AS393792, maxLength 23. |
| Route object: none | 161.38.214.0/23 | No route object for it. A route object for 161.38.208.0/21 with origin AS393792 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393792 in the RIR database for the space. |
| ROA: none | 8.45.131.0/24 | No ROA covers it. Add a ROA for AS393792, maxLength 24. |
| ROA: none | 8.30.173.0/24 | No ROA covers it. Add a ROA for AS393792, maxLength 24. |
| ROA: none | 8.36.70.0/24 | No ROA covers it. Add a ROA for AS393792, maxLength 24. |
| Route object: none | 204.141.37.0/24 | No route object for it. Add a route object with origin AS393792 in the RIR database for the space. |
| Route object: none | 204.141.41.0/24 | No route object for it. Add a route object with origin AS393792 in the RIR database for the space. |
| Route object: none | 204.141.97.0/24 | No route object for it. Add a route object with origin AS393792 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS393792 whose prefix no peer sees AS393792 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 161.38.208.0/21 | ARIN | No ROA |
| 2602:fcee::/36 | ARIN | No ROA |
| 2602:fcee:ffe::/48 | ARIN | 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.