Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Störungsverlauf von Upcloud

    59 Upcloud incidents · August 2024 — official updates, affected components, duration and resolution details.

    Zurück zum aktuellen Status

    UpCloud API und Control Panel Connectivity Probleme

    Beginn 23. Oktober 2026 um 00:20 UTC · 1h 48m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    UpCloud Control PanelAPI
    1. 23. Oktober 2026 um 00:20 UTCinvestigating

      Wir untersuchen ein Verbindungsproblem mit dem Control Panel und der API.

    2. 23. Oktober 2026 um 00:51 UTCmonitoring

      Es wurde ein Fix umgesetzt, und wir beobachten die Situation.

    3. 23. Oktober 2026 um 02:09 UTCresolved

      Dieser Vorfall wurde behoben.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    [SG-SIN1] Managed Object Storage Problem

    Beginn 6. Oktober 2026 um 06:58 UTC · 7d 7h

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    APAC-1: Managed Object Storage
    1. 6. Oktober 2026 um 06:58 UTCidentified

      Wir haben ein Service-Degradationsproblem identifiziert, das Managed Object Storage in unserem Rechenzentrum in Singapur (SG-SIN1) betrifft. Das Problem verursacht periodische Latenzspitzen und HTTP 503-Fehler, die 10 bis 15 Minuten dauern. Wir haben die Ursache identifiziert und arbeiten aktiv daran, das Problem zu lösen und den Service vollständig wiederherzustellen. Wir entschuldigen uns für die Unannehmlichkeiten und werden so schnell wie möglich weitere Updates bereitstellen. Wenn Sie Fragen haben, kontaktieren Sie bitte unser Support-Team per Live-Chat oder E-Mail [email protected]

    2. 6. Oktober 2026 um 18:13 UTCmonitoring

      Wir haben die Ursache der Service-Degradation in unserem Rechenzentrum in Singapur (SG-SIN1) identifiziert und einen Fix implementiert. Wir überwachen derzeit das System, um langfristige Stabilität zu gewährleisten. Vielen Dank für Ihre Geduld und wir entschuldigen uns für alle Unannehmlichkeiten. Wenn Sie Probleme haben, kontaktieren Sie bitte unser Support-Team per Live-Chat oder unter [email protected].

    3. 13. Oktober 2026 um 14:50 UTCresolved

      Dieser Vorfall wurde behoben.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    [FI-HEL2]: Dateispeicherprobleme

    Beginn 28. September 2026 um 14:01 UTC · 2h 40m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    FI-HEL2: File Storage
    1. 28. September 2026 um 14:01 UTCinvestigating

      Wir untersuchen ein Backend-Problem mit dem Dateispeicherdienst, das einige Dateispeicherdienste in unserem FI-HEL2-Rechenzentrum betrifft. Wir haben einige unerwünschte Failovers für einige File Storage NFS-Dienste festgestellt, und als Sicherheitsmaßnahme führen wir einige weitere Failovers durch, um die verbleibenden Probleme zu beheben und zu isolieren und das Backend in seinen normalen Zustand zurückzukehren. Während dieser zusätzlichen Failovers für einige von FI-HEL2 können die File Storage NFS-Dienste auftreten. Wir bedauern die Unannehmlichkeiten.

    2. 28. September 2026 um 15:34 UTCmonitoring

      Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

    3. 28. September 2026 um 16:41 UTCresolved

      Dieser Vorfall wurde behoben.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    [DE-FRA1]: Storage Backend Problem

    Beginn 25. August 2026 um 23:45 UTC · 7h 4m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    DE-FRA1: Storage Backends
    1. 25. August 2026 um 23:45 UTCinvestigating

      Wir untersuchen ein Storage-Backend-Problem, das einige Ressourcen wie Cloud-Server in unserem DE-FRA1-Rechenzentrum betrifft. Wir arbeiten aktiv daran, dieses Problem so schnell wie möglich zu lösen. Wir bedauern jede Unannehmlichkeit, die dies verursachen könnte, und danken Ihnen für Ihre Geduld, während wir daran arbeiten, dies anzugehen. Wenn Sie Fragen oder Bedenken haben, kontaktieren Sie bitte unseren 24/7 Live-Support in unserem Control Panel oder per E-Mail unter [email protected].

    2. 26. August 2026 um 03:47 UTCmonitoring

      Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

    3. 26. August 2026 um 06:49 UTCresolved

      Dieser Vorfall wurde behoben.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    Cloud Server Deployment Error

    Beginn 11. August 2026 um 09:12 UTC · 1h 57m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    SG-SIN1: Cloud ServersPL-WAW1: Cloud ServersAU-SYD1: Cloud ServersDK-CPH1: Cloud ServersUK-LON1: Cloud ServersSE-STO1: Cloud ServersUS:CHI1: Cloud ServersDE-FRA1: Cloud ServersNO-SVG1: Cloud ServersNL-AMS1: Cloud ServersFI-HEL2: Cloud ServersES-MAD1: Cloud ServersUS-NYC1: Cloud ServersUS-SJO1: Cloud ServersFI-HEL1: Cloud Servers
    1. 11. August 2026 um 09:12 UTCidentified

      The issue has been identified, and we are working on fixing it. It affects all new deployments in all zones.

    2. 11. August 2026 um 09:23 UTCidentified

      We have identified the cause of the issue affecting Cloud Server Deployments and are actively working on a fix. The issue may impact new Cloud Server Deployments. Please refrain from attempting management operations, including Start, Restart, Shut down, and Force Shutdown, to avoid unexpected complications while we work to bring all affected services back online as swiftly as possible. We apologize for the inconvenience and will provide further updates as more information becomes available. If you have any questions or concerns regarding your services, please reach out to our support team via live chat at  or via email: [email protected]

    3. 11. August 2026 um 09:48 UTCidentified

      A fix has been implemented, and new Cloud Server deployments are now proceeding without errors. We are currently cleaning up Cloud Servers that were left in an error state during the incident.

    4. 11. August 2026 um 10:05 UTCmonitoring

      We thank you for your continued patience throughout this process and apologize for any impact. The incident is now resolved, and all affected services should be operational. For any further issues, please contact our Support team via live chat or email at [email protected]. We are compiling a detailed post-mortem to outline the sequence of events, the steps taken to rectify the situation, and the measures we are implementing to prevent such occurrences in the future. We understand the gravity of this disruption and extend our sincerest apologies to all affected customers.

    5. 11. August 2026 um 11:09 UTCresolved

      Our team has confirmed the full resolution of the issue. All affected services should now be functioning normally. If you continue to experience any further issues, please contact our Support team via Live Chat or email [email protected] Thank you for your patience, and we apologize for any inconvenience caused.

    Live Chat vorübergehend nicht verfügbar

    Beginn 3. August 2026 um 15:29 UTC · 5h 26m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    UpCloud Control Panel
    1. 3. August 2026 um 15:29 UTCidentified

      Wir haben derzeit technische probleme mit unserem live-chat-system. Sie können unser Support-Team weiterhin erreichen, indem Sie [email protected] per E-Mail kontaktieren. Wir entschuldigen uns für die unannehmlichkeiten und werden ein update bereitstellen, sobald der live-chat wiederhergestellt ist.

    2. 3. August 2026 um 20:55 UTCresolved

      Dieser Vorfall wurde behoben.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    [EUROPE 2]: Objektspeicherproblem identifiziert

    Beginn 7. Juli 2026 um 12:02 UTC · 1h 1m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    EUROPE-2: Managed Object Storage
    1. 7. Juli 2026 um 12:02 UTCidentified

      Wir haben ein Problem mit unserem Europe 2 Object Storage in unserem DE-FRA1 Rechenzentrum festgestellt. Das Problem kann dazu führen, dass betroffene Dienste den Objektspeicher nicht lesen oder schreiben können. Wir arbeiten daran, alle betroffenen Dienste wieder online zu bringen und die Situation so schnell wie möglich zu lösen.

    2. 7. Juli 2026 um 12:18 UTCmonitoring

      Ein Fix wurde implementiert, und wir überwachen dies.

    3. 7. Juli 2026 um 13:02 UTCresolved

      Dieser Vorfall wurde behoben.

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    DNS Resolution Issues in FI-HEL1 and FI-HEL2

    Beginn 16. Juni 2026 um 10:18 UTC · 3h 12m

    Pending
    Betroffene Komponenten
    GeneralFI-HEL2: OtherFI-HEL1: Other
    1. 16. Juni 2026 um 10:18 UTCmonitoring

      We have resolved the DNS resolution issue that was causing increased response times. Impacting our control panel https://hub.upcloud.com/ and certain cloud services in the FI-HEL1 and FI-HEL2 data centres. All systems are now stable, and there should be no further visible impact. We are continuing to monitor performance closely while we investigate the root cause. We apologise for the inconvenience. If you have any questions, please don't hesitate to contact us via email [email protected] or via live chat https://hub.upcloud.com/.

    2. 16. Juni 2026 um 13:30 UTCresolved

      We have resolved the DNS resolution issue that was causing increased response times. Impacting our control panel https://hub.upcloud.com/ and certain cloud services in the FI-HEL1 and FI-HEL2 data centres. After monitoring our systems for a some time, we can confirm now the situation is stable. We apologise for the inconvenience. If you have any questions, please don't hesitate to contact us via email [email protected] or via live chat https://hub.upcloud.com/.

    Zahlungsprozessorprobleme mit American Express

    Beginn 15. Juni 2026 um 13:12 UTC · 23d 20h

    Pending
    1. 15. Juni 2026 um 13:12 UTCinvestigating

      Wir untersuchen ein Problem, das American Express Kartenzahlungen betrifft, für die wir erhöhte Ausfallraten sehen. Alle anderen Zahlungsmethoden bleiben voll funktionsfähig. Wir empfehlen denjenigen, die American Express für automatisierte Zahlungen verwenden, zu überprüfen, ob diese erfolgreich waren. Als Workaround können Kunden eine alternative Zahlungsmethode verwenden, während wir mit unserem Zahlungsanbieter zusammenarbeiten, um das Problem zu lösen. Die verfügbaren Zahlungsmethoden sind hier aufgeführt: https://upcloud.com/docs/getting-started/billing/payment-methods/ Wir werden weitere Updates bereitstellen, sobald sie verfügbar sind. Wenn Sie Fragen haben oder weitere Hilfe benötigen, kontaktieren Sie uns bitte per E-Mail: [email protected] oder Live Chat in unserem Bedienfeld https://hub.upcloud.com

    2. 18. Juni 2026 um 12:43 UTCidentified

      Das Problem wurde erkannt, und wir arbeiten an einer Lösung. Es betrifft speziell Zahlungen in Euro, mit American Express-Karten. Als Workaround können Kunden eine alternative Zahlungsmethode verwenden, während wir mit unserem Zahlungsanbieter zusammenarbeiten, um das Problem zu lösen. Die verfügbaren Zahlungsmethoden sind hier aufgeführt: https://upcloud.com/docs/getting-started/billing/payment-methods/ Wir werden weitere Updates bereitstellen, sobald sie verfügbar sind. Wenn Sie Fragen haben oder weitere Hilfe benötigen, kontaktieren Sie uns bitte per E-Mail: [email protected] oder Live Chat in unserem Bedienfeld https://hub.upcloud.com

    3. 8. Juli 2026 um 13:44 UTCmonitoring

      Ein Fix wurde implementiert, und Euro (EUR) Zahlungen mit American Express-Karten werden wieder normal verarbeitet. Wir werden die Situation weiterhin genau beobachten, um eine anhaltende Stabilität zu gewährleisten. Wenn Sie Fragen haben oder weitere Hilfe benötigen, kontaktieren Sie uns bitte per E-Mail unter [email protected] oder über den Live Chat in unserem Bedienfeld: https://hub.upcloud.com

    4. 9. Juli 2026 um 09:18 UTCresolved

      Das ist jetzt gelöst. Wenn Sie Fragen haben oder weitere Hilfe benötigen, kontaktieren Sie uns bitte per E-Mail unter [email protected] oder über den Live Chat in unserem Bedienfeld: https://hub.upcloud.com

    Automatisch aus der offiziellen Störungsmeldung übersetzt.

    [SG-SIN1]: Networking issue

    Beginn 5. Juni 2026 um 14:50 UTC · 4h 21m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    SG-SIN1: Managed KubernetesAU-SYD1: Managed KubernetesAPAC-1: Managed Object StorageSG-SIN1: Network Connections
    1. 5. Juni 2026 um 14:50 UTCidentified

      We have identified an issue with network connectivity in our SG-SIN1 data centre. The affected cloud servers may experience slow connections or become unreachable. We are working to restore connectivity and resolve the situation as soon as possible.

    2. 5. Juni 2026 um 14:58 UTCinvestigating

      We are currently investigating this issue.

    3. 5. Juni 2026 um 15:32 UTCidentified

      We have identified an issue with network connectivity in our SG-SIN1 data centre and AU-SYD1 🟢 Managed Kubernetes Cluster Workloads: Not Affected (100% Uptime) 🟢 Kubernetes API / kubectl: Not Affected 🔴 UpCloud Managed Kubernetes API & Control Panel Section: Temporarily Unavailable (Cannot create, view, delete, scale, or modify clusters) 🟢 Managed Object Storage Workloads: Not Affected (100% Uptime) 🔴 UpCloud Managed Object Storage API & Control Panel Section: Temporarily Unavailable (Cannot create, view, delete, scale, or modify clusters) We are actively working to resolve the incident. We sincerely apologise for any inconvenience this may cause to your operations. We will provide regular updates here as more information becomes available. If you have any questions or need further assistance, please reach out to us via email: [email protected] or Live Chat in our control panel https://hub.upcloud.com

    4. 5. Juni 2026 um 16:10 UTCmonitoring

      We have restored all affected Managed Kubernetes and Managed Object Storage to normal operating status and will continue to monitor the situation. 🟢 Managed Kubernetes Cluster Workloads: Not Affected (100% Uptime) 🟢 Kubernetes API / kubectl: Not Affected 🟢 UpCloud Managed Kubernetes API & Control Panel Section: Temporarily Unavailable (Cannot create, view, delete, scale, or modify clusters) 🟢 Managed Object Storage Workloads: Not Affected (100% Uptime) 🟢UpCloud Managed Object Storage API & Control Panel Section: Temporarily Unavailable (Cannot create, view, delete, scale, or modify clusters) If your services is still not fully functional, please contact our support at [email protected]. We apologise for the incident.

    5. 5. Juni 2026 um 19:11 UTCresolved

      We have resolved the root cause of the networking issue affecting our Managed Object Storage and our Managed Kubernetes service in our SG-SIN1 data center. All affected services should now be functioning normally. If you continue to experience any further issues, please contact our Support team via Live Chat or email [email protected]. Thank you for your patience and we apologize for any inconvenience caused.

    Error with new cloud service deployments

    Beginn 26. Mai 2026 um 14:42 UTC · 3h 2m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    General
    1. 26. Mai 2026 um 14:42 UTCinvestigating

      We are currently investigating an issue affecting new cloud service deployments. We apologise for the inconvenience and will provide an update in 30 minutes with more information.

    2. 26. Mai 2026 um 15:15 UTCmonitoring

      We have implemented the fix and isolated the issue. And we will keep monitoring the situation. We sincerely apologise for any inconvenience. And if you have any issues or questions, please don't hesitate to contact us via email: [email protected] or via live chat from our control panel.

    3. 26. Mai 2026 um 17:44 UTCresolved

      This incident has been resolved.

    [SG-SIN1]: Managed Kubernetes Issue

    Beginn 13. Mai 2026 um 03:26 UTC · 9h 13m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    SG-SIN1: Managed Kubernetes
    1. 13. Mai 2026 um 03:26 UTCinvestigating

      We are currently investigating an issue affecting the Managed Kubernetes Service in our SG-SIN1 region. Users may find that their clusters are stuck in a Pending state. Our team is currently investigating the issue to identify the root cause. We will provide additional updates as more information becomes available. We apologise for any inconvenience this may cause.

    2. 13. Mai 2026 um 06:11 UTCidentified

      We have identified the root cause of the issues affecting the Managed Kubernetes service in the SG-SIN1 region. Our team is currently working on a resolution to address the issue. We will provide further updates once the fix is applied.

    3. 13. Mai 2026 um 08:20 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. 13. Mai 2026 um 12:39 UTCresolved

      This incident has been resolved.

    Control Panel https://hub.upcloud.com/ login issues

    Beginn 4. Mai 2026 um 11:15 UTC · 2h 6m

    Pending
    Betroffene Komponenten
    UpCloud Control PanelAPI
    1. 4. Mai 2026 um 11:15 UTCidentified

      We have identified an issue causing slowness with new logins to our control panel at https://hub.upcloud.com/ And we are currently working on fully stabilising the situation. This may also delay calls to our API, and dependent systems such as Terraform. Please note that this issue does not affect your active cloud services. If you experience any issues, please do not hesitate to contact our support team via email [email protected]. We apologise for the inconvenience.

    2. 4. Mai 2026 um 12:28 UTCidentified

      We are continuing to work on a fix for this issue.

    3. 4. Mai 2026 um 12:35 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. 4. Mai 2026 um 13:21 UTCresolved

      This incident has been fully resolved. Please contact our support team via live chat or [email protected] if you have any further questions regarding the incident.

    [FI-HEL2]: EUROPE-1 Managed Object Storage Performance Issues

    Beginn 29. April 2026 um 18:28 UTC · 3h 23m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    EUROPE-1: Managed Object Storage
    1. 29. April 2026 um 18:28 UTCidentified

      We have identified an issue causing latency and timeouts when accessing or managing Managed Object Storage in the Europe-1 region. Users may experience temporary timeouts or failure which management operations or to load bucket details. All other Managed Object Storage regions (Europe-2, Europe-3, US-1, APAC-1) are unaffected. If you have any questions or concerns regarding your services, please reach out to our support team via live chat at https://hub.upcloud.com/ or via email: [email protected]

    2. 29. April 2026 um 19:30 UTCidentified

      We are continuing to work on a fix for this issue.

    3. 29. April 2026 um 20:43 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. 29. April 2026 um 21:51 UTCresolved

      Our team has confirmed the full resolution of the issue affecting our EUROPE-1 Managed Object Storage in our FI-HEL2 data center. All affected services should now be functioning normally. If you continue to experience any further issues, please contact our Support team via Live Chat or email [email protected] Thank you for your patience and we apologize for any inconvenience caused.

    [SG-SIN1]: Compute node issue

    Beginn 22. April 2026 um 03:47 UTC · 3h 10m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    SG-SIN1: Cloud Servers
    1. 22. April 2026 um 03:47 UTCidentified

      We have identified an issue with one of the compute nodes in our SG-SIN1 data centre. The problem may cause affected cloud servers to become slow or unresponsive. We are working to bring all affected servers back online and resolve the situation as soon as possible.

    2. 22. April 2026 um 04:53 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. 22. April 2026 um 05:07 UTCmonitoring

      Our team continues to be fully engaged and focused on finding a mitigation. To avoid unexpected complications during the recovery process, please refrain from attempting server management operations, including Start, Restart, Shut down, and Force Shutdown. We apologize for the inconvenience and appreciate your patience as we continue working to address the situation. If you have any questions or concerns regarding your services, please reach out to our Support team via Live Chat or via email [email protected]

    4. 22. April 2026 um 06:57 UTCresolved

      This incident has been resolved.

    Issue with new Cloud Server Deployments

    Beginn 15. April 2026 um 07:44 UTC · 3h 33m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    US-SJO1: Cloud Servers
    1. 15. April 2026 um 07:44 UTCinvestigating

      We are currently investigating reports of issues affecting the deployment of new Cloud Servers in our US-SJO1 data center. We sincerely apologize for the inconvenience and will share more information as soon as it becomes available.

    2. 15. April 2026 um 08:09 UTCidentified

      We have identified the cause of the issue and applied a fix. While we are seeing signs of new Cloud Server deployment operations recovering, we are continuing to work on a permanent resolution to prevent a recurrence. If you have any questions or concerns regarding your services, please reach out to our support team via Live Chat or email [email protected]

    3. 15. April 2026 um 09:00 UTCmonitoring

      We have been monitoring the fix implemented earlier and all internal systems are performing as expected. All affected services have been fully restored. We will continue to monitor the situation until we can confirm the full resolution of the issue. If you continue to experience any persistent issues with your cloud services in the US-SJO1 region, please reach out to our support team immediately via Live Chat or email [email protected]

    4. 15. April 2026 um 11:17 UTCresolved

      This incident has been resolved.

    [US-NYC1]: Storage backend issue

    Beginn 31. März 2026 um 01:48 UTC · 4h 45m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    US-NYC1: Storage Backends
    1. 31. März 2026 um 01:48 UTCinvestigating

      We are investigating a storage backend issue that is affecting some cloud servers in our US-NYC1 data centre.

    2. 31. März 2026 um 06:03 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. 31. März 2026 um 06:33 UTCresolved

      This incident has been resolved.

    [FI-HEL1]: Compute Node Issue

    Beginn 16. März 2026 um 19:28 UTC · 17h 33m

    Pending
    Betroffene Komponenten
    FI-HEL1: Managed Load BalancerFI-HEL1: Managed KubernetesFI-HEL1: Cloud Servers
    1. 16. März 2026 um 19:28 UTCidentified

      We have identified a compute node issue affecting some Cloud Servers, Managed Load Balancers and Managed Kubernetes services in our FI-HEL1 data center. You may experience unresponsive servers, delays or failures in provisioning new resources, or errors when managing existing clusters and load balancers in this zone. We are working to bring all affected services back online and resolve the situation as soon as possible. If you have any questions or concerns regarding your services, please reach out to our support team via live chat or at [email protected].

    2. 16. März 2026 um 20:33 UTCidentified

      Our team is working to ensure all services are fully restored and operating normally. We have deployed a fix for the issue affecting the managed resources. It may take a short time for these changes to take effect across all resources. If you have any questions or concerns regarding your services, please reach out to our support team via live chat at hub.upcloud.com or via email: [email protected]

    3. 16. März 2026 um 21:34 UTCidentified

      We are continuing to work on this issue to ensure all services are fully restored to normal operation. The earlier fix is still finishing propagating to all managed resources.

    4. 16. März 2026 um 23:37 UTCidentified

      We are continuing to work on this issue to ensure all services are fully restored to normal operation.

    5. 17. März 2026 um 00:36 UTCidentified

      We are continuing to work on this issue to ensure all services are fully restored to normal operation. Normal operational status has been restored across the majority of our cloud infrastructure and managed services.

    6. 17. März 2026 um 01:38 UTCmonitoring

      We have restored all affected cloud servers to normal operating status and continue to monitor the situation. If your server is still not fully functional, please contact our support at [email protected] or reach out to us via live chat at hub.upcloud.com We apologise for the incident.

    7. 17. März 2026 um 13:01 UTCresolved

      We have been monitoring the situation closely over the 12 hours and can confirm that all affected services have now been fully restored. The Issue impacted some of our Managed Load Balancer instances within the FI-HEL1 Data Centre, which subsequently impacted some Managed Kubernetes clusters in that region. We sincerely apologise for this incident and we continue our internal investigation. If you have any remaining questions, please contact us via email at [email protected] or through our live chat https://hub.upcloud.com/

    [APAC-1]: Object Storage 503 Errors

    Beginn 16. März 2026 um 12:02 UTC · 3h 4m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    APAC-1: Managed Object Storage
    1. 16. März 2026 um 12:02 UTCinvestigating

      We are currently investigating an issue affecting Managed Object Storage in our APAC-1 location, specifically returning 503 errors during operations sporadically. We apologise for the inconvenience and will provide further updates as more information becomes available.

    2. 16. März 2026 um 14:32 UTCmonitoring

      We thank you for your continued patience throughout this process and apologize for any impact. The incident is now resolved, and all affected services should be operational. For any further issues, please contact our Support team via live chat or email at [email protected] We are compiling a detailed post-mortem to outline the sequence of events, the steps taken to rectify the situation, and the measures we are implementing to prevent such occurrences in the future. We understand the gravity of this disruption and extend our sincerest apologies to all affected customers.

    3. 16. März 2026 um 15:06 UTCresolved

      This incident has been resolved.

    [Europe-1] Object Storage

    Beginn 12. März 2026 um 13:24 UTC · 5h 5m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    EUROPE-1: Managed Object Storage
    1. 12. März 2026 um 13:24 UTCinvestigating

      We are currently witnessing degraded performance with our Object Storage instances in our Europe-1 zone. We are actively working to resolve this issue as swiftly as possible. We regret any inconvenience this might be causing and thank you for your patience as we work to address this. If you have any questions or concerns, please feel free to contact our 24/7 live Support team in our control panel or by emailing [email protected].

    2. 12. März 2026 um 16:36 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. 12. März 2026 um 18:29 UTCresolved

      This incident has been resolved.