Degraded performance
Slow instance provisioning in US West (Oregon)
Launches took about 5 minutes in US West (Oregon) for 62 minutes.
- Status
- ResolvedResolved — last update 30 Dec 2025, 21:09 UTC
- Started
- 30 Dec, 20:07Tuesday 30 December 2025 UTC
- Duration
- 1 h 2 minEnded 30 Dec 2025, 21:09 UTC
- Components
- 2Instance launch and lifecycle — US West (Oregon), Spot pool and reclaim notices — US West (Oregon)
Timeline
What we posted, as we posted it.
Resolved5 updates · UTC
- ResolvedThis incident has been resolved. Boot time is never billed.30 Dec, 21:09
- MonitoringLaunch times have been back under a minute since 20:51 UTC. We are monitoring.30 Dec, 20:51
- IdentifiedA batch of nodes was reimaged overnight and came back with an empty image cache, so every launch on them pulls the template from the registry.30 Dec, 20:21
- UpdateWe have narrowed the cause down and are applying a fix. Next update within 30 minutes.30 Dec, 20:15
- InvestigatingInstances in US West (Oregon) are taking longer than usual to become reachable: median launch time is about 5 minutes instead of under one.30 Dec, 20:07
Affected components
- Instance launch and lifecycleUS West · OregonOperational
- Spot pool and reclaim noticesUS West · OregonOperational
Details
- Type
- Degraded performance
- Started
- 30 Dec 2025, 20:07 UTC
- Ended
- 30 Dec 2025, 21:09 UTC
- Region
- US West (Oregon)
- Impact
- Launches took about 5 minutes in US West (Oregon) for 62 minutes.
- Reference
- 934492e8f2a4