bgpreport

Network · data from 2026-11-12

AS6950 LAMBDA - Lambda Telecom

Registry name: LAMBDA - Lambda Telecom, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS6950, 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.
192.77.144.0/24 No ROA Other IRR onlyBBOI 666 99% 67
192.206.124.0/24 No ROA Other IRR onlyBBOI 666 99% 67
198.178.225.0/24 No ROA Other IRR onlyBBOI 666 99% 67
198.183.206.0/23 No ROA Other IRR onlyBBOI 666 99% 67
198.183.208.0/23 No ROA Other IRR onlyBBOI 666 99% 67
192.152.115.0/24 No ROA Other IRR onlyBBOI 2 0%low visibility 2
198.49.251.0/24 No ROA Other IRR onlyBBOI 2 0%low visibility 2

AS-SET

AS6950 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 15 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none192.77.144.0/24No ROA covers it. Add a ROA for AS6950, maxLength 24.666 of 673
Route object: RIR192.77.144.0/24Route object only in BBOI. Add it in the RIR database for the space.666 of 673
ROA: none192.206.124.0/24No ROA covers it. Add a ROA for AS6950, maxLength 24.666 of 673
Route object: RIR192.206.124.0/24Route object only in BBOI. Add it in the RIR database for the space.666 of 673
ROA: none198.178.225.0/24No ROA covers it. Add a ROA for AS6950, maxLength 24.666 of 673
Route object: RIR198.178.225.0/24Route object only in BBOI. Add it in the RIR database for the space.666 of 673
ROA: none198.183.206.0/23No ROA covers it. Add a ROA for AS6950, maxLength 23.666 of 673
Route object: RIR198.183.206.0/23Route object only in BBOI. Add it in the RIR database for the space.666 of 673
ROA: none198.183.208.0/23No ROA covers it. Add a ROA for AS6950, maxLength 23.666 of 673
Route object: RIR198.183.208.0/23Route object only in BBOI. Add it in the RIR database for the space.666 of 673
ROA: none192.152.115.0/24No ROA covers it. Add a ROA for AS6950, maxLength 24.2 of 673
Route object: RIR192.152.115.0/24Route object only in BBOI. Add it in the RIR database for the space.2 of 673
ROA: none198.49.251.0/24No ROA covers it. Add a ROA for AS6950, maxLength 24.2 of 673
Route object: RIR198.49.251.0/24Route object only in BBOI. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

206.82.240.0/21BBOINo 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.