Atlassian Developer 中断历史

1. 2026年9月2日 UTC 03:09investigating

   我们正在调查关于Forge开发商安装请求的报告, 与“ 安装请求失败” 消息断断续续失效 。 我们将在今后1小时内或更早地分享更多信息.

2. 2026年9月2日 UTC 03:17resolved

   我们查明了影响安装要求的问题的原因,并安装了固定装置。 这个问题现已解决,这项服务正在向所有受影响的客户正常运营.

自动翻译自官方事件更新。

1. 2026年8月25日 UTC 10:58monitoring

   已经成功地为影响某些 " 市场 " 应用程序的预定触发器的问题(间隔5分钟)安装了一个固定装置。 我们继续监测局势并应尽快完全恢复。 我们应当在一个小时内提供更多的最新情况.

2. 2026年8月25日 UTC 11:11resolved

   2026年8月25日,从协调世界时08:12到协调世界时11:03之间,一些"市场"(Marketplace)的应用软件可能经历了预定的触发(5分钟间隔)而未如所预期地开火. 这个问题现已得到解决,5分钟的预定触发器对所有客户正常运行.

自动翻译自官方事件更新。

1. 2026年8月3日 UTC 03:26investigating

   我们的团队意识到,在协调世界时2026-08-03 01:47和协调世界时02:29之间,一个影响安装,卸载或管理福热和OAuth 2.0集成应用的能力的问题. 已经安装的App应该在这个撞击窗口内继续正常运行. 我们认为,我们已经纠正了这一问题,并且正在监测目前的影响。 我们对此可能造成的不便表示歉意.

2. 2026年8月3日 UTC 03:37resolved

   我们确认,安装、取消和管理Forge和OAuth 2.0应用软件的问题现在应该完全解决.

自动翻译自官方事件更新。

1. 2026年7月13日 UTC 15:48investigating

   未提供采购网伙伴网页。 合作伙伴无法访问仪表板和管理界面,在试图加载这些页面时出现超时. 所有与合作伙伴有关的功能都受到影响。 正在调查其根本原因。 下一份通讯将在60分钟后或重大进展后发送.

2. 2026年7月13日 UTC 17:17monitoring

   这一问题已经解决,目前所有受影响客户的服务都正常运行。 我们将继续密切监测,以确认稳定.

3. 2026年7月13日 UTC 17:46resolved

   2026年7月13日,合作伙伴业务可能经历了一些服务中断. 这个问题现已解决,这项服务对所有受影响的客户正常运行.

自动翻译自官方事件更新。

1. 2026年6月30日 UTC 02:45investigating

   我们知道,一些使用"时间追踪器"(Time Tracker)的Jira Cloud和DC应用程序的客户被错误地通知了该应用程序转换为免费或试用订阅. 我们的小组正在紧急调查这一问题,我们正在采取步骤,确保受影响的客户了解情况。 没有要求不正确收到这些电子邮件的客户采取行动。 我们对此可能造成的不便表示歉意.

2. 2026年7月2日 UTC 04:43resolved

   所有先前收到关于Jira Cloud和DCapp时间追踪器错误通知的客户,此时都应该收到更正的函件. 我们现在正在解决这一问题.

自动翻译自官方事件更新。

1. 2026年6月26日 UTC 14:32identified

   我们找出了服务业绩问题的根源 影响了你的远程应用服务 我们的小组已开始进行补救,并正在积极监测恢复情况。 我们将在下一个小时内提供下一次最新情况.

2. 2026年6月26日 UTC 15:28identified

   我们的团队已经采取了缓解措施,我们正在看到复苏。 我们将继续在获得更多信息后,在此分享其他最新情况.

3. 2026年6月26日 UTC 19:43identified

   我们的小组继续监测正在恢复的情况,我们将在获得更多信息后在此分享其他最新情况.

4. 2026年6月26日 UTC 21:24monitoring

   这一问题已经解决,目前所有受影响客户的服务都正常运行。 我们将继续密切监测,以确认稳定.

5. 2026年6月26日 UTC 21:39resolved

   2026年6月26日,一些客户可能因远程Forge应用面临限速问题而出现性能退化. 这个问题现已解决,这项服务对所有受影响的客户正常运行.

自动翻译自官方事件更新。

1. 2026年6月10日 UTC 04:55investigating

   We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

2. 2026年6月10日 UTC 05:39identified

   Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

3. 2026年6月10日 UTC 06:14monitoring

   Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

4. 2026年6月10日 UTC 06:31resolved

   We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

1. 2026年5月26日 UTC 11:58investigating

   We are investigating an issue where some custom extensions may fail to load when editing Confluence Cloud pages. Affected users may see 'Error loading the extension!' messages or notice that certain macros are missing from the editor's extension selection menu. Viewing published pages is not affected. Our engineering team is actively investigating and working toward a resolution. We will provide an update within an hour or as more information becomes available.

