https://approjects-vendor-status-watch.static.hf.space/v/jira-product-discovery.htmlIncidents from Jira Product Discovery's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/dlwn2p30gnvljira-product-discovery:2026-06-12T13:50:49.333ZFri, 12 Jun 2026 13:50:49 +0000On June 12th 2026, between 07:30 UTC to 13:48 UTC, some users experienced viewing disruptions with our product discovery service. The issue has now been resolved and the service is operating normally for all the customers.https://stspg.io/9hvn6hwzjs3rjira-product-discovery:2026-06-10T06:14:02.182ZWed, 10 Jun 2026 06:14:02 +0000We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.https://stspg.io/nzltxgcf7bd7jira-product-discovery:2026-05-14T05:11:18.586ZThu, 14 May 2026 05:11:18 +0000### Summary On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes. ### **IMPACT** During the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access serviceshttps://stspg.io/c8f30qf860hwjira-product-discovery:2026-05-08T01:31:37.519ZFri, 08 May 2026 01:31:37 +0000All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution. The incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15. ### **IMPACT** The primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Ahttps://stspg.io/chf4bly6nxndjira-product-discovery:2026-03-10T00:06:29.000ZTue, 10 Mar 2026 00:06:29 +0000On 9 March UTC, Automation users in the APAC region may have experienced performance degradation within Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, Confluence. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/602vyd489ht6jira-product-discovery:2026-01-28T18:12:17.430ZWed, 28 Jan 2026 18:12:17 +0000On Jan 28, 2026, Jira, Jira Product Discovery, and Jira Service Management users in eu-west-1 region may have experienced delays in viewing recently submitted updates on the web page and/or mobile apps. Updates continued to process successfully during the incident.  There are no actions needed from customers.  The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/b51f0h4gns3qjira-product-discovery:2025-12-15T16:16:25.298ZMon, 15 Dec 2025 16:16:25 +0000On December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced performance degradations and errors on the web page and mobile apps. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/tw0dcmrb9wkcjira-product-discovery:2025-10-20T07:56:12.543ZMon, 20 Oct 2025 07:56:12 +0000### Postmortem publish date: Nov 19th, 2025 ### Summary All dates and times below are in UTC unless stated otherwise. Customers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service disruptions were triggered due to an [AWS DynamoDB outage](https://aws.amazon.com/message/101925/#:~:text=1%3A50%20PM.-,DynamoDB,-Between%2011%3A48) and further affected by subsequent failures in [AWS EC2](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) and [AWS Network Load Balancer](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) within the us-east-1 region. The incident started at Oct 2https://stspg.io/6h5k9sxzrkx8jira-product-discovery:2025-09-22T05:38:58.037ZMon, 22 Sep 2025 05:38:58 +0000### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### *https://stspg.io/0zd0mz108znwjira-product-discovery:2025-09-09T10:23:55.783ZTue, 09 Sep 2025 10:23:55 +0000An update has been released by Microsoft to resolve this issue for users of the Edge browser. To verify that you are running the required version of Edge, you can navigate to edge://components/ in the address bar, click the 'Check for update' button for the 'Trust Protections List', ensuring that you are on version 1.0.0.31 or higher to ensure you are running the version that contains the fixed release. All Edge browsers should otherwise receive this update within 10 hours without user intervention.