Announced routes
Every prefix a peer of the route collectors sees with origin AS52015, 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.
| 46.39.0.14/32 | No ROA | Nonecovered by 46.39.0.0/24 | 8 1%low visibility |
| 46.39.0.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 46.39.16.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 46.39.28.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 46.39.0.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.39.2.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.39.3.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.39.4.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.39.5.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.39.6.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.39.7.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.39.23.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 46.39.24.0/24 | No ROA | RIR databaseRIPE | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS52015: RIPE::AS-DANCER RIPE::AS-DANCER6. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS52015 isn't in the set, or no route object for AS52015 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS52015 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-DANCER | RIPE | 1 | 1 | Yes | 1 |
| RIPE::AS-DANCER6 | RIPE | 1 | 1 | Yes | 1 |
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 24 are in fix.csv.
- ROA: none13
- Route object: none1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 46.39.0.14/32 | No ROA covers it. Add a ROA for AS52015, maxLength 32. |
| Route object: none | 46.39.0.14/32 | No route object for it. A route object for 46.39.0.0/24 with origin AS52015 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS52015 in the RIR database for the space. |
| ROA: none | 46.39.0.0/19 | No ROA covers it. Add a ROA for AS52015, maxLength 19. |
| ROA: none | 46.39.16.0/21 | No ROA covers it. Add a ROA for AS52015, maxLength 21. |
| ROA: none | 46.39.28.0/22 | No ROA covers it. Add a ROA for AS52015, maxLength 22. |
| ROA: none | 46.39.0.0/24 | No ROA covers it. Add a ROA for AS52015, maxLength 24. |
| ROA: none | 46.39.2.0/24 | No ROA covers it. Add a ROA for AS52015, maxLength 24. |
| ROA: none | 46.39.3.0/24 | No ROA covers it. Add a ROA for AS52015, maxLength 24. |
| ROA: none | 46.39.4.0/24 | No ROA covers it. Add a ROA for AS52015, maxLength 24. |
| ROA: none | 46.39.5.0/24 | No ROA covers it. Add a ROA for AS52015, maxLength 24. |
| ROA: none | 46.39.6.0/24 | No ROA covers it. Add a ROA for AS52015, maxLength 24. |
| ROA: none | 46.39.7.0/24 | No ROA covers it. Add a ROA for AS52015, maxLength 24. |
| ROA: none | 46.39.23.0/24 | No ROA covers it. Add a ROA for AS52015, maxLength 24. |
| ROA: none | 46.39.24.0/24 | No ROA covers it. Add a ROA for AS52015, maxLength 24. |
Route objects not announced
Route objects with origin AS52015 whose prefix no peer sees AS52015 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.39.1.0/24 | RIPE | No ROA |
| 46.39.8.0/21 | RIPE | No ROA |
| 46.39.8.0/24 | RIPE | No ROA |
| 46.39.9.0/24 | RIPE | No ROA |
| 46.39.11.0/24 | RIPE | No ROA |
| 46.39.12.0/24 | RIPE | No ROA |
| 46.39.13.0/24 | RIPE | No ROA |
| 46.39.14.0/24 | RIPE | No ROA |
| 46.39.15.0/24 | RIPE | No ROA |
| 2a03:6a40::/32 | 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.