{
"vendor": "Jira Work Management",
"slug": "jira-work-management",
"platform": "statuspage",
"status_url": "https://jira-work-management.status.atlassian.com",
"last_checked": "2026-09-16T12:28:20Z",
"last_state": "ok",
"history_backfilled": true,
"first_watched": "2026-09-04T07:06:16Z",
"incidents": [
{
"body": "On 1st Sept 2026, between 04:22 UTC to 10:59 UTC, some Jira users may have experienced service disruptions. \n\nThe issue has now been resolved and the service is operating normally for all the customers.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-09-01T11:44:04.832Z",
"resolved_inferred": false,
"started_at": "2026-09-01T09:12:36.805Z",
"state": "resolved",
"title": "Jira - Work Item transition failures",
"updated_at": "2026-09-01T11:44:04.848Z",
"url": "https://stspg.io/l0d6pngd9rrt"
},
{
"body": "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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-07T01:46:47.642Z",
"resolved_inferred": false,
"started_at": "2026-08-07T01:26:48.663Z",
"state": "resolved",
"title": "Degraded performance of JIRA",
"updated_at": "2026-08-07T01:46:47.655Z",
"url": "https://stspg.io/1sndnjmt785j"
},
{
"body": "**SUMMARY**\n\n  \n\nOn 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.\n\n  \n\n**IMPACT**\n\n  \n\nThe 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.\n\n  \n\n**ROOT CAUSE**\n\n  \n\nThe 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.\n\nOur 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.\n\nWith 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.\n\n  \n\n**REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\n  \n\nWe 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:\n\n  \n\n-   **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.\n-   **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.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability.\n\n  \n\nThanks,\n\nAtlassian Customer Support",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-01T13:23:43.580Z",
"resolved_inferred": false,
"started_at": "2026-06-01T08:06:30.785Z",
"state": "postmortem",
"title": "For Jira-software viewIssues and viewBoard are degraded",
"updated_at": "2026-06-12T06:49:17.766Z",
"url": "https://stspg.io/zkfjwt0k03lr"
},
{
"body": "### Summary\n\nOn 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.\n\n### **IMPACT**\n\nDuring 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.\n\n### **ROOT CAUSE**\n\nThe 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.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that outages impact your productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future:\n\n* **Refine deployment orchestration safeguards**\n\n    * Harden our deployment platform to prevent similar race conditions or resulting capacity loss during a rollback operation.\n    * Streamline mitigation steps when a service becomes unavailable in a region.\n    \n* **Reduce cross-region impact**\n\n    * 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.\n    \n\nWe recognise how critical reliable access to Atlassian products is for our customers' productivity, and we apologize to customers who were impacted by this incident.\n\nThanks,\n\nAtlassian",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-14T06:48:27.825Z",
"resolved_inferred": false,
"started_at": "2026-05-14T05:11:20.113Z",
"state": "postmortem",
"title": "Users experiencing issues accessing multiple Atlassian products",
"updated_at": "2026-05-19T19:08:54.832Z",
"url": "https://stspg.io/dd2wp6425d3y"
},
{
"body": "All dates and times below are in UTC unless stated otherwise.\n\n### Summary\n\nOn 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.\n\nThe 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.\n\n### **IMPACT**\n\nThe primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Atlassian services and underpins background operations such as automation execution, search indexing, notifications, permission synchronisation.\n\n* Between 00:22 and 06:08, an infrastructure incident in our hosting provider triggered an ingestion failure in our event processing pipeline.\n* At 02:50, event ingestion was failed over to an unaffected availability zone, progressively restoring live event flows.\n* At 06:08, reliability for new ingestion in prod-east recovered to 100%. The remaining work was to drain the accumulated cross-region backlog of messages, which completed by 17:00.\n* By 18:48, Automation had processed their backlog of events that were created while processing\n\n**Automation**\n\nBetween 00:22 and 02:50, customers with automation rules triggered by events originating from the prod-east region experienced a significant reduction in rule executions. During this window, event-triggered automation rules were not firing because the events that trigger them were not being delivered. Rule authoring, saving, and rules triggered manually, by schedules, or by webhooks were not affected.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of live events to Automation and allowing new event-triggered rules to begin executing normally. However, events generated during the impact window still needed to be replayed before delayed automations could be processed.\n\nBeginning at 08:28, upstream services replayed their queued events in a coordinated sequence, and all replayed events were processed by 18:48. During the replay window, customers may have experienced automation rules executing later than expected, a small number of rules reaching daily processing limits due to compressed replay, and time-sensitive rules not completing as expected if internal timeout thresholds were exceeded.\n\n**Jira and Jira Service Management**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruption to Jira and Jira Service Management event-driven features like automation, along with a short period of elevated errors during infrastructure failover. Core Jira experiences, including issue view, boards, and project navigation, remained available throughout the incident.\n\nJira event delivery was affected by the primary impact, preventing downstream services from receiving issue lifecycle events. This affected automation rules triggered by Jira events, AI agent orchestration in Jira, notifications for issue updates and transitions, search indexing for newly created or modified issues, and event-driven integrations between Jira and other Atlassian products.\n\nAt 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of new events. All events generated during the impact window were retained in a recovery queue and required replaying. This began at 08:28 and completed at 12:00. During the replay window, customers may have experienced automation rules executing later than expected, delayed notifications arriving hours after the triggering action, temporary gaps in search results for content created or modified during the impact window, and AI agent workflows not completing as expected where internal timeout thresholds were exceeded.\n\n**Confluence**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruptions to event-driven services in Confluence. This resulted in delays to search indexing, notifications, automation rule execution, and permission synchronisation.\n\nThe underlying event processing infrastructure failed over to an unaffected availability zone, after which live Confluence operations resumed normally. However, events generated during the impact window were queued for replay, and some background services remained delayed until that replay and related validation work completed.\n\nBetween 10:14 and 17:00, a bulk replay of all the queued tenant replay tasks was completed to restore data consistency. During and immediately after the replay window, customers may have experienced search results not reflecting content created or modified during the outage, delayed or missing notifications for page and comment activity, automation rules firing later than expected, and brief delays in permission synchronisation for tenants relying on incremental identity sync.\n\n**Bitbucket and Pipelines**\n\nBetween 00:22 and 06:08, customers using Bitbucket and Pipelines experienced failures and degraded functionality across event-driven workflows. Core Git operations, including push, pull, and clone, were not affected and continued to operate normally throughout the incident.\n\nAutomatic pipeline triggers initiated by push or pull request events were unavailable during the impact window. Merge queues, custom merge checks, Forge-based triggers, workspace permission changes, and some workspace provisioning flows were also affected. Customers using merge queues were unable to merge pull requests, and some pipeline steps failed because queued work contributed to elevated concurrency limits.\n\nAt approximately 03:57, Pipelines was reconfigured to consume events through an alternative path, restoring automatic pipeline triggering. Merge queues, custom merge checks, Forge triggers, and other affected workflows were progressively restored as the underlying event processing infrastructure recovered. All Bitbucket and Pipelines services were confirmed fully operational by 06:08. After recovery, queued events were reviewed and replayed where safe to restore data consistency for billing, audit logging, and other background processes.\n\n**Identity Services**\n\nBetween 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced delays in the propagation of identity and group membership changes to downstream Atlassian products. Core identity operations, including authentication, login, and direct group management actions, were not affected and continued to function normally throughout the incident.\n\nThe impact was limited to asynchronous, event-driven operations that depend on the event processing pipeline. This included delays in delivering group membership and user profile changes to products such as Jira and Confluence, which affected downstream permission synchronisation and crowd sync flows. A small number of SCIM-based identity synchronisation and site provisioning workflows also experienced temporary delays.\n\nAfter the event processing infrastructure recovered, backed-up identity and group directory events were replayed where required, restoring downstream consistency for affected products. No identity data was lost. Group membership changes, user profile updates, and provisioning-related events that occurred during the impact window were retained and processed after recovery.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know outages impact your productivity. While our monitoring and recovery processes helped us respond quickly, this incident highlighted opportunities to further strengthen resilience for event-driven services.\n\nWe are prioritizing improvements that will:\n\n* **Enhance failover coverage** so critical event processing can recover more smoothly during infrastructure disruptions.\n* **Strengthen recovery handling** so replayed events can be processed more quickly.\n\nWe apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform\u2019s performance and availability.\n\nThanks,\n\nAtlassian Customer Support.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-08T19:45:32.372Z",
"resolved_inferred": false,
"started_at": "2026-05-08T01:31:38.250Z",
"state": "postmortem",
"title": "Multiple Atlassian services are experiencing issues",
"updated_at": "2026-05-20T06:51:56.704Z",
"url": "https://stspg.io/dpplsyqbtp8p"
},
{
"body": "The issue causing Jira users inability to log time on business board has been resolved. A fix was deployed to address the problem and the service is operating normally for all affected customers.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-06T06:39:27.320Z",
"resolved_inferred": false,
"started_at": "2026-05-06T03:18:26.388Z",
"state": "resolved",
"title": "Jira users unable to log time while on business board",
"updated_at": "2026-05-06T06:39:27.335Z",
"url": "https://stspg.io/bgbskn8ns4jl"
},
{
"body": "### SUMMARY\n\n###   \n\nBetween 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.\n\n  \n\nThe issue also affected Atlassian's customer support operations and temporarily impacted Atlassian\u2019s ability to respond to incoming support requests. Customers were able to raise tickets as usual.\n\n  \n\nAtlassian\u2019s automated monitoring systems detected the issue on May 1, 2026 at 23:41 UTC, and engineering teams promptly began investigating.\n\n  \n\nThe issue was reported on Statuspage on May 2, 2026 at 00:55 UTC.\n\n  \n\nThe issue was resolved after 3 hours and 19 minutes on May 2, 2026 at 02:53 UTC when the previous version of the schema configuration was successfully redeployed to all regions.\n\n  \n\n### IMPACT\n\n###   \n\n-   **Duration**: 3 hours 19 minutes (May 1, 2026 at 23:34 UTC \u2013 May 2, 2026 at 02:53 UTC)\n-   **Affected regions**: All regions.\n-   **Affected products**: Jira, JSM, Jira Mobile\n-   **Customer experience**:\n-   Users were unable to view work items using the work item view; consequently updating and creating work items from the work item view was affected.\n-   Editing work items was degraded.\n-   Boards did not show under Spaces in the Jira navigation.\n-   Certain board interactions were affected.\n-   Other areas of Jira not dependent on the broken schema configuration continued to operate normally.\n\n###   \n\n### ROOT CAUSE\n\n###   \n\nThe root cause was a deployment sequencing issue. A schema configuration change was deployed to the API gateway layer before the corresponding application-level change had been deployed across all production environments. This created a mismatch between the schema expected by the gateway and the schema served by the application servers.\n\n###   \n\n### MITIGATIONS\n\n###   \n\nThe engineering team identified the problematic schema change and initiated a rollback of the deployment. A deployment blocker was put in place to prevent further changes while the rollback was executed. The previous version of the schema configuration was redeployed, and service was restored across all regions.\n\n###   \n\n### REMEDIAL ACTION PLAN & NEXT STEPS\n\n###   \n\nWe understand that service disruptions impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritizing the following actions to help reduce the likelihood and impact of similar incidents in the future and to speed up recovery when issues occur:\n\n-   We are adding automated pre-deployment checks to verify that schema configurations are compatible across all production environments before changes are deployed.\n-   We will streamline our incident communication processes, incident response training and tooling to reduce the time between incident detection and customer notification.\n-   We are working to improve resilience of critical customer-facing support services to ensure SLA continuity during outages.\n\nWe apologize to customers whose services were impacted during this incident. We are taking immediate steps to reduce the risk and impact of similar issues in future.\n\n  \n\nThanks,\n\nAtlassian",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-02T02:48:03.104Z",
"resolved_inferred": false,
"started_at": "2026-05-02T00:55:47.610Z",
"state": "postmortem",
"title": "The Work Item view experience of Jira is restored",
"updated_at": "2026-05-14T19:44:10.014Z",
"url": "https://stspg.io/m8y33t0z5tzq"
},
{
"body": "On 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-14T16:11:31.119Z",
"resolved_inferred": false,
"started_at": "2026-04-14T12:12:58.255Z",
"state": "resolved",
"title": "Disrupted Rovo availability for Automation rules",
"updated_at": "2026-04-14T16:11:31.138Z",
"url": "https://stspg.io/1q440l8q743p"
},
{
"body": "### Summary\n\nOn 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.\n\n### **IMPACT**\n\n* **Duration**: ~40 minutes \\(05:49\u201306:29 UTC, April 13, 2026\\)\n* **Affected regions**: US East and EU \\(authentication infrastructure serves EU traffic from US East, with traffic primarily from EU at this time of day\\).\n* **Affected products**: All Atlassian cloud products requiring authentication, including Jira, Confluence, Jira Service Management, and Trello.\n* **Customer experience**: Users attempting to log in, sign up, reset passwords, or complete MFA flows received errors. Users already logged in with active sessions were unaffected.\n\n### **ROOT CAUSE**\n\nThis incident had several contributing factors that combined to produce a failure that the system could not recover from without manual intervention.\n\n**The primary cause** was a recently enabled change that caused our authentication infrastructure to retry requests to a downstream identity service when those requests were slow to respond. This retry behaviour was rolled out to 100% of traffic earlier the same day. Under normal conditions this would be benign, but it meant that any slowness in the downstream service was amplified. Since multiple upstream services were also independently retrying their own failed requests, the amplification compounded further into a retry storm.\n\n**The trigger** was a burst of legitimate user traffic. A pattern of many parallel link preview requests for a single user caused a concentrated load spike on a downstream identity service, pushing its response times above the retry threshold. On its own, this kind of spike had occurred many times before and always recovered. With the retry amplification now in effect, the spike instead created a runaway feedback loop: slow responses caused retries, retries increased load, increased load caused slower responses, preventing recovery.\n\nThe incident was mitigated by manually scaling up the downstream identity service to provide sufficient capacity to absorb the amplified load. Once scaled, the service recovered immediately, bringing authentication error rates to zero within one minute.\n\n**REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe are taking the following actions designed to prevent recurrence and improve our resilience:\n\n1. **Immediate**: The retry-on-timeout change has been disabled.\n2. **Load shedding and self-healing**: We are adding load shedding capabilities to our authentication services so that they can automatically shed excess load and self-recover during traffic spikes, without requiring action before automatic scaling starts.\n3. **Reducing request fan-out**: We are reviewing patterns where a single user action can generate many parallel downstream requests, and will introduce methods where possible to reduce the amplification potential.\n\nWe apologize to customers whose services were interrupted by this incident and we are taking immediate steps to improve the platform\u2019s reliability.\n\nThanks,\n\nAtlassian Customer Support",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-13T10:17:21.304Z",
"resolved_inferred": false,
"started_at": "2026-04-13T07:29:45.520Z",
"state": "postmortem",
"title": "Users experiencing issues with login across Atlassian products",
"updated_at": "2026-04-21T02:34:15.858Z",
"url": "https://stspg.io/ys9yfmqzr7c4"
},
{
"body": "On 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-10T00:59:02.593Z",
"resolved_inferred": false,
"started_at": "2026-03-10T00:06:29.000Z",
"state": "resolved",
"title": "Automation events delayed for some customers in the APAC region",
"updated_at": "2026-03-10T00:59:02.611Z",
"url": "https://stspg.io/lms5h6xqxtkg"
},
{
"body": "### Summary\n\nOn **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence functionality remained available.\n\nThe issue was triggered when **TLS certificates used by Atlassian\u2019s monitoring infrastructure expired**, causing parts of our metrics pipeline to stop accepting traffic. Services responsible for email and mobile notifications had a critical path dependency on monitoring path leading to service disruptions.\n\nAll impacted services were fully restored by **05:20 UTC**, around **2.5 hours** after customer impact began.\n\n### IMPACT\n\nDuring the impact window, customers experienced:\n\n* **Outbound product email failures** \\(notifications and other product emails did not send\\).\n* **Identity and account flow failures** where emails were required \\(e.g. sign\u2011ups, password resets, one\u2011time\u2011password / step\u2011up challenges\\).\n* **Jira and Confluence mobile push notifications**\n* **Customer site activations and some admin policy changes** failing and requiring later reprocessing.\n\n### ROOT CAUSE\n\nThe incident was caused by:\n\n1. **Expired TLS certificates** on domains used by our monitoring and metrics infrastructure caused by **misconfigured DNS authorization record** which prevented automatic renewal.\n2. **Tight coupling of services to metrics publishing**, which caused them to fail when monitoring endpoints became unavailable, instead of degrading gracefully.\n\n### REMEDIAL ACTIONS PLAN & NEXT STEPS\n\nWe recognize that outages like this have a direct impact on customers\u2019 ability to receive important notifications, complete account tasks, and operate their sites.\n\nWe are prioritizing the following actions to improve our existing testing, monitoring and certificate management processes:\n\n* **Hardening monitoring and certificate infrastructure**\n\n    * We are refining DNS and certificate configuration across our monitoring domains and strengthening proactive checks to detect and address failed renewals and certificate issues well before expiry.\n    * We are also improving alerting on our monitoring and metrics pipeline.\n    \n* **Decoupling monitoring from critical customer flows**  \n  We are updating services such as outbound email, identity, mobile push, provisioning, and admin policy changes so they no longer depend on metrics publishing to operate. If monitoring becomes unavailable, these services will continue to run and degrade gracefully by dropping or buffering metrics instead of failing customer operations.\n\nWe apologize to customers impacted during this incident. We are implementing the improvements above to help ensure that similar issues are avoided.\n\nThanks,  \nAtlassian Customer Support",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-27T05:20:20.949Z",
"resolved_inferred": false,
"started_at": "2025-12-27T04:42:32.892Z",
"state": "postmortem",
"title": "Outbound Email, Mobile Push Notifications, and Support Ticket Delivery Impacting All Cloud Products",
"updated_at": "2026-01-30T04:10:27.735Z",
"url": "https://stspg.io/5w3x2w72gv3w"
},
{
"body": "On 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.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-15T19:02:03.638Z",
"resolved_inferred": false,
"started_at": "2025-12-15T16:26:38.689Z",
"state": "resolved",
"title": "Degraded performance of Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo",
"updated_at": "2025-12-15T19:02:03.658Z",
"url": "https://stspg.io/6mr1xtcyt6n2"
},
{
"body": "Impact\n\nJira Software users experienced degraded performance affecting their ability to view issues and boards. Users may have encountered an error or slowdown during this time.\n\nCurrent Status\n\nThe situation is currently mitigated due to actions taken on the affected systems, leading to a stabilization of services. \n\nNext Steps\n\nThe team is actively monitoring the systems.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-01T18:26:46.054Z",
"resolved_inferred": false,
"started_at": "2025-12-01T17:24:45.034Z",
"state": "resolved",
"title": "Degraded Performance for Some Jira Users",
"updated_at": "2025-12-01T18:26:46.070Z",
"url": "https://stspg.io/sxvkv1d8nw5s"
},
{
"body": "The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-17T11:50:17.349Z",
"resolved_inferred": false,
"started_at": "2025-11-15T16:29:42.996Z",
"state": "resolved",
"title": "Some users are unable to send emails from Jira",
"updated_at": "2025-11-17T11:50:17.367Z",
"url": "https://stspg.io/4nghwhzdgl4s"
},
{
"body": "Between 15:09 UTC to 17:16 UTC, some customers experienced partial outage for Jira Work Management, Jira Service Management, and Jira viewIssue, createIssue and editIssue caused by a faulty code rollout.  We have deployed a fix to mitigate the issue and have verified that the services have recovered.  The root cause is still being investigated and will be provided in the post incident review. The conditions that cause the errors are being addressed and we're actively working on a permanent fix. The issue has been resolved and the services are operating normally.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-27T17:50:17.754Z",
"resolved_inferred": false,
"started_at": "2025-10-27T16:33:50.764Z",
"state": "resolved",
"title": "Jira Platform Incident - viewIssue and createIssue Service Disruption",
"updated_at": "2025-10-27T17:50:17.768Z",
"url": "https://stspg.io/7mbbwffjq45p"
},
{
"body": "### Postmortem publish date: Nov 19th, 2025\n\n### Summary\n\nAll dates and times below are in UTC unless stated otherwise.\n\nCustomers 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.\n\nThe incident started at Oct 20, 2025 06:48 and was detected within six minutes by our automated monitoring systems. Our teams worked to restore all core services by Oct 21, 2025 04:05. Final cleanup of backlogged processes and minor issues was completed on Oct 22, 2025.\n\nWe recognize the critical role our products play in your daily operations, and we offer our sincere apologies for any impact this incident had on your teams. We are taking immediate steps to enhance the reliability and performance of our services, so that you continue to receive the standard of service you have come to trust.\n\n### IMPACT\n\nBefore examining product-level impacts, it's helpful to understand Atlassian's service topology and internal dependencies.\n\nProducts such as Jira and Confluence are deployed across multiple AWS regions. The data for each tenant is stored and processed exclusively within its designated host region. This design is intentional and represents the desired operational state, as it limits the impact of any regional outage strictly to tenants in-region, in this case us-east-1.\n\nWhile in-scope application data is pinned to the region selected by the customer, there are times when systems need to call other internal services that may be based in a different region. If a problem occurs in the main region where these services operate, systems are designed to automatically fail over to a backup region, usually within three minutes.\n\nHowever, if unexpected issues arise during this failover, it can take longer to restore services. In rare cases, this could affect customers in more than one region. It\u2019s important to note that all in-scope application data for supported products is pinned according to a customer\u2019s chosen region.\n\n**Jira**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 20:00, customers with tenants hosted in the us-east-1 region experienced increased error rates when accessing core entities such as Issues, Boards, and Backlogs. This disruption was caused by AWS's inability to allocate AWS EC2 instances and elevated errors in AWS Network Load Balancer \\(NLB\\). During this window, users may also have observed intermittent timeouts, slow page loads, and failures when performing operations like creating or updating issues, loading board views, and executing workflow transitions.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced elevated failure rates when attempting to load Jira pages. This disruption was caused by the regional frontend service entering an unhealthy state during this specific time interval.\n\nNormally, the frontend service connects to the primary AWS DynamoDB instance located in the us-east-1 to retrieve the most recent configuration data necessary for proper operation. Additionally, the service is designed with a fallback mechanism that references static configuration data in the event that the primary database becomes inaccessible. Unfortunately, a latent bug existed in the local fallback path. When the frontend service nodes restarted, they were unable to load critical operational configuration data from primary or fallback sources, leading to the observed failures experienced by customers.\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 06:30, customers experienced significant delays and missing Jira in-app notifications across all regions. The notification ingestion service, which is hosted exclusively in us-east-1, exhibited an increased failure rate when processing notification messages due to AWS EC2 and NLB issues. This issue resulted in notifications being delayed - and in some cases, not delivered at all - to users worldwide.\n\n**Jira Service Management \\(JSM\\)**\n\nJSM was impacted similarly to Jira above, with the same timeframes and for the same reasons.\n\nBetween Oct 20, 2025 08:36 and Oct 20, 2025 09:23, customers across all regions experienced significantly elevated failure rates when attempting to load JSM pages. This affected all JSM experiences including the Help Centre, Portal, Queues, Work Items, Operations, and Alerts.\n\n**Confluence**\n\nBetween Oct 20, 2025 06:48 and Oct 21, 2025 02:45, customers using Confluence in the us-east-1 region experienced elevated failure rates when performing common operations such as editing pages or adding comments. The primary cause of this service degradation was the system's inability to auto-scale due to AWS EC2 issues to manage peak traffic load effectively.\n\nThough the AWS outage ended at Oct 20, 21:09, a subset of customers continued to experience failures as some Confluence web server nodes across multiple clusters remained in an unhealthy state. This was ultimately mitigated by recycling the affected nodes.\n\nTo protect our systems while AWS recovered, we made a deliberate decision to enable node termination protection. This action successfully preserved our server capacity but, as a trade-off, it extended the time required for a full recovery once AWS services were restored.\n\n**Automation**\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 23:59, automation customers whose rules are processed in us-east-1 experienced delays of up to 23 hours in rule execution.\n\nDuring this window, some events triggering rule executions were processed out of order because they arrived later during backlog processing. This caused potential inconsistencies in workflow executions, as rules were run in the order events were received, not when the action causing the event occurred. Additionally, some rule actions failed because they depend on first-party and third-party systems, which were also affected by the AWS outage. Customers can see most of these failures in their audit logs; however, a few updates were not logged due to the nature of the outage.\n\nBy Oct 21, 2025 5:30, the backlog of rule runs in us-east-1 was cleared. Although most of these delayed rules were successfully handled, there were some additional replays of events to ensure completeness. Our investigation confirmed that a few events may never have triggered their associated rules due to the outage.\n\nBetween Oct 20, 2025 06:55 and Oct 20, 2025 11:20, all non-us-east-1 regional automation services experienced delays of up to 4 hours in rule execution. This was caused by an upstream service that was unable to deliver events as expected. The delivery service encountered a failure due to a cross-region dependency call to a service hosted in the us-east-1 region. Because of this dependency issue, the delivery service was unable to successfully deliver events throughout this time frame, resulting in customer-defined rules not being executed in a timely manner.\n\n**Bitbucket and Pipelines**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:33, Bitbucket experienced intermittent unavailability across core services. During this period, users faced increased error rates and latency when signing in, navigating repositories, and performing essential actions such as creating, updating, or approving pull requests. The primary cause was an AWS DynamoDB outage that impacted downstream services.\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 22:46, numerous Bitbucket Pipeline steps failed to start, stalled mid-execution, or experienced significant queueing delays. Impact varied, with partial recoveries followed by degradation as downstream components re-synchronized. The primary cause was an AWS DynamoDB outage, compounded by instability in AWS EC2 instance availability and AWS Network Load Balancers.\n\nFurthermore, Bitbucket Pipelines continued to experience a low but persistent rate of step timeouts and scheduling errors due to AWS bare-metal capacity shortages in select availability zones. Atlassian coordinated with AWS to provision additional bare-metal hosts and addressed a significant backlog of pending pods, successfully restoring services by 01:30 on Oct 21, 2025.\n\n**Trello**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 15:25, users of Trello experienced widespread service degradation and intermittent failures due to upstream AWS issues affecting multiple components, including AWS DynamoDB and subsequent AWS EC2 capacity constraints. During this period, customers reported elevated error rates when loading boards, opening cards, adding comments or attachments.\n\n**Login**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, a small subset of users experienced failures when attempting to initiate new login sessions using SAML tokens. This resulted in an inability for those users to access Atlassian products during that time period. However, users who already had valid active sessions were not affected by this issue and continued to have uninterrupted access.\n\nThe issue impacted all regions globally because regional identity services relied on a write replica located in the us-east-1 region to synchronize profile data. When the primary region became unavailable, the failover to a secondary database in another region failed, which delayed recovery. This failover defect has since been addressed.\n\n**Statuspage**\n\nBetween Oct 20, 2025 06:48 and Oct 20, 2025 09:30, Statuspage customers who were not already logged in to the management portal were unable to log in to create or update incident statuses. This impact was restricted only to users who were not already logged in at the time. The root cause was the same as described in the Login section above, and it was resolved by the same remediation steps.\n\n### REMEDIAL ACTION PLAN & NEXT STEPS\n\nWe have completed the following critical actions designed to help prevent cross-region impact from similar issues:\n\n* Resolved the code defect in the fallback option to ensure that Jira Frontend Services in other regions remain unaffected during a region-wide outage.\n* Fixed the issue that prevented timely failover of the identity service which impacted new login sessions.\n* Resolved the code defect so that delivery services in unaffected regions remain operational during region-wide outages.\n\nAdditionally, we are prioritizing the following improvement actions:\n\n* Implement mitigation strategies to strengthen resilience against region-wide outages in the notification ingestion service.\n\nAlthough disruptions to our cloud services are sometimes unavoidable during outages of the underlying cloud provider, we continuously evaluate and improve test coverage to strengthen resilience of our cloud services against these issues.\n\nWe recognize the critical importance of our products to your daily operations and overall productivity, and we extend our sincere apologies for any disruptions this incident may have caused your teams. If you were impacted and require additional details for internal post-incident reviews, please reach out to your Atlassian support representative with affected timeframes and tenant identifiers so we can correlate logs and provide guidance.\n\nThanks,\n\nAtlassian Customer Support",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-21T05:24:27.257Z",
"resolved_inferred": false,
"started_at": "2025-10-20T07:56:12.526Z",
"state": "postmortem",
"title": "Atlassian Cloud Services impacted",
"updated_at": "2025-11-25T03:57:33.031Z",
"url": "https://stspg.io/pw7bm5jwf7b6"
},
{
"body": "Between 14:00 UTC to 16:00 UTC, we experienced automation rule functionality degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. \n\nImpact\n\nSome customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Approximately 50 percent of Automation API calls were affected in the us-east-1 region with customers receiving 429 status codes.\n\nCurrent Status\n\nThe incident has been mitigated by increasing the API Gateway rate limit service quota and disabling the internal service that was causing high traffic volume. \n\nNext Steps\n\nWe are conducting a root cause analysis of the internal service. A post incident review will be conducted.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-15T16:16:06.994Z",
"resolved_inferred": false,
"started_at": "2025-10-15T13:43:56.095Z",
"state": "resolved",
"title": "Unable to perform UI Operations",
"updated_at": "2025-10-15T16:16:07.013Z",
"url": "https://stspg.io/31j420tkykfr"
},
{
"body": "### **SUMMARY**\n\nOn 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.\n\nThe 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.\n\nThe 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.\n\n### **IMPACT**\n\nThe acute impact occurred on\u00a0September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered.\n\n### **ROOT CAUSE**\n\nThe issue was caused by a change to the hostname configuration of our Content Delivery Network \\(CDN\\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors.\n\nMore specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWe know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation.\n\nWe are prioritizing the following improvement actions to help avoid repeating this type of incident:\n\n* Improved pre-deployment change controls and testing.\n* Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed.\n* Sharding of our CDN configuration to enable progressive changes.\n\nWe sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience.\n\nThank you,\n\nAtlassian Customer Support",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-22T07:17:23.583Z",
"resolved_inferred": false,
"started_at": "2025-09-22T05:38:57.880Z",
"state": "postmortem",
"title": "Degraded performance to multiple Atlassian experiences",
"updated_at": "2025-10-01T06:21:32.656Z",
"url": "https://stspg.io/ks66j52hl5n1"
},
{
"body": "An 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.\nAll Edge browsers should otherwise receive this update within 10 hours without user intervention.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-15T06:40:39.713Z",
"resolved_inferred": false,
"started_at": "2025-09-09T10:23:55.773Z",
"state": "resolved",
"title": "Degraded performance in Confluence and Jira for Microsoft Edge users",
"updated_at": "2025-09-15T06:40:39.731Z",
"url": "https://stspg.io/y3lhks0rbpkn"
}
]
}