bgpreport

Network · data from 2026-11-12

AS197465 MBQT Sierra Wireless France SAS

Registry name: MBQT Sierra Wireless France SAS, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS197465, 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.
46.23.241.0/24 Valid Nonecovered by 46.23.240.0/20 672 100% 67
46.23.242.0/24 Valid Nonecovered by 46.23.240.0/20 672 100% 67
46.23.244.0/24 Valid Nonecovered by 46.23.240.0/20 672 100% 67
46.23.245.0/24 Valid Nonecovered by 46.23.240.0/20 672 100% 67
46.23.248.0/24 Valid Nonecovered by 46.23.240.0/20 672 100% 67
46.23.249.0/24 Valid Nonecovered by 46.23.240.0/20 672 100% 67
2a02:5000::/32 Valid None 635 100% 68
46.23.240.0/20 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • Route object: none7
ChangePrefix or setDetailFull-table peers
Route object: none46.23.241.0/24No route object for it. A route object for 46.23.240.0/20 with origin AS197465 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197465 in the RIR database for the space.672 of 673
Route object: none46.23.242.0/24No route object for it. A route object for 46.23.240.0/20 with origin AS197465 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197465 in the RIR database for the space.672 of 673
Route object: none46.23.244.0/24No route object for it. A route object for 46.23.240.0/20 with origin AS197465 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197465 in the RIR database for the space.672 of 673
Route object: none46.23.245.0/24No route object for it. A route object for 46.23.240.0/20 with origin AS197465 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197465 in the RIR database for the space.672 of 673
Route object: none46.23.248.0/24No route object for it. A route object for 46.23.240.0/20 with origin AS197465 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197465 in the RIR database for the space.672 of 673
Route object: none46.23.249.0/24No route object for it. A route object for 46.23.240.0/20 with origin AS197465 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197465 in the RIR database for the space.672 of 673
Route object: none2a02:5000::/32No route object for it. Add a route object with origin AS197465 in the RIR database for the space.635 of 636

Route objects not announced

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