Network · data from 2026-11-12
AS39291 macroIS
Registry name: MACROIS-AS Dominik Schubert, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39291, 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.
| 185.86.156.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.49.72.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.49.110.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.55.158.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a05:b940::/30 | No ROA | RIR databaseRIPE | 634 100% |
AS-SET
AS39291'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 12 are in fix.csv.
- ROA: none5
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.86.156.0/24 | No ROA covers it. Add a ROA for AS39291, maxLength 24. |
| ROA: none | 194.49.72.0/24 | No ROA covers it. Add a ROA for AS39291, maxLength 24. |
| ROA: none | 194.49.110.0/24 | No ROA covers it. Add a ROA for AS39291, maxLength 24. |
| ROA: none | 194.55.158.0/24 | No ROA covers it. Add a ROA for AS39291, maxLength 24. |
| ROA: none | 2a05:b940::/30 | No ROA covers it. Add a ROA for AS39291, maxLength 30. |
Route objects not announced
Route objects with origin AS39291 whose prefix no peer sees AS39291 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.86.156.0/22 | RIPE | No ROA |
| 185.86.158.0/24 | RIPE | No ROA |
| 185.86.159.0/24 | RIPE | No ROA |
| 185.141.148.0/22 | RIPE | No ROA |
| 2001:678:e9c::/48 | RIPE | No ROA |
| 2a05:b940::/29 | RIPE | No ROA |
| 2a05:b940:0:100::/56 | 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.