bgpreport

Network · data from 2026-11-12

AS30008 ColoGuys

Registry name: COLOGUYS - ColoGuys, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30008, 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.
209.135.16.0/20 No ROA Other IRR onlyALTDB 670 100% 68

AS-SET

AS30008's PeeringDB record names no 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 12 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none209.135.16.0/20No ROA covers it. Add a ROA for AS30008, maxLength 20.670 of 673
Route object: RIR209.135.16.0/20Route object only in ALTDB. Add it in the RIR database for the space.670 of 673

Route objects not announced

Route objects with origin AS30008 whose prefix no peer sees AS30008 announce. Many are kept on purpose (backup routes, space announced only in some places).

64.209.56.0/21ARINNo ROA
64.209.68.0/22ARINNo ROA
64.214.184.0/21ARINNo ROA
66.207.160.0/20ARINNo ROA
67.43.48.0/20ARIN, RADBNo ROA
72.5.250.0/24RADBNo ROA
207.126.64.0/19ALTDBNo ROA
209.130.152.0/22ARINNo ROA
209.135.0.0/19ALTDBNo ROA
2001:49e8::/32ARINNo 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.