Ubicloud Outage History

Ubicloud is up right now

Pingoru has recorded 35 incidents for Ubicloud: 35 in the last 12 months and 19 in the last 90 days.

Source: status.ubicloud.com

35incidents recorded
35last 12 months
19last 90 days
8 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct12
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct6%
Pingoru began tracking Ubicloud in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 20263143 of 744 (19%)
June 2026251 of 720 (7%)
July 202625 of 744 (1%)
August 202612 of 744 (0%)
September 2026512 of 720 (2%)
October 20261232 of 511 (6%)

Incidents, newest first

Major October 21, 2026 Delays for Pull Requests and Webhook deliveries 4h 30m GitHub Actions Service (GitHub → Actions), GitHub Actions Service (GitHub → Webhooks)

Started Oct 21, 2026, 02:52 PM UTC· resolved Oct 21, 2026, 07:22 PM UTC

  1. investigating Oct 21, 2026, 02:52 PM UTC

    We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks

  2. investigating Oct 21, 2026, 03:15 PM UTC

    Actions is experiencing degraded performance. We are continuing to investigate.

  3. investigating Oct 21, 2026, 03:36 PM UTC

    We are investigating delays affecting pull request updates and webhook deliveries. Increased load on our event streaming platform is contributing to hotspots. We are shifting traffic away from affected areas and adding processing capacity; impact is ongoing while these mitigations take effect.

  4. investigating Oct 21, 2026, 03:58 PM UTC

    We continue to see delays affecting pull request updates, webhook deliveries, and audit log events. The event streaming platform is showing signs of recovery, and we are monitoring as the impact continues.

  5. investigating Oct 21, 2026, 04:17 PM UTC

    Audit log events and Actions workflow status updates continue to be delayed. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring the recovery and will share further updates as we learn more.

  6. investigating Oct 21, 2026, 04:25 PM UTC

    Audit log events are delayed by up to 100 minutes, and Actions workflow status updates continue to experience extended delays. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring recovery and will share further updates as we learn more.

  7. investigating Oct 21, 2026, 04:33 PM UTC

    Pull Requests is operating normally.

  8. investigating Oct 21, 2026, 04:34 PM UTC

    Audit log events continue to be delayed by up to 110 minutes. Pull request updates have recovered. Actions is recovering, and users should no longer experience impact in Actions. Webhook deliveries continue to recover as we work through backlogs. We are monitoring recovery and will share further updates as we learn more.

  9. investigating Oct 21, 2026, 04:57 PM UTC

    Actions and Webhooks are operating normally.

  10. investigating Oct 21, 2026, 04:59 PM UTC

    Actions and webhook deliveries have recovered. Audit log events are still delayed by about 100 minutes. We are working through the backlog, and full recovery will take some time. We will share more updates as recovery continues.

  11. investigating Oct 21, 2026, 05:09 PM UTC

    Pull request updates, Actions, and webhook deliveries have recovered. Audit log events are recovering and delays are decreasing, but we expect the remaining backlog to take approximately two to three hours to clear. We’re monitoring recovery and will share further updates.

  12. investigating Oct 21, 2026, 06:18 PM UTC

    Audit log events are recovering, with delays now below 90 minutes as the remaining backlog is processed. We’ve reduced load on the event-streaming platform and are monitoring recovery. Further updates will follow.

  13. investigating Oct 21, 2026, 06:52 PM UTC

    Audit log events continue to recover, with delays now below 70 minutes. We’ve applied mitigations to speed recovery and expect audit logs to fully recover in about 40 minutes. Pull request updates, Actions, and webhook deliveries remain recovered. We are monitoring progress and will share further updates.

  14. investigating Oct 21, 2026, 07:22 PM UTC

    Pull request updates, Actions, and webhook deliveries have recovered. Audit log delays are now below 40 minutes, within the healthy threshold, and continue to decrease as the remaining backlog is processed.

  15. resolved Oct 21, 2026, 07:22 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Read the full incident report →

Major October 19, 2026 Degraded availability for GitHub Actions, GitHub Pages and Webhooks 1h 54m GitHub Actions Service (Ubicloud Runners), GitHub Actions Service (GitHub → Actions), GitHub Actions Service (GitHub → Webhooks)

