Categories
Pages
-

IT Center Blog

Schlagwort: ‘Störung’

The Status Message Portal – Keep up to Date!

October 20th, 2025 | by
Orange background with text "New design, improved features! Information about maintenance, mailfunctions, and various notices can be found on our status message portal"

Source: Own illustration

Are you familiar with the Status Message Portal?

The website maintenance.rz.rwth-aachen.de provides you with messages about current maintenance, (partial) malfunctions, and outages of all central IT systems of the IT Center. The details specify what is going on, since when, and – if known – when it is expected to be resolved.

Since October 15, 2025, it has a new look and improved features.

Read the rest of this entry »

What Was Going on? – Disruption on November 21, 2024

December 17th, 2024 | by

Source: Own Illustration

Anyone who was at RWTH on that day or tried to connect via VPN from the road felt it: On November 21, 2024, starting around 10 a.m., many of our IT services no longer functioned as we wanted them to. RWTH e-mail, Eduroam, VPN, RWTHmoodle as well as the entire RWTH Single Sign-On—the login for a large part of the services at RWTH—stopped working. All this was due to a malfunction of our F5 load balancer. In this blog post, we will transparently explain how this massive disruption occurred.

Read the rest of this entry »

Always up-to-date with the status message portal!

January 26th, 2022 | by
Sign with „Out of Service“

Source: Freepik

Error message. Nothing works anymore?

Have you ever woken up in the morning, started to study or work on your PC, but then you got an error message and didn’t know what was going on? We have the solution! Especially for this purpose, we have the status message portal!

Read the rest of this entry »

#moodletrouble² – The chronology of a malfunction

June 28th, 2021 | by
Malfunction picture

Source: Pixabay

As some of you may have noticed, RWTHmoodle was unavailable to RWTH Aachen University employees and students for a total of two days in the second week of June 2021. As we already reported on our channels during the malfunction, a serious database error was the cause. We would like to take this opportunity to briefly explain how this error occurred. Read the rest of this entry »