Feb 3, 05:26 UTC
This incident has been resolved.
Jan 26, 15:44 UTC
Our upstream provider has applied a fix that should resolve this issue. We are continuing to monitor this on our side. If you are continuing to see 404 errors navigating to parts of Octopus.com (sign-in, documentation, blog etc.), please contact email@example.com
Jan 26, 15:07 UTC
Mitigations didn't hold.
We're back to investigating new options.
Signin / docs and blog are still impacted.
Jan 26, 12:38 UTC
**Advice**: go to www.octopus.com (your browser cache will be in your way), and try incognito/private browsing.
We are 302 redirecting from octopus.com to www.octopus.com and are seeing signs of improved availability for impacted systems /signin /docs /blog
Northcentral US may still experience a partial outage depending on how your traffic is routed. Most regions should be healthy or just experience some degraded performance.
The only impact to Octopus Cloud is the log in capabilities.
Jan 26, 11:07 UTC
We have identified a cause of this incident and are working to remediate.
Jan 26, 04:19 UTC
We have escalated with our Cloud provider and are working with them to resolve. Further updates will be posted when they are available.
Jan 25, 22:59 UTC
We are continuing to investigate and have escalated internally to specialist engineers for additional support. Further updates will be posted when they are available.
Jan 25, 21:36 UTC
We currently believe that this is only affecting certain geographical locations and their related CDN endpoints. We are continuing to investigate and have engaged our CDN provider for further assistance/investigation. Further updates will be posted when they are available.
Jan 25, 18:32 UTC
We are continuing to investigate this issue
Jan 25, 17:22 UTC
We are currently investigating this issue.
Jan 25, 15:41 UTC