bgpreport

Network · data from 2026-11-12

AS269376 AS269376 - JETFIBER SERVICOS DE COMUNICACAO MULTIMIDIA EIRELI

Registry name: AS269376 - JETFIBER SERVICOS DE COMUNICACAO MULTIMIDIA EIRELI, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269376, 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.
2804:63ac::/33 No ROA Nonecovered by 2804:63ac::/32 636 100% 67
2804:63ac:8000::/33 No ROA Nonecovered by 2804:63ac::/32 636 100% 67
45.185.132.0/23 No ROA Other IRR onlyRADB 672 100% 67
45.185.134.0/23 No ROA Other IRR onlyRADB 672 100% 67
45.185.135.0/24 No ROA Other IRR onlyRADB 670 100% 67
45.185.132.0/24 No ROA Other IRR onlyRADB 669 99% 67
45.185.133.0/24 No ROA Other IRR onlyRADB 669 99% 67
45.185.134.0/24 No ROA Other IRR onlyRADB 669 99% 67
45.185.132.0/22 No ROA Other IRR onlyRADB 668 99% 67
2804:63ac::/32 No ROA Other IRR onlyRADB 635 100% 69

AS-SET

AS269376 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 20 are in fix.csv.

  • ROA: none10
  • Route object: none2
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none2804:63ac::/33No ROA covers it. Add a ROA for AS269376, maxLength 33.636 of 636
Route object: none2804:63ac::/33No route object for it. A route object for 2804:63ac::/32 with origin AS269376 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269376 in the RIR database for the space.636 of 636
ROA: none2804:63ac:8000::/33No ROA covers it. Add a ROA for AS269376, maxLength 33.636 of 636
Route object: none2804:63ac:8000::/33No route object for it. A route object for 2804:63ac::/32 with origin AS269376 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269376 in the RIR database for the space.636 of 636
ROA: none45.185.132.0/23No ROA covers it. Add a ROA for AS269376, maxLength 23.672 of 673
Route object: RIR45.185.132.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.185.134.0/23No ROA covers it. Add a ROA for AS269376, maxLength 23.672 of 673
Route object: RIR45.185.134.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.185.135.0/24No ROA covers it. Add a ROA for AS269376, maxLength 24.670 of 673
Route object: RIR45.185.135.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.185.132.0/24No ROA covers it. Add a ROA for AS269376, maxLength 24.669 of 673
Route object: RIR45.185.132.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none45.185.133.0/24No ROA covers it. Add a ROA for AS269376, maxLength 24.669 of 673
Route object: RIR45.185.133.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none45.185.134.0/24No ROA covers it. Add a ROA for AS269376, maxLength 24.669 of 673
Route object: RIR45.185.134.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none45.185.132.0/22No ROA covers it. Add a ROA for AS269376, maxLength 22.668 of 673
Route object: RIR45.185.132.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:63ac::/32No ROA covers it. Add a ROA for AS269376, maxLength 32.635 of 636
Route object: RIR2804:63ac::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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