Precios
Historial de estadoActualizaciones RSSAPI de estado

Desarrollado por Uptimus

    Historial de interrupciones de Upcloud

    59 incidentes de Upcloud registrados desde agosto de 2024, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.

    Volver al estado actual

    Temas de conectividad de API y panel de control

    Comenzó 23 de octubre de 2026 a las 0:20 UTC · 1h 48m

    IssuesIncidente menor
    Componentes afectados
    UpCloud Control PanelAPI
    1. 23 de octubre de 2026 a las 0:20 UTCinvestigating

      Estamos investigando un problema de conectividad con el Panel de Control y API.

    2. 23 de octubre de 2026 a las 0:51 UTCmonitoring

      Se ha aplicado una solución y estamos monitoreando la situación.

    3. 23 de octubre de 2026 a las 2:09 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    [SG-SIN1] Edición de almacenamiento de objetos gestionados

    Comenzó 6 de octubre de 2026 a las 6:58 UTC · 7d 7h

    IssuesIncidente menor
    Componentes afectados
    APAC-1: Managed Object Storage
    1. 6 de octubre de 2026 a las 6:58 UTCidentified

      Hemos identificado un problema de degradación de los servicios que afecta al almacenamiento de objetos gestionados en nuestro centro de datos de Singapur (SG-SIN1). El problema causa picos periódicos de latencia y errores HTTP 503 que duran de 10 a 15 minutos. Hemos identificado la causa raíz y estamos trabajando activamente para resolver la cuestión y restaurar plenamente el servicio. Nos disculpamos por la molestia y proporcionaremos nuevas actualizaciones lo antes posible. Si tiene alguna pregunta, comuníquese con nuestro equipo de soporte a través de chat en vivo o correo electrónico [email protected]

    2. 6 de octubre de 2026 a las 18:13 UTCmonitoring

      Hemos identificado la causa raíz de la degradación del servicio que afecta al almacenamiento de objetos gestionados en nuestro centro de datos de Singapur (SG-SIN1) y hemos desplegado una solución. Actualmente monitorizamos el sistema para garantizar la estabilidad a largo plazo. Gracias por su paciencia, y nos disculpamos por cualquier inconveniente causado. Si experimenta algún problema, póngase en contacto con nuestro equipo de soporte a través de chat en vivo o en [email protected].

    3. 13 de octubre de 2026 a las 14:50 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    [FI-HEL2]: Problemas de almacenamiento de archivos

    Comenzó 28 de septiembre de 2026 a las 14:01 UTC · 2h 40m

    IssuesIncidente menor
    Componentes afectados
    FI-HEL2: File Storage
    1. 28 de septiembre de 2026 a las 14:01 UTCinvestigating

      Estamos investigando un problema de backend de servicio de almacenamiento de archivos que está afectando algunos servicios de almacenamiento de archivos en nuestro centro de datos FI-HEL2. Hemos notado algunas fallas no deseadas para algunos servicios de almacenamiento de archivos NFS y como medida de seguridad estamos realizando algunas más fallas para resolver y aislar los problemas restantes y devolver el backend a su estado normal. Durante estos fallos adicionales para algunos de FI-HEL2 los servicios de almacenamiento de archivos NFS pueden suceder. Lo sentimos por la molestia.

    2. 28 de septiembre de 2026 a las 15:34 UTCmonitoring

      Se ha aplicado una solución y estamos monitoreando los resultados.

    3. 28 de septiembre de 2026 a las 16:41 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    [DE-FRA1]: Cuestión del Backend de Almacenamiento

    Comenzó 25 de agosto de 2026 a las 23:45 UTC · 7h 4m

    IssuesIncidente menor
    Componentes afectados
    DE-FRA1: Storage Backends
    1. 25 de agosto de 2026 a las 23:45 UTCinvestigating

      Estamos investigando un problema de backend de almacenamiento que está afectando algunos recursos incluyendo servidores de nube en nuestro centro de datos DE-FRA1. Estamos trabajando activamente para resolver esta cuestión lo antes posible. Lamentamos cualquier inconveniente que esto pueda estar causando y agradeciéndole por su paciencia mientras trabajamos para abordar esto. Si tiene alguna pregunta o inquietud, por favor no dude en ponerse en contacto con nuestro soporte en vivo 24/7 en nuestro panel de control o por correo electrónico a [email protected].

    2. 26 de agosto de 2026 a las 3:47 UTCmonitoring

      Se ha aplicado una solución y estamos monitoreando los resultados.

    3. 26 de agosto de 2026 a las 6:49 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    Cloud Server Deployment Error

    Comenzó 11 de agosto de 2026 a las 9:12 UTC · 1h 57m

    OutageIncidente mayor
    Componentes afectados
    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 de agosto de 2026 a las 9:12 UTCidentified

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

    2. 11 de agosto de 2026 a las 9: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 de agosto de 2026 a las 9: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 de agosto de 2026 a las 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 de agosto de 2026 a las 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.

    Chat en vivo temporalmente no disponible

    Comenzó 3 de agosto de 2026 a las 15:29 UTC · 5h 26m

    IssuesIncidente menor
    Componentes afectados
    UpCloud Control Panel
    1. 3 de agosto de 2026 a las 15:29 UTCidentified

      Actualmente estamos experimentando problemas técnicos con nuestro sistema Live Chat. Usted todavía puede llegar a nuestro equipo de soporte por correo electrónico [email protected]. Nos disculpamos por la molestia y proporcionaremos una actualización tan pronto como se restablezca el chat en vivo.

    2. 3 de agosto de 2026 a las 20:55 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    [EUROPE 2]: Asunto de almacenamiento de objetos identificado

    Comenzó 7 de julio de 2026 a las 12:02 UTC · 1h 1m

    IssuesIncidente menor
    Componentes afectados
    EUROPE-2: Managed Object Storage
    1. 7 de julio de 2026 a las 12:02 UTCidentified

      Hemos identificado un problema con nuestro almacén de objetos Europa 2 en nuestro centro de datos DE-FRA1. El problema puede causar que los servicios afectados no puedan leer o escribir al almacenamiento de objetos. Estamos trabajando para traer todos los servicios afectados en línea y resolver la situación lo antes posible.

    2. 7 de julio de 2026 a las 12:18 UTCmonitoring

      Se ha aplicado una solución y estamos monitoreando esto.

    3. 7 de julio de 2026 a las 13:02 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    DNS Resolution Issues in FI-HEL1 and FI-HEL2

    Comenzó 16 de junio de 2026 a las 10:18 UTC · 3h 12m

    Pending
    Componentes afectados
    GeneralFI-HEL2: OtherFI-HEL1: Other
    1. 16 de junio de 2026 a las 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 de junio de 2026 a las 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/.

    Cuestiones del procesador de pago con American Express

    Comenzó 15 de junio de 2026 a las 13:12 UTC · 23d 20h

    Pending
    1. 15 de junio de 2026 a las 13:12 UTCinvestigating

      Estamos investigando un problema que afecta los pagos de tarjetas American Express, por lo que estamos viendo mayores tasas de fracaso. Todos los demás métodos de pago siguen siendo plenamente operativos. Recomendamos a aquellos que usan American Express para pagos automatizados para comprobar que estos han sido exitosos. Como solución de trabajo, los clientes pueden utilizar un método de pago alternativo mientras trabajamos con nuestro proveedor de pagos para resolver el problema. Los métodos de pago disponibles se enumeran aquí: https://upcloud.com/docs/getting-started/billing/payment-methods/ Proporcionaremos más actualizaciones a medida que estén disponibles. Si tiene alguna pregunta o necesita más asistencia, comuníquese con nosotros por correo electrónico: [email protected] o Chat en vivo en nuestro panel de control https://hub.upcloud.com

    2. 18 de junio de 2026 a las 12:43 UTCidentified

      El problema ha sido identificado y estamos trabajando en una resolución. Afecta específicamente los pagos realizados en Euro, con tarjetas American Express. Como solución de trabajo, los clientes pueden utilizar un método de pago alternativo mientras trabajamos con nuestro proveedor de pagos para resolver el problema. Los métodos de pago disponibles se enumeran aquí: https://upcloud.com/docs/getting-started/billing/payment-methods/ Proporcionaremos más actualizaciones a medida que estén disponibles. Si tiene alguna pregunta o necesita más asistencia, comuníquese con nosotros por correo electrónico: [email protected] o Chat en vivo en nuestro panel de control https://hub.upcloud.com

    3. 8 de julio de 2026 a las 13:44 UTCmonitoring

      Se ha implementado una solución, y los pagos Euro (EUR) utilizando tarjetas American Express se procesan de nuevo normalmente. Seguimos vigilando de cerca la situación para garantizar la estabilidad en curso. Si tiene alguna pregunta o necesita más asistencia, comuníquese con nosotros por correo electrónico a [email protected] o a través de Chat en vivo en nuestro panel de control: https://hub.upcloud.com

    4. 9 de julio de 2026 a las 9:18 UTCresolved

      Esto ya está resuelto. Si tiene alguna pregunta o necesita más asistencia, comuníquese con nosotros por correo electrónico a [email protected] o a través de Chat en vivo en nuestro panel de control: https://hub.upcloud.com

    Traducido automáticamente desde la actualización oficial del incidente.

    [SG-SIN1]: Networking issue

    Comenzó 5 de junio de 2026 a las 14:50 UTC · 4h 21m

    IssuesIncidente menor
    Componentes afectados
    SG-SIN1: Managed KubernetesAU-SYD1: Managed KubernetesAPAC-1: Managed Object StorageSG-SIN1: Network Connections
    1. 5 de junio de 2026 a las 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 de junio de 2026 a las 14:58 UTCinvestigating

      We are currently investigating this issue.

    3. 5 de junio de 2026 a las 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 de junio de 2026 a las 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 de junio de 2026 a las 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

    Comenzó 26 de mayo de 2026 a las 14:42 UTC · 3h 2m

    OutageIncidente mayor
    Componentes afectados
    General
    1. 26 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 17:44 UTCresolved

      This incident has been resolved.

    [SG-SIN1]: Managed Kubernetes Issue

    Comenzó 13 de mayo de 2026 a las 3:26 UTC · 9h 13m

    IssuesIncidente menor
    Componentes afectados
    SG-SIN1: Managed Kubernetes
    1. 13 de mayo de 2026 a las 3: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 de mayo de 2026 a las 6: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 de mayo de 2026 a las 8:20 UTCmonitoring

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

    4. 13 de mayo de 2026 a las 12:39 UTCresolved

      This incident has been resolved.

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

    Comenzó 4 de mayo de 2026 a las 11:15 UTC · 2h 6m

    Pending
    Componentes afectados
    UpCloud Control PanelAPI
    1. 4 de mayo de 2026 a las 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 de mayo de 2026 a las 12:28 UTCidentified

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

    3. 4 de mayo de 2026 a las 12:35 UTCmonitoring

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

    4. 4 de mayo de 2026 a las 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

    Comenzó 29 de abril de 2026 a las 18:28 UTC · 3h 23m

    IssuesIncidente menor
    Componentes afectados
    EUROPE-1: Managed Object Storage
    1. 29 de abril de 2026 a las 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 de abril de 2026 a las 19:30 UTCidentified

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

    3. 29 de abril de 2026 a las 20:43 UTCmonitoring

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

    4. 29 de abril de 2026 a las 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

    Comenzó 22 de abril de 2026 a las 3:47 UTC · 3h 10m

    IssuesIncidente menor
    Componentes afectados
    SG-SIN1: Cloud Servers
    1. 22 de abril de 2026 a las 3: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 de abril de 2026 a las 4:53 UTCmonitoring

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

    3. 22 de abril de 2026 a las 5: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 de abril de 2026 a las 6:57 UTCresolved

      This incident has been resolved.

    Issue with new Cloud Server Deployments

    Comenzó 15 de abril de 2026 a las 7:44 UTC · 3h 33m

    IssuesIncidente menor
    Componentes afectados
    US-SJO1: Cloud Servers
    1. 15 de abril de 2026 a las 7: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 de abril de 2026 a las 8: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 de abril de 2026 a las 9: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 de abril de 2026 a las 11:17 UTCresolved

      This incident has been resolved.

    [US-NYC1]: Storage backend issue

    Comenzó 31 de marzo de 2026 a las 1:48 UTC · 4h 45m

    IssuesIncidente menor
    Componentes afectados
    US-NYC1: Storage Backends
    1. 31 de marzo de 2026 a las 1:48 UTCinvestigating

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

    2. 31 de marzo de 2026 a las 6:03 UTCmonitoring

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

    3. 31 de marzo de 2026 a las 6:33 UTCresolved

      This incident has been resolved.

    [FI-HEL1]: Compute Node Issue

    Comenzó 16 de marzo de 2026 a las 19:28 UTC · 17h 33m

    Pending
    Componentes afectados
    FI-HEL1: Managed Load BalancerFI-HEL1: Managed KubernetesFI-HEL1: Cloud Servers
    1. 16 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 23:37 UTCidentified

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

    5. 17 de marzo de 2026 a las 0: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 de marzo de 2026 a las 1: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 de marzo de 2026 a las 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

    Comenzó 16 de marzo de 2026 a las 12:02 UTC · 3h 4m

    IssuesIncidente menor
    Componentes afectados
    APAC-1: Managed Object Storage
    1. 16 de marzo de 2026 a las 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 de marzo de 2026 a las 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 de marzo de 2026 a las 15:06 UTCresolved

      This incident has been resolved.

    [Europe-1] Object Storage

    Comenzó 12 de marzo de 2026 a las 13:24 UTC · 5h 5m

    IssuesIncidente menor
    Componentes afectados
    EUROPE-1: Managed Object Storage
    1. 12 de marzo de 2026 a las 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 de marzo de 2026 a las 16:36 UTCmonitoring

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

    3. 12 de marzo de 2026 a las 18:29 UTCresolved

      This incident has been resolved.