Network · data from 2026-11-12
AS60610 Amito (AS60610)
Registry name: EVEREST-AS Amito Ltd, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS60610, 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.
| 2a04:4040::/29 | No ROA | Other origin only | 633 100% |
| 194.110.241.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 185.28.164.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 185.38.36.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 195.200.211.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a04:1640::/29 | No ROA | RIR databaseRIPE | 634 100% |
| 193.105.231.0/24 | No ROA | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS60610's PeeringDB record names no AS-SET.
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 21 are in fix.csv.
- ROA: none7
- Route object: none1
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a04:4040::/29 | No ROA covers it. Add a ROA for AS60610, maxLength 29. |
| Route object: none | 2a04:4040::/29 | Route objects for it name AS12703. Add a route object with origin AS60610 in the RIR database for the space. |
| ROA: none | 194.110.241.0/24 | No ROA covers it. Add a ROA for AS60610, maxLength 24. |
| ROA: none | 185.28.164.0/22 | No ROA covers it. Add a ROA for AS60610, maxLength 22. |
| ROA: none | 185.38.36.0/22 | No ROA covers it. Add a ROA for AS60610, maxLength 22. |
| ROA: none | 195.200.211.0/24 | No ROA covers it. Add a ROA for AS60610, maxLength 24. |
| ROA: none | 2a04:1640::/29 | No ROA covers it. Add a ROA for AS60610, maxLength 29. |
| ROA: none | 193.105.231.0/24 | No ROA covers it. Add a ROA for AS60610, maxLength 24. |
Route objects not announced
Route objects with origin AS60610 whose prefix no peer sees AS60610 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 83.136.65.0/24 | RIPE | No ROA |
| 83.136.66.0/24 | RIPE | No ROA |
| 83.136.67.0/24 | RIPE | No ROA |
| 83.136.68.0/24 | RIPE | No ROA |
| 83.136.69.0/24 | RIPE | No ROA |
| 91.198.99.0/24 | RIPE | No ROA |
| 185.59.62.0/24 | RIPE | No ROA |
| 185.136.248.0/22 | RIPE | No ROA |
| 185.221.92.0/22 | RIPE | No ROA |
| 194.176.124.0/24 | RIPE | No ROA |
| 195.242.154.0/23 | RIPE | No ROA |
| 2001:4c21::/32 | RIPE | No ROA |
| 2a00:67a1::/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.