Network · data from 2026-11-12
AS210791 AIRCOM ASPWIFI S.L.
Registry name: AIRCOM ASPWIFI S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS210791, 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.
| 78.136.110.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.119.96.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 92.119.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.119.97.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.119.98.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.119.99.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.167.106.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.32.136.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.32.136.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.32.137.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.32.138.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.32.139.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.78.0.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.78.0.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.78.1.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.78.2.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.78.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS210791 isn't in PeeringDB, where networks name their AS-SET.
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 AS210791 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.