bgpreport

Network · data from 2026-11-12

AS200567 mdex

Registry name: MDEX Wireless Logic mdex GmbH, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200567, 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.
185.39.176.0/24 Valid Nonecovered by 185.39.176.0/23 673 100% 66
2a05:2a80::/32 Valid Nonecovered by 2a05:2a80::/29 635 100% 67
2a05:2a80:1::/48 Valid Nonecovered by 2a05:2a80::/29 635 100% 67
45.146.132.0/22 Valid RIR databaseRIPE 673 100% 66
46.16.216.0/22 Valid RIR databaseRIPE 673 100% 66
46.16.216.0/23 Valid RIR databaseRIPE 673 100% 66
46.16.218.0/23 Valid RIR databaseRIPE 673 100% 66
46.16.220.0/22 Valid RIR databaseRIPE 673 100% 66
46.16.220.0/23 Valid RIR databaseRIPE 673 100% 66
46.16.222.0/23 Valid RIR databaseRIPE 673 100% 66
185.39.176.0/23 Valid RIR databaseRIPE 673 100% 66
185.39.178.0/23 Valid RIR databaseRIPE 673 100% 66
185.70.144.0/23 Valid RIR databaseRIPE 673 100% 66
185.70.146.0/23 Valid RIR databaseRIPE 673 100% 66
185.109.32.0/23 Valid RIR databaseRIPE 673 100% 66
185.109.34.0/23 Valid RIR databaseRIPE 673 100% 66
192.109.223.0/24 Valid RIR databaseRIPE 673 100% 66
192.109.231.0/24 Valid RIR databaseRIPE 673 100% 66
192.109.235.0/24 Valid RIR databaseRIPE 673 100% 66
192.109.239.0/24 Valid RIR databaseRIPE 673 100% 66
2a02:4500::/32 Valid RIR databaseRIPE 635 100% 67
2a05:2a80::/29 Valid RIR databaseRIPE 634 100% 67
2a06:4e40::/29 Valid RIR databaseRIPE 634 100% 67
2a0f:1000::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS200567'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 6 are in fix.csv.

  • Route object: none3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none185.39.176.0/24No route object for it. A route object for 185.39.176.0/23 with origin AS200567 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200567 in the RIR database for the space.673 of 673
Route object: none2a05:2a80::/32No route object for it. A route object for 2a05:2a80::/29 with origin AS200567 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200567 in the RIR database for the space.635 of 636
Route object: none2a05:2a80:1::/48No route object for it. A route object for 2a05:2a80::/29 with origin AS200567 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200567 in the RIR database for the space.635 of 636

Route objects not announced

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

185.39.176.0/22RIPENo ROA
185.70.144.0/22RIPENo ROA
185.109.32.0/22RIPENo 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.