https://approjects-vendor-status-watch.static.hf.space/v/jira-service-management.htmlIncidents from Jira Service Management's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/l18v31t3cqnqjira-service-management:2026-09-14T16:46:06.318ZMon, 14 Sep 2026 16:46:06 +0000On September 14, 2026, Opsgenie and Jira Service Management experienced a disruption, and impacted users saw delayed alerts notification and inability to view the alerts in the user interface. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/3mw650bc2djsjira-service-management:2026-09-11T07:46:31.093ZFri, 11 Sep 2026 07:46:31 +0000On 11 September 2026, Between 07:02 UTC and 07:56 UTC, some Jira Software and Jira Service Management users may have experienced degraded performance and errors when accessing Work Items and Boards. The issue has now been resolved, and all services are operating normally.https://stspg.io/kdjpr5v3lh24jira-service-management:2026-09-03T14:20:25.580ZThu, 03 Sep 2026 14:20:25 +0000On September 3, 2026, some Jira Service Management users may have experienced errors viewing the Affected Services field or performance degradation on the web. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/0wpylxd56m7mjira-service-management:2026-09-01T10:11:45.330ZTue, 01 Sep 2026 10:11:45 +0000On 1st Sept 2026, between 04:22 UTC to 10:59 UTC, some Jira users may have experienced service disruptions. The issue has now been resolved and the service is operating normally for all the customers.https://stspg.io/wtpl0h6xdf9gjira-service-management:2026-08-27T04:22:09.128ZThu, 27 Aug 2026 04:22:09 +0000**SUMMARY** On August 27, 2026, between 03:51 and 04:35 UTC, Atlassian customers in the Western Europe and Southeast APAC regions were unable to reach Atlassian Cloud products, including Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo Search, and Talent. The event was triggered by a defective code change to the routing layer of one of our proxy fleets. This led to HTTP 404 errors being served to all customer traffic through these proxy fleets in Western Europe and Southeast APAC regions. The incident was detected within 1 minute by our automated monitoring systems, and mitigated by rolling back to the previous configuration release, which put the proxy fleet into a known good state. After the proxy fleet recovered, some Jira and Confluence custohttps://stspg.io/0tny3nv6gn6gjira-service-management:2026-08-25T08:42:48.027ZTue, 25 Aug 2026 08:42:48 +0000On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers.https://stspg.io/h46b3jvp1lrcjira-service-management:2026-08-24T19:22:47.461ZMon, 24 Aug 2026 19:22:47 +0000On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally. There may be older notifications that are being processed, and we expect them to be completed in next few hours.https://stspg.io/64t7mdzvgmb3jira-service-management:2026-08-07T11:30:55.293ZFri, 07 Aug 2026 11:30:55 +0000On August 7th - 2026, between 10:27 UTC to 11:49 UTC, some users in the Central European region may have experienced service access issues. The issue has now been resolved and the service is operating normally for all the customers.https://stspg.io/nbfx7rvx8yhxjira-service-management:2026-08-07T01:33:21.116ZFri, 07 Aug 2026 01:33:21 +0000On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/jnwlc1hc7c38jira-service-management:2026-07-21T09:48:22.457ZTue, 21 Jul 2026 09:48:22 +0000Our notification provider has identified the root of the issue that is causing voice call failures to some India-based mobile numbers. We understand the inconvenience this may cause and appreciate your patience while our provider works on restoring the service. If you have experienced any issues with voice notifications, please contact our Support for assistance.https://stspg.io/2h64wj6psytmjira-service-management:2026-07-20T20:18:31.402ZMon, 20 Jul 2026 20:18:31 +0000Our team has been able to validate that all rule executions are performing normally and this issue is now resolved.https://stspg.io/g65shv8fkbgmjira-service-management:2026-07-20T16:03:35.374ZMon, 20 Jul 2026 16:03:35 +0000On July 20, 2026, some Jira and Jira Service Management users may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/tr43y4jdgclrjira-service-management:2026-07-06T09:23:39.292ZMon, 06 Jul 2026 09:23:39 +0000## Summary On Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker, and related workflows. The incident began when a core identity service experienced database saturation in EU regions, increasing latency and error rates. While responders worked to restore capacity, an emergency mitigation was applied which blocked automation rules from accessing the identity endpoint. In parallel, the elevated identity latency contributed to a cascading failure in a downstream user search service, degrading user search and user picker experiences across multiple products. Service was progressively restored after additional database read capacity was added, thttps://stspg.io/x932djl5306zjira-service-management:2026-06-19T22:46:56.478ZFri, 19 Jun 2026 22:46:56 +0000Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.https://stspg.io/9y0yybjd7jsnjira-service-management:2026-06-10T09:42:42.542ZWed, 10 Jun 2026 09:42:42 +0000On June 10 2026, between 08:10 and 09:08 UTC, users experienced degraded performance and inability to load the Assets page, which is impacting the ability to create, update, and delete assets. We have implemented a fix and services have been restored to normal operation for all affected customers.https://stspg.io/2pq565q12h85jira-service-management:2026-06-10T04:55:13.724ZWed, 10 Jun 2026 04:55:13 +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/ws0xswrspv8vjira-service-management:2026-06-09T05:29:37.539ZTue, 09 Jun 2026 05:29:37 +0000The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/gn5h3tg2qchzjira-service-management:2026-06-08T01:53:57.093ZMon, 08 Jun 2026 01:53:57 +0000On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.https://stspg.io/tcc90nhgnszzjira-service-management:2026-06-02T15:32:55.551ZTue, 02 Jun 2026 15:32:55 +0000On June 2, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Previously delayed automation rules are expected to be completed within 12 hours.https://stspg.io/wbmjtjlrrvzdjira-service-management:2026-06-01T08:06:30.496ZMon, 01 Jun 2026 08:06:30 +0000**SUMMARY** On June 01, 2026, between 06:54 and 08:28 UTC, Atlassian customers using Jira, Jira Service Management, and Jira Work Management were unable to view issues, boards, and backlogs, and experienced errors when performing transitions, adding comments, and navigating the product. The event was triggered by caching infrastructure autoscaling failure. The issue only impacted customers hosted in Europe. The incident was detected within 8 minutes by our automated monitoring system and mitigated by progressively scaling the caching clusters manually. The total time to resolution was 1 hour and 34 minutes due to the progressive recovery. **IMPACT** The incident caused service disruption for customers hosted in the Europe region who were unable to access core experiences acrhttps://stspg.io/bnp82y79shhsjira-service-management:2026-05-14T05:03:32.407ZThu, 14 May 2026 05:03:32 +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/sbqbvjppht1xjira-service-management:2026-05-14T01:15:35.189ZThu, 14 May 2026 01:15:35 +0000This incident has been resolved. During the incident window, some customers using Atlassian Assist experienced excessive notifications as our team replayed delayed events caused by this prior incident: https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7 Our engineering team identified and addressed the issue. All services have fully recovered, and notification delivery is operating normally. No data loss occurred as a result of this incident. We apologize for the disruption and any confusion caused by the excessive notifications.https://stspg.io/nnf50c1jnjdkjira-service-management:2026-05-13T01:37:34.583ZWed, 13 May 2026 01:37:34 +0000### Summary ### On May 12, 2026 between 19:01 and 20:46 UTC, a subset of Atlassian customers may have experienced delays in background operations and automation processes. Some background operations, such as notifications or search indexing, were delayed until May 14, 2026 19:25 UTC due to increased cross-region traffic. The issue stemmed from a latent bug in the event processing pipeline. Automated monitoring detected the incident within 16 minutes, and it was mitigated through manual rollback within 1 hour and 45 minutes. Recovery of cross-region event delivery from the affected timeframe took 48 hours due to infrastructure scale constraints. ### IMPACT ### During the incident, customers may have experienced delays in background operations like automation, search indehttps://stspg.io/vw9bc0r2f93qjira-service-management:2026-05-08T01:31:38.339ZFri, 08 May 2026 01:31:38 +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/rqrjwwsqnf7wjira-service-management:2026-05-06T09:35:20.062ZWed, 06 May 2026 09:35:20 +0000The issue causing failures in the lookup objects within JSM Automation has been resolved. A fix was implemented to address the problem and the service is now operating normally for all affected customers.https://stspg.io/7657bc1x11mtjira-service-management:2026-05-02T00:55:47.627ZSat, 02 May 2026 00:55:47 +0000### SUMMARY ### Between May 1, 2026 at 23:34 UTC and May 2, 2026 at 02:53 UTC Atlassian customers using Jira and Jira Service Management (JSM) across all Cloud tenants received an error page when attempting to open a work item due to a schema incompatibility, and editing work item fields was degraded for both products. Navigating to and interacting with boards were degraded for Jira specifically. On Jira mobile, users were unable to view work items and work item search was degraded. This was caused by a deployment of a schema configuration change that had only been validated against some production environments. The issue also affected Atlassian's customer support operations and temporarily impacted Atlassian’s ability to respond to incoming support requests. Customers were able https://stspg.io/7qpnq2sp04tnjira-service-management:2026-04-14T12:12:58.154ZTue, 14 Apr 2026 12:12:58 +0000On April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected customers.https://stspg.io/920pm1cky7grjira-service-management:2026-04-13T07:29:45.552ZMon, 13 Apr 2026 07:29:45 +0000### Summary On April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed during the peak impact window, affecting users in the US East and EU regions. The incident was mitigated within 40 minutes through manual intervention, and full service was restored by 06:29 UTC. ### **IMPACT** * **Duration**: ~40 minutes \(05:49–06:29 UTC, April 13, 2026\) * **Affected regions**: US East and EU \(authentication infrastructure serves EU traffic from US East, with traffic primarily from EU at this time of day\). * **Affected products**: All Atlassian cloud products requiring authentication, includinghttps://stspg.io/gv0tw9530tbtjira-service-management:2026-04-08T06:24:47.129ZWed, 08 Apr 2026 06:24:47 +0000### Summary On April 8, 2026, between 04:46 UTC and 12:09 UTC, search functionality was unavailable or degraded across several Atlassian Cloud products, including Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and Atlassian Administration. A configuration change increased the resources reserved for a core system component that runs on nodes in our compute platform. On a subset of clusters configured for high‑density workloads, the increased reservations exceeded available node capacity interrupting search and related experiences for affected customers. The root cause was identified and a rollback was merged at 05:42 UTC with some systems seeing recovery by 07:33 UTC**.** Core search functionality was restored approximately bhttps://stspg.io/9f7zz880mxggjira-service-management:2026-03-18T11:32:44.090ZWed, 18 Mar 2026 11:32:44 +0000### Summary On March 18, 2026, between 10:06 and 13:47 UTC, customers experienced delays in Automation rules executing when triggered by Jira events such as Work Item creation, Work Item updates, and comments. Automation rules using other trigger types, including scheduled triggers, manual triggers, and incoming webhooks, continued to operate normally. The incident was caused by an internal configuration change that inadvertently disabled the event delivery pathway used to notify the automation platform of changes in Jira. The incident was identified through customer support tickets and verified through our monitoring; engineering teams were engaged for resolution. Once the root cause was identified, the configuration was corrected and normal automation processing resumed. Following res