Network · data from 2026-11-12
AS30740 Exa Networks Limited
Registry name: EXA-NETWORKS Exa Networks Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS30740, 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.
| 82.219.31.0/24 | No ROA | Nonecovered by 82.219.0.0/16 | 669 99% |
| 82.219.5.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 82.219.0.0/16 | No ROA | RIR databaseRIPE | 671 100% |
| 185.140.8.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 2a02:b80::/29 | No ROA | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS30740: AS-EXA. 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 (AS30740 isn't in the set, or no route object for AS30740 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 | AS30740 in it | Not covered |
|---|---|---|---|---|---|
| AS-EXA | RIPElists itself further down3 member sets in no database: AS-202076-OUT, AS-PBB, AS203105:AS-FLIMPIE | 36 | 19 | 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 19 are in fix.csv.
- ROA: none5
- Route object: none1
- AS-SET: missing member3
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 82.219.31.0/24 | No ROA covers it. Add a ROA for AS30740, maxLength 24. |
| Route object: none | 82.219.31.0/24 | No route object for it. A route object for 82.219.0.0/16 with origin AS30740 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30740 in the RIR database for the space. |
| ROA: none | 82.219.5.0/24 | No ROA covers it. Add a ROA for AS30740, maxLength 24. |
| ROA: none | 82.219.0.0/16 | No ROA covers it. Add a ROA for AS30740, maxLength 16. |
| ROA: none | 185.140.8.0/22 | No ROA covers it. Add a ROA for AS30740, maxLength 22. |
| ROA: none | 2a02:b80::/29 | No ROA covers it. Add a ROA for AS30740, maxLength 29. |
| AS-SET: missing member | AS-EXA | AS-EXA (RIPE) lists AS-202076-OUT; no IRR database read has it. |
| AS-SET: missing member | AS-EXA | AS-EXA (RIPE) lists AS-PBB; no IRR database read has it. |
| AS-SET: missing member | AS-EXA | AS-EXA (RIPE) lists AS203105:AS-FLIMPIE; no IRR database read has it. |
Route objects not announced
Route objects with origin AS30740 whose prefix no peer sees AS30740 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.219.4.0/23 | RIPE | No ROA |
| 82.219.4.0/24 | RIPE | No ROA |
| 82.219.6.0/24 | RIPE | No ROA |
| 82.219.50.0/24 | RIPE | No ROA |
| 185.140.8.0/24 | RIPE | No ROA |
| 185.140.9.0/24 | RIPE | No ROA |
| 185.140.10.0/24 | RIPE | No ROA |
| 185.140.11.0/24 | RIPE | No ROA |
| 2a02:b80::/32 | RIPE | No ROA |
| 2a02:b80:50::/48 | 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.