Affected components
Update timeline
- identified May 05, 2026, 01:18 PM UTC
We have observed issues provisioning Dynamic Workers in our West US 2 region. We are working on mitigations and monitoring. A small number of customers have experienced lease failures.
- identified May 05, 2026, 01:25 PM UTC
We are in the process of switching Octopus Cloud instances in the West US 2 region to use dynamic workers in our standby region (Central US). Customers who have experienced leasing failures should retry their deployments or runbook runs.
- monitoring May 05, 2026, 01:43 PM UTC
We have completed switching Octopus Cloud instances in the West US 2 region to use dynamic workers in our standby region (Central US). This should mitigate this issue for all customers. We will update this incident when dynamic workers in West US 2 are stable and we have reverted all Cloud instances back to using workers in West US 2.
Looking to track Octopus downtime and outages?
Pingoru polls Octopus's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Octopus reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Octopus alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required