Network · data from 2026-11-12
AS62021 LATISYS-DENVER Zayo Group, LLC
Registry name: LATISYS-DENVER Zayo Group, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62021, 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.
| 79.141.37.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 94.31.28.0/24 | Valid | Other IRR onlyRADB | 672 100% |
AS-SET
AS62021 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 5 are in fix.csv.
- Route object: RIR2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 79.141.37.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 94.31.28.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS62021 whose prefix no peer sees AS62021 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.51.4.0/22 | RADB | No ROA |
| 209.197.228.0/22 | RADB | No ROA |
| 2a01:a9e0::/32 | 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.