Started Oct 19, 2026, 03:49 PM UTC· resolved Oct 19, 2026, 05:44 PM UTC

  1. investigating Oct 19, 2026, 03:49 PM UTC

    We are investigating reports of degraded performance for Actions and Pages

  2. investigating Oct 19, 2026, 03:50 PM UTC

    Webhooks is experiencing degraded performance. We are continuing to investigate.

  3. investigating Oct 19, 2026, 03:56 PM UTC

    We’re currently investigating degraded availability affecting GitHub Actions, GitHub Pages and Webhooks. Customers may experience delays in workflow processing, site builds and webhook delivery.

  4. investigating Oct 19, 2026, 04:30 PM UTC

    We’re seeing recovery following mitigation and are continuing to monitor. Customers may still experience delays in GitHub Actions workflow status updates, GitHub Pages deployments, and check and workflow webhook events generated by Actions runs.

  5. monitoring Oct 19, 2026, 04:56 PM UTC

    Actions, Pages and Webhooks are operating normally.

  6. resolved Oct 19, 2026, 04:56 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

  7. monitoring Oct 19, 2026, 05:14 PM UTC

    GitHub had a major incident that delayed webhook delivery. They have resolved the issue, and we are able to provision runners successfully. Since they released the queued jobs all at once, there might be some delays in processing jobs due to the backlog.

  8. resolved Oct 19, 2026, 05:44 PM UTC

    Following GitHub’s earlier incident, the queued jobs released at once created a backlog on our runners. That backlog has now cleared, and jobs are being picked up normally. We’ll continue to monitor. Thank you for your patience.

Read the full incident report →

Major October 13, 2026 Console is back up 1m Web Services (Console)

Started Oct 13, 2026, 10:22 PM UTC· resolved Oct 13, 2026, 10:24 PM UTC

  1. investigating Oct 13, 2026, 10:22 PM UTC

    Console is down at the moment. This incident was automatically created by Instatus monitoring.

  2. resolved Oct 13, 2026, 10:24 PM UTC

    Console is back up. This incident was automatically resolved by Instatus monitoring.

Read the full incident report →

Minor October 13, 2026 Increased provisioning times for GitHub runners 4h 31m GitHub Actions Service (Ubicloud Runners)

Started Oct 13, 2026, 04:56 PM UTC· resolved Oct 13, 2026, 09:28 PM UTC

  1. investigating Oct 13, 2026, 04:56 PM UTC

    Our control plane has been experiencing increased provisioning times for GitHub runners. This may result in longer wait times for jobs to start. We are actively investigating the issue and will provide updates as we have more information.

  2. identified Oct 13, 2026, 06:22 PM UTC

    We identified the issue's root cause and we implemented a fix. We expect the fix to start improving the queue times in a short amount of time.

  3. monitoring Oct 13, 2026, 09:15 PM UTC

    The fix that we implemented didn't have the intended effect due to a high backlog. We took manual action to reduce the backlog. Queue times should be back to normal now. We're monitoring the situation.

  4. resolved Oct 13, 2026, 09:28 PM UTC

    This incident has been resolved. We are going to prepare and provide a retrospective in the upcoming days.

  5. resolved Oct 19, 2026, 02:12 PM UTC

    $18

Read the full incident report →

Minor October 12, 2026 Incident with Actions, Pull Requests and Issues 7h 54m GitHub Actions Service (GitHub → Actions)

