All systems are operational.
This page shows an overview of the status of infrastructure, services and systems of FeM e.V.
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 send us a ticket via our helpdesk: https://helpdesk.fem.tu-ilmenau.de.
Last updated 2026-03-19 19:44:57
Last updated 2025-11-03 20:55:28
House A, CJD
Last updated 2026-01-19 23:57:13
House B, C, D, E, H, I, K, L, N, P, Q and FeM-Office
Last updated 2026-01-19 23:58:28
Ethernet sockets
Last updated 2026-04-23 21:48:54
FeM AdminDB and network services (DHCP, DNS...)
Last updated 2026-01-30 15:05:19
Last updated 2026-01-30 15:05:22
Mail servers, inboxes & list systems
Last updated 2026-01-28 13:53:18
Last updated 2026-01-30 15:05:20
Last updated 2025-11-04 14:15:17
All monitoring systems, e.g. Icinga, Grafana, ...
Last updated 2026-01-17 14:09:13
Storage systems for servers (e.g. Ceph, ha-storage)
Last updated 2026-01-30 15:05:44
Last updated 2025-10-31 12:35:48
Federated social network
View DetailsLast updated 2025-10-31 12:35:48
Internal Messenger
Last updated 2025-10-31 12:35:48
A Service to Sell Tickets and Manage Events
View DetailsLast updated 2025-10-31 12:35:48
A Mirror for some selected Linux Distributions
View DetailsLast updated 2025-10-31 12:35:48
A Browser based Video-Conferencing Software
View DetailsLast updated 2025-10-31 12:35:48
XMPP / Jabber Instant Messaging
View DetailsLast updated 2025-12-12 09:58:46
FeM Content Infrastructure
View DetailsLast updated 2026-01-30 17:39:52
Our homepage
View DetailsLast updated 2026-02-22 09:15:18
Federated Instant Messaging
View DetailsSome new devices do not receive addresses via DHCP or get wrong the wrong address.
Update 2019-08-09 14:00: The issue was caused by an malfunctioning DHCP config generator.
Due to an faulty configuration the WLAN in house N was unavailable for some minutes.
There are reports of connectivity problems with IPv4 at some of the access points.
Update 2019-08-07 19:20: It seems the error was caused by a malfunction in our network address translations (NAT) system. The error was resolved but we are still monitoring this issue.
Update 2019-08-08 22:00: It was confirmed that this issue is resolved.