| Description | Due to persistent unusual, massive access and increased data traffic from various IP addresses (including from Venezuela, Jamaica, Turkey, Ukraine) to KIT GitLab (gitlab.kit.edu), we have decided to completely block access to GitLab on December 24 between 5:50 p.m. and 11:30 p.m. until a more detailed investigation is possible. Starting December 25, access to GitLab will be restricted to the KIT network. - https://www.scc.kit.edu/forbidden.php Access to GitLab is only possible via the KIT VPN or requires a connection to GitLab via the KIT network. All users must activate the VPN in order to use GitLab at KIT via a public Internet connection. - https://www.scc.kit.edu/dienste/vpn.php We will only allow access from the public Internet after consultation with the KIT-CERT team in order to minimize denial-of-service attacks via HTTPS requests. |
|---|---|
| Affected users | Users of KIT GitLab |
| Exists since | 2025-12-24 17:50 |
| Description | Performance issues have been observed since the firewall software upgrade on August 11, 2025. Individual connections require too many resources, which disadvantages other users. These users experience higher latencies, which can lead to slow websites, file transfers, etc. As a first step, the software update suggested by the manufacturer was installed on September 16. This has not yet led to any actual improvement. Troubleshooting together with the manufacturer is ongoing. |
|---|---|
| Affected users | Users of Firewall Stufe 2 (Area D) und Extranet (Area B) |
| Exists since | 2025-08-11 20:00 |
Störungen