Is Octopus down?

Last checked 6m ago
Current status
Octopus is up

No incidents right now.

Official status page: https://status.octopus.com · Polled every 5 minutes · 6 components tracked

Octopus is operational right now. Last checked 6m ago; the most recent incident resolved 15d ago.

Real-time Octopus status, recent outages, and incident history — pulled directly from Octopus's official status page at https://status.octopus.com every 5 minutes. Pingoru tracks 6 Octopus services and has captured 6 incidents in the last 90 days (97.13% uptime). Get email, Slack, Discord, or webhook alerts the moment Octopus reports a new incident — free for 5 monitors, no credit card.

Users who monitor Octopus also follow these DevOps services: GitHub Confluence Circle CI OpsGenie JFrog Papertrail Airbrake Splunk OnCall Datadog EU RubyGems View all 6,000+ providers
Octopus uptime 97.13% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 18h 28m
    Started May 29, 2026, 06:10 AM UTC · Resolved May 30, 2026, 12:38 AM UTC
    Octopus Cloud
    Timeline · 2 updates
    • monitoring · May 29, 2026, 06:10 AM UTC

      Our upstream provider, Azure in West US2, is currently experiencing an issue which might be affecting your ability to deploy. We will resolve this incident once we have received confirmation the issue has been resolved from our upstream provider.

    • resolved · May 30, 2026, 12:38 AM UTC

      Our upstream provider, Azure in West US2, has resolved their issue. While the issue was ongoing, some Octopus Cloud instances in West US2 may have experienced brief downtime and network communication issues. For more details, see Azure's incident report (Tracking ID: GHRP-84G) at https://azure.status.microsoft/en-us/status/history/.

    Latest: Our upstream provider, Azure in West US2, has resolved their issue. While the issue was ongoing, some Octopus Cloud instances in West US2 may have experienced brief downtime and ne…

  2. Resolved 2d 22h
    Started May 15, 2026, 12:36 PM UTC · Resolved May 18, 2026, 10:49 AM UTC
    Octopus Cloud
    Timeline · 2 updates
    • identified · May 15, 2026, 12:36 PM UTC

      We have identified the issue and are working on a fix. If you are experiencing this please see the Github issue below for workarounds - https://github.com/OctopusDeploy/Issues/issues/10026

    • resolved · May 18, 2026, 10:49 AM UTC

      We have pushed out a fix for this issue and it should be rolling out to Octopus Cloud customers over the next few days. Please contact [email protected] if you are seeing this issue and we can arrange to get your instance upgraded.

    Latest: We have pushed out a fix for this issue and it should be rolling out to Octopus Cloud customers over the next few days. Please contact [email protected] if you are seeing this is…

  3. Resolved 1d 17h
    Started May 05, 2026, 01:18 PM UTC · Resolved May 07, 2026, 06:40 AM UTC
    Octopus Cloud
    Timeline · 5 updates
    • identified · May 05, 2026, 01:18 PM UTC

      We have observed issues provisioning Dynamic Workers in our West US 2 region. We are working on mitigations and monitoring. A small number of customers have experienced lease failures.

    • identified · May 05, 2026, 01:25 PM UTC

      We are in the process of switching Octopus Cloud instances in the West US 2 region to use dynamic workers in our standby region (Central US). Customers who have experienced leasing failures should retry their deployments or runbook runs.

    • monitoring · May 05, 2026, 01:43 PM UTC

      We have completed switching Octopus Cloud instances in the West US 2 region to use dynamic workers in our standby region (Central US). This should mitigate this issue for all customers. We will update this incident when dynamic workers in West US 2 are stable and we have reverted all Cloud instances back to using workers in West US 2.

    • monitoring · May 07, 2026, 12:51 AM UTC

      We are continuing to monitor for any further issues.

    • resolved · May 07, 2026, 06:40 AM UTC

      We have not observed any further issues in the West US 2 region so all Octopus Cloud instances in the West US 2 region are using dynamic workers in West US 2 once again.

    Latest: We have not observed any further issues in the West US 2 region so all Octopus Cloud instances in the West US 2 region are using dynamic workers in West US 2 once again.

  4. Resolved 6d 19h
    Started Apr 01, 2026, 08:36 AM UTC · Resolved Apr 08, 2026, 04:11 AM UTC
    Octopus Cloud
    Timeline · 3 updates
    • investigating · Apr 01, 2026, 08:06 AM UTC

      We are aware of an issue affecting Octopus Cloud customers running deployments that interact with AWS, including EKS/Kubernetes targets and AWS health checks. Impacted customers may see authentication errors when running these deployments. Our team is actively investigating and working to resolve the issue. Workaround: If you are affected, adding your AWS region as an environment variable in your script steps may resolve the issue: export AWS_REGION= for Bash $env:AWS_REGION = "" for Powershell E.g export AWS_REGION=ap-southeast-2 $env:AWS_REGION = "ap-southeast-2" We apologise for the disruption and will share further updates as our investigation progresses. If you need help in the meantime, please contact us at [email protected]

    • investigating · Apr 01, 2026, 08:36 AM UTC

      We are aware of an issue affecting Octopus Cloud customers running deployments that interact with AWS, including EKS/Kubernetes targets and AWS health checks. Impacted customers may see authentication errors when running these deployments. Our team is actively investigating and working to resolve the issue. Workaround: If you are affected, adding your AWS region as an environment variable in your script steps may resolve the issue: export AWS_REGION=[REGION] for Bash $env:AWS_REGION = "[REGION]" for Powershell E.g export AWS_REGION=ap-southeast-2 $env:AWS_REGION = "ap-southeast-2" We apologise for the disruption and will share further updates as our investigation progresses. If you need help in the meantime, please contact us at [email protected]

    • resolved · Apr 08, 2026, 04:11 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved
    Started Mar 30, 2026, 12:43 PM UTC · Resolved Mar 30, 2026, 12:43 PM UTC
    Octopus Cloud
    Timeline · 1 update
    • resolved · Mar 30, 2026, 12:43 PM UTC

      We have identified the cause of this issue and have produced a fix in Octopus version 2026.2.3825. Please email [email protected] if you are seeing AWS region endpoint errors in your deployments similar to the one in the title and we can discuss upgrade options.

    Latest: We have identified the cause of this issue and have produced a fix in Octopus version 2026.2.3825. Please email [email protected] if you are seeing AWS region endpoint errors in …

See the full Octopus outage history

1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Octopus outage history →

Or sign up free to get alerts when Octopus breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 6 incidents View full outage history →