bgpreport

Network · data from 2026-11-12

AS269603 AS269603 - lynn telecom

Registry name: AS269603 - lynn telecom, BR · not in PeeringDB

7IPv4 routes 0.0% RPKI valid · 100.0% with a route object
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No 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 AS269603, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269603, 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.
45.189.248.0/22 No ROA Other IRR onlyBBOI, RADB, TC 671 100% 67
45.189.248.0/23 No ROA Other IRR onlyTC 671 100% 67
45.189.248.0/24 No ROA Other IRR onlyTC 671 100% 67
45.189.249.0/24 No ROA Other IRR onlyTC 671 100% 67
45.189.250.0/23 No ROA Other IRR onlyTC 671 100% 67
45.189.250.0/24 No ROA Other IRR onlyTC 671 100% 67
45.189.251.0/24 No ROA Other IRR onlyTC 671 100% 67
2804:6718::/32 No ROA Other IRR onlyBBOI, RADB, TC 636 100% 67
2804:6718:8000::/33 No ROA Other IRR onlyTC 636 100% 67

AS-SET

AS269603 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: none45.189.248.0/22No ROA covers it. Add a ROA for AS269603, maxLength 22.671 of 673
Route object: RIR45.189.248.0/22Route object only in BBOI, RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none45.189.248.0/23No ROA covers it. Add a ROA for AS269603, maxLength 23.671 of 673
Route object: RIR45.189.248.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none45.189.248.0/24No ROA covers it. Add a ROA for AS269603, maxLength 24.671 of 673
Route object: RIR45.189.248.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none45.189.249.0/24No ROA covers it. Add a ROA for AS269603, maxLength 24.671 of 673
Route object: RIR45.189.249.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none45.189.250.0/23No ROA covers it. Add a ROA for AS269603, maxLength 23.671 of 673
Route object: RIR45.189.250.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none45.189.250.0/24No ROA covers it. Add a ROA for AS269603, maxLength 24.671 of 673
Route object: RIR45.189.250.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none45.189.251.0/24No ROA covers it. Add a ROA for AS269603, maxLength 24.671 of 673
Route object: RIR45.189.251.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:6718::/32No ROA covers it. Add a ROA for AS269603, maxLength 32.636 of 636
Route object: RIR2804:6718::/32Route object only in BBOI, RADB, TC. Add it in the RIR database for the space.636 of 636
ROA: none2804:6718:8000::/33No ROA covers it. Add a ROA for AS269603, maxLength 33.636 of 636
Route object: RIR2804:6718:8000::/33Route object only in TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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