bgpreport

Network · data from 2026-11-12

AS22984 ECC-65 - Lightspeed Communications

Registry name: ECC-65 - Lightspeed Communications, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22984, 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.
64.128.100.0/24 No ROA Other IRR onlyRADB 672 100% 67
64.128.167.0/24 No ROA Other IRR onlyRADB 672 100% 67
64.132.178.0/23 No ROA Other IRR onlyRADB 672 100% 67
66.192.194.0/24 No ROA Other IRR onlyRADB 672 100% 67
168.215.98.0/24 No ROA Other IRR onlyRADB 672 100% 67
168.215.103.0/24 No ROA Other IRR onlyRADB 672 100% 67
64.128.101.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
66.162.71.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
66.192.195.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS22984 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 18 are in fix.csv.

  • ROA: none9
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none64.128.100.0/24No ROA covers it. Add a ROA for AS22984, maxLength 24.672 of 673
Route object: RIR64.128.100.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none64.128.167.0/24No ROA covers it. Add a ROA for AS22984, maxLength 24.672 of 673
Route object: RIR64.128.167.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none64.132.178.0/23No ROA covers it. Add a ROA for AS22984, maxLength 23.672 of 673
Route object: RIR64.132.178.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none66.192.194.0/24No ROA covers it. Add a ROA for AS22984, maxLength 24.672 of 673
Route object: RIR66.192.194.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none168.215.98.0/24No ROA covers it. Add a ROA for AS22984, maxLength 24.672 of 673
Route object: RIR168.215.98.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none168.215.103.0/24No ROA covers it. Add a ROA for AS22984, maxLength 24.672 of 673
Route object: RIR168.215.103.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none64.128.101.0/24No ROA covers it. Add a ROA for AS22984, maxLength 24.2 of 673
Route object: RIR64.128.101.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none66.162.71.0/24No ROA covers it. Add a ROA for AS22984, maxLength 24.2 of 673
Route object: RIR66.162.71.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none66.192.195.0/24No ROA covers it. Add a ROA for AS22984, maxLength 24.2 of 673
Route object: RIR66.192.195.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS22984 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.