Started Oct 12, 2026, 12:21 PM UTC· resolved Oct 12, 2026, 08:16 PM UTC

  1. investigating Oct 12, 2026, 12:21 PM UTC

    We are investigating reports of degraded performance for Actions, Issues and Pull Requests

  2. investigating Oct 12, 2026, 12:33 PM UTC

    Users may experience issues loading the Actions tab UI, interacting with the Checks API, queueing new Actions runs, creating and updating issues, and requesting PR reviews, including via REST and GraphQL APIs.

  3. investigating Oct 12, 2026, 12:57 PM UTC

    We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.

  4. investigating Oct 12, 2026, 01:02 PM UTC

    Pull Requests is operating normally.

  5. investigating Oct 12, 2026, 01:38 PM UTC

    Our initial mitigation was not fully successful, and users may still experience delays and errors with Actions, issues and projects, and notifications are delayed. We're continuing to investigate the root cause and work on additional mitigations.

  6. investigating Oct 12, 2026, 02:35 PM UTC

    The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

  7. investigating Oct 12, 2026, 02:36 PM UTC

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  8. investigating Oct 12, 2026, 02:37 PM UTC

    We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.

  9. investigating Oct 12, 2026, 03:19 PM UTC

    We have successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog.

  10. investigating Oct 12, 2026, 03:50 PM UTC

    Notifications have resumed but will continue to be delayed as we work through a backlog.

  11. investigating Oct 12, 2026, 05:34 PM UTC

    Web and email notifications continue to be delayed as we work through a backlog of notifications.

  12. investigating Oct 12, 2026, 07:28 PM UTC

    Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.

  13. resolved Oct 12, 2026, 08:16 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Read the full incident report →

Major October 7, 2026 Incident with Git Operations, Issues, Actions and Pull Requests 47m GitHub Actions Service (GitHub → Actions)

Started Oct 07, 2026, 05:17 PM UTC· resolved Oct 07, 2026, 06:04 PM UTC

  1. investigating Oct 07, 2026, 05:17 PM UTC

    We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests

  2. investigating Oct 07, 2026, 05:25 PM UTC

    We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update shortly.

  3. monitoring Oct 07, 2026, 05:27 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  4. monitoring Oct 07, 2026, 06:00 PM UTC

    All systems have recovered. We have applied mitigations and do not anticipate another recurrence.

  5. resolved Oct 07, 2026, 06:04 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Read the full incident report →

Major October 7, 2026 Incident with Git Operations, Pull Requests and Actions 1h 10m GitHub Actions Service (GitHub → Actions), GitHub Actions Service (GitHub → Webhooks)

Started Oct 07, 2026, 03:14 PM UTC· resolved Oct 07, 2026, 04:25 PM UTC

  1. investigating Oct 07, 2026, 03:14 PM UTC

    We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests

  2. investigating Oct 07, 2026, 03:14 PM UTC

    Webhooks is experiencing degraded performance. We are continuing to investigate.

  3. investigating Oct 07, 2026, 03:15 PM UTC

    Issues is experiencing degraded performance. We are continuing to investigate.

  4. investigating Oct 07, 2026, 03:16 PM UTC

    Webhooks is experiencing degraded availability. We are continuing to investigate.

  5. investigating Oct 07, 2026, 03:21 PM UTC

    Git Operations is experiencing degraded performance. We are continuing to investigate.

  6. investigating Oct 07, 2026, 03:24 PM UTC

    We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.

  7. investigating Oct 07, 2026, 03:25 PM UTC

    Pull Requests is experiencing degraded performance. We are continuing to investigate.

  8. investigating Oct 07, 2026, 03:27 PM UTC

    Git Operations is operating normally.

  9. investigating Oct 07, 2026, 03:27 PM UTC

    Webhooks is experiencing degraded performance. We are continuing to investigate.

  10. investigating Oct 07, 2026, 03:31 PM UTC

    The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

  11. investigating Oct 07, 2026, 03:32 PM UTC

    Actions is operating normally.

  12. investigating Oct 07, 2026, 03:35 PM UTC

    Git Operations is experiencing degraded performance. We are continuing to investigate.

  13. investigating Oct 07, 2026, 03:41 PM UTC

    We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.

  14. investigating Oct 07, 2026, 03:47 PM UTC

    The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

  15. investigating Oct 07, 2026, 03:49 PM UTC

    The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.

  16. monitoring Oct 07, 2026, 03:49 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  17. monitoring Oct 07, 2026, 03:56 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  18. monitoring Oct 07, 2026, 03:58 PM UTC

    We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.

  19. monitoring Oct 07, 2026, 04:23 PM UTC

    Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.

  20. resolved Oct 07, 2026, 04:25 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Read the full incident report →

