Octopus incident
Octopus.com and billing portal may be unavailable in certain regions
Octopus experienced a critical incident on October 29, 2025 affecting Octopus.com and Octopus Cloud and 1 more component, lasting 8h 41m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 29, 2025, 04:31 PM UTC
We are currently investigating the issue.
- identified Oct 29, 2025, 04:39 PM UTC
It appears this outage is due to a DNS issue with our upstream provider. We are currently awaiting for mitigation from the upstream provider to restore Octopus.com and related services.
- identified Oct 29, 2025, 07:00 PM UTC
Customers may notice intermittent access to Octopus.com and Octopus services. Our upstream provider has made progress to mitigate the issue. We will continue to monitor the situation. We have contingency plans we are prepared to deploy if service recovery progress from the upstream provider mitigation stalls.
- identified Oct 29, 2025, 09:13 PM UTC
As we continue to monitor Octopus.com and Octopus services, metrics are showing services becoming more reliably available. Our upstream provider is currently estimating full or near full mitigation approximately 2 hours from now (approximately 23:20 UTC on 29 October 2025). We will provide additional updates as the situation necessitates.
- identified Oct 29, 2025, 11:57 PM UTC
As we continue to monitor Octopus.com and Octopus services, metrics are showing services becoming more reliably available. We are still waiting for our upstream provider's resolution and expect to give another update approximately 1 hour from now (approximately 00:55 UTC on 30 October 2025). We will continue to provide additional updates as the situation necessitates.
- resolved Oct 30, 2025, 01:13 AM UTC
All Octopus services affected by this outage are now operational.