Announced routes
Every prefix a peer of the route collectors sees with origin AS64476, 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.
| 85.190.70.0/24 | No ROA | RIR databaseRIPE | 669 99% |
| 85.190.76.0/24 | No ROA | RIR databaseRIPE | 669 99% |
| 46.247.136.0/23 | Valid | RIR databaseRIPE | 669 99% |
| 46.247.138.0/23 | Valid | RIR databaseRIPE | 669 99% |
| 85.190.64.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 85.190.65.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 85.190.67.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 85.190.68.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 85.190.71.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 85.190.72.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 85.190.74.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 85.190.84.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 85.190.85.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 85.190.88.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 87.121.208.0/21 | Valid | RIR databaseRIPE | 669 99% |
| 185.161.168.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 185.253.168.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.253.169.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.253.170.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.253.171.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 46.247.140.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 46.247.141.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a0a:e805:210::/44 | Valid | RIR databaseRIPE | 631 99% |
| 2a0a:e805:610::/44 | Valid | RIR databaseRIPE | 631 99% |
| 2a0a:e805:710::/44 | Valid | RIR databaseRIPE | 631 99% |
AS-SET
PeeringDB's irr_as_set for AS64476: AS-BLADE. 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 (AS64476 isn't in the set, or no route object for AS64476 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 | AS64476 in it | Not covered |
|---|---|---|---|---|---|
| AS-BLADE | RIPE | 2 | 1 | Yes | 0 |
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 7 are in fix.csv.
- ROA: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 85.190.70.0/24 | No ROA covers it. Add a ROA for AS64476, maxLength 24. |
| ROA: none | 85.190.76.0/24 | No ROA covers it. Add a ROA for AS64476, maxLength 24. |
Route objects not announced
Route objects with origin AS64476 whose prefix no peer sees AS64476 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 85.190.66.0/24 | RIPE | No ROA |
| 85.190.69.0/24 | RIPE | No ROA |
| 85.190.75.0/24 | RIPE | No ROA |
| 185.231.8.0/22 | RIPE | Valid |
| 2a0a:e805:500::/40 | RIPE | Valid |
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.