Major October 6, 2026 Several services are degraded 3h 43m GitHub Actions Service (GitHub → Webhooks)

Started Oct 06, 2026, 07:57 PM UTC· resolved Oct 06, 2026, 11:40 PM UTC

  1. investigating Oct 06, 2026, 07:57 PM UTC

    We are investigating reports of degraded performance for Pull Requests and Webhooks

  2. investigating Oct 06, 2026, 08:04 PM UTC

    Webhooks is operating normally.

  3. investigating Oct 06, 2026, 08:12 PM UTC

    Pull Requests is operating normally.

  4. investigating Oct 06, 2026, 08:22 PM UTC

    A number of services including issues, pull requests, and webhooks, were briefly degraded, but have now recovered. Enterprise migrations are paused while we validate causes and mitigations.

  5. monitoring Oct 06, 2026, 08:26 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  6. investigating Oct 06, 2026, 08:57 PM UTC

    All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.

  7. investigating Oct 06, 2026, 09:29 PM UTC

    We are working towards a mitigation that will allow us to resume processing enterprise migrations.

  8. investigating Oct 06, 2026, 10:40 PM UTC

    We are deploying a mitigation and plan to resume migrations shortly thereafter

  9. resolved Oct 06, 2026, 11:40 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Read the full incident report →

Major October 5, 2026 Incident with Actions 3h 37m GitHub Actions Service (GitHub → Actions)

Started Oct 05, 2026, 07:11 PM UTC· resolved Oct 05, 2026, 10:49 PM UTC

  1. investigating Oct 05, 2026, 07:11 PM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating Oct 05, 2026, 07:15 PM UTC

    We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.

  3. investigating Oct 05, 2026, 07:50 PM UTC

    We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.

  4. investigating Oct 05, 2026, 08:39 PM UTC

    We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.

  5. investigating Oct 05, 2026, 08:47 PM UTC

    Actions is experiencing degraded availability. We are continuing to investigate.

  6. investigating Oct 05, 2026, 09:09 PM UTC

    In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.

  7. investigating Oct 05, 2026, 09:22 PM UTC

    Pages is experiencing degraded performance. We are continuing to investigate.

  8. investigating Oct 05, 2026, 09:31 PM UTC

    Actions is experiencing degraded performance. We are continuing to investigate.

  9. investigating Oct 05, 2026, 09:32 PM UTC

    We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.

  10. investigating Oct 05, 2026, 09:54 PM UTC

    Actions is operating normally.

  11. investigating Oct 05, 2026, 10:40 PM UTC

    Pages is operating normally.

  12. resolved Oct 05, 2026, 10:49 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Read the full incident report →

Minor October 1, 2026 Actions Job Delays 3h 9m GitHub Actions Service (GitHub → Actions)

Started Oct 01, 2026, 02:47 PM UTC· resolved Oct 01, 2026, 05:56 PM UTC

  1. investigating Oct 01, 2026, 02:47 PM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating Oct 01, 2026, 02:54 PM UTC

    We have identified the cause of increased Actions run start delays on Ubuntu runners and are actively deploying a fix. Customers may continue to experience intermittent delays while the mitigation rolls out and service metrics return to normal.

  3. investigating Oct 01, 2026, 03:02 PM UTC

    Run-start delays on Ubuntu runners have been resolved. We are investigating run-start delays on Windows runners and will share more information as it becomes available.

  4. monitoring Oct 01, 2026, 03:10 PM UTC

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  5. investigating Oct 01, 2026, 03:20 PM UTC

    Actions is experiencing degraded performance. We are continuing to investigate.

  6. investigating Oct 01, 2026, 03:29 PM UTC

    We are seeing a reoccurrence in run-start delays, and are continuing to investigate the issue. Customers will potentially experience delays of up to ten minutes.

  7. investigating Oct 01, 2026, 04:10 PM UTC

    We have identified an issue with our upstream provider which is causing Actions requests to 429 which is creating the delays. We have escalated to the owning team and are investigating how to mitigate the 429s.

  8. investigating Oct 01, 2026, 04:48 PM UTC

    We are currently applying a mitigation and anticipate recovery within thirty minutes.

  9. investigating Oct 01, 2026, 05:50 PM UTC

    GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition.

  10. resolved Oct 01, 2026, 05:56 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Read the full incident report →

