bgpreport

Network · data from 2026-11-12

AS268942 AS268942 - G. PEREIRA NORONHA - ME

Registry name: AS268942 - G. PEREIRA NORONHA - ME, BR · not in PeeringDB

5IPv4 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
8No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS268942, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268942, 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:5cf4::/33 No ROA Nonecovered by 2804:5cf4::/32 328 52% 64
2804:5cf4:8000::/33 No ROA Nonecovered by 2804:5cf4::/32 328 52% 64
45.176.132.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
2804:5cf4::/32 No ROA Other IRR onlyRADB, TC 631 99% 67
45.176.134.0/24 No ROA Other IRR onlyRADB 130 19% 43
45.176.135.0/24 No ROA Other IRR onlyRADB 130 19% 43
45.176.132.0/24 No ROA Other IRR onlyRADB 127 19% 42
45.176.133.0/24 No ROA Other IRR onlyRADB 127 19% 42

AS-SET

AS268942 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 17 are in fix.csv.

  • ROA: none8
  • Route object: none2
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:5cf4::/33No ROA covers it. Add a ROA for AS268942, maxLength 33.328 of 636
Route object: none2804:5cf4::/33No route object for it. A route object for 2804:5cf4::/32 with origin AS268942 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268942 in the RIR database for the space.328 of 636
ROA: none2804:5cf4:8000::/33No ROA covers it. Add a ROA for AS268942, maxLength 33.328 of 636
Route object: none2804:5cf4:8000::/33No route object for it. A route object for 2804:5cf4::/32 with origin AS268942 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268942 in the RIR database for the space.328 of 636
ROA: none45.176.132.0/22No ROA covers it. Add a ROA for AS268942, maxLength 22.671 of 673
Route object: RIR45.176.132.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:5cf4::/32No ROA covers it. Add a ROA for AS268942, maxLength 32.631 of 636
Route object: RIR2804:5cf4::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none45.176.134.0/24No ROA covers it. Add a ROA for AS268942, maxLength 24.130 of 673
Route object: RIR45.176.134.0/24Route object only in RADB. Add it in the RIR database for the space.130 of 673
ROA: none45.176.135.0/24No ROA covers it. Add a ROA for AS268942, maxLength 24.130 of 673
Route object: RIR45.176.135.0/24Route object only in RADB. Add it in the RIR database for the space.130 of 673
ROA: none45.176.132.0/24No ROA covers it. Add a ROA for AS268942, maxLength 24.127 of 673
Route object: RIR45.176.132.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
ROA: none45.176.133.0/24No ROA covers it. Add a ROA for AS268942, maxLength 24.127 of 673
Route object: RIR45.176.133.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673

Route objects not announced

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

2804:5cf4::/36RADBNo 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.