Octopus incident

Octopus ID and a subset of Octopus.com URLS unavailable

Critical Resolved View vendor source →

Octopus experienced a critical incident on August 27, 2024 affecting Octopus.com and Octopus Cloud and 1 more component, lasting 6d 15h. The incident has been resolved; the full update timeline is below.

Started
Aug 27, 2024, 01:30 PM UTC
Resolved
Sep 03, 2024, 04:55 AM UTC
Duration
6d 15h
Detected by Pingoru
Aug 27, 2024, 01:30 PM UTC

Affected components

Octopus.comOctopus CloudControl Center (billing.octopus.com)

Update timeline

  1. 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

  2. monitoring Aug 27, 2024, 02:07 PM UTC

    Services are currently operational. Our team is continuing to investigate the root cause.

  3. 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.