Octopus incident
Octopus ID and a subset of Octopus.com URLS unavailable
Resolved after 6 days 15 hours, affecting Octopus.com and Octopus Cloud and 1 more, on August 27, 2024.
Services have been operational and stable since recovery 6 days ago. The incident was caused by an abnormally high frequency of requests, resulting in degraded service. We have relieved the bottleneck and are investigating why the compensating controls we had in place didn't compensate as expected.
Affected components
Update timeline
- investigating Aug 27, 2024, 02:05 PM UTC
Users are reporting 502 and 504 timeouts when attempting to log into their Octopus.com accounts, limiting access to Octopus Cloud and Control Center. A small subset of Octopus.com URLs are also impacted: Octopus.com/blog Octopus.com/start
- monitoring Aug 27, 2024, 02:07 PM UTC
Services are currently operational. Our team is continuing to investigate the root cause.
- resolved Sep 03, 2024, 04:55 AM UTC
Services have been operational and stable since recovery 6 days ago. The incident was caused by an abnormally high frequency of requests, resulting in degraded service. We have relieved the bottleneck and are investigating why the compensating controls we had in place didn't compensate as expected.
Your product runs on more than Octopus
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services