bgpreport

Network · data from 2026-11-12

AS39290 MGI-DE-AS METRO Digital GmbH

Registry name: MGI-DE-AS METRO Digital GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39290, 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.
164.139.34.0/24 No ROA Nonecovered by 164.139.32.0/20 673 100% 67
164.139.80.0/22 No ROA None 673 100% 67
194.156.40.0/22 No ROA Other origin only 673 100% 67
194.156.56.0/22 No ROA Other origin only 672 100% 67
164.139.32.0/20 No ROA RIR databaseRIPE 673 100% 67
194.156.48.0/21 No ROA RIR databaseRIPE 673 100% 67
164.61.168.0/21 No ROA RIR databaseRIPE 672 100% 67
164.139.12.0/22 No ROA RIR databaseRIPE 672 100% 67
164.139.128.0/21 No ROA RIR databaseRIPE 672 100% 67
164.139.168.0/21 No ROA RIR databaseRIPE 672 100% 67
2001:4d20:c000::/34 No ROA RIR databaseRIPE 636 100% 67
2001:4d20:8000::/34 No ROA RIR databaseRIPE 635 100% 67
194.99.204.0/22 No ROA RIR databaseRIPE 21 3%low visibility 12

AS-SET

AS39290 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: none13
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: none164.139.34.0/24No ROA covers it. Add a ROA for AS39290, maxLength 24.673 of 673
Route object: none164.139.34.0/24No route object for it. A route object for 164.139.32.0/20 with origin AS39290 covers it (filters allowing more-specifics accept it). Add a route object with origin AS39290 in the RIR database for the space.673 of 673
ROA: none164.139.80.0/22No ROA covers it. Add a ROA for AS39290, maxLength 22.673 of 673
Route object: none164.139.80.0/22No route object for it. Add a route object with origin AS39290 in the RIR database for the space.673 of 673
ROA: none194.156.40.0/22No ROA covers it. Add a ROA for AS39290, maxLength 22.673 of 673
Route object: none194.156.40.0/22Route objects for it name AS8569. Add a route object with origin AS39290 in the RIR database for the space.673 of 673
ROA: none194.156.56.0/22No ROA covers it. Add a ROA for AS39290, maxLength 22.672 of 673
Route object: none194.156.56.0/22Route objects for it name AS8569. Add a route object with origin AS39290 in the RIR database for the space.672 of 673
ROA: none164.139.32.0/20No ROA covers it. Add a ROA for AS39290, maxLength 20.673 of 673
ROA: none194.156.48.0/21No ROA covers it. Add a ROA for AS39290, maxLength 21.673 of 673
ROA: none164.61.168.0/21No ROA covers it. Add a ROA for AS39290, maxLength 21.672 of 673
ROA: none164.139.12.0/22No ROA covers it. Add a ROA for AS39290, maxLength 22.672 of 673
ROA: none164.139.128.0/21No ROA covers it. Add a ROA for AS39290, maxLength 21.672 of 673
ROA: none164.139.168.0/21No ROA covers it. Add a ROA for AS39290, maxLength 21.672 of 673
ROA: none2001:4d20:c000::/34No ROA covers it. Add a ROA for AS39290, maxLength 34.636 of 636
ROA: none2001:4d20:8000::/34No ROA covers it. Add a ROA for AS39290, maxLength 34.635 of 636
ROA: none194.99.204.0/22No ROA covers it. Add a ROA for AS39290, maxLength 22.21 of 673

Route objects not announced

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