Notice October 1, 2026 Increased provisioning times for large runner sizes (16 and 30 vCPUs) 1h 47m Ubicloud Runners

Started Oct 01, 2026, 02:37 PM UTC· resolved Oct 01, 2026, 04:24 PM UTC

  1. investigating Oct 01, 2026, 02:37 PM UTC

    We're seeing higher than usual demand for our runners. This is causing longer than usual provisioning times for larger runners (16 and 30 vCPUs). We're working to increase our capacity as quickly as possible and mitigate the issue.

  2. resolved Oct 01, 2026, 04:24 PM UTC

    Following an initial capacity increase, provisioning times have returned to normal. We're continuing to expand our fleet to meet future demand.

Read the full incident report →

Notice September 11, 2026 Intermittent failures on Canonical's official Ubuntu apt repositories 7h 38m Ubicloud Runners

Started Sep 11, 2026, 03:00 PM UTC· resolved Sep 11, 2026, 10:38 PM UTC

  1. monitoring Sep 11, 2026, 03:00 PM UTC

    Canonical's Ubuntu archive mirrors have gone down four separate times today. Their status page (https://status.canonical.com/#/?section=spIncidentHistory) lists each incident as brief and now resolved, but we are still seeing intermittent connection failures against those mirrors, which can cause apt-get steps to hang or fail. The Azure mirrors are holding up better right now. As a workaround, you can point your apt sources at azure.archive.ubuntu.com instead of archive.ubuntu.com and security.ubuntu.com by adding this step to your workflow: - run: printf "http://azure.archive.ubuntu.com/ubuntu/\tpriority:1\nhttps://archive.ubuntu.com/ubuntu/\tpriority:2\nhttps://security.ubuntu.com/ubuntu/\tpriority:3\n" | sudo tee /etc/apt/apt-mirrors.txt This keeps the official mirrors as lower-priority fallbacks, so builds still resolve packages if Azure becomes unreachable. We are monitoring the situation closely.

  2. resolved Sep 11, 2026, 10:38 PM UTC

    Canonical's Ubuntu apt mirrors have stabilized and we are no longer seeing failures on apt installs.

Read the full incident report →

Major July 25, 2026 Degraded availability for GitHub runners 39m GitHub Actions, GitHub API Requests

Started Jul 25, 2026, 12:36 PM UTC· resolved Jul 25, 2026, 01:15 PM UTC

  1. investigating Jul 25, 2026, 12:36 PM UTC

    Github runners availability has been degraded because of an incident in the upstream Github API. https://www.githubstatus.com/incidents/pz7g535gbs6p

  2. investigating Jul 25, 2026, 12:46 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 25, 2026, 01:04 PM UTC

    Number of errors from the upstream Github API has reduced. Although, the upstream incident is still active https://www.githubstatus.com/incidents/pz7g535gbs6p

  4. resolved Jul 25, 2026, 02:07 PM UTC

    The runners should be back to normal. The upstream github actions API incident has been resolved.

Read the full incident report →

Minor June 27, 2026 Issues with Postgres databases 1h 8m PostgreSQL

Started Jun 27, 2026, 07:00 PM UTC· resolved Jun 27, 2026, 08:09 PM UTC

  1. investigating Jun 27, 2026, 07:29 PM UTC

    We are currently investigating issues which mostly impacts Postgres services.

  2. monitoring Jun 27, 2026, 08:08 PM UTC

    Hetzner experienced a network outage at Falkenstein that affected some of our services: https://status.hetzner.com/incident/49567296-8543-43c1-a0e2-9755ad4bd018

  3. resolved Jun 27, 2026, 08:09 PM UTC

    The issue should now be resolved. Please let us know if you are still experiencing any problems. We appreciate your patience while we worked to resolve this.

Read the full incident report →

Notice June 10, 2026 Service Disruption in the US region due to networking outage 7h 1m Compute, PostgreSQL, Networking, Kubernetes

