Network · data from 2026-11-12
AS8569 MSYS METRO Digital GmbH
Registry name: MSYS METRO Digital GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS8569, 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.36.0/24 | No ROA | None | 673 100% |
| 164.139.40.0/24 | No ROA | None | 673 100% |
| 164.139.64.0/20 | No ROA | Nonecovered by 164.139.64.0/18 | 673 100% |
| 164.139.84.0/22 | No ROA | Nonecovered by 164.139.64.0/18 | 673 100% |
| 164.139.88.0/21 | No ROA | Nonecovered by 164.139.64.0/18 | 673 100% |
| 164.139.96.0/19 | No ROA | Nonecovered by 164.139.64.0/18 | 673 100% |
| 194.99.212.0/22 | No ROA | Other origin onlycovered by 194.99.192.0/18 | 673 100% |
| 194.156.54.0/23 | No ROA | None | 673 100% |
| 164.139.0.0/16 | No ROA | None | 672 100% |
| 164.139.252.0/22 | No ROA | Other origin only | 672 100% |
| 194.99.232.0/22 | No ROA | Other origin onlycovered by 194.99.192.0/18 | 672 100% |
| 194.99.240.0/22 | No ROA | Other origin onlycovered by 194.99.192.0/18 | 672 100% |
| 164.139.160.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 164.61.0.0/16 | No ROA | RIR databaseRIPE | 672 100% |
| 164.61.128.0/19 | No ROA | RIR databaseRIPE | 672 100% |
| 164.61.160.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 164.61.176.0/20 | No ROA | RIR databaseRIPE | 672 100% |
| 164.61.192.0/18 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.0.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.8.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.16.0/20 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.48.0/20 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.136.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.144.0/20 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.160.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.176.0/20 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.192.0/19 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.224.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.236.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.244.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 164.139.248.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 194.99.160.0/19 | No ROA | RIR databaseRIPE | 672 100% |
| 194.99.192.0/18 | No ROA | RIR databaseRIPE | 672 100% |
| 194.99.192.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 194.99.196.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 194.99.200.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 194.99.208.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 194.99.220.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 194.99.244.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 194.120.192.0/19 | No ROA | RIR databaseRIPE | 672 100% |
| 194.156.32.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 2001:4d20::/34 | No ROA | RIR databaseRIPE | 636 100% |
| 2001:4d20:4000::/34 | No ROA | RIR databaseRIPE | 635 100% |
| 194.99.204.0/22 | No ROA | RIR databaseRIPE | 601 89% |
AS-SET
AS8569 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 61 are in fix.csv.
- ROA: none44
- Route object: none12
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 164.139.36.0/24 | No ROA covers it. Add a ROA for AS8569, maxLength 24. |
| Route object: none | 164.139.36.0/24 | No route object for it. Add a route object with origin AS8569 in the RIR database for the space. |
| ROA: none | 164.139.40.0/24 | No ROA covers it. Add a ROA for AS8569, maxLength 24. |
| Route object: none | 164.139.40.0/24 | No route object for it. Add a route object with origin AS8569 in the RIR database for the space. |
| ROA: none | 164.139.64.0/20 | No ROA covers it. Add a ROA for AS8569, maxLength 20. |
| Route object: none | 164.139.64.0/20 | No route object for it. A route object for 164.139.64.0/18 with origin AS8569 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8569 in the RIR database for the space. |
| ROA: none | 164.139.84.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| Route object: none | 164.139.84.0/22 | No route object for it. A route object for 164.139.64.0/18 with origin AS8569 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8569 in the RIR database for the space. |
| ROA: none | 164.139.88.0/21 | No ROA covers it. Add a ROA for AS8569, maxLength 21. |
| Route object: none | 164.139.88.0/21 | No route object for it. A route object for 164.139.64.0/18 with origin AS8569 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8569 in the RIR database for the space. |
| ROA: none | 164.139.96.0/19 | No ROA covers it. Add a ROA for AS8569, maxLength 19. |
| Route object: none | 164.139.96.0/19 | No route object for it. A route object for 164.139.64.0/18 with origin AS8569 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8569 in the RIR database for the space. |
| ROA: none | 194.99.212.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| Route object: none | 194.99.212.0/22 | Route objects for it name AS18403, AS38010. A route object for 194.99.192.0/18 with origin AS8569 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8569 in the RIR database for the space. |
| ROA: none | 194.156.54.0/23 | No ROA covers it. Add a ROA for AS8569, maxLength 23. |
| Route object: none | 194.156.54.0/23 | No route object for it. Add a route object with origin AS8569 in the RIR database for the space. |
| ROA: none | 164.139.0.0/16 | No ROA covers it. Add a ROA for AS8569, maxLength 16. |
| Route object: none | 164.139.0.0/16 | No route object for it. Add a route object with origin AS8569 in the RIR database for the space. |
| ROA: none | 164.139.252.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| Route object: none | 164.139.252.0/22 | Route objects for it name AS43083. Add a route object with origin AS8569 in the RIR database for the space. |
| ROA: none | 194.99.232.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| Route object: none | 194.99.232.0/22 | Route objects for it name AS35466. A route object for 194.99.192.0/18 with origin AS8569 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8569 in the RIR database for the space. |
| ROA: none | 194.99.240.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| Route object: none | 194.99.240.0/22 | Route objects for it name AS35497. A route object for 194.99.192.0/18 with origin AS8569 covers it (filters allowing more-specifics accept it). Add a route object with origin AS8569 in the RIR database for the space. |
| ROA: none | 164.139.160.0/19 | No ROA covers it. Add a ROA for AS8569, maxLength 19. |
| ROA: none | 164.61.0.0/16 | No ROA covers it. Add a ROA for AS8569, maxLength 16. |
| ROA: none | 164.61.128.0/19 | No ROA covers it. Add a ROA for AS8569, maxLength 19. |
| ROA: none | 164.61.160.0/21 | No ROA covers it. Add a ROA for AS8569, maxLength 21. |
| ROA: none | 164.61.176.0/20 | No ROA covers it. Add a ROA for AS8569, maxLength 20. |
| ROA: none | 164.61.192.0/18 | No ROA covers it. Add a ROA for AS8569, maxLength 18. |
| ROA: none | 164.139.0.0/21 | No ROA covers it. Add a ROA for AS8569, maxLength 21. |
| ROA: none | 164.139.8.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| ROA: none | 164.139.16.0/20 | No ROA covers it. Add a ROA for AS8569, maxLength 20. |
| ROA: none | 164.139.48.0/20 | No ROA covers it. Add a ROA for AS8569, maxLength 20. |
| ROA: none | 164.139.136.0/21 | No ROA covers it. Add a ROA for AS8569, maxLength 21. |
| ROA: none | 164.139.144.0/20 | No ROA covers it. Add a ROA for AS8569, maxLength 20. |
| ROA: none | 164.139.160.0/21 | No ROA covers it. Add a ROA for AS8569, maxLength 21. |
| ROA: none | 164.139.176.0/20 | No ROA covers it. Add a ROA for AS8569, maxLength 20. |
| ROA: none | 164.139.192.0/19 | No ROA covers it. Add a ROA for AS8569, maxLength 19. |
| ROA: none | 164.139.224.0/21 | No ROA covers it. Add a ROA for AS8569, maxLength 21. |
| ROA: none | 164.139.236.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| ROA: none | 164.139.244.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| ROA: none | 164.139.248.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| ROA: none | 194.99.160.0/19 | No ROA covers it. Add a ROA for AS8569, maxLength 19. |
| ROA: none | 194.99.192.0/18 | No ROA covers it. Add a ROA for AS8569, maxLength 18. |
| ROA: none | 194.99.192.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| ROA: none | 194.99.196.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| ROA: none | 194.99.200.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| ROA: none | 194.99.208.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| ROA: none | 194.99.220.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| ROA: none | 194.99.244.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
| ROA: none | 194.120.192.0/19 | No ROA covers it. Add a ROA for AS8569, maxLength 19. |
| ROA: none | 194.156.32.0/21 | No ROA covers it. Add a ROA for AS8569, maxLength 21. |
| ROA: none | 2001:4d20::/34 | No ROA covers it. Add a ROA for AS8569, maxLength 34. |
| ROA: none | 2001:4d20:4000::/34 | No ROA covers it. Add a ROA for AS8569, maxLength 34. |
| ROA: none | 194.99.204.0/22 | No ROA covers it. Add a ROA for AS8569, maxLength 22. |
Route objects not announced
Route objects with origin AS8569 whose prefix no peer sees AS8569 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 164.61.0.0/17 | RIPE | No ROA |
| 164.139.64.0/18 | RIPE | No ROA |
| 194.99.252.0/22 | RIPE | No ROA |
| 194.156.40.0/22 | RIPE | No ROA |
| 194.156.56.0/22 | RIPE | No 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.