All systems are operational.
This page shows an overview of our system status.
Please keep in mind that all helpers do this voluntarily in their free time.
If you have any questions or specific problems, feel free to open a ticket in our helpdesk.
Last updated 2025-08-22 00:52:06
Last updated 2025-08-22 10:03:58
House A, CJD
Last updated 2025-08-22 11:07:30
House B, C, D, E, H, I, K, L, N, P, Q and FeM-Office
Last updated 2025-09-11 22:19:35
FeM AdminDB and network services (DHCP, DNS...)
Last updated 2025-09-01 18:43:59
Last updated 2025-09-01 18:44:00
Mail servers, inboxes & list systems
Last updated 2025-09-01 18:43:58
Last updated 2025-08-22 00:52:02
Last updated 2025-09-01 18:43:59
Storage systems for servers (e.g. Ceph, ha-storage)
Last updated 2025-07-13 21:19:41
Federated social network
View DetailsLast updated 2025-05-15 16:21:07
A Service to Sell Tickets and Manage Events
View DetailsLast updated 2019-08-19 18:39:41
A Mirror for some selected Linux Distributions
View DetailsLast updated 2025-07-13 21:19:42
A Browser based Video-Conferencing Software
View DetailsLast updated 2025-02-16 10:03:47
XMPP / Jabber Instant Messaging
View DetailsLast updated 2019-12-11 11:52:44
FeM Content Infrastructure
View DetailsLast updated 2025-07-14 07:06:00
Our homepage
View DetailsLast updated 2024-10-17 12:36:00
Federated Instant Messaging
View DetailsOur Mailserver is unable to receive emails from other mailservers or forward emails submitted from users. We are investigating the situation. The current assumption is that the database behind the mailserver might be broken or unreachable.
We have successfully tested other components which are using the database cluster in question. It is unlikely that the database is the source of the problems.
We have identified a misconfiguration in the mailserver system. The mailing list software tried to connect to the database using a target IP address, which was not the high-availability IP. Thus, during maintenance on the database cluster, the mailing list software was now unable to connect to the database when that one node with the right IP address went offline.
The mailserver config has been adjusted so that the highly available IP address will be used in the future. This should prevent an outage like this in the future.