VM and CMK cluster creation issue in us-east2 region
minor- Started
- Sep 2, 4:22 AM EDT
- Resolved
- Sep 2, 11:57 AM EDT
- Duration
- 7h 35m
Crusoe's updates (6)
- investigating · Sep 2, 4:22 AM EDT
We are investigating "insufficient capacity" errors when creating/starting VMs or creating scaling CMK clusters in us-east2 region. Existing VMs continue to run normally. We'll share an update as soon as we have more information available.
- investigating · Sep 2, 5:44 AM EDT
We continue investigating "insufficient capacity" errors when creating/starting VMs or creating scaling CMK clusters in us-east2 region, and have narrowed down a likely cause. We'll share an update as soon as we have more information available.
- investigating · Sep 2, 7:07 AM EDT
We continue investigating "insufficient capacity" errors when creating/starting VMs or creating scaling CMK clusters in us-east2 region. We'll share an update as soon as we have more information available.
- investigating · Sep 2, 8:56 AM EDT
We continue investigating "insufficient capacity" errors when creating/starting VMs or creating scaling CMK clusters in us-east2 region. We'll share an update as soon as we have more information available.
- monitoring · Sep 2, 9:40 AM EDT
We've identified the cause of the errors when creating/starting VMs or creating scaling CMK clusters in us-east2 region and applied a fix. We'll continue monitoring.
- resolved · Sep 2, 11:57 AM EDT
This incident has been resolved.
What our checks recorded
We checked Crusoe 91 times from Crusoe's start time to its resolution, once every five minutes. Every one of them reached Crusoe's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 133 ms, against 131 ms over the 24 hours before. Crusoe posted the incident at Sep 2, 4:22 AM EDT.
Updates are Crusoe's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