Network · data from 2026-11-12
AS29085 PORSCHE-AS Porsche Informatik Gesellschaft m.b.H
Registry name: PORSCHE-AS Porsche Informatik Gesellschaft m.b.H, AT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29085, 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.
| 2a06:7040::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 185.116.28.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.116.28.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.116.29.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.116.30.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.116.31.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.109.74.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.109.74.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.109.75.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.183.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS29085 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 1 are in fix.csv.
- ROA: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a06:7040::/48 | No ROA covers it. Add a ROA for AS29085, maxLength 48. |
Route objects not announced
Every route object with origin AS29085 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.