Vendor Status Watch

← all vendors

Octopus status history

Current state: operational — “All Systems Operational” per https://status.octopus.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
3incidents, last 90 days
19incidents on record
Incidents per week, last 12 weeks:

How long do Octopus incidents last?

8.7 hmedian incident duration19 measured
2.9 days90th percentile1 in 10 ran longer
6.3 hmedian, major/critical only16 incidents

From 19 incidents with a vendor-posted start and resolve time. Longest on record: Bicep deployments may fail after upgrading to 2026.3.4658 or later — 32.5 days (2026-07-03 00:25 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (19)

StartedIncidentStatusImpactDuration
2026-07-31 13:32 UTChttps://g.octopushq.com Certificate issuesresolvedmajor1 h 31 min
2026-07-23 16:08 UTCService connectivity issues due to upstream Azure outageresolvedminor4 h 19 min
2026-07-03 00:25 UTCBicep deployments may fail after upgrading to 2026.3.4658 or laterresolvedmajor32 d 11 h
2026-05-29 06:10 UTCAbility to deploy in West US 2 might be affectedresolvedminor18 h 28 min
2026-05-15 12:36 UTCAmazon ECS Service Steps fail with 'Container.image contains invalid cha...resolvedmajor2 d 22 h
2026-05-05 13:18 UTCDynamic Worker issues in West US 2resolvedmajor41 h 21 min
2026-04-01 08:06 UTCAWS Deployment Failures for Cloud Customersresolvedmajor6 d 20 h
2026-03-30 12:43 UTCDeployments using AWS-dependent resources may fail with “No RegionEndpoint or ServiceURL configured.”resolvedmajor0 min
2026-03-24 04:13 UTCgRPC port (8443) shows Octopus Cloud instance is Undergoing Maintenanceresolvedmajor25 h 56 min
2026-02-26 01:51 UTCEmails are currently not being deliveredresolvedmajor3 h 55 min
2026-02-02 21:31 UTCUbuntu Dynamic Workers are failing to leasepostmortemcritical24 h 07 min
2025-11-25 12:34 UTCOctopusID signin intermittent for cloud customerspostmortemmajor2 h 23 min
2025-11-18 21:11 UTCGitHub upstream outage causing issues with VCS-backed elementsresolvedmajor3 h 36 min
2025-10-29 16:31 UTCOctopus.com and billing portal may be unavailable in certain regionsresolvedcritical8 h 41 min
2025-10-20 07:34 UTCDocker Hub is downresolvedmajor17 h 37 min
2025-10-12 23:43 UTCKubernetes deployments using Kubernetes agent may failresolvedmajor41 min
2025-09-25 01:06 UTCDocker Hub authentication issuespostmortemmajor3 h 12 min
2025-09-15 03:11 UTCIntermittent Azure authentication issuesresolvedmajor2 h 54 min
2025-09-04 02:31 UTC(Resolved) Some Deployments/Runbooks in Octopus Cloud may be failing to startresolvedminor25 h 18 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Octopus with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "octopus"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}