Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebAssetsJira Service Management Email Requests
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebAssetsJira Service Management Email Requests
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebAssetsJira Service Management Email Requests
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebAssetsJira Service Management Email Requests
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebAssetsJira Service Management Email Requests
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebAssetsJira Service Management Email Requests
investigating
We are investigating issues affecting your services.
We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.
monitoring
Some customers experienced issues accessing affected services in the Central European region.
We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon.
We should be able to provide more updates in the next one hour or earlier.
resolved
On 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.
Degraded performance of JIRA
์์ 2026๋ 8์ 7์ผ AM 1:33 UTC ยท 13m
Issues๊ฒฝ๋ฏธํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebAssetsJira Service Management Email Requests
investigating
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards.
We will share updates here as more information is available.
monitoring
The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
resolved
On 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.
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebAssetsJira Service Management Email Requests
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebAssetsJira Service Management Email Requests
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebAssetsJira Service Management Email Requests
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebAssetsJira Service Management Email Requests
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebAssetsJira Service Management Email Requests
Users are facing degraded performance while accessing Assets page which is impacting Assets object creation, updation and deletion activities. Our teams are investigating actively and will be sharing more details in next 1 hour.
resolved
On 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.
Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps
์์ 2026๋ 6์ 10์ผ AM 4:55 UTC ยท 1h 36m
Issues๊ฒฝ๋ฏธํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebJira Service Management Email Requests
investigating
We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.
Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.
identified
Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.
At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.
We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.
monitoring
Our team has now determined that performance has returned to expected levels for those impacted by this incident.
Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.
We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.
resolved
We 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.
Some users experiencing issues viewing boards and work items
์์ 2026๋ 6์ 9์ผ AM 5:29 UTC ยท 12h 58m
Outage์ค๋ํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Jira Service Management Web
investigating
We are investigating reports of intermittent errors and degredated performance for some Jira Service Management and Jira Cloud customers.
We will provide further updates within one hour.
identified
Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.
We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.
monitoring
Our team has been able to apply the fix and mitigate the issue. The services have been restored to normal operations.
We will continue to actively monitor over the next 8 hours to confirm stability.
resolved
The issue has now been resolved, and the service is operating normally for all affected customers.
Users experiencing issues loading work items in Jira and JSM
์์ 2026๋ 6์ 8์ผ AM 1:53 UTC ยท 1h 3m
Issues๊ฒฝ๋ฏธํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Authentication and User ManagementJira Service Management Web
investigating
We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.
identified
We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions.
Our engineering team is actively working on a resolution. We will provide an update within the next hour.
resolved
On 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.
Degraded performance of Jira and JSM automations in US East
์์ 2026๋ 6์ 2์ผ PM 3:32 UTC ยท 1h 19m
Issues๊ฒฝ๋ฏธํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebJira Service Management Email Requests
investigating
We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. Some customers may experiences delays in rule execution. We'll provide an update here within the next hour, or sooner if new information becomes available.
resolved
On 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.
For Jira-software viewIssues and viewBoard are degraded
์์ 2026๋ 6์ 1์ผ AM 8:06 UTC ยท 5h 17m
Outage์ค๋ํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebJira Service Management Email Requests
investigating
We are investigating cases of partial-outage for Jira-software in the EU Region.
We will provide more details within the next hour.
identified
We have identified an issue causing degraded performance for Jira Software, Jira Work Management, and Jira Service Management in the EU region. affected users may experience 5XX errors when accessing issues, boards, and navigation.
Our engineering team is actively working on a resolution. We will provide an update within the next hour.
monitoring
We have implemented a fix for the issue causing degraded performance for Jira Software and Jira Service Management in the EU region. The impact has been mitigated, and we are actively monitoring the stability.
resolved
This incident has been resolved. The issue causing degraded performance for Jira Software and Jira Service Management in the EU region has been fully mitigated. We have deployed a fix to prevent recurrence.
If you continue to experience issues, please contact Atlassian Support.
We apologise for the disruption and thank you for your patience.
postmortem
**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 across Jira Software, Jira Service Management, and Jira Work Management.
**ROOT CAUSE**
The root cause of the incident was a capacity constraint on our caching infrastructure in one availability zone of our EU Central cloud region. As morning traffic increased, our caching clusters attempted to scale out automatically. However, the cloud infrastructure was unable to provision additional nodes in that availability zone due to insufficient underlying capacity.
Our caching infrastructure is designed to scale across multiple availability zones to ensure balanced and resilient capacity. On this occasion, a capacity constraint in one availability zone prevented the scaling operation from completing as expected.
With the caching layer unable to grow to meet demand, the clusters began to experience network and/or CPU saturation and could not handle all incoming requests within the expected timeout window. Since a single user request to Jira typically involves multiple cache calls, timeouts compound rapidly. As more threads became blocked waiting on timed-out or slow cache operations, the application nodes reached its busy thread limit and began shedding load. While additional application nodes were added, these also experienced the same thread limit saturation due to the saturation of the cache layer resulting in widespread 503 service unavailable errors for customers.
**REMEDIAL ACTIONS PLAN & NEXT STEPS**
We know that outages impact your productivity. In addition to existing safeguards and monitoring, Atlassian is prioritizing the following actions to help prevent similar incidents in future:
- **Increased minimum caching cluster size**: We have increased the minimum number of nodes in all affected caching clusters in the EU Central region. This ensures sufficient capacity headroom to handle peak traffic without relying on autoscaling, reducing the risk of a similar failure occurring.
- **Change autoscaling behaviour**: We are working on improvements to our autoscaling behaviour to fall back to other availability zones when capacity is unavailable in a single zone.
We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platformโs performance and availability.
Thanks,
Atlassian Customer Support
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebJira Service Management Email Requests
investigating
We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time.
We will provide further update within one hour or sooner as information is available.
identified
Further confirmations of impacted products have now been added to the incident.
Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.
identified
It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident.
We are continuing to receive reports about expanded product impact resulting from this incident.
While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information.
We will provide further update within one hour, or sooner as further information becomes available.
identified
Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products.
At this time, Atlassian customers should also be able to once again raise support requests with our team.
We will provide further update within an hour as we are able to progress mitigating this issue.
monitoring
Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products.
We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.
monitoring
We are now able to see recovery for all impacted products, and users should be able to access their products as expected.
Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.
monitoring
We are approaching full system recovery at this time, and are performing final confirmations that services are restored.
resolved
All products and services impacted by this incident should now be fully recovered, and this incident is resolved.
postmortem
### 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 services. Customers also experienced errors when accessing the support portal until Atlassian fell back to an alternate support method. This was caused by a core identity service in the us-east region becoming unavailable. Affected products included Atlassian Administration, Atlassian Analytics, Bitbucket, Compass, Confluence, Jira, Jira Product Discovery, Jira Service Management and Trello. Some users outside us-east may have been affected in certain scenarios.
### **ROOT CAUSE**
The incident 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.
### **REMEDIAL ACTIONS PLAN & NEXT STEPS**
We know that outages impact your productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future:
* **Refine deployment orchestration safeguards**
* Harden our deployment platform to prevent similar race conditions or resulting capacity loss during a rollback operation.
* Streamline mitigation steps when a service becomes unavailable in a region.
* **Reduce cross-region impact**
* Improve regional isolation and fallback handling so an issue affecting a single region is less likely to impact customers or product functionality in other regions.
We recognise how critical reliable access to Atlassian products is for our customers' productivity, and we apologize to customers who were impacted by this incident.
Thanks,
Atlassian
Excessive notifications being received by some Jira Service Management users
์์ 2026๋ 5์ 14์ผ AM 1:15 UTC ยท 8h 26m
Issues๊ฒฝ๋ฏธํ ์ธ์๋ํธ
์ํฅ์ ๋ฐ์ ๊ตฌ์ฑ ์์
Opsgenie Alert FlowAuthentication and User ManagementSignupPurchasing & LicensingOpsgenie Incident FlowOpsgenie Incident FlowOpsgenie Alert FlowAutomation for JiraAssistService PortalJira Service Management WebJira Service Management Email Requests
investigating
We are aware that some users are experiencing an excessive number of notifications arriving from Jira Service Management (Assist) as our team replays delayed events experienced in this prior incident:
https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7
At this time we expect that the vast majority of these notifications will be arriving within the next two hours.
We will provide further update at that time or sooner if further information becomes available.
investigating
Some of the users continue to experience an excessive number of notifications arriving from JSM (Assist) as our team replays delayed events experienced in this prior incident:
https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7
At this time we expect that these notifications will be arriving for the next few hours, until the recovery of the delayed events are processed which is taking longer than expected (ETA approx. 4 hours). We will provide further updates within 6 hours or sooner if the recovery occurs.
resolved
This 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.