bgpreport

Network · data from 2026-11-12

AS41728 MGE Mangas Gambling Engineering SARL

Registry name: MGE Mangas Gambling Engineering SARL, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS41728, 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.
194.37.250.0/24 Valid Nonecovered by 194.37.250.0/23 2 0%low visibility 2
194.37.251.0/24 Valid Nonecovered by 194.37.250.0/23 2 0%low visibility 2
194.37.250.0/23 Valid RIR databaseRIPE 2 0%low visibility 2
194.39.78.0/23 Valid RIR databaseRIPE 2 0%low visibility 2
194.39.78.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
194.39.79.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none194.37.250.0/24No route object for it. A route object for 194.37.250.0/23 with origin AS41728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41728 in the RIR database for the space.2 of 673
Route object: none194.37.251.0/24No route object for it. A route object for 194.37.250.0/23 with origin AS41728 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41728 in the RIR database for the space.2 of 673

Route objects not announced

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