UpCloud incident

Issue with TLS Certification

Notice Resolved View vendor source →

UpCloud experienced a notice incident on January 20, 2026 affecting DK-CPH1: Managed Load Balancer and NO-SVG1: Managed Load Balancer and 1 more component, lasting 16h 51m. The incident has been resolved; the full update timeline is below.

Started
Jan 20, 2026, 12:40 PM UTC
Resolved
Jan 21, 2026, 05:31 AM UTC
Duration
16h 51m
Detected by Pingoru
Jan 20, 2026, 12:40 PM UTC

Affected components

DK-CPH1: Managed Load BalancerNO-SVG1: Managed Load BalancerAU-SYD1: Managed Load BalancerDE-FRA1: Managed Load BalancerES-MAD1: Managed Load BalancerFI-HEL1: Managed Load BalancerFI-HEL2: Managed Load BalancerNL-AMS1: Managed Load BalancerPL-WAW1: Managed Load BalancerSG-SIN1: Managed Load Balancer

Update timeline

  1. identified Jan 20, 2026, 12:40 PM UTC

    We have identified an issue on newly created Managed Object Storage, Managed Kubernetes and Managed Load Balancer instances. This affects the creation and renewal of TLS/SSL certifications and is causing newly created instances to enter a pending state. We apologize for any inconvenience that this may cause and are working towards resolving the issue as soon as possible.

  2. identified Jan 20, 2026, 12:40 PM UTC

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

  3. identified Jan 20, 2026, 04:22 PM UTC

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

  4. monitoring Jan 21, 2026, 03:03 AM UTC

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

  5. resolved Jan 21, 2026, 05:31 AM UTC

    This incident has been resolved.