Network · data from 2026-11-12
AS48753 AVAHOHST AVA HOST SRL
Registry name: AVAHOHST AVA HOST SRL, MD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48753, 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.
| 80.96.109.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.120.255.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.121.179.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 143.246.213.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 143.246.214.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 143.246.223.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.20.18.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.156.66.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.156.122.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.181.1.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 37.221.64.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 37.221.66.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.97.160.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.97.161.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.121.148.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.122.129.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.84.71.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.156.62.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.156.67.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.102.104.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a0f:5f44::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS48753 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 AS48753 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.