Vendor Status Watch

← all vendors

Jira Product Discovery status history

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

0incidents, last 30 days
0incidents, last 90 days
10incidents on record

How long do Jira Product Discovery incidents last?

97 minmedian incident duration10 measured
21.5 h90th percentile1 in 10 ran longer
97 minmedian, major/critical only3 incidents

From 10 incidents with a vendor-posted start and resolve time. Longest on record: Degraded performance in Confluence and Jira for Microsoft Edge users — 5.8 days (2025-09-09 10:23 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 (10)

StartedIncidentStatusImpactDuration
2026-06-12 13:50 UTCData viewing issues on Jira Product Discoveryresolvedminor38 min
2026-06-10 06:14 UTCDelays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Appsresolvedminor17 min
2026-05-14 05:11 UTCUsers experiencing issues accessing multiple Atlassian productspostmortemcritical1 h 37 min
2026-05-08 01:31 UTCMultiple Atlassian services are experiencing issuespostmortemminor18 h 13 min
2026-03-10 00:06 UTCAutomation events delayed for some customers in the APAC regionresolvedmajor52 min
2026-01-28 18:12 UTCDegraded performance of Jira, JPD, and JSM in eu-west-1resolvedminor1 h 30 min
2025-12-15 16:16 UTCDegraded performance of Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovoresolvedminor2 h 45 min
2025-10-20 07:56 UTCAtlassian Cloud Services impactedpostmortemmajor21 h 28 min
2025-09-22 05:38 UTCDegraded performance to multiple Atlassian experiencespostmortemminor1 h 38 min
2025-09-09 10:23 UTCDegraded performance in Confluence and Jira for Microsoft Edge usersresolvednone5 d 20 h

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 Jira Product Discovery with the template

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

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