Network · data from 2026-11-12
AS43915 Truespeed Communications
Registry name: TRUESPEED TrueSpeed Communications Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43915, 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.
| 79.135.122.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 91.239.57.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.224.224.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 147.189.214.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.116.116.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 5.181.104.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 31.210.27.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.66.36.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 45.80.160.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 45.130.56.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 45.143.112.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 45.152.28.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 62.169.148.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.64.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 87.117.68.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 94.154.184.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 109.224.216.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 109.224.226.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 109.224.234.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 109.224.236.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 109.224.240.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 137.44.112.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 144.178.104.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 144.178.118.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 144.178.252.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 147.189.156.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 150.251.120.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 178.248.128.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 185.23.254.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 185.147.184.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.161.4.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.231.136.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 188.214.236.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.35.146.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 194.105.134.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 194.145.242.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 194.146.160.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 194.169.152.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 195.72.56.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 195.184.250.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 195.206.172.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 195.242.148.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 195.244.2.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 212.59.72.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 212.108.90.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 213.225.224.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 217.14.184.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 217.20.244.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 217.171.100.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 217.171.104.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 2a07:5940::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS43915: AS-TRUESPEED. 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 (AS43915 isn't in the set, or no route object for AS43915 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 | AS43915 in it | Not covered |
|---|---|---|---|---|---|
| AS-TRUESPEED | RIPE | 2 | 1 | Yes | 0 |
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS43915 is announced.
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.