Is Octopus down?

Last checked 6m ago
Current status
Octopus is having a partial outage

Active incident: Bicep deployments may fail after upgrading to 2026.3.4658 o…

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

Octopus is reporting a partial outage right now (last checked 6m ago). Some components are affected; others remain operational.

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.50% 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.50% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Active incident 1

  1. Ongoing ● 29d 17h
    Started Jul 03, 2026, 12:25 AM UTC
    Timeline · 1 update
    • identified · Jul 03, 2026, 12:25 AM UTC

      We have identified an issue in Octopus Server 2026.3.4658 or later when existing Bicep deployments may start failing. We have a public issue tracking this with a workaround https://github.com/OctopusDeploy/Issues/issues/10129 We are working on a fix and will update this incident and the public issue when it's resolved.

    Latest: We have identified an issue in Octopus Server 2026.3.4658 or later when existing Bicep deployments may start failing. We have a public issue tracking this with a workaround https:/…

Recent outages & incidents

Past 90 days
  1. Resolved 1h 31m
    Started Jul 31, 2026, 01:32 PM UTC · Resolved Jul 31, 2026, 03:04 PM UTC
    Octopus.comOctopus Cloud
    Timeline · 3 updates
    • investigating · Jul 31, 2026, 01:32 PM UTC

      We are currently investigating issues with our certificate for https://g.octopushq.com. Customers may see issues with build servers trying to download the CLI using V5 and below build server steps. Customers may also see issues with octopus.com.

    • monitoring · Jul 31, 2026, 02:02 PM UTC

      We have identified and mitigated the certificate issues for https://g.octopushq.com. Customers should now be able to download the CLI using V5 and below build server steps. Any certificate issues with octopus.com should now be resolved. Please email [email protected] if you are still seeing issues, we will continue to monitor this over the next few hours.

    • resolved · Jul 31, 2026, 03:04 PM UTC

      This issue has now been resolved. Thank you for your patience whilst we investigated the incident. If you are having any further issues please email [email protected].

    Latest: This issue has now been resolved. Thank you for your patience whilst we investigated the incident. If you are having any further issues please email [email protected].

  2. Resolved 4h 19m
    Started Jul 23, 2026, 04:08 PM UTC · Resolved Jul 23, 2026, 08:28 PM UTC
    Octopus.com
    Timeline · 4 updates
    • identified · Jul 23, 2026, 04:08 PM UTC

      Due to upstream Azure issues in the West US region, some services may have no or intermittent connectivity. We are continuing to monitor the impact on our systems.

    • identified · Jul 23, 2026, 04:09 PM UTC

      Known impacted services: - The Octopus.com blog

    • monitoring · Jul 23, 2026, 06:35 PM UTC

      Azure's mitigation has allowed access to the impacted services. We will continue to monitor service availability.

    • resolved · Jul 23, 2026, 08:28 PM UTC

      Azure has resolved this issue.

    Latest: Azure has resolved this issue.

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

  4. 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…

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

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 →