bgpreport

Network · data from 2026-11-12

AS262188 AS262188 - Satel NV

Registry name: AS262188 - Satel NV, BQ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262188, 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.

190.2.176.0/24 No ROA None 671 100% 67
190.2.177.0/24 No ROA None 671 100% 67
190.2.178.0/24 No ROA None 671 100% 67
190.2.179.0/24 No ROA None 671 100% 67
190.97.112.0/24 Valid Nonecovered by 190.97.112.0/21 670 100% 67
190.97.113.0/24 Valid Nonecovered by 190.97.112.0/21 670 100% 67
190.97.114.0/24 Valid Nonecovered by 190.97.112.0/21 670 100% 67
190.97.115.0/24 Valid Nonecovered by 190.97.112.0/21 670 100% 67
190.97.116.0/24 Valid Nonecovered by 190.97.112.0/21 670 100% 67
190.97.117.0/24 Valid Nonecovered by 190.97.112.0/21 670 100% 67
190.97.118.0/24 Valid Nonecovered by 190.97.112.0/21 670 100% 67
190.97.119.0/24 Valid Nonecovered by 190.97.112.0/21 670 100% 67

AS-SET

AS262188 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: none4
  • Route object: none12
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none190.2.176.0/24No ROA covers it. Add a ROA for AS262188, maxLength 24.671 of 673
Route object: none190.2.176.0/24No route object for it. Add a route object with origin AS262188 in the RIR database for the space.671 of 673
ROA: none190.2.177.0/24No ROA covers it. Add a ROA for AS262188, maxLength 24.671 of 673
Route object: none190.2.177.0/24No route object for it. Add a route object with origin AS262188 in the RIR database for the space.671 of 673
ROA: none190.2.178.0/24No ROA covers it. Add a ROA for AS262188, maxLength 24.671 of 673
Route object: none190.2.178.0/24No route object for it. Add a route object with origin AS262188 in the RIR database for the space.671 of 673
ROA: none190.2.179.0/24No ROA covers it. Add a ROA for AS262188, maxLength 24.671 of 673
Route object: none190.2.179.0/24No route object for it. Add a route object with origin AS262188 in the RIR database for the space.671 of 673
Route object: none190.97.112.0/24No route object for it. A route object for 190.97.112.0/21 with origin AS262188 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262188 in the RIR database for the space.670 of 673
Route object: none190.97.113.0/24No route object for it. A route object for 190.97.112.0/21 with origin AS262188 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262188 in the RIR database for the space.670 of 673
Route object: none190.97.114.0/24No route object for it. A route object for 190.97.112.0/21 with origin AS262188 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262188 in the RIR database for the space.670 of 673
Route object: none190.97.115.0/24No route object for it. A route object for 190.97.112.0/21 with origin AS262188 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262188 in the RIR database for the space.670 of 673
Route object: none190.97.116.0/24No route object for it. A route object for 190.97.112.0/21 with origin AS262188 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262188 in the RIR database for the space.670 of 673
Route object: none190.97.117.0/24No route object for it. A route object for 190.97.112.0/21 with origin AS262188 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262188 in the RIR database for the space.670 of 673
Route object: none190.97.118.0/24No route object for it. A route object for 190.97.112.0/21 with origin AS262188 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262188 in the RIR database for the space.670 of 673
Route object: none190.97.119.0/24No route object for it. A route object for 190.97.112.0/21 with origin AS262188 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262188 in the RIR database for the space.670 of 673

Route objects not announced

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

190.97.112.0/21LACNIC, RADBValid

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.