Started Jun 10, 2026, 05:10 PM UTC· resolved Jun 11, 2026, 12:11 AM UTC

  1. investigating Jun 10, 2026, 06:52 PM UTC

    We are currently investigating and working on fixing the problem.

  2. investigating Jun 10, 2026, 06:56 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 10, 2026, 07:56 PM UTC

    We experience problems in a subset of the underlying hardware, we are working with the provider to address these issues.

  4. resolved Jun 11, 2026, 12:11 AM UTC

    All customers have been migrated from affected hardware. If you notice anything out of place, email [email protected]

Read the full incident report →

Minor May 26, 2026 Degraded git checkouts on GitHub Actions runners (upstream GitHub) 7d 7h GitHub Actions

Started May 26, 2026, 11:37 AM UTC· resolved Jun 02, 2026, 06:57 PM UTC

  1. investigating May 26, 2026, 11:02 AM UTC

    We are investigating reports of slow or failing git checkout and git fetch steps on Ubicloud GitHub Actions runners. Jobs may stall, run very slowly, or time out during the checkout step. We are working to confirm the source.

  2. identified May 26, 2026, 11:06 AM UTC

    We have traced this to an upstream GitHub issue affecting git data transfer. Connections to GitHub establish normally (DNS, TCP, and TLS are healthy), but transfers stall mid-stream, producing very slow clone and fetch speeds, HTTP/2 stream cancellations, or checkout steps that hang for several minutes. This is occurring across multiple regions and is not specific to Ubicloud infrastructure. The behavior is being reported and tracked by others in the GitHub community here: https://github.com/orgs/community/discussions/196638. We will continue to monitor and update as GitHub addresses the underlying problem. If you need to mitigate in the meantime, the following can help on affected jobs: shallow clones (fetch-depth: 1), forcing HTTP/1.1 (git config --global http.version HTTP/1.1), and adding retry logic around the checkout step.

  3. identified May 26, 2026, 11:37 AM UTC

    GitHub has a separate, major outage https://www.githubstatus.com/incidents/gnftqj9htp0g

  4. identified May 29, 2026, 08:04 AM UTC

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

  5. resolved Jun 02, 2026, 06:57 PM UTC

    GitHub confirmed that they resolved the issue on their edge servers.

Read the full incident report →

Minor May 19, 2026 Degraged GitHub Webhooks 2h 25m GitHub Webhooks

Started May 19, 2026, 03:05 PM UTC· resolved May 19, 2026, 05:31 PM UTC

  1. identified May 19, 2026, 03:05 PM UTC

    At approximately 14:55 UTC, we observed a drop in incoming GitHub webhooks as GitHub temporarily stopped sending events. Delivery has since partially recovered. Our system automatically detects missing webhooks every 5 minutes and self-heals by reconciling the missed events. As a result, you may experience longer-than-usual job assignment times until delivery fully stabilizes. We are continuing to monitor the situation.

  2. resolved May 19, 2026, 05:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 20, 2026 Networking issue impacting multiple services 25m PostgreSQL, Networking

Started Mar 20, 2026, 10:34 AM UTC· resolved Mar 20, 2026, 11:00 AM UTC

  1. investigating Mar 20, 2026, 10:34 AM UTC

    We are currently investigating issues which mostly impacts Postgres services.

  2. investigating Mar 20, 2026, 10:35 AM UTC

    We are continuing to investigate this issue.

  3. resolved Mar 20, 2026, 11:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 6, 2026 High job provisioning delays for arm64 GitHub runners 58m Ubicloud Runners

Started Mar 06, 2026, 01:58 PM UTC· resolved Mar 06, 2026, 02:56 PM UTC

  1. identified Mar 06, 2026, 01:58 PM UTC

    Due to an unexpected spike in arm64 demand, there is currently a delay in provisioning arm64 runners. We are working to increase our capacity as quickly as possible to meet the demand and mitigate the issue.

  2. resolved Mar 06, 2026, 02:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 25, 2026 Occassional DNS Resolution Failures 1h 34m Compute, PostgreSQL, Networking, Kubernetes

