bgpreport

Network · data from 2026-11-12

AS57118 CommunityRack.org

Registry name: COMMUNITYRACK CommunityRack.org Verein, CH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57118, 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.95.219.0/24 Valid Other origin only 673 100% 66
2a05:fc87::/32 Valid Other origin onlycovered by 2a05:fc80::/29 633 100% 69
91.199.218.0/24 Valid RIR databaseRIPE 673 100% 66
185.72.236.0/23 Valid RIR databaseRIPE 673 100% 66
185.95.216.0/23 Valid RIR databaseRIPE 673 100% 66
185.95.218.0/24 Valid RIR databaseRIPE 673 100% 66
185.104.19.0/24 Valid RIR databaseRIPE 673 100% 66
2001:67c:2d70::/48 Valid RIR databaseRIPE 633 100% 69
2a00:f740:400::/48 Valid RIR databaseRIPE 633 100% 69
2a05:fc80::/29 Valid RIR databaseRIPE 632 99% 69

AS-SET

PeeringDB's irr_as_set for AS57118: AS-COMRACK. 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 (AS57118 isn't in the set, or no route object for AS57118 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 objectsAS57118 in itNot covered
AS-COMRACK RIPElists itself further down 2019217 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.

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none185.95.219.0/24Route objects for it name AS39540. Add a route object with origin AS57118 in the RIR database for the space.673 of 673
Route object: none2a05:fc87::/32Route objects for it name AS39540. A route object for 2a05:fc80::/29 with origin AS57118 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57118 in the RIR database for the space.633 of 636

Route objects not announced

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