bgpreport

Network · data from 2026-11-12

AS2722 CULR, LLC

Registry name: C-LIGHT - CULR, LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS2722, 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.
205.186.37.0/24 No ROA Nonecovered by 205.186.32.0/19 673 100% 67
199.74.15.0/24 No ROA Other IRR onlyRADB 673 100% 67
205.186.32.0/19 No ROA Other IRR onlyRADB 673 100% 68
205.186.32.0/24 No ROA Other IRR onlyRADB 673 100% 67
192.188.108.0/24 No ROA Other IRR onlyRADB 669 99% 68
2605:4000::/32 No ROA Other IRR onlyRADB 636 100% 68
2602:80a::/40 No ROA Other IRR onlyRADB 634 100% 68

AS-SET

AS2722'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 25 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none205.186.37.0/24No ROA covers it. Add a ROA for AS2722, maxLength 24.673 of 673
Route object: none205.186.37.0/24No route object for it. A route object for 205.186.32.0/19 with origin AS2722 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2722 in the RIR database for the space.673 of 673
ROA: none199.74.15.0/24No ROA covers it. Add a ROA for AS2722, maxLength 24.673 of 673
Route object: RIR199.74.15.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none205.186.32.0/19No ROA covers it. Add a ROA for AS2722, maxLength 19.673 of 673
Route object: RIR205.186.32.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none205.186.32.0/24No ROA covers it. Add a ROA for AS2722, maxLength 24.673 of 673
Route object: RIR205.186.32.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none192.188.108.0/24No ROA covers it. Add a ROA for AS2722, maxLength 24.669 of 673
Route object: RIR192.188.108.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2605:4000::/32No ROA covers it. Add a ROA for AS2722, maxLength 32.636 of 636
Route object: RIR2605:4000::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2602:80a::/40No ROA covers it. Add a ROA for AS2722, maxLength 40.634 of 636
Route object: RIR2602:80a::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

128.23.0.0/16RADBNo ROA
130.127.0.0/16RADBNo ROA
192.251.46.0/23RADBNo ROA
198.21.128.0/17RADBNo ROA
198.102.206.0/24RADBNo ROA
205.186.33.0/24RADBNo ROA
205.186.47.0/24RADBNo ROA
205.186.50.0/24RADBNo ROA
205.186.56.0/23RADBNo ROA
205.186.60.0/24RADBNo ROA
205.186.224.0/19RADBNo 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.