Chatmail relays are a really great thing which help to increase resiliency of communication. And they work really really well 
But to get real resilience it would make sense to help users to choose relays which are not hosted in the same datacenter. Some of you might have noticed that hosters and services like VSys / njal.la / nerdvpn.de and others have been hit hard by the terroristic attack from Russia against two Kyiv datacenters on 23th of September. If you want to know more, I added two links here. [1][2]
Because of this my idea was to add four more details to the official relay list which are way more relevant than the current text telling which country the chatmail operator wants to address with the CM relay:
- Datacenter
- Country this datacenter resides
- Availability (maybe use a tool like Uptime Kuma for that)
- IPv6 available yes/no
As all those things can change at any time I would recommend to make the list dynamic so it updates on a hourly / daily / weekly basis.
I’m thinking about the list looking like this as an example (created 2026-09-26 20:15):
| Relay | Availability | AS (Datacenter) | Country | Description | IPv6 |
|---|---|---|---|---|---|
| nine.testrun.org | 99,99% | 24940 (HETZNER-AS): 77.42.49.4124940 (HETZNER-AS): 2a01:4f9:fff1:59::1 |
DE  |
is the default onboarding relay for many chatmail apps |  |
| mehl.cloud | 99,99% | 24940 (HETZNER-AS): 95.217.223.17224940 (HETZNER-AS): 2a01:4f9:c012:a1bc::1 |
DE |
is geared towards German speaking users | |
| mailchat.pl | 99,99% | 24940 (HETZNER-AS): 46.62.144.13724940 (HETZNER-AS): 2a01:4f9:c012:e6c3::1 |
DE |
is geared towards Polish speaking users | |
| chatmail.woodpeckersnest.space | 99,99% | 8560 (IONOS-AS): 85.215.162.146 |
DE |
are focused on Italian speaking users |  |
| chatmail.culturanerd.it | 99,99% | 8560 (IONOS-AS): 82.165.94.1658560 (IONOS-AS): 2a02:2479:60:c900::1 |
DE ??? |
are focused on Italian speaking users | |
| chat.adminforge.de | 99,99% | 24940 (HETZNER-AS): 94.130.17.14224940 (HETZNER-AS): 2a01:4f8:10b:1666::142 |
DE |
is hosted in Falkenstein, Germany and is geared towards German speaking users | |
| chika.aangat.lahat.computer | 99,99% | 47066 (PRGMR, US): 71.19.150.11347066 (PRGMR, US): 2605:2700:0:5:a800:ff:fed7:6162 |
US  |
is hosted in Santa Clara, California US | |
| tarpit.fun | 99,99% | 197540 (NETCUP-AS): 152.53.86.246197540 (NETCUP-AS): 2a0a:4cc0:c0:229c:9409:d6ff:fe22:4270 |
DE |
is hosted in Nuremberg, Germany | |
| d.gaufr.es | 99,99% | 16276 (OVH, FR): 51.77.140.9116276 (OVH, FR): 2001:41d0:404:200::787 |
FR  |
is hosted in Roubaix, France | |
| chtml.ca | 99,99% | 16276 (OVH, FR): 51.222.156.17716276 (OVH, FR): 2607:5300:205:200::21eb |
FR ??? |
is hosted in Quebec, Canada | |
| e2ee.wang | 99,99% | 20473 (AS-VULTR, US): 139.84.233.16120473 (AS-VULTR, US): 2a05:f480:3000:26a8:5400:5ff:fe6c:9f19 |
US ??? |
is hosted in Johannesburg, South Africa | |
| chat.privittytech.com | 99,99% | 16509 (AMAZON-02, US): 35.154.144.0 |
US ??? |
is hosted in Bangalore, India | |
| e2ee.im | 99,99% | 215659 (MOEMOEKYUN, RO): 93.113.25.61 |
RO  |
is hosted in Orastie, Romania | |
| chatmail.email | 99,99% | 16276 (OVH, FR): 57.128.220.12016276 (OVH, FR): 2001:41d0:601:1100::2674 |
FR ??? |
is hosted in Warsaw, Poland | |
| chat.in-the.eu | 99,99% | 24940 (HETZNER-AS): 78.46.190.12924940 (HETZNER-AS): 2a01:4f8:1c17:7b06::1 |
DE |
is hosted in Falkenstein, Germany | |
| chat.nuvon.app | 99,99% | 24971 (MASTER-AS): 178.238.38.165 |
CZ  |
is hosted in Prague, Czechia | |
| nibblehole.com | 99,99% | 51395 (AS-SOFTPLUS): 94.247.42.20951395 (AS-SOFTPLUS): 2a0b:7140:4:1:5054:ff:fe4f:df37 |
CH  |
is hosted in Zug, Switzerland | |
| chat.zashm.org | 99,99% | 49824 (ACTPA-AS): 91.245.76.39 |
UA  |
is hosted in Lviv, Ukraine | |
| chat.sus.fr | 99,99% | 60068 (CDN77 _, GB): 89.187.165.194200325 (BUNNYCDN, SI): 2400:52e0:1e09::889:1 |
GB  / SI  |
is hosted in Iceland, Japan, Kenya, and South Africa | |
| delta.thelab.uno | 99,99% | 16276 (OVH, FR): 146.59.228.3916276 (OVH, FR): 2001:41d0:305:2100::debe |
FR |
is hosted in Gravelines, France | |
| chat.vim.wtf | 99,99% | 24940 (HETZNER-AS): 116.203.206.17024940 (HETZNER-AS): 2a01:4f8:1c19:1c94::1 |
DE |
is hosted in Frankfurt, Germany | |
| uninterest.ing | 99,99% | 36352 (AS-COLOCROSSING, US): 172.245.70.237 |
US |
is hosted in Elk Grove Village, Illinois US | |
| sweetfern.net | 99,99% | 16276 (OVH, FR): 51.81.78.16716276 (OVH, FR): 2604:2dc0:401:800:0:ffff:3351:4ea7 |
FR ??? |
is hosted in Ashburn, Virginia US | |
| delta.disobey.net | 99,99% | 200651 (FLOKINET, IS): 185.246.190.71200651 (FLOKINET, IS): 2a06:1700:4:357::7b57:2a6a |
IS  |
is hosted in Roon, Netherlands | |
Disclaimer: Table was 100% crafted by a human hand, no “AI” involved for absolutely nothing. #fckaislop
Maybe we could also offer to group / sort relays by availability, datacenter or country then.
Regarding the availability topic I could imagine (or also host this on a volunteer basis if it helps the project) to have a page like this for every publicly communicated relay which ping-checks all relevant chatmail services.
The table also showed me that chat.sus.fr for example claims being hosted in different countries. But as there seems to be a CDN involved (which from my perspective is a single-point-of-failure) I don’t know yet how to deal with such a situation in practice. Because if the CDN is down the server is down as well. I think a CDN like Cloudflare ditches the whole idea of resilience somehow 
Regarding the work:
If nobody wants to pick up the task to create a script which automatically generates an output like the table above I would provide my help here and offer to do it. But I wanted to talk to you guys first before starting (I mean I already started by creating this table as a PoC) 
Looking forward to your thoughts on that 