bgpreport

Network · data from 2026-11-12

AS268030 J R BOLDRINI INFORMATICA

Registry name: AS268030 - J R BOLDRINI INFORMATICA ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268030, 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.168.56.0/23 No ROA Nonecovered by 45.168.56.0/22 671 100% 67
45.168.58.0/23 No ROA Nonecovered by 45.168.56.0/22 671 100% 67
45.168.56.0/24 No ROA Nonecovered by 45.168.56.0/22 669 99% 67
45.168.57.0/24 No ROA Nonecovered by 45.168.56.0/22 668 99% 67
45.168.58.0/24 No ROA Nonecovered by 45.168.56.0/22 668 99% 67
45.168.56.0/22 No ROA Other IRR onlyTC 671 100% 67

AS-SET

AS268030's PeeringDB record names no 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 13 are in fix.csv.

  • ROA: none6
  • Route object: none5
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none45.168.56.0/23No ROA covers it. Add a ROA for AS268030, maxLength 23.671 of 673
Route object: none45.168.56.0/23No route object for it. A route object for 45.168.56.0/22 with origin AS268030 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268030 in the RIR database for the space.671 of 673
ROA: none45.168.58.0/23No ROA covers it. Add a ROA for AS268030, maxLength 23.671 of 673
Route object: none45.168.58.0/23No route object for it. A route object for 45.168.56.0/22 with origin AS268030 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268030 in the RIR database for the space.671 of 673
ROA: none45.168.56.0/24No ROA covers it. Add a ROA for AS268030, maxLength 24.669 of 673
Route object: none45.168.56.0/24No route object for it. A route object for 45.168.56.0/22 with origin AS268030 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268030 in the RIR database for the space.669 of 673
ROA: none45.168.57.0/24No ROA covers it. Add a ROA for AS268030, maxLength 24.668 of 673
Route object: none45.168.57.0/24No route object for it. A route object for 45.168.56.0/22 with origin AS268030 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268030 in the RIR database for the space.668 of 673
ROA: none45.168.58.0/24No ROA covers it. Add a ROA for AS268030, maxLength 24.668 of 673
Route object: none45.168.58.0/24No route object for it. A route object for 45.168.56.0/22 with origin AS268030 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268030 in the RIR database for the space.668 of 673
ROA: none45.168.56.0/22No ROA covers it. Add a ROA for AS268030, maxLength 22.671 of 673
Route object: RIR45.168.56.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

2804:56e4::/32TCNo 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.