Network · data from 2026-11-12
AS211095 MBS-Usingen MBS Operations GmbH
Registry name: MBS-Usingen MBS Operations GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS211095, 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.
| 145.249.96.0/24 | No ROA | Nonecovered by 145.249.96.0/21 | 673 100% |
| 185.237.134.0/24 | No ROA | Nonecovered by 185.237.132.0/22 | 673 100% |
| 185.237.135.0/24 | No ROA | Nonecovered by 185.237.132.0/22 | 673 100% |
| 45.143.228.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 78.41.26.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 145.249.96.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 185.87.220.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.87.222.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 185.87.222.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.193.108.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.237.132.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.87.223.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a12:7ec0::/29 | No ROA | RIR databaseRIPE | 631 99% |
AS-SET
AS211095 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 19 are in fix.csv.
- ROA: none13
- Route object: none3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 145.249.96.0/24 | No ROA covers it. Add a ROA for AS211095, maxLength 24. |
| Route object: none | 145.249.96.0/24 | No route object for it. A route object for 145.249.96.0/21 with origin AS211095 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211095 in the RIR database for the space. |
| ROA: none | 185.237.134.0/24 | No ROA covers it. Add a ROA for AS211095, maxLength 24. |
| Route object: none | 185.237.134.0/24 | No route object for it. A route object for 185.237.132.0/22 with origin AS211095 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211095 in the RIR database for the space. |
| ROA: none | 185.237.135.0/24 | No ROA covers it. Add a ROA for AS211095, maxLength 24. |
| Route object: none | 185.237.135.0/24 | No route object for it. A route object for 185.237.132.0/22 with origin AS211095 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211095 in the RIR database for the space. |
| ROA: none | 45.143.228.0/22 | No ROA covers it. Add a ROA for AS211095, maxLength 22. |
| ROA: none | 78.41.26.0/24 | No ROA covers it. Add a ROA for AS211095, maxLength 24. |
| ROA: none | 145.249.96.0/21 | No ROA covers it. Add a ROA for AS211095, maxLength 21. |
| ROA: none | 185.87.220.0/23 | No ROA covers it. Add a ROA for AS211095, maxLength 23. |
| ROA: none | 185.87.222.0/23 | No ROA covers it. Add a ROA for AS211095, maxLength 23. |
| ROA: none | 185.87.222.0/24 | No ROA covers it. Add a ROA for AS211095, maxLength 24. |
| ROA: none | 185.193.108.0/24 | No ROA covers it. Add a ROA for AS211095, maxLength 24. |
| ROA: none | 185.237.132.0/22 | No ROA covers it. Add a ROA for AS211095, maxLength 22. |
| ROA: none | 185.87.223.0/24 | No ROA covers it. Add a ROA for AS211095, maxLength 24. |
| ROA: none | 2a12:7ec0::/29 | No ROA covers it. Add a ROA for AS211095, maxLength 29. |
Route objects not announced
Route objects with origin AS211095 whose prefix no peer sees AS211095 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.68.234.0/24 | RIPE | Valid |
| 185.68.235.0/24 | RIPE | Valid |
| 185.87.220.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.