bgpreport

Network · data from 2026-11-12

AS25864 ZAYO-CLOUD-TOR01 - Latisys-Irvine, LLC

Registry name: ZAYO-CLOUD-TOR01 - Latisys-Irvine, LLC, US · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 100.0% with a route object
2IPv6 routes 50.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS25864, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS25864, 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.
199.246.218.0/24 No ROA Other IRR onlyRADB 673 100% 67
199.246.219.0/24 No ROA Other IRR onlyRADB 673 100% 67
199.246.221.0/24 No ROA Other IRR onlyRADB 673 100% 67
209.151.86.0/24 No ROA Other IRR onlyRADB 673 100% 67
2604:9100:1000::/48 No ROA Other IRR onlyRADB 634 100% 68
2001:4c8:1008::/48 Valid Other IRR onlyRADB 634 100% 68

AS-SET

AS25864 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 11 are in fix.csv.

  • ROA: none5
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none199.246.218.0/24No ROA covers it. Add a ROA for AS25864, maxLength 24.673 of 673
Route object: RIR199.246.218.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.246.219.0/24No ROA covers it. Add a ROA for AS25864, maxLength 24.673 of 673
Route object: RIR199.246.219.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none199.246.221.0/24No ROA covers it. Add a ROA for AS25864, maxLength 24.673 of 673
Route object: RIR199.246.221.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none209.151.86.0/24No ROA covers it. Add a ROA for AS25864, maxLength 24.673 of 673
Route object: RIR209.151.86.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2604:9100:1000::/48No ROA covers it. Add a ROA for AS25864, maxLength 48.634 of 636
Route object: RIR2604:9100:1000::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2001:4c8:1008::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS25864 is announced.

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.