Network · data from 2026-11-12
AS42873 MPG-FR-S Max-Planck-Gesellschaft zur Forderung der Wissenschaften e.V.
Registry name: MPG-FR-S Max-Planck-Gesellschaft zur Forderung der Wissenschaften e.V., DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42873, 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.
| 134.105.0.0/16 | No ROA | RIR databaseRIPE | 673 100% |
| 192.124.25.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 192.124.26.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 192.124.28.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 134.107.202.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 192.129.30.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a02:d480:240::/42 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS42873 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 6 are in fix.csv.
- ROA: none4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 134.105.0.0/16 | No ROA covers it. Add a ROA for AS42873, maxLength 16. |
| ROA: none | 192.124.25.0/24 | No ROA covers it. Add a ROA for AS42873, maxLength 24. |
| ROA: none | 192.124.26.0/23 | No ROA covers it. Add a ROA for AS42873, maxLength 23. |
| ROA: none | 192.124.28.0/24 | No ROA covers it. Add a ROA for AS42873, maxLength 24. |
Route objects not announced
Route objects with origin AS42873 whose prefix no peer sees AS42873 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 134.107.195.0/24 | RIPE | Invalid: origin |
| 193.196.12.0/24 | RIPE | Valid |
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.