checked Oct 22, 2026 7:07 PM UTC · Ubicloud's official status page
We don't have a current reading for Ubicloud.
All components operational
Statusfield watches Ubicloud alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
3 reports published by Ubicloud in the last 30 days
When Ubicloud breaks, it is typically resolved in 2h 22m — median across 1 resolved incidents over 30 days.
resolvedOct 1 · 16:24 UTC
Following an initial capacity increase, provisioning times have returned to normal. We're continuing to expand our fleet to meet future demand.
Reported by Ubicloud on their status page.
resolvedSep 29 · 16:37 UTC
Following an initial capacity increase, provisioning times have returned to normal. We're continuing to expand our fleet to meet future demand.
Reported by Ubicloud on their status page.
resolvedSep 23 · 16:59 UTC
Between approximately 15:00 UTC and 17:00 UTC on September 23, jobs took longer than usual to start, and some jobs were cancelled mid-run. Overall demand for our runners exceeded our dedicated capacity, and larger runners (16 and 30 vCPUs) were hit hardest, since they're the hardest to place when capacity is tight. To absorb the extra demand, we ran some jobs on external compute resources. Some of those machines were reclaimed mid-run, which cancelled their jobs. Handling the lost machines slowed down our control plane, so jobs on our own servers also took longer to start. The more demand grew, the more interruptions we saw, and the further provisioning fell behind. We stopped using reclaimable external compute resources and added more dedicated capacity. We're also changing how our control plane handles unreachable machines, so problems with external compute resources can't slow down provisioning on our own servers. This incident is resolved.
Reported by Ubicloud on their status page.
