Network · data from 2026-11-12
AS48151 Red Bull GmbH
Registry name: REDBULL-AS Red Bull GmbH, AT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48151, 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.
| 91.204.192.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 91.204.192.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.204.193.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.204.194.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.204.195.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2001:67c:23d8::/47 | No ROA | RIR databaseRIPE | 636 100% |
AS-SET
AS48151'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 8 are in fix.csv.
- ROA: none6
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.204.192.0/22 | No ROA covers it. Add a ROA for AS48151, maxLength 22. |
| ROA: none | 91.204.192.0/24 | No ROA covers it. Add a ROA for AS48151, maxLength 24. |
| ROA: none | 91.204.193.0/24 | No ROA covers it. Add a ROA for AS48151, maxLength 24. |
| ROA: none | 91.204.194.0/24 | No ROA covers it. Add a ROA for AS48151, maxLength 24. |
| ROA: none | 91.204.195.0/24 | No ROA covers it. Add a ROA for AS48151, maxLength 24. |
| ROA: none | 2001:67c:23d8::/47 | No ROA covers it. Add a ROA for AS48151, maxLength 47. |
Route objects not announced
Route objects with origin AS48151 whose prefix no peer sees AS48151 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:67c:23d8::/48 | RIPE | No ROA |
| 2001:67c:23d9::/48 | 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.