2. 2026年5月26日 UTC 11:58investigating

   We are actively investigating an issue affecting the editing macros in Confluence Cloud editor. Our team is working to identify the root cause. We will provide an update within approximately one hour.

3. 2026年5月26日 UTC 13:55resolved

   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.

1. 2026年5月20日 UTC 12:06identified

   Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 3 hours, or sooner if we have any meaningful developments to report. The impact is limited to new deployments with Forge custom fields on Jira work items, however existing deployments with custom fields are running without any issues.

2. 2026年5月20日 UTC 14:14resolved

   The root cause has been identified and a fix has been applied. Full service restoration has been completed.

1. 2026年5月20日 UTC 10:16resolved

   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. The 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. We apologise for any confusion this may have caused.

1. 2026年5月14日 UTC 21:04identified

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inaccessibility for Developer and Marketplace service desks. We will continue to share additional updates here as more information is available.

2. 2026年5月14日 UTC 21:20monitoring

   The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

3. 2026年5月14日 UTC 21:35resolved

   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.

1. 2026年5月14日 UTC 05:11identified

   Further confirmations of impacted products have now been added to the incident. Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

2. 2026年5月14日 UTC 05:24identified

   It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information. We will provide further update within one hour, or sooner as further information becomes available.

3. 2026年5月14日 UTC 05:34identified

   Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products. At this time, Atlassian customers should also be able to once again raise support requests with our team. We will provide further update within an hour as we are able to progress mitigating this issue.

4. 2026年5月14日 UTC 05:43monitoring

   Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

5. 2026年5月14日 UTC 06:40monitoring

   We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

6. 2026年5月14日 UTC 06:41monitoring

   We are approaching full system recovery at this time, and are performing final confirmations that services are restored.

7. 2026年5月14日 UTC 06:49resolved

   All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

1. 2026年5月12日 UTC 15:50identified

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience intermittent failures with forge invocations for some applications. We will continue to share additional updates here as more information is available.

2. 2026年5月12日 UTC 16:57identified

   We are seeing improvements in intermittent failures with forge invocations for some applications. Our team continues to work diligently on full mitigation, and we will continue to share additional updates as more information becomes available.

3. 2026年5月12日 UTC 17:17monitoring

   Intermittent failures with forge invocations for some applications have been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

4. 2026年5月12日 UTC 17:40resolved

   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.

1. 2026年5月12日 UTC 14:03investigating

   We are aware of delays in Webhook event delivery that may be impacting Marketplace app integrations, primarily in the EU-West region. Some partners may experience delayed or queued Webhook Events. Our teams are investigating the root cause, and we will provide further updates within the next 1 hour.

2. 2026年5月12日 UTC 15:00investigating

   Our teams are still investigating the root cause, and we will provide further updates within the next 2 hours.

3. 2026年5月12日 UTC 16:27identified

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience delayed or queued webhook events. We will continue to share additional updates here as more information is available.

4. 2026年5月12日 UTC 17:52monitoring

   Delayed or queued webhook events issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

5. 2026年5月12日 UTC 18:11resolved

   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.

1. 2026年5月11日 UTC 14:24identified

   We are aware of delays in webhook event delivery that may be impacting Marketplace app integrations, primarily in the EU west region. Some partners may experience delayed or queued webhook events. Our team has identified the root cause and has taken action to mitigate the issue. We will continue to monitor and provide updates as the situation progresses.

2. 2026年5月11日 UTC 14:48identified

   Webhook event delivery in the EU West region has recovered and is operating normally. However, we are now seeing reports of similar delays in the US East region. Our team is actively investigating and working to resolve this. We will continue to monitor and provide further updates.

3. 2026年5月11日 UTC 15:45identified

   Our team has applied mitigation and is seeing improvement in US East region. Next update will be provided in one hour.

4. 2026年5月11日 UTC 16:42identified

   Our team continues to see improvements in US East region with delayed or queued webhook events declining. Next update will be provided in 90 minutes.

5. 2026年5月11日 UTC 18:00monitoring

   The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability.

6. 2026年5月11日 UTC 18:16resolved

   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.

1. 2026年5月8日 UTC 04:10investigating

   We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

2. 2026年5月8日 UTC 04:10identified

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

3. 2026年5月8日 UTC 04:10identified

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

4. 2026年5月8日 UTC 04:10identified

   We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

5. 2026年5月8日 UTC 05:53monitoring

   The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

6. 2026年5月8日 UTC 08:03monitoring

   We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

7. 2026年5月8日 UTC 11:12monitoring

   Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We apologise for the disruption and thank you for your patience.

