Announced routes
Every prefix a peer of the route collectors sees with origin AS215685, 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.
| 2a06:9801:1591::/48 | No ROA | None | 1 0%low visibility |
| 2a14:6782:101::/48 | Valid | Nonecovered by 2a14:6782:100::/40 | 636 100% |
| 2a14:6782:100::/48 | Valid | Nonecovered by 2a14:6782:100::/40 | 634 100% |
| 2a14:6782:102::/48 | Valid | Nonecovered by 2a14:6782:100::/40 | 633 100% |
| 2a14:6782:103::/48 | Valid | Nonecovered by 2a14:6782:100::/40 | 632 99% |
| 5.175.239.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2001:678:a90::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a06:de00:10::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS215685: AS215685:AS-NESOX. 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 (AS215685 isn't in the set, or no route object for AS215685 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 | AS215685 in it | Not covered |
|---|---|---|---|---|---|
| AS215685:AS-NESOX | RIPE2 member sets in no database: AS215110:AS-CUSTOMERS, AS39753:AS-LIUXYON | 8 | 4 | 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 14 are in fix.csv.
- ROA: none1
- Route object: none5
- AS-SET: missing member2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a06:9801:1591::/48 | No ROA covers it. Add a ROA for AS215685, maxLength 48. |
| Route object: none | 2a06:9801:1591::/48 | No route object for it. Add a route object with origin AS215685 in the RIR database for the space. |
| Route object: none | 2a14:6782:101::/48 | No route object for it. A route object for 2a14:6782:100::/40 with origin AS215685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS215685 in the RIR database for the space. |
| Route object: none | 2a14:6782:100::/48 | No route object for it. A route object for 2a14:6782:100::/40 with origin AS215685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS215685 in the RIR database for the space. |
| Route object: none | 2a14:6782:102::/48 | No route object for it. A route object for 2a14:6782:100::/40 with origin AS215685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS215685 in the RIR database for the space. |
| Route object: none | 2a14:6782:103::/48 | No route object for it. A route object for 2a14:6782:100::/40 with origin AS215685 covers it (filters allowing more-specifics accept it). Add a route object with origin AS215685 in the RIR database for the space. |
| AS-SET: missing member | AS215685:AS-NESOX | AS215685:AS-NESOX (RIPE) lists AS215110:AS-CUSTOMERS; no IRR database read has it. |
| AS-SET: missing member | AS215685:AS-NESOX | AS215685:AS-NESOX (RIPE) lists AS39753:AS-LIUXYON; no IRR database read has it. |
Route objects not announced
Route objects with origin AS215685 whose prefix no peer sees AS215685 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a02:2fc0:3::/48 | RIPE | Invalid: origin |
| 2a06:de00:11::/48 | RIPE | Valid |
| 2a06:de00:12::/48 | RIPE | Valid |
| 2a0c:9a40:8890::/48 | RIPE | Valid |
| 2a0f:b240:b0::/44 | RIPE | Valid |
| 2a14:6782:100::/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.