Started Feb 25, 2026, 09:15 PM UTC· resolved Feb 25, 2026, 10:50 PM UTC

  1. identified Feb 25, 2026, 09:37 PM UTC

    DNS queries can fail sporadically, linked to a UDP-related fault at Hetzner https://status.hetzner.com/incident/5e901309-0873-42af-90c5-84f38304f592 We're monitoring and looking to work around this issue.

  2. resolved Feb 25, 2026, 10:55 PM UTC

    Caused by a DDOS attack against Hetzner and its mitigation routines. We will be diversifying our DNS upstreams in the future.

Read the full incident report →

Minor February 13, 2026 Erratic restarts on some VMs and Databases 38m Compute, PostgreSQL, Kubernetes

Started Feb 13, 2026, 07:38 PM UTC· resolved Feb 13, 2026, 08:16 PM UTC

  1. monitoring Feb 13, 2026, 08:13 PM UTC

    Some systems have been restarting erratically due to a recent code change. We backed this out and are recovering.

  2. resolved Feb 13, 2026, 08:16 PM UTC

    All systems operational again. Write to [email protected] about anything unexpected.

Read the full incident report →

Major February 6, 2026 Postgres DNS resolution issues 2h 13m PostgreSQL

Started Feb 06, 2026, 08:00 PM UTC· resolved Feb 06, 2026, 10:13 PM UTC

  1. investigating Feb 06, 2026, 08:33 PM UTC

    There is a defect in Postgres that causes unbound DNS records. Negative caching can exacerbate the incident after our fix. Databases affected: many at the outset, some now. Diagnosing the last records.

  2. monitoring Feb 06, 2026, 09:16 PM UTC

    We've hotfixed the remaining records. Negative caching of DNS can slow recovery, depending on the upstream DNS server. We will remain in contact with all affected customer until all symptoms are resolved.

  3. identified Feb 06, 2026, 09:35 PM UTC

    Some records are proving more difficult to address than we expected.

  4. monitoring Feb 06, 2026, 09:41 PM UTC

    We've identified this problem, and believe negative caching of DNS records to be all that remains. We are going to continue to check for at least thirty minutes, the longest time reported for negative caching so far.

  5. resolved Feb 06, 2026, 10:13 PM UTC

    Cross checking DNS records has been successful for some time. Customers report negative caches have since expired. Likely cause: race condition that caused misapplication of DNS records that was exposed under higher parallelism. We have to analyze it and patch it in the coming days.

Read the full incident report →

Notice January 26, 2026 Intermittent Kubernetes Networking Outages –

Started Jan 26, 2026, 04:30 PM UTC· resolved Jan 26, 2026, 04:30 PM UTC

  1. resolved Feb 09, 2026, 10:06 AM UTC

    We are observed temporary networking issues impacting mesh stability and external connectivity.

Read the full incident report →

Minor January 19, 2026 A host in eu-central-h1 is experiencing a hardware failure 47m Compute, PostgreSQL

Started Jan 19, 2026, 02:26 PM UTC· resolved Jan 19, 2026, 03:13 PM UTC

  1. identified Jan 19, 2026, 02:26 PM UTC

    Instances running on this host are currently unreachable. We are actively working to mitigate the issue and restore services. We will keep you updated as we make progress.

  2. resolved Jan 19, 2026, 03:13 PM UTC

    Our hardware provider has replaced the failed hardware, and all systems are now fully operational.

Read the full incident report →

Minor December 15, 2025 Increased job queue times in Ubicloud runners 3h 30m Ubicloud Runners

Started Dec 15, 2025, 01:37 PM UTC· resolved Dec 15, 2025, 05:07 PM UTC

  1. investigating Dec 15, 2025, 01:37 PM UTC

    Ubicloud runners are currently experiencing a partial outage, resulting in high queue for job requests. We are investigating the incident.

  2. monitoring Dec 15, 2025, 02:11 PM UTC

    We've mitigated the issue and are actively monitoring the results. Queue times have started to improve, but due to the high load caused by the incident, some delays are still expected. We’ll share another update once everything is fully resolved. Thank you for your patience.

  3. resolved Dec 15, 2025, 05:07 PM UTC

    Our provisioning times are back to normal.

Read the full incident report →