8. 2026年5月8日 UTC 19:45resolved

   On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

9. 2026年5月20日 UTC 06:58postmortem

   All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution. The incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15. ### **IMPACT** The primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Atlassian services and underpins background operations such as automation execution, search indexing, notifications, permission synchronisation. * Between 00:22 and 06:08, an infrastructure incident in our hosting provider triggered an ingestion failure in our event processing pipeline. * At 02:50, event ingestion was failed over to an unaffected availability zone, progressively restoring live event flows. * 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. * By 18:48, Automation had processed their backlog of events that were created while processing **Automation** Between 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. At 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. Beginning 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. **Jira and Jira Service Management** Between 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. Jira 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. At 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. **Confluence** Between 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. The 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. Between 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. **Bitbucket and Pipelines** Between 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. Automatic 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. At 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. **Identity Services** Between 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. The 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. After 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. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We 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. We are prioritizing improvements that will: * **Enhance failover coverage** so critical event processing can recover more smoothly during infrastructure disruptions. * **Strengthen recovery handling** so replayed events can be processed more quickly. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support.

1. 2026年5月5日 UTC 17:40investigating

   We are actively investigating reports of performance degradation affecting Forge webhook delivery in the US East region. We will share updates here as more information is available.

2. 2026年5月5日 UTC 18:58identified

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. We are seeing signs of improvement. Affected users may experience some delays in web hook delivery in the US East region. We'll continue to share additional updates here as more information is available.

3. 2026年5月5日 UTC 20:37identified

   Our teams have identified the cause of the issue and are continuing to work on mitigations. We continue to see signs of improvement. Affected users may experience some delays in web hook delivery in the US East region. We'll continue to share additional updates here as more information is available.

4. 2026年5月5日 UTC 22:34resolved

   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.

1. 2026年4月30日 UTC 08:59investigating

   We are investigating reports of delays in webhook delivery. Customers may experience intermittent delays when receiving webhooks. Our engineering teams are actively investigating and working to resolve the issue. We will provide updates as more information becomes available.

2. 2026年4月30日 UTC 10:05identified

   We have identified the cause of the delayed Jira webhook delivery and are deploying a fix. We will continue to provide updates as more information becomes available.

3. 2026年4月30日 UTC 13:36monitoring

   A fix has been deployed to address the intermittent delays in Jira webhook delivery. We are actively monitoring the situation to confirm full recovery. We will continue to provide updates as available.

4. 2026年4月30日 UTC 14:56resolved

   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.

1. 2026年4月28日 UTC 18:28investigating

   We are actively investigating reports of performance degradation affecting Forge webhook delivery in prod-euwest region. We will share updates here as more information is available.

2. 2026年4月28日 UTC 18:34investigating

   We are actively investigating reports of performance degradation affecting Forge triggers in prod-euwest region. We will share updates here as more information is available.

3. 2026年4月28日 UTC 20:16identified

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users in prod-euwest region may experience performance degradation affecting Forge triggers. We will continue to share additional updates here as more information is available.

4. 2026年4月28日 UTC 21:34monitoring

   The performance degradation of Forge triggers has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

5. 2026年4月28日 UTC 21:50resolved

   The issue has now been resolved, and the service is operating normally for all affected customers.

1. 2026年4月22日 UTC 06:57investigating

   We are aware that some Forge apps are experiencing an increased number of 429 Too Many Requests errors when making calls to the Jira REST API. This is causing disruption for end users of affected apps. Confluence APIs are not impacted. If your app is impacted by this issue, the 429 response will contain the following headers: X-Failure-Category: FAILURE CLIENT RATE LIMITED X-Ratelimit-Limit: 360000 X-Ratelimit-Remaining: 0 Note that this gateway-level rate limiting does not return a Retry-After header. You can use the X-Ratelimit-Reset header to determine when the rate limit window resets and implement a backoff strategy accordingly. Our teams are investigating this issue with urgency, and we will provide an update within two hours.

2. 2026年4月22日 UTC 08:53identified

   Our teams have implemented initial remediation by increasing certain rate limits, and we will continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if we have any meaningful developments to report.

3. 2026年4月22日 UTC 16:21identified

   After the initial remediation, we are seeing improvements and our teams continue to monitor the situation closely to confirm stability. We will share further updates within the next 8 hours, or sooner if there are any major developments.

4. 2026年4月22日 UTC 23:29identified

   We continue to see improvements in error rates, and our teams are evaluating further mitigation to expedite resolution.

5. 2026年4月23日 UTC 15:27monitoring

   The performance degradation has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

6. 2026年4月23日 UTC 16:14resolved

   The issue has now been resolved, and the service is operating normally for all affected customers.