Octopus incident

Intermittent service disruption for a small number of customers

Major Resolved View vendor source →

Octopus experienced a major incident on January 30, 2025 affecting Octopus Cloud, lasting 4d 19h. The incident has been resolved; the full update timeline is below.

Started
Jan 30, 2025, 07:24 AM UTC
Resolved
Feb 04, 2025, 03:07 AM UTC
Duration
4d 19h
Detected by Pingoru
Jan 30, 2025, 07:24 AM UTC

Affected components

Octopus Cloud

Update timeline

  1. investigating Jan 30, 2025, 07:24 AM UTC

    Internal monitoring notified us that a small number of Octopus Cloud instances were terminated for excess memory use up to 12 hours after a recent a software upgrade. These instances were automatically restarted and resumed functioning correctly. At this stage we are investigating to determine the cause of the excess memory use. If you believe you are affected by this issue please contact [email protected]

  2. resolved Feb 04, 2025, 03:07 AM UTC

    Two seperate recent changes were identified as causes of the excess memory use. These changes have been rolled back, and we have confirmed through monitoring that memory use has returned to normal on the affected instances. No further crashes terminations have been observed.