Network · data from 2026-11-12
AS204770 Cherry Servers US
Registry name: CHERRYSERVERS3-AS UAB "Cherry Servers", LT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204770, 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.
| 154.88.3.0/24 | Invalid: origin | Other origin only | 4 1%low visibility |
| 154.193.55.0/24 | Invalid: origin | RIR databaseAFRINIC | 3 0%low visibility |
| 88.216.20.0/24 | No ROA | RIR databaseRADB, RIPE | 672 100% |
| 198.59.116.0/24 | Valid | Nonecovered by 198.59.116.0/23 | 672 100% |
| 51.146.20.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 82.27.98.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 84.32.32.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 84.32.34.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 84.32.48.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 84.32.53.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 84.32.54.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 84.32.61.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 84.32.63.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 84.32.70.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 84.32.71.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 84.32.128.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 84.32.131.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 84.32.220.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 88.216.57.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 88.216.68.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 88.216.73.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 88.216.183.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 88.216.184.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 88.216.195.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 88.216.198.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 88.216.210.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 88.216.222.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 88.216.255.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.106.6.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 109.176.236.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 109.176.237.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 109.176.238.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 137.175.60.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 143.20.150.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 167.148.119.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 181.214.166.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 185.8.106.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 185.8.106.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.8.107.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.216.149.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 217.216.215.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 84.32.130.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 88.216.39.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 154.194.204.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 154.194.205.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
| 88.216.254.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 2a02:ae02::/36 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS204770: AS204770:AS-ALL. 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 (AS204770 isn't in the set, or no route object for AS204770 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 | AS204770 in it | Not covered |
|---|---|---|---|---|---|
| AS204770:AS-ALL | RIPE | 8 | 1 | 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 12 are in fix.csv.
- ROA: origin2
- ROA: none1
- Route object: none2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 154.88.3.0/24 | ROAs covering it name AS17561, AS25198, not AS204770. If AS204770 should announce it, add a ROA for AS204770. |
| Route object: none | 154.88.3.0/24 | Route objects for it name AS25198. Add a route object with origin AS204770 in the RIR database for the space. |
| ROA: origin | 154.193.55.0/24 | ROAs covering it name AS17561, AS134494, AS218568, not AS204770. If AS204770 should announce it, add a ROA for AS204770. |
| ROA: none | 88.216.20.0/24 | No ROA covers it. Add a ROA for AS204770, maxLength 24. |
| Route object: none | 198.59.116.0/24 | No route object for it. A route object for 198.59.116.0/23 with origin AS204770 covers it (filters allowing more-specifics accept it). Add a route object with origin AS204770 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS204770 whose prefix no peer sees AS204770 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.199.165.0/24 | RIPE | Valid |
| 84.32.128.0/24 | RIPE | Valid |
| 84.32.129.0/24 | RIPE | Valid |
| 154.196.15.0/24 | AFRINIC | Invalid: origin |
| 192.48.200.0/24 | ARIN, RADB | Valid |
| 198.59.116.0/23 | ARIN | Valid |
| 2a02:ae02::/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.