Network · data from 2026-11-12
AS29644 Airspeed Telecom
Registry name: AIRSPEED-AS AIRSPEED COMMUNICATIONS LIMITED, IE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29644, 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.113.232.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 148.252.8.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 2a03:5f00:102::/48 | Valid | Nonecovered by 2a03:5f00::/32 | 634 100% |
| 2a03:5f00:103::/48 | Valid | Nonecovered by 2a03:5f00::/32 | 634 100% |
| 178.250.112.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.51.104.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.69.212.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 31.193.216.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 77.75.96.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 2a03:5f00::/32 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS29644: AS-AIRSPEED. 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 (AS29644 isn't in the set, or no route object for AS29644 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 | AS29644 in it | Not covered |
|---|---|---|---|---|---|
| AS-AIRSPEED | RIPE | 20 | 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 36 are in fix.csv.
- ROA: none2
- Route object: none2
- Route object: not announced32
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.113.232.0/22 | No ROA covers it. Add a ROA for AS29644, maxLength 22. |
| ROA: none | 148.252.8.0/21 | No ROA covers it. Add a ROA for AS29644, maxLength 21. |
| Route object: none | 2a03:5f00:102::/48 | No route object for it. A route object for 2a03:5f00::/32 with origin AS29644 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29644 in the RIR database for the space. |
| Route object: none | 2a03:5f00:103::/48 | No route object for it. A route object for 2a03:5f00::/32 with origin AS29644 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29644 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29644 whose prefix no peer sees AS29644 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.193.216.0/24 | RIPE | Valid |
| 31.193.217.0/24 | RIPE | Valid |
| 31.193.218.0/24 | RIPE | Valid |
| 31.193.219.0/24 | RIPE | Valid |
| 31.193.220.0/24 | RIPE | Valid |
| 31.193.221.0/24 | RIPE | Valid |
| 31.193.222.0/24 | RIPE | Valid |
| 31.193.223.0/24 | RIPE | Valid |
| 77.75.96.0/24 | RIPE | Valid |
| 77.75.97.0/24 | RIPE | Valid |
| 77.75.98.0/24 | RIPE | Valid |
| 77.75.99.0/24 | RIPE | Valid |
| 77.75.100.0/24 | RIPE | Valid |
| 77.75.101.0/24 | RIPE | Valid |
| 77.75.102.0/24 | RIPE | Valid |
| 77.75.103.0/24 | RIPE | Valid |
| 167.3.34.0/23 | RIPE-NONAUTH | No ROA |
| 167.3.34.0/24 | RIPE-NONAUTH | No ROA |
| 178.250.112.0/24 | RIPE | Valid |
| 178.250.113.0/24 | RIPE | Valid |
| 178.250.114.0/24 | RIPE | Valid |
| 178.250.115.0/24 | RIPE | Valid |
| 178.250.116.0/24 | RIPE | Valid |
| 178.250.117.0/24 | RIPE | Valid |
| 178.250.118.0/24 | RIPE | Valid |
| 178.250.119.0/24 | RIPE | Valid |
| 185.39.164.0/22 | RIPE | No ROA |
| 185.39.164.0/24 | RIPE | No ROA |
| 185.51.104.0/24 | RIPE | Valid |
| 185.51.105.0/24 | RIPE | Valid |
| 185.51.106.0/24 | RIPE | Valid |
| 185.51.107.0/24 | 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.