openfactory nordic oy · service status

No known incidents

Last updated . This page refreshes from our ticket system every five minutes.

Current incidents

No known incidents at the moment.

Planned maintenance

No maintenance announced at the moment, apart from the daily window below.

Completed changes

Maintenance and incidents closed in the last 30 days.

Completed Urgent security maintenance on shared web services
  1. The security maintenance is complete. The updated proxy and affected shared services are running, and HTTPS and webmail upload checks have passed. Normal service has resumed. Further security updates will be scheduled separately when vendor fixes become available.

    Kind regards,
    Silvan Gebhardt

  2. The proxy security update is installed. Final webmail checks are taking longer than expected, so we are extending the maintenance window to 15:00 UTC on 19 November (17:00 Finland time). Brief webmail interruptions remain possible during these checks. We will publish a completion update once verification is finished.

    Kind regards,
    Silvan Gebhardt

  3. The security update has passed testing on a separate system. We will now update the production proxy during the window from 13:25 to 14:30 UTC on 19 November (15:25 to 16:30 Finland time). Shared websites and webmail may briefly disconnect while services restart. We will check the services and publish a completion update afterwards.

    Kind regards,
    Silvan Gebhardt

  4. Testing of the security update is taking longer than expected and maintenance remains in progress. Shared web services are available. We are testing the update on a separate system before changing production, and will announce the next service-interruption window before applying it.

    Kind regards,
    Silvan Gebhardt

  5. Security maintenance continues while we test the proxy update on a separate system before applying it to production. The maintenance window is extended until 12:20 UTC (14:20 Finland time). Brief interruptions to shared web services remain possible during the update and checks. We will post a further update once those checks are complete.

    Kind regards,
    Silvan Gebhardt

  6. Security maintenance is in progress. We are preparing and applying updates to the shared web services, followed by service checks. Brief connection interruptions remain possible within the announced window, until 10:20 UTC (12:20 Finland time).

    Kind regards,
    Silvan Gebhardt

  7. We are carrying out urgent security maintenance on our shared HTTPS access,
    webmail and conferencing services on 19 November 2026, from 08:20 to 10:20 UTC
    (10:20 to 12:20 Finland time).

    Brief connection interruptions may occur while web services reload. Please
    retry if a page does not load. We will post an update when the work and
    service checks are complete.

    Kind regards,
    Silvan Gebhardt

Reference 2026111962000539

Completed Amsterdam network routing maintenance
  1. Amsterdam routing maintenance is complete. IPv4 and IPv6 BGP sessions have recovered, and route validation and connectivity checks have passed. RPKI Invalid routes are now rejected on external sessions.

    Normal monitoring has resumed. The routing-software fault observed during maintenance remains under investigation; the current routing processes are stable. No further interruption is planned.

  2. The routing changes have been applied and BGP sessions have recovered. We are extending the maintenance window until 14:00 UTC on 15 November 2026 (16:00 Finland time) to finish route validation and recovery backups.

    No further service interruption is currently planned. We will post a completion update after these checks finish.

  3. We are extending the Amsterdam routing maintenance until 13:00 UTC (15:00 Finland time) on 15 November 2026. A routing-software fault interrupted the first change; the previous configuration has been restored and connections have recovered. We are testing an alternative activation method before continuing route-origin validation. Reputation-based blocking will be handled separately at the firewall. Brief routing interruptions remain possible during the remaining work.

  4. The Amsterdam routing maintenance has started. We are applying route-origin validation and malicious-network filters in stages. The planned window remains 15 November 2026, 10:00-12:00 UTC (12:00-14:00 Finland time). Brief routing changes may occur as connections reconnect.

  5. On 15 November 2026, 10:00-12:00 UTC (12:00-14:00 Finland time), we are
    updating route-origin validation on our Amsterdam network. BGP connections
    will be refreshed in stages. Brief routing changes or interruptions may occur
    while individual connections reconnect. Redundant transit paths will be
    maintained throughout the work. We will post an update when validation is
    complete.

Reference 2026111562000359

