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 DetailsWe are currently experiencing problems with new devices interacting with DHCP. This leads to newly registered devices being unable to connect to some websits (i.e. those which don't offer only IPv4 connectivity). We are investigating the problem.
We were able to pin down the issue to the filesystem of the active DHCP node being corrupted and thus the configuration for newly registered devices unable to be written. For now, we have switched over to the backup DHCP node, so DHCP operation should now be working as intended. We are still working on bringing up the primary node again.
The primary node is back online. We have noticed that parts of the filesystem have been corrupted, but it seems the node is working as intended again.