{
"vendor": "Atlassian Developer",
"slug": "atlassian-developer",
"platform": "statuspage",
"status_url": "https://developer.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": "We have identified the cause of the issue impacting installation requests and deployed a fix. The issue is now 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-09-02T03:17:39.246Z",
"resolved_inferred": false,
"started_at": "2026-09-02T03:09:23.978Z",
"state": "resolved",
"title": "Forge developer installation requests failing intermittently",
"updated_at": "2026-09-02T03:17:39.268Z",
"url": "https://stspg.io/mypl93j6b9nb"
},
{
"body": "On Aug 25th, 2026, between 08:12 UTC and 11:03 UTC, some Marketplace apps may have experienced scheduled triggers (5-minute intervals) not firing as expected.\n\nThe issue has now been resolved and the 5-minute scheduled triggers are operating normally for all customers.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-25T11:11:04.824Z",
"resolved_inferred": false,
"started_at": "2026-08-25T10:58:56.965Z",
"state": "resolved",
"title": "Scheduled 5 min-triggers not firing for some Apps",
"updated_at": "2026-08-25T11:11:04.844Z",
"url": "https://stspg.io/zs1zj1nv8650"
},
{
"body": "We have confirmed that the issues relating to installing, uninstalling and managing Forge and OAuth 2.0 apps should now be fully resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-08-03T03:37:51.207Z",
"resolved_inferred": false,
"started_at": "2026-08-03T03:26:36.528Z",
"state": "resolved",
"title": "Issues installing, uninstalling and managing Forge or OAuth 2.0 apps",
"updated_at": "2026-08-03T03:37:51.229Z",
"url": "https://stspg.io/hj54238khqkd"
},
{
"body": "On Jul 13, 2026, partner operations may have experienced some service disruption. 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-07-13T17:46:03.265Z",
"resolved_inferred": false,
"started_at": "2026-07-13T15:48:27.246Z",
"state": "resolved",
"title": "Marketplace : Partner operations are down",
"updated_at": "2026-07-13T17:46:03.322Z",
"url": "https://stspg.io/5dkx7d1v0trd"
},
{
"body": "All customers that had previously received the incorrect notifications about the Time Tracker for Jira Cloud and DC app should have received corrective communications at this time.\n\nWe are now resolving this issue.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-07-02T04:43:17.909Z",
"resolved_inferred": false,
"started_at": "2026-06-30T02:45:58.000Z",
"state": "resolved",
"title": "Some customers received incorrect Time Tracker for Jira Cloud and DC app emails relating to free and trial subscriptions.",
"updated_at": "2026-07-02T04:43:17.946Z",
"url": "https://stspg.io/hv9nrqtfx55k"
},
{
"body": "On June 26, 2026, some customers may have experienced performance degradation with remote Forge apps facing rate-limiting issues. 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-06-26T21:39:37.248Z",
"resolved_inferred": false,
"started_at": "2026-06-26T14:32:39.810Z",
"state": "resolved",
"title": "Remote Forge Apps facing rate-limiting issues",
"updated_at": "2026-06-26T21:39:37.298Z",
"url": "https://stspg.io/42b2zjt692z6"
},
{
"body": "We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.\n\nWe apologize for any inconvenience that this issue may have caused.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-06-10T06:31:05.820Z",
"resolved_inferred": false,
"started_at": "2026-06-10T04:55:13.006Z",
"state": "resolved",
"title": "Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps",
"updated_at": "2026-06-10T06:31:05.916Z",
"url": "https://stspg.io/vj6kw99hc4f2"
},
{
"body": "Between 08:30 UTC and 13:51 UTC on 26 May 2026, some users were unable to load or edit certain macros in the Confluence Cloud page editor. Our engineering team identified and resolved the underlying issue, and macro functionality has been fully restored.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-26T13:55:52.263Z",
"resolved_inferred": false,
"started_at": "2026-05-26T10:40:00.326Z",
"state": "resolved",
"title": "Some macros failing to load in the Confluence Cloud editor",
"updated_at": "2026-05-26T13:55:52.304Z",
"url": "https://stspg.io/cnzdpbl7d10r"
},
{
"body": "The root cause has been identified and a fix has been applied.\n\nFull service restoration has been completed.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-20T14:14:35.345Z",
"resolved_inferred": false,
"started_at": "2026-05-20T12:06:23.836Z",
"state": "resolved",
"title": "Forge custom fields are not getting created",
"updated_at": "2026-05-20T14:14:35.362Z",
"url": "https://stspg.io/m392fcsn7blz"
},
{
"body": "Due to an incorrect deployment, a banner stating 'This app may stop working soon' was briefly displayed on the Marketplace Apps. This banner was not intended to appear on these apps.\n\nThe feature has since been corrected and the banner is no longer appearing. No action is required, the banner was displayed in error and there is no impact to app functionality or availability.\n\nWe apologise for any confusion this may have caused.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-20T10:16:52.997Z",
"resolved_inferred": false,
"started_at": "2026-05-20T10:16:52.944Z",
"state": "resolved",
"title": "Incorrect Banner appeared on MarketPlace Apps",
"updated_at": "2026-05-20T10:16:53.008Z",
"url": "https://stspg.io/77y4s47z9z1k"
},
{
"body": "On May 14, 2026, Developer and Marketplace service desks were inaccessible for affected users. 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-05-14T21:35:12.921Z",
"resolved_inferred": false,
"started_at": "2026-05-14T21:04:04.214Z",
"state": "resolved",
"title": "Disrupted Service Desk availability",
"updated_at": "2026-05-14T21:35:12.941Z",
"url": "https://stspg.io/fr3x919k5vgr"
},
{
"body": "All products and services impacted by this incident should now be fully recovered, and this incident is resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-05-14T06:49:28.904Z",
"resolved_inferred": false,
"started_at": "2026-05-14T05:11:20.261Z",
"state": "resolved",
"title": "Users experiencing issues accessing multiple Atlassian products",
"updated_at": "2026-05-15T00:00:56.862Z",
"url": "https://stspg.io/nyhyvczzvhq6"
},
{
"body": "On May 12, 2026, some users in US East region may have experienced intermittent failures with forge invocations for some applications. 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-05-12T17:40:43.123Z",
"resolved_inferred": false,
"started_at": "2026-05-12T15:50:29.317Z",
"state": "resolved",
"title": "Degraded performance of forge invocations",
"updated_at": "2026-05-12T17:40:43.141Z",
"url": "https://stspg.io/8ns1t49c6k4k"
},
{
"body": "On May 12, 2026, some users in EU West region may have experienced delayed or queued webhook events. 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-05-12T18:11:26.274Z",
"resolved_inferred": false,
"started_at": "2026-05-12T14:03:20.536Z",
"state": "resolved",
"title": "Delay in Jira Webhook Delivery",
"updated_at": "2026-05-12T18:11:26.293Z",
"url": "https://stspg.io/vyhrjmvzl0zt"
},
{
"body": "On May 11, 2026, users in EU West and US East regions may have experienced performance degradation with delayed or queued webhook events. 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-05-11T18:16:05.697Z",
"resolved_inferred": false,
"started_at": "2026-05-11T14:24:14.135Z",
"state": "resolved",
"title": "Delays in Jira Webhook delivery",
"updated_at": "2026-05-11T18:16:05.714Z",
"url": "https://stspg.io/215xxfzm4tkj"
},
{
"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:31.603Z",
"resolved_inferred": false,
"started_at": "2026-05-08T04:10:28.630Z",
"state": "postmortem",
"title": "Multiple Atlassian services are experiencing issues",
"updated_at": "2026-05-20T06:58:25.828Z",
"url": "https://stspg.io/pyqk9nvwdq6s"
},
{
"body": "On Tuesday, May 5, 2026, some Forge users may have experienced performance delays in webhook delivery in the US East region. 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-05-05T22:34:14.686Z",
"resolved_inferred": false,
"started_at": "2026-05-05T17:40:11.867Z",
"state": "resolved",
"title": "Degraded performance of Forge trigger",
"updated_at": "2026-05-05T22:34:14.706Z",
"url": "https://stspg.io/70kfhv36kknn"
},
{
"body": "The issue causing intermittent delays in our webhook delivery has been resolved. A fix was deployed to address a resource constraint in our systems. Our monitoring shows webhook delivery is now operating normally.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-30T14:56:57.972Z",
"resolved_inferred": false,
"started_at": "2026-04-30T08:59:04.029Z",
"state": "resolved",
"title": "Delays in Jira webhook delivery",
"updated_at": "2026-04-30T14:56:57.992Z",
"url": "https://stspg.io/30zp1pwcnpmy"
},
{
"body": "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-04-28T21:50:42.758Z",
"resolved_inferred": false,
"started_at": "2026-04-28T18:28:20.767Z",
"state": "resolved",
"title": "Degraded performance of Forge trigger",
"updated_at": "2026-04-28T21:50:42.777Z",
"url": "https://stspg.io/lz45708vc6ht"
},
{
"body": "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-04-23T16:14:43.771Z",
"resolved_inferred": false,
"started_at": "2026-04-22T06:57:00.565Z",
"state": "resolved",
"title": "Some Forge apps experiencing increased Jira API rate limiting errors (429)",
"updated_at": "2026-04-23T16:14:43.790Z",
"url": "https://stspg.io/q9l67zf8v98g"
},
{
"body": "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-04-13T15:11:45.243Z",
"resolved_inferred": false,
"started_at": "2026-04-13T10:58:02.547Z",
"state": "resolved",
"title": "Missing Marketplace transaction data in partner reports since April, 10 2026",
"updated_at": "2026-04-13T15:11:45.264Z",
"url": "https://stspg.io/qltjjtmhskdp"
},
{
"body": "The outage affecting Forge app logs between 05:00 UTC and 07:00 UTC on 8 April 2026 has been resolved, and systems are now stable.\n\nWe are currently working on recovery efforts, including retrieving logs from this downtime window and validating data completeness. During this process, you may temporarily see duplicate log entries; however, this will not result in duplicate usage or additional costs.\n\nWe will continue to monitor the system closely and provide further updates as needed.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-04-08T07:45:13.000Z",
"resolved_inferred": false,
"started_at": "2026-04-08T06:55:07.248Z",
"state": "resolved",
"title": "Read/Write logs for Forge Apps down",
"updated_at": "2026-04-08T08:44:54.171Z",
"url": "https://stspg.io/vhfsk5dn55p5"
},
{
"body": "On April 2, 2026, affected users may have experienced some service disruption. 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-04-02T22:36:41.280Z",
"resolved_inferred": false,
"started_at": "2026-04-02T20:46:43.730Z",
"state": "resolved",
"title": "Disrupted Forge availability",
"updated_at": "2026-04-02T22:36:41.301Z",
"url": "https://stspg.io/ybm4lpz1r4dv"
},
{
"body": "On March 24, 2026, between 04:14 AM UTC and 08:40 AM UTC, Connect Apps using connect API's experienced performance degradation. 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-24T08:44:23.346Z",
"resolved_inferred": false,
"started_at": "2026-03-24T07:59:20.308Z",
"state": "resolved",
"title": "Connect Apps Performance Degradation",
"updated_at": "2026-03-24T08:44:23.371Z",
"url": "https://stspg.io/z00jqjyn5qjh"
},
{
"body": "On March 17th, 2026, between 9:05 AM UTC and 11:10 AM UTC,  Forge app management and related developer tooling experienced some service disruption. The issue has now been resolved, and the service is operating normally for affected customers.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-17T11:37:37.061Z",
"resolved_inferred": false,
"started_at": "2026-03-17T10:05:28.000Z",
"state": "resolved",
"title": "Incident impacting Forge app installations and Dev console",
"updated_at": "2026-03-17T11:37:37.079Z",
"url": "https://stspg.io/bcjndp22tv8g"
},
{
"body": "On March 12, 2026, affected Confluence Cloud users may have experienced some service disruption. 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-13T00:26:04.153Z",
"resolved_inferred": false,
"started_at": "2026-03-12T11:42:38.845Z",
"state": "resolved",
"title": "Static macro rendering is failing in Confluence Cloud",
"updated_at": "2026-03-13T00:26:04.173Z",
"url": "https://stspg.io/v2b9k8yymtjt"
},
{
"body": "We are providing a further update regarding the install count discrepancy that some partners may have observed for some apps since Feb 27, 2026.\n\n- The Active Installations tab in the Marketplace Partner Portal is now showing accurate install counts for impacted apps from Mar 3, 2026 onward.\n- The install counts displayed on app listings remain accurate for impacted apps.\n- Please note that data from Mar 3, 2026 onward will remain accurate going forward.\n- You may notice a temporary dip in install counts for Mar 2, 2026. We are backfilling the data, and counts for that date will be restored once complete.\n- Actual customer installs were not impacted; only the reported counts displayed in the Partner Portal and on app listings were affected for some apps, and this is now fully functional.\n\nThank you for your patience and understanding.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-03-04T03:04:15.737Z",
"resolved_inferred": false,
"started_at": "2026-03-02T16:15:12.562Z",
"state": "resolved",
"title": "Inaccurate install counts for some Marketplace apps on Marketplace",
"updated_at": "2026-03-04T03:04:15.753Z",
"url": "https://stspg.io/l5g7rrvxb1rx"
},
{
"body": "We have now reactivated all subscriptions that were previously cancelled. Impacted users may have received email notifications confirming this change. There has been no impact to the functioning of the app, it should continue to work as expected.\nTo help prevent any future interruptions, we kindly request that billing admins ensure a valid billing payment method is added before the next billing cycle.\nWe apologise for any confusion and appreciate your understanding.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-19T17:12:31.473Z",
"resolved_inferred": false,
"started_at": "2026-02-16T11:24:02.892Z",
"state": "resolved",
"title": "Forge billing subscriptions cancelled for some apps",
"updated_at": "2026-02-19T17:12:31.491Z",
"url": "https://stspg.io/0xtcwl805sph"
},
{
"body": "This issue is resolved. In our monitoring no other unexpected issues were seen.\n\nFor customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-19T08:04:57.460Z",
"resolved_inferred": false,
"started_at": "2026-02-13T07:41:39.717Z",
"state": "resolved",
"title": "Increased error rates on Jira and Jira Service Management Ecosystem Apps",
"updated_at": "2026-02-19T08:04:57.491Z",
"url": "https://stspg.io/4vmdg9xzj5f6"
},
{
"body": "Impact\n\nWe are currently experiencing an issue affecting the Forge platform, specifically related to scheduled triggers. Users may encounter instances where these triggers are not executing as anticipated, disrupting the normal operation of their Forge apps. This behavior began approximately at 2 AM UTC.\n\nCurrent Status\n\nOur engineering team identified the root cause and performed a rollback deployment to resolve the issue.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-06T11:32:35.358Z",
"resolved_inferred": false,
"started_at": "2026-02-06T09:37:35.831Z",
"state": "resolved",
"title": "Scheduled Triggers not working for Forge apps",
"updated_at": "2026-02-06T11:32:35.377Z",
"url": "https://stspg.io/19gs46myvlrv"
},
{
"body": "Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2026-02-03T10:50:35.750Z",
"resolved_inferred": false,
"started_at": "2026-02-03T10:19:54.355Z",
"state": "resolved",
"title": "Confluence, Jira Mobile and Forge users may experience authentication issues",
"updated_at": "2026-02-03T10:50:35.771Z",
"url": "https://stspg.io/srbplv26kl2g"
},
{
"body": "On January 28, 2026, some customers may have experienced Forge function invocation availability disruption. 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-01-28T19:20:20.274Z",
"resolved_inferred": false,
"started_at": "2026-01-28T17:34:56.308Z",
"state": "resolved",
"title": "Disrupted Forge Function Invocation availability",
"updated_at": "2026-01-28T19:20:20.293Z",
"url": "https://stspg.io/cjc2bry7h1sf"
},
{
"body": "The issue is completely resolved and Developer Console is now displaying all the usage metrics correctly. We apologize for any inconvenience this may have caused.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-17T06:07:27.782Z",
"resolved_inferred": false,
"started_at": "2025-12-16T05:47:29.672Z",
"state": "resolved",
"title": "Forge usage and charges data is missing from the developer console",
"updated_at": "2025-12-17T06:07:27.799Z",
"url": "https://stspg.io/1xkrw65mwfj4"
},
{
"body": "The rollback required to resolve this issue is now completed, and we have verified across the impacted products that App installation behaviour is now working as expected. We apologize for any inconvenience this may have caused.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-11T04:37:14.124Z",
"resolved_inferred": false,
"started_at": "2025-12-11T01:08:44.953Z",
"state": "resolved",
"title": "Errors installing Connect on Forge Apps in Confluence",
"updated_at": "2025-12-11T04:37:14.144Z",
"url": "https://stspg.io/zvnmzkd9vldn"
},
{
"body": "Between Dec 8 05:30 UTC and Dec 9 05:30 UTC, new Forge app versions were not auto-published to Atlassian Marketplace. We\u2019ve implemented a mitigation and auto-publish is operating normally.\n\nAction required: If you deployed during this window, please manually publish those versions in Marketplace (or re-deploy your app with forge deploy). \n\nWe\u2019re sorry for the inconvenience.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-09T08:14:04.000Z",
"resolved_inferred": false,
"started_at": "2025-12-09T08:14:04.000Z",
"state": "resolved",
"title": "Auto publish failure for Marketplace forge app versions",
"updated_at": "2025-12-09T08:46:59.208Z",
"url": "https://stspg.io/8pwvxnjwt37s"
},
{
"body": "The feature flag causing the issue has been reverted, fixing the problem. With that this incident is resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-12-05T12:09:05.554Z",
"resolved_inferred": false,
"started_at": "2025-12-05T08:08:53.836Z",
"state": "resolved",
"title": "Multiple customer sites have lost access to Support tickets",
"updated_at": "2025-12-05T12:09:05.575Z",
"url": "https://stspg.io/xsv42v5c5wwh"
},
{
"body": "Impact\n\nCustomers experienced degraded performance in log ingestion services affecting the Ecosystem, particularly the Forge platform. Due to this issue, accessing logs ingested from the morning of the incident (starting 06:00 UTC) was impacted, leading to delays or incomplete data visibility through the Dev Console and related channels.\n\nCurrent Status\n\nThis incident has been resolved, and Forge Logs are back in operational mode.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-11-10T14:03:18.231Z",
"resolved_inferred": false,
"started_at": "2025-11-10T10:41:39.876Z",
"state": "resolved",
"title": "Degradation in forge logs availability",
"updated_at": "2025-11-10T14:03:18.254Z",
"url": "https://stspg.io/784l8c8gpvd9"
},
{
"body": "Validation is complete. All tables backing Aggregated Sales Reporting, Transaction Reporting, and Export Transaction APIs have been fully repopulated. Data for the impacted window (25 Oct 2025 00:00 IST \u2013 27 Oct 2025 14:00 IST) has been restored and verified. No action is required from vendors. We are closing this incident.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-28T13:42:21.577Z",
"resolved_inferred": false,
"started_at": "2025-10-27T12:04:05.344Z",
"state": "resolved",
"title": "Marketplace | Aggregated Sales, Transaction Reporting, and Export Transaction APIs experiencing Data Discrepancies",
"updated_at": "2025-10-28T13:42:21.593Z",
"url": "https://stspg.io/6m477p3pp1xt"
},
{
"body": "### Summary\n\nOn October 22, 2025, Confluence Cloud webhook events were not delivered to Connect apps and Forge apps that use webhooks via `connectModules`. This outage began after a backend deployment introduced a code change that prevented Confluence from recognizing registered webhook listeners. As a result, no webhook events were generated for approximately 20 hours, impacting apps that depend on webhooks. The issue was resolved by rolling back to a previous stable deployment. We\u2019re taking steps to improve detection and rollback processes.\n\n### **IMPACT**\n\nBetween 01:12 UTC and 21:46 UTC on October 22, 2025, Confluence was unable to send out webhook events. As a result, none of the apps that rely on these events received them during this time. This includes Connect apps and Forge apps that use webhooks through `connectModules`.\n\nCustomers may have noticed outdated content appearing in their Marketplace apps, or new content not syncing.\n\n### **ROOT CAUSE**\n\nThe issue was caused by a change to Confluence backend systems. As a result, no webhook events were delivered to Connect and Forge apps that use webhooks via `connectModules`. This occurred because a Java class was loaded by 2 different classloaders, causing Confluence to fail to find registered webhook listeners and thus not emit events.\n\n### **REMEDIAL ACTIONS PLAN & NEXT STEPS**\n\nWebhooks are a critical functionality for many apps. On this occasion, our system did not generate any errors because it was inadvertently using an incorrect version of a Java class, which was loaded by a different ClassLoader. As a result, the issue occurred silently and couldn\u2019t be detected via existing automated error monitoring.\n\n\u00a0\n\nWe are prioritizing the following improvement actions to help prevent this issue from reoccurring:\n\n* Additional integration tests to identify problems before merging code to our main branch.\n* Additional detectors and alerts to identify when webhook event volume drops below a certain threshold.\n* Exploring resync / lost event recovery mechanism without overloading Atlassian infrastructure\n\n    * We acknowledge that the availability of Connect apps is important for our customers and ecosystem partners, and we will endeavour to provide support for these apps in line with our public roadmap for Connect end of life. You can read our announcement here: [Announcing Connect End of Support: Timeline and Next Steps - Work Life by Atlassian](https://www.atlassian.com/blog/developer/announcing-connect-end-of-support-timeline-and-next-steps)\n    \n        While this incident primarily impacted Connect, we would like to note that Forge currently includes additional internal capabilities, such as retry [Atlassian app events](https://developer.atlassian.com/platform/forge/events-reference/product_events/#retry-atlassian-app-events) and internal DLQ, that could assist with recovery in these types of incidents..\n\n    \n    \n        We highly encourage partners to migrate to Forge to utilize the latest webhook infrastructure.\n\n    \n    \n\nWe apologize to customers and ecosystem partners 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": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-22T22:09:20.000Z",
"resolved_inferred": false,
"started_at": "2025-10-22T12:15:57.948Z",
"state": "postmortem",
"title": "Confluence Webhooks are not being delivered",
"updated_at": "2025-11-08T04:25:35.915Z",
"url": "https://stspg.io/03swc83gc942"
},
{
"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": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-21T05:24:25.603Z",
"resolved_inferred": false,
"started_at": "2025-10-20T07:56:11.430Z",
"state": "postmortem",
"title": "Atlassian Cloud Services impacted",
"updated_at": "2025-11-25T03:53:25.855Z",
"url": "https://stspg.io/32pq1zx6k01x"
},
{
"body": "Between 06:58 12 Oct UTC to 18:30 12 Oct UTC, we experienced calls from a some forge apps to external services (outside of Atlassian) intermittently fail. The issue has been resolved and the service is operating normally.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-12T19:25:16.839Z",
"resolved_inferred": false,
"started_at": "2025-10-12T15:25:53.472Z",
"state": "resolved",
"title": "Forge authenticated egress intermittent failure",
"updated_at": "2025-10-12T19:25:16.859Z",
"url": "https://stspg.io/f7hs2srk82vd"
},
{
"body": "Between 06:30 12th Oct, 2025 UTC to 08:33 12th Oct, 2025 UTC, we experienced a degradation in us-east and ca-central regions affecting authenticated egress calls from Forge functions and from Forge bridge. \n\nThe issue has been resolved and the service is operating normally.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-12T09:14:40.272Z",
"resolved_inferred": false,
"started_at": "2025-10-12T07:29:47.822Z",
"state": "resolved",
"title": "Forge authenticated egress intermittent failure",
"updated_at": "2025-10-12T09:14:40.290Z",
"url": "https://stspg.io/2d9z8839rpqr"
},
{
"body": "Between 29 Sep 2025 07:10 UTC and 03 Oct 2025 06:00 UTC, some customers experienced unexpected Allow access OAuth consent prompts when using the Forge app UI. The issue has been resolved, and the service is operating normally.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-10-03T06:24:19.291Z",
"resolved_inferred": false,
"started_at": "2025-10-03T03:43:27.000Z",
"state": "resolved",
"title": "Forge app user OAuth consent prompt being shown unnecessarily",
"updated_at": "2025-10-03T06:24:19.310Z",
"url": "https://stspg.io/c50gjjpdsmgg"
},
{
"body": "Between 08:30 AM UTC to 16:30 UTC on September 29, 2025, some developers experienced delays of log delivery for the Dev Console. The root cause was an unexpected spike in volume that required updates to autoscaling configurations to address. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we\u2019re actively working on a permanent fix. The issue has been resolved and the service is processing logs normally. We are currently processing the delayed logs and anticipate completion by 17:00 UTC today, September 29, 2025.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "minor",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-29T17:07:09.374Z",
"resolved_inferred": false,
"started_at": "2025-09-29T15:32:40.124Z",
"state": "resolved",
"title": "Delays in Dev Console log delivery",
"updated_at": "2025-09-29T17:07:09.389Z",
"url": "https://stspg.io/fs9jjp0ygj89"
},
{
"body": "Issues affecting Marketplace Reporting APIs and Partner Portal have been resolved. Both services are now back up and running normally. This incident has been resolved.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "critical",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-26T10:45:55.450Z",
"resolved_inferred": false,
"started_at": "2025-09-26T10:09:49.455Z",
"state": "resolved",
"title": "Marketplace Reporting APIs and Partner Portal Disruption",
"updated_at": "2025-09-26T10:45:55.465Z",
"url": "https://stspg.io/v923bfl6qfc5"
},
{
"body": "We experienced a disruption affecting all JSM assets APIs using Connect JWT and user impersonation for connect apps, starting on September 13th at 2:05 AM UTC and lasting until September 17th at 3:36 PM UTC. This issue was caused by an internal routing change within Atlassian systems. During this time, all Assets API calls using Connect authentications were disrupted. The issue has now been resolved, and all affected APIs are fully operational again. We sincerely apologise for any inconvenience caused and thank you for your patience and understanding.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "none",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-25T08:14:11.708Z",
"resolved_inferred": false,
"started_at": "2025-09-25T08:14:11.610Z",
"state": "resolved",
"title": "JSM Assets API using connect authentications were disrupted",
"updated_at": "2025-09-25T08:14:11.718Z",
"url": "https://stspg.io/ghbst3pxbzxd"
},
{
"body": "No customer impact has been observed seen since mitigation began. We are now closing this incident.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-19T02:02:51.884Z",
"resolved_inferred": false,
"started_at": "2025-09-15T02:06:05.594Z",
"state": "resolved",
"title": "Intermittent failure on all app networking calls (including product apis, egress, storage and resolvers)",
"updated_at": "2025-09-19T02:02:51.902Z",
"url": "https://stspg.io/z0sh0g89vyjr"
},
{
"body": "Changes have landed in production at 11:40 AM (UTC). The issue is resolved and the endpoint is now operating normally.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-12T11:56:02.700Z",
"resolved_inferred": false,
"started_at": "2025-09-12T08:14:51.720Z",
"state": "resolved",
"title": "Intermittent 500 errors on Confluence endpoint /wiki/api/v2/spaces/properties",
"updated_at": "2025-09-12T11:56:02.719Z",
"url": "https://stspg.io/kd026td3bjbq"
},
{
"body": "Between 12:50 UTC to 13:20 UTC, we experienced partial failures for deploying forge apps via forge cli for Atlassian Developers. \nThe issue has been resolved and the service is operating normally.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-08T13:46:29.610Z",
"resolved_inferred": false,
"started_at": "2025-09-08T13:35:23.947Z",
"state": "resolved",
"title": "Deploying a forge app using the forge CLI",
"updated_at": "2025-09-08T13:46:29.629Z",
"url": "https://stspg.io/7rrmkzmqhmtr"
},
{
"body": "This incident is resolved now.  Between 6:30 AM and 8:35 AM UTC on September 8th, there was an issue with one of the dependent vendor services, due to which invocations were intermittently failing, primarily in the EU-CENTRAL-1 Region.  This issue is fixed now.",
"first_seen": "2026-09-04T07:06:16Z",
"impact": "major",
"last_seen": "2026-09-16T12:28:20Z",
"resolved_at": "2025-09-08T10:05:53.000Z",
"resolved_inferred": false,
"started_at": "2025-09-08T07:44:14.089Z",
"state": "resolved",
"title": "Forge App Invocations failing intermittently",
"updated_at": "2025-09-09T01:34:01.133Z",
"url": "https://stspg.io/bfwspwd18kzm"
}
]
}