Completed Customer portal maintenance, 14 November 2026
  1. The customer portal update is complete. Ticket synchronisation and portal access have been checked successfully. The application reload completed at 15:29 UTC on 14 November 2026 (17:29 Finland time).

    Kind regards
    Silvan Gebhardt

  2. We are updating the ticket connection in the connectionpoint and openfactory
    customer portals on 14 November 2026, between 15:05 and 15:25 UTC (17:05 to
    17:25 Finland time). Portal requests may briefly take longer while the change
    is applied. Customer internet and telephone services are unaffected.

    Kind regards
    Silvan Gebhardt

Reference 2026111462000682

Completed Backbone routing maintenance in Amsterdam
  1. Maintenance is complete.

    The routing changes on our Amsterdam backbone routers were finished at 11:33 Finland time (09:33 UTC). The temporary routes added during the work have been removed again, and all routing sessions stayed up throughout. Our monitoring shows all services as normal.

    Some monitored connections saw a short interruption of about one minute at 10:01 Finland time (08:01 UTC). They recovered on their own.

  2. We are making routing changes on our Amsterdam backbone routers today.

    Maintenance started on 12 November 2026 at 09:58 Finland time (07:58 UTC) and
    is planned to finish by 14:00 Finland time (12:00 UTC).

    The changes add routes and do not move existing customer traffic. Individual
    connections may still see short interruptions of up to about a minute while
    routing updates. We are monitoring the network during the work and will post
    an update here when it is complete.

Reference 2026111262000337

Completed GitLab security maintenance in progress
  1. Maintenance is complete. GitLab is available again.

    GitLab Community Edition was updated from 19.5.3 to 19.5.4. The server also received the Perl security update for CVE-2026-82560, which fixes a denial-of-service issue when processing specially crafted documentation, and a SQLite stability fix.

    All GitLab services are running, application readiness checks passed, and the public sign-in page is responding normally.

  2. We are updating GitLab (gitlab.openfactory.ch) now to apply security updates.
    Maintenance started on 10 November 2026 at 21:15 Finland time (19:15 UTC).
    GitLab may be temporarily unavailable during the update. The completion time
    is not yet confirmed. We will post an update once maintenance is complete.

Reference 2026111062000984

Completed Amsterdam: short network interruption for router maintenance, 10 November 2026
  1. Completed. The Amsterdam edge router was restarted at 04:30 Finland time (02:30 UTC) and was back in service about one minute later. The router and the containers on the internal network in Amsterdam now use the standard packet size of 1500 bytes again. Services were checked after the change.

  2. Planned network maintenance in our Amsterdam data centre on Tuesday, 10
    November 2026, 04:30 to 05:30 Finland time (03:30 to 04:30 Central European
    Time, 02:30 to 03:30 UTC).

    We are restarting the Amsterdam edge router to raise the packet size (MTU) on
    the internal network back to the standard 1500 bytes. During the recent
    migration of our virtual machines to Amsterdam we had to apply some temporary
    workarounds with a smaller packet size, which we are now removing.

    Expected impact: services hosted in Amsterdam are unreachable for about one to
    three minutes, including websites, the ticket system, GitLab, email and VPN
    access. Existing connections may be interrupted and reconnect afterwards.

    We will post an update here once the work is complete.

Reference 2026110962001137

Completed Wartung: GitLab-Anmeldung und Sicherheit
  1. Die Wartungsarbeiten an GitLab sind abgeschlossen. GitLab ist wieder regulär erreichbar. Die zusätzliche Anmeldung über Openfactory Authentik ist eingerichtet; bestehende Konten, Projekte und Zugriffsrechte bleiben erhalten.

    Freundliche Grüsse
    Silvan Gebhardt

  2. Wir verbessern die Anmeldung und Sicherheit von GitLab. Bestehende Konten und
    Projekte bleiben erhalten. Während der Umstellung kann GitLab kurzzeitig nicht
    erreichbar sein. Wir melden den Abschluss hier.

    Freundliche Grüsse
    Silvan Gebhardt

Reference 2026110962000594

