Octopus incident
Intermittent service disruption for a small number of customers
Resolved after 4 days 19 hours, affecting Octopus Cloud, on January 30, 2025.
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.
Affected components
Update timeline
- 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]
- 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.
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