bgpreport

Network · data from 2026-11-12

AS269587 OMEGA PROVEDOR E SERVIÇOS DE INTERNET

Registry name: AS269587 - OMEGA PROVEDOR E SERVICOS DE INTERNET EIRELI-ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269587, 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.188.80.0/23 No ROA Nonecovered by 45.188.80.0/22 670 100% 67
45.188.80.0/24 No ROA Nonecovered by 45.188.80.0/22 670 100% 67
45.188.81.0/24 No ROA Nonecovered by 45.188.80.0/22 670 100% 67
2804:66dc::/33 No ROA Nonecovered by 2804:66dc::/32 633 100% 67
2804:66dc:8100::/40 No ROA Nonecovered by 2804:66dc::/32 633 100% 67
45.188.83.0/24 Valid Nonecovered by 45.188.80.0/22 671 100% 67
45.188.82.0/24 Valid Nonecovered by 45.188.80.0/22 667 99% 67

AS-SET

AS269587'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 14 are in fix.csv.

  • ROA: none5
  • Route object: none7
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.188.80.0/23No ROA covers it. Add a ROA for AS269587, maxLength 23.670 of 673
Route object: none45.188.80.0/23No route object for it. A route object for 45.188.80.0/22 with origin AS269587 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269587 in the RIR database for the space.670 of 673
ROA: none45.188.80.0/24No ROA covers it. Add a ROA for AS269587, maxLength 24.670 of 673
Route object: none45.188.80.0/24No route object for it. A route object for 45.188.80.0/22 with origin AS269587 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269587 in the RIR database for the space.670 of 673
ROA: none45.188.81.0/24No ROA covers it. Add a ROA for AS269587, maxLength 24.670 of 673
Route object: none45.188.81.0/24No route object for it. A route object for 45.188.80.0/22 with origin AS269587 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269587 in the RIR database for the space.670 of 673
ROA: none2804:66dc::/33No ROA covers it. Add a ROA for AS269587, maxLength 33.633 of 636
Route object: none2804:66dc::/33No route object for it. A route object for 2804:66dc::/32 with origin AS269587 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269587 in the RIR database for the space.633 of 636
ROA: none2804:66dc:8100::/40No ROA covers it. Add a ROA for AS269587, maxLength 40.633 of 636
Route object: none2804:66dc:8100::/40No route object for it. A route object for 2804:66dc::/32 with origin AS269587 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269587 in the RIR database for the space.633 of 636
Route object: none45.188.83.0/24No route object for it. A route object for 45.188.80.0/22 with origin AS269587 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269587 in the RIR database for the space.671 of 673
Route object: none45.188.82.0/24No route object for it. A route object for 45.188.80.0/22 with origin AS269587 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269587 in the RIR database for the space.667 of 673

Route objects not announced

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

45.188.80.0/22RADB, TCNo ROA
2804:66dc::/32RADB, TCNo 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.