Completed Planned Pegaprox update until 20:00 CET
  1. Pegaprox maintenance is complete. The management portal is available again and now runs version 1.4.1. Access to both the Amsterdam and Finland clusters has been verified. The connection problem after the restart has been corrected. No hosted virtual machines were restarted during this work.

  2. Access to Pegaprox has been restored. The version update is still pending, so maintenance is extended until 22:00 Switzerland time on 8 November 2026 (21:00 UTC / 23:00 Finland time). Brief interruptions to the management portal are expected during the update. Hosted virtual machines are not being restarted. We will publish a completion update after verification.

  3. We plan to update Pegaprox this afternoon, 8 November 2026, until 20:00
    Switzerland time (CET, 19:00 UTC / 21:00 Finland time). Access to Pegaprox may
    be interrupted during the update. We will publish an update when the
    maintenance is complete.

Reference 2026110862000514

Completed Wartung: Sicherheitsverbesserungen fuer Browser-Desktops
  1. Die Wartung der Browser-Desktops ist abgeschlossen. Die zentrale Anmeldung mit Zwei-Faktor-Authentifizierung ist eingerichtet und die Anmeldung wurde erfolgreich getestet. Bestehende Verbindungen und Berechtigungen bleiben erhalten. Beim Start einer Windows-Sitzung kann das persoenliche Windows-Passwort abgefragt werden.

  2. Wir verbessern die Sicherheit der Browser-Desktops und richten die zentrale
    Anmeldung mit Zwei-Faktor-Authentifizierung ein. Dabei wird der Zugang kurz
    neu gestartet; laufende Browser-Desktop-Verbindungen koennen getrennt werden.
    Dies ist eine geplante Wartung. Nach der Umstellung pruefen wir Anmeldung und
    Verbindungszugriff und melden den Abschluss hier.

Reference 2026110862000694

Completed Central login security maintenance
  1. The central login security maintenance is complete. Sign-in and security notification delivery have been checked. Connected applications are available and normal monitoring has resumed.

  2. We are updating the central login service to improve security notifications.
    Sign-in to connected applications, including the ticket system, may be briefly
    unavailable during this work. Existing ticket access and background processing
    are not being changed. We will update this notice when the checks are
    complete.

Reference 2026110862000667

Completed OFORK security improvements in progress
  1. The security improvements to the OFORK ticket system are complete. Staff sign-in now uses our central login with two-factor authentication. Access to the ticket system has been checked and normal monitoring has resumed.

  2. We are working on security improvements for the OFORK ticket system today, 8
    November 2026. Sign-in may be briefly unavailable or require a new login while
    the changes are applied. We will update this notice when the work is complete.

Reference 2026110862000505

Completed Zimbra maintenance closed: false alert, patch already installed
  1. The announced Zimbra maintenance is no longer required. Our supplier's messages presented the patch as an upcoming release, which we interpreted as a new update. In fact, it had already been made available before publication for security reasons and was installed on our server long ago.

    We have confirmed that Zimbra 10.1.21 is already installed. No additional update or service interruption is needed for this announcement. We are closing this notice as a false alert. We apologise for the confusion.

  2. We plan to update Zimbra tonight, 5 November 2026, after 19:00 Swiss time (CET, 18:00 UTC / 20:00 Finland time). Mail access and mail delivery may be temporarily interrupted during the update. We will post an update here when maintenance is complete.

Reference 2026110562000556

Completed Security maintenance completed: zero SSHhole issues found
  1. Our infrastructure checks for the SSHhole issue are complete. We found zero SSHhole issues. The remaining Amsterdam container has also been confirmed as unaffected.

    No patching or reboots were required, and the checks caused no service interruption. This security maintenance is now closed.

  2. Initial checks have not identified any systems affected by the SSHhole issue. We have checked the SSH configuration and operating system on 61 Linux hosts, including 33 of the 34 running Amsterdam containers. These hosts use glibc rather than the affected musl configuration.

    One internal container still requires access verification. The maintenance notice remains open while this check is outstanding. No patching or reboot has been required as a result of these checks so far.

  3. Security maintenance is starting now. We will scan our public infrastructure and internal Amsterdam containers for the SSHhole issue described at https://sshhole.com/.

    The advisory describes a password-authentication bypass affecting certain OpenSSH installations on musl-based Linux. We are checking which systems, if any, are affected. No service interruption is planned during these checks.

    This maintenance notice will remain open while the checks are underway. We will post findings and any required follow-up here.

Reference 2026110562000976