Network · data from 2026-11-12
AS47309 INFO-AS q.beyond AG
Registry name: INFO-AS q.beyond AG, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47309, 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.
| 193.16.72.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 130.0.20.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 194.8.90.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 130.0.22.0/23 | Valid | RIR databaseRIPE | 669 99% |
| 212.99.128.0/19 | Valid | RIR databaseRIPE | 669 99% |
| 212.99.173.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.99.174.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.99.177.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 2a02:e240::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS47309 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 4 are in fix.csv.
- ROA: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.16.72.0/21 | No ROA covers it. Add a ROA for AS47309, maxLength 21. |
Route objects not announced
Route objects with origin AS47309 whose prefix no peer sees AS47309 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 130.0.16.0/21 | RIPE | No ROA |
| 185.60.0.0/23 | RIPE | No ROA |
| 193.16.64.0/21 | 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.