bgpreport

Network · data from 2026-11-12

AS213896 Cherry Servers DE

Registry name: CHERRYSERVERS6-AS UAB "Cherry Servers", LT · PeeringDB

25IPv4 routes 96.0% RPKI valid · 96.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS213896, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS213896, 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.
94.192.0.0/20 No ROA None 2 0%low visibility 2
82.24.88.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
84.32.59.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
84.32.98.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
84.32.100.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
84.32.223.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
84.75.210.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
88.216.36.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
88.216.70.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
88.216.74.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
88.216.132.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
88.216.182.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
88.216.190.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
88.216.220.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
89.106.12.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
164.152.216.0/24 Valid RIR databaseRIPE 672 100% 67
185.191.116.0/22 Valid RIR databaseRIPE 672 100% 67
185.191.116.0/24 Valid RIR databaseRIPE 672 100% 67
185.191.117.0/24 Valid RIR databaseRIPE 672 100% 67
185.191.118.0/24 Valid RIR databaseRIPE 672 100% 67
185.191.119.0/24 Valid RIR databaseRIPE 672 100% 67
217.60.12.0/24 Valid RIR databaseRIPE 672 100% 67
5.253.65.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
48.103.136.0/24 Valid RIR databaseRIPE 671 100% 67
88.216.211.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
2a02:ae00:3000::/36 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS213896: AS213896: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 (AS213896 isn't in the set, or no route object for AS213896 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.

NameDatabaseASNsSets Route objectsAS213896 in itNot covered
AS213896:AS-ALL RIPE 4172 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 2 are in fix.csv.

  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none94.192.0.0/20No ROA covers it. Add a ROA for AS213896, maxLength 20.2 of 673
Route object: none94.192.0.0/20No route object for it. Add a route object with origin AS213896 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS213896 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.