FeM e.V. Infrastructure and System Status
Dashboard

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.

Some systems are under maintenance.

Last updated 1 month ago

    • Internet Uplink

      Operational
      Last updated 2026-08-23 21:59:06

    • Wireless (Freescale system)

      House A

      Under maintenance
      Last updated 2026-08-01 21:43:16

    • Wireless (Aruba system)

      House B, C, D, E, H, I, K, L, N, P, Q, CJD and FeM-Office

      Operational
      Last updated 2026-07-28 17:49:29

    • Wired

      Ethernet sockets

      Operational
      Last updated 2026-01-19 23:58:28

    • Network Management

      FeM AdminDB and network services (DHCP, DNS...)

      Operational
      Last updated 2026-04-23 21:48:54

    • Helpdesk

      Operational
      Last updated 2026-01-30 15:05:44

    • Storage systems

      Storage systems for servers (e.g. Ceph, ha-storage)

      Operational
      Last updated 2026-01-17 14:09:13

    • Monitoring

      All monitoring systems, e.g. Icinga, Grafana, ...

      Operational
      Last updated 2025-11-04 14:15:17

    • Databases

      Operational
      Last updated 2026-08-23 19:28:39

    • VM-Hosts

      Operational
      Last updated 2026-08-23 19:28:40

    • Mailserver

      Mail servers, inboxes & list systems

      Operational
      Last updated 2026-01-30 15:05:22

    • Webcluster

      Operational
      Last updated 2026-08-23 19:28:38

    • Mastodon

      Federated social network

      Operational
      Last updated 2026-05-10 14:39:06

    • Mattermost

      Internal Messenger

      Operational
      Last updated 2026-08-23 19:28:41

    • Pretix

      A Service to Sell Tickets and Manage Events

      Operational
      Last updated 2026-08-23 19:28:42

    • Dist-Mirror

      A Mirror for some selected Linux Distributions

      Operational
      Last updated 2025-10-31 12:35:48

    • XMPP

      XMPP / Jabber Instant Messaging

      Operational
      Last updated 2026-05-05 23:21:05

    • FeMCI

      FeM Content Infrastructure

      Operational
      Last updated 2026-08-23 19:28:43

    • Homepage

      Our homepage

      Operational
      Last updated 2026-05-22 15:00:39

    • Matrix

      Federated Instant Messaging

      Operational
      Last updated 2026-08-23 19:28:44

Planned maintenance

  • Sunsetting of the FreeScale WiFi (House A)

    1 day ago 2026-09-30 22:00 UTC
    In progress

    We are shutting down our old WiFi system (FreeScale-WiFi) on 2026-10-01. This WiFi system is currently only used in House A. All other houses are not affected by this change!

    After this date, the usage of the FeM-Net in house A is only possible via LAN or with a private router. Please keep in mind, that the usage of registered private routers (without NAT, AP mode enabled) is only allowed in accordance with the Terms of Use in houses A, N, P and houses in the Professor-Philippow-Str.

    If you have any questions, please open a ticket in our helpdesk at https://helpdesk.fem.tu-ilmenau.de/.

    Affected Components: Wireless (Freescale system)

Past incidents

—

Kea DHCP outage

3 years ago 2022-10-22 16:51 UTC
Fixed

Fixed

3 years ago 2022-10-22 16:51 UTC

During updates of lower campus VM host cluster, the experimental Kea DHCP nodes, which are currently providing DHCP for house N in a field test went down.

Normally, the HA mechanism should have prevented this, as one node was kept alive at all times. However, the first node didn't start again due to a software bug killing the DHCP server if it was unable to connect to the local database and the system not having automatic restarts on failure enabled.

As soon as the problem was noticed, it could be fixed by simply restarting the nodes, as they now were able to connect to their database servers.

No incidents reported.

No incidents reported.

No incidents reported.

No incidents reported.

No incidents reported.

No incidents reported.

Previous Today Next