FeM e.V. Infrastructure and System Status
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. Therefore, there are no guarantees for any given timelines or time estimations.
If you have any questions or specific problems, feel free to send us a ticket via our helpdesk: https://helpdesk.fem.tu-ilmenau.de.
All systems are operational.
-
-
Internet Uplink
OperationalLast updated 2026-08-23 21:59:06 -
Wireless (Aruba system)
House B, C, D, E, H, I, K, L, N, P, Q, CJD and FeM-Office
OperationalLast updated 2026-07-28 17:49:29 -
Wired
Ethernet sockets
OperationalLast updated 2026-01-19 23:58:28 -
Network Management
FeM AdminDB and network services (DHCP, DNS...)
OperationalLast updated 2026-04-23 21:48:54
-
-
-
Helpdesk
OperationalLast updated 2026-01-30 15:05:44 -
Storage systems
Storage systems for servers (e.g. Ceph, ha-storage)
OperationalLast updated 2026-01-17 14:09:13 -
Monitoring
All monitoring systems, e.g. Icinga, Grafana, ...
OperationalLast updated 2025-11-04 14:15:17 -
Databases
OperationalLast updated 2026-08-23 19:28:39 -
VM-Hosts
OperationalLast updated 2026-08-23 19:28:40 -
Mailserver
Mail servers, inboxes & list systems
OperationalLast updated 2026-01-30 15:05:22 -
Webcluster
OperationalLast updated 2026-08-23 19:28:38
-
-
-
Mastodon
Federated social network
OperationalLast updated 2026-05-10 14:39:06 -
Mattermost
Internal Messenger
OperationalLast updated 2026-08-23 19:28:41 -
Pretix
A Service to Sell Tickets and Manage Events
OperationalLast updated 2026-08-23 19:28:42 -
Dist-Mirror
A Mirror for some selected Linux Distributions
OperationalLast updated 2025-10-31 12:35:48 -
XMPP
XMPP / Jabber Instant Messaging
OperationalLast updated 2026-05-05 23:21:05 -
FeMCI
FeM Content Infrastructure
OperationalLast updated 2026-08-23 19:28:43 -
Homepage
Our homepage
OperationalLast updated 2026-05-22 15:00:39 -
Matrix
Federated Instant Messaging
OperationalLast updated 2026-08-23 19:28:44
-
Past incidents
Fixed
This incident has been resolved.
Watching
The reboot is finished. We are seeing system recovery and are monitoring the situation.
Identified
We are currently in the process of rebooting the switch.
Reported
We are seeing the same inresponsiveness of the networking switch in House D as yesterday with the switch in House N. We are preparing for physical reboot.
Fixed
This incident has been resolved.
Watching
The have identified the issue to be the n switch issue. Most access points are back on line. We are monitoring the situation and are discussing countermesures against future cascading issues.
Reported
We have registered the inresponsiveness of the network switch in House D. We are currently in the process of rebooting the device, which could cause a minor outage.
Fixed
This incident has been resolved.
Watching
The switch has been restarted via an on-premise operation. Most access points are recovering. We are monitoring the situation.
Reported
We also see a small outage in House D. This can be a result of the outage in House N. We are investigating.
Reported
We have registered the inresponsiveness of the network switch in House N. We are currently in the process of rebooting the device, which could cause a minor outage.
No incidents reported.
No incidents reported.
No incidents reported.
No incidents reported.
Fixed
This issue has been resolved.
Identified
We have identified the single VLAN which responsible for the problems. We are working hard on resolving this issue. Broad operations are not impacted.
Reported
We are registering issues with IPv4 connectivity on some of our VM hosts. Internet connectivity of VMs may suffer.