Network · data from 2026-11-12
AS47242 Host.it S.p.A.
Registry name: HOST-SPA Host SpA, IT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47242, 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.73.137.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 82.119.36.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.59.155.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 185.73.136.0/24 | No ROA | RIR databaseRIPE | 404 60% |
| 185.73.139.0/24 | No ROA | RIR databaseRIPE | 404 60% |
| 185.73.138.0/24 | No ROA | RIR databaseRIPE | 403 60% |
| 149.62.184.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.84.96.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.84.97.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.84.99.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.201.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.31.144.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.31.145.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.31.150.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.31.152.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.31.153.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.31.157.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.31.159.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 83.220.28.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 83.220.29.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.84.98.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 185.201.65.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.201.66.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 149.62.185.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 149.62.186.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 149.62.187.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 149.62.188.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 149.62.189.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 149.62.190.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 149.62.191.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 81.31.146.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.31.147.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.31.148.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.31.149.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.31.151.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.31.154.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.31.155.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.31.156.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.31.158.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS47242: AS47242:AS-CUSTOMERS. 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 (AS47242 isn't in the set, or no route object for AS47242 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 | AS47242 in it | Not covered |
|---|---|---|---|---|---|
| AS47242:AS-CUSTOMERS | RIPE | 10 | 2 | Yes | 1 |
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 16 are in fix.csv.
- ROA: origin1
- ROA: none5
- Route object: none1
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.73.137.0/24 | ROAs covering it name AS199466, not AS47242. If AS47242 should announce it, add a ROA for AS47242. |
| Route object: none | 185.73.137.0/24 | Route objects for it name AS199466. Add a route object with origin AS47242 in the RIR database for the space. |
| ROA: none | 82.119.36.0/24 | No ROA covers it. Add a ROA for AS47242, maxLength 24. |
| ROA: none | 185.59.155.0/24 | No ROA covers it. Add a ROA for AS47242, maxLength 24. |
| ROA: none | 185.73.136.0/24 | No ROA covers it. Add a ROA for AS47242, maxLength 24. |
| ROA: none | 185.73.139.0/24 | No ROA covers it. Add a ROA for AS47242, maxLength 24. |
| ROA: none | 185.73.138.0/24 | No ROA covers it. Add a ROA for AS47242, maxLength 24. |
Route objects not announced
Route objects with origin AS47242 whose prefix no peer sees AS47242 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 81.31.144.0/20 | RIPE | No ROA |
| 149.62.184.0/21 | RIPE | No ROA |
| 185.59.152.0/24 | RIPE | No ROA |
| 185.59.153.0/24 | RIPE | No ROA |
| 185.59.154.0/24 | RIPE | No ROA |
| 185.201.64.0/22 | RIPE | No ROA |
| 185.201.67.0/24 | RIPE | Valid |
| 192.81.193.0/24 | RIPE | Valid |
| 2a01:a600::/32 | 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.