Is Confluence Down Right Now? Check if there is a current outage ongoing.

We are investigating an issue impacting a subset of market place apps for some Confluence, Jira Service Management, and Jira, and Atlassian Developer Cloud customers in the Singapore region. We will provide more details within the next hour.

We are investigating an issue affecting the search functionality in Confluence for some users in Europe. Our team is working diligently to resolve the degradation and restore services promptly. We will keep you updated with further information.

We were experiencing cases of degraded performance for outgoing emails from Confluence, Jira Work Management, Jira Service Management, Jira, Opsgenie, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass, and Loom Cloud customers. The system is recovering and mail is being processed normally as of 16:45 UTC. We will continue to monitor system performance and will provide more details within the next hour.

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

The issues causing access problems to Administration have been resolved, and services are now functioning normally for all affected customers. We will monitor it closely for the next 30 minutes to ensure stability.

We are aware of an issue where users are receiving a 403 error when attempting to reach Administration. Our team is looking into this issue with urgency and will provide an update as soon as possible.

We are aware of an issue where users are receiving a 403 error when attempting to reach Administration. Our team is looking into this issue with urgency and will provide an update as soon as possible.

Monitoring has indicated that users are no longer receiving the error messages caused by this issue and it should now be fully resolved.

A fix for the issue causing authentication errors across multiple apps has been rolled out. We will provide further update when can confirm the issue has been fully resolved.

We are aware of issues relating to authentication resulting in 503 gateway error messages. Our team is investigating with urgency and will provide an update when available.

We are aware of issues relating to authentication resulting in 503 gateway error messages. Our team is investigating with urgency and will provide an update when available.

### Summary On Apr 15, 2025, between 14:29 and 14:55 UTC, some Atlassian customers in the EU central region using Confluence Cloud products encountered errors when viewing pages. The event was triggered by a temporarily spiked error on Confluence backend services due to a capacity issue. Our alerts detected the incident within 1 minute and the impact was mitigated by scaling up the backend service that was under load. This restored the Atlassian services to a fully operational state. The total time to resolution was approximately 26 minutes. ### **IMPACT** The impact was on Apr 15, 2025, between 14:29 and 14:55 UTC, to customers using Confluence Cloud. The incident caused service disruption to some EU central region customers, resulting in reduced functionality and limited access when loading Confluence pages, space overviews, and the home page. ### **ROOT CAUSE** The incident's root cause stemmed from one of Confluence's non-critical backend services not being fully scaled to accommodate an unusual spike in traffic. Although failures from this backend service shouldn't affect page views critically, it was treated as a severe failure, impacting the Confluence core experience in this incident. ### **REMEDIAL ACTION PLAN & NEXT STEPS** We fully understand that outages impact your productivity. We continuously evaluate and validate the capacity of our backend services that are critical to the Confluence user experience. However, the impact of this non-critical backend service on the Confluence page view functionality was not identified beforehand. We are prioritizing the following improvement actions designed to avoid repeating this type of incident: * Reviewing the peak capacity allocated for critical backend services and ensuring that adequate capacity is reserved to encounter traffic spikes. * Introducing fallback mechanisms for failures from non-critical backend services to improve Confluence service resiliency. We apologize to customers whose services were impacted by this incident. We are taking steps designed to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Between 14:29 UTC to 14:55 UTC, some users may have experienced page load errors for Confluence. The issue has been resolved and the service is operating normally. Once we complete our internal incident review process, we will publish a more detailed postmortem of what went wrong, along with steps we're taking designed to prevent this from happening again in the future.

Between 14:29 UTC to 14:55 UTC, some users may have experienced page load errors for Confluence. The issue has been resolved and the service is operating normally. Once we complete our internal incident review process, we will publish a more detailed postmortem of what went wrong, along with steps we're taking designed to prevent this from happening again in the future.

### Summary On Apr 14, 2025, between 18:40 and 19:00 UTC, some Atlassian customers in the US East region using Confluence Cloud products encountered errors when viewing pages. The event was triggered by a temporarily spiked error on Confluence backend services due to a capacity issue. Our alerts detected the incident within 11 minutes and the impact was mitigated by scaling up the backend service that was under load. This restored the Atlassian services to a fully operational state. The total time to resolution was approximately 20 minutes. ### **IMPACT** The impact occurred on Apr 14, 2025, between 18:40 and 19:00 UTC, to customers using Confluence Cloud. The incident caused service disruption to some US East region customers, resulting in reduced functionality and limited access when loading Confluence pages, space overviews, and the home page. ### **ROOT CAUSE** The incident's root cause stemmed from one of Confluence's non-critical backend services not being fully scaled to accommodate an unusual spike in traffic. Although failures from this backend service shouldn't affect page views critically, it was treated as a severe failure, impacting the Confluence core experience in this incident. ### **REMEDIAL ACTION PLAN & NEXT STEPS** We fully understand that outages impact your productivity. We continuously evaluate and validate the capacity of our backend services that are critical to the Confluence user experience. However, the impact of this non-critical backend service on the Confluence page view functionality was not identified beforehand. We are prioritizing the following improvement actions designed to avoid repeating this type of incident: * Reviewing the peak capacity allocated for critical backend services and ensuring that adequate capacity is reserved to encounter traffic spikes. * Introducing fallback mechanisms for failures from non-critical backend services to improve Confluence service resiliency. We apologize to customers whose services were impacted by this incident. We are taking steps designed to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Between 18:40 UTC to 19:00 UTC, some users may have experienced page load errors for Confluence. The issue has been resolved and the service is operating normally. Once we complete our internal incident review process, we will publish a more detailed postmortem of what went wrong, along with steps we're taking designed to prevent this from happening again in the future.

Between 2025/05/03 21:38 UTC to 2025/05/06 05:26 UTC, we experienced an outage in Smart Answers in search and AI definitions for all Confluence Cloud Atlassian Intelligence customers. Rovo experiences were not impacted. The issue has been resolved and the service is operating normally.

We have identified the root cause of the intermittent errors for Smart Answers and AI definitions in Confluence Cloud Atlassian Intelligence customers are progressively rollout out a fix to customers, with a fix expected to reach all customers over the next 2 hours. We are monitoring closely to confirm all errors have resolved.

We are investigating reports of intermittent errors for Atlassian Intelligence Confluence Cloud customers. We have identified the root cause and are preparing a hotfix

We are investigating reports of intermittent errors for Atlassian Intelligence Confluence Cloud customers. We have identified the root cause and are preparing a hotfix

Between 7:37 and 8:06 UTC, Confluence, Jira, and JSM were unavailable or experienced degraded performance for some users in the European region. The issue has now been resolved, and the services are operating normally for all impacted customers.

From 7:37 to 8:06 UTC, we experienced issues that made Confluence, JIRA, and JSM unavailable or degraded the experience of some users in the European region. The issue has been mitigated, and services operate normally for all impacted customers. We will continue to monitor it closely for stability.

From 7:37 to 8:06 UTC, we experienced issues that made Confluence, JIRA, and JSM unavailable or degraded the experience of some users in the European region. The issue has been mitigated, and services operate normally for all impacted customers.We will continue to monitor it closely for stability.

Between 13:00 UTC to 23:00 UTC on April 23, 2025, we experienced automation rule execution delays for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally. For some high volume customers who regularly have rule throttling, there may be an extended period to clear full backlogs. For those high volume customers we expect any extended period rule throttling to be resolved by 07:00 UTC on April 24, 2025.

New executions are continuing to run without delay. Remaining delayed executions will complete in approximately one hour. We will continue to monitor the progress and provide an update within the next hour.

New executions are running without delay. Remaining delayed executions will complete in the next 2 hours. We will continue to monitor the progress and provide an update within the next hour.

A majority of new automation executions are running without delay. Remaining delayed automation executions should be completed within 3 hours. We will continue to monitor the progress and provide an update within the next hour.

We have applied significant mitigations and the majority of delayed automation executions should be completed within 2 hours. Some customers may experience some delay in some executions during the 2 hours following. Rule execution delays should be mitigated in 4 hours. We will continue to monitor the progress and provide an update within the next hour.

We are still investigating automation rule delays that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. The backlog of previous mitigations has decreased and continues to decrease, however some customers may be still be experiencing delays. The backlog of automations is being processed as we continue to apply mitigations and will provide more details within the next hour.

We are still investigating automation rule delays that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. Previous mitigations have decreased the average delays across executions, however some customers may be still be experiencing delays. We are applying more mitigations and will provide more details within the next hour.

We are investigating automation rule execution delays that are impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We have applied a temporary mitigation and are continuing to investigate for root cause. We will provide more details within the next hour.

We are investigating cases of degraded performance for automation rules for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We will provide more details within the next hour.

We are investigating cases of degraded performance for automation rules for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We will provide more details within the next hour.

This incident has been resolved.

Between 14:29 UTC to 14:55 UTC, some users may have experienced page load errors for Confluence. The issue has been resolved and the service is operating normally. Once we complete our internal incident review process, we will publish a more detailed postmortem of what went wrong, along with steps we're taking designed to prevent this from happening again in the future.

Between 18:40 UTC to 19:00 UTC, some users may have experienced page load errors for Confluence. The issue has been resolved and the service is operating normally. Once we complete our internal incident review process, we will publish a more detailed postmortem of what went wrong, along with steps we're taking designed to prevent this from happening again in the future.

Between 00:00 UTC to 01:05 UTC 14 April, users attempting to load the Administration page for Atlassian products. The issue has been resolved and the service is operating normally.

We are aware of an issue where users attempting to load the Administration page are instead seeing a blank page. Our team is investigating with urgency and will provide further update as soon as possible.

We are aware of an issue where users attempting to load the Administration page are instead seeing a blank page. Our team is investigating with urgency and will provide further update as soon as possible.

We identified a temporary access issue affecting some customers using several Atlassian Cloud products. All affected products are now back online, and no further impacts have been observed. We apologize for any inconvenience this may have caused.

Our systems are stable, and no recurrences have been observed. We will continue to monitor closely and provide updates as they become available.

We have identified the root cause of the access issues and have mitigated the problem. We are now monitoring this closely and will resolve this incident within the next hour.

For customers that are currently experiencing issues accessing their Jira and Confluence sites, you are able to add /wiki/ to the end of your site name in order to continuing accessing Confluence. For example: https://site.atlassian.net/wiki/ Our team is continuing to investigate an issue impacting Jira sites with urgency.

For customers that are currently experiencing issues accessing their Jira and Confluence sites, you are able to add /wiki/ to the end of your site name in order to continuing accessing Confluence. For example: https://site.atlassian.net/wiki/Our team is continuing to investigate an issue impacting Jira sites with urgency.

### Summary Jira, Confluence and JSM Automation rules triggered or scheduled to run between 10am and 5pm UTC on March 17, 2025, and between 1pm UTC on March 18 and 12:30am UTC on March 19 were delayed on average by 1.5 hours and up to 12 hours maximum. The incident was triggered by the deployment of a monitoring library upgrade, which slowed the execution of all rules. This reduced the throughput of rule processing which resulted in rules being backed up and delayed. The change manifested in poor rule performance only during periods of high traffic. This incident occurred over two time windows. For the first incident window, backed-up rule executions began to reduce 4 hours 15 minutes after the first alert, and all rules had caught up 7 hours after the first alert. For the second incident window, backed-up rule executions began to reduce 1 hour, 50 minutes after the first alert, and all rules had caught up 10 hours after the first alert. The root cause of both incidents was identified and a change to address it was deployed by 10am UTC on March 19, 2025. ### **IMPACT** The customer’s rules were delayed on average by 1.5 hours and up to 12 hours during both incident windows. A very small number of rules encountered the following error: “_The rule actor doesn't have permission to view the event that triggered this rule_.” This error occurred because of rate limiting implemented by an internal Atlassian service due to increased throughput resulting from our mitigation efforts. These rules failed to complete successfully. All other rules eventually ran successfully. ### **ROOT CAUSE** The issue was caused by a change introduced to an Atlassian monitoring library, which significantly degraded the Automation rule engine's performance. The performance degradation prevented Automation's system from keeping pace with processing throughput, causing a back-up of executions and subsequent customer rule delays. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific issue didn’t manifest itself until our systems were at peak load. The change to the Atlassian monitoring library that was the root cause of the incident has been fixed. We are prioritizing the following improvement actions that are designed to avoid a repeat of this type of incident: * Deploying the fixed monitoring library after thorough testing * Implementing additional monitoring and alerting to the area of our system affected with performance degradation * Introducing additional pre-deployment testing designed to identify performance degradations before they impact customers * Increasing rate limits of certain downstream Atlassian systems to reduce the likelihood of the rule failures that occurred in this incident * Increasing the processing capacity of parts of our system to reduce the impact of backed up rule executions We apologize to customers whose automation rules were impacted during this incident; we are taking immediate steps designed to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Between 13:00 UTC to 16:30 UTC, we experienced delays in automation processing across Confluence, Jira Service Management, and Jira, which was causing rules to appear stuck. The issue has been resolved and we expect new automations to continue processing without delay. For automation processes initiated before 16:30 UTC, they may take until 08:00 UTC March 19th, 2025, however, we anticipate processing to be completed quicker. No action is required from users for these automations to be completed.

We have successfully identified and mitigated the issue affecting all automation customers, which was causing rules to appear stuck. New automations should now process as expected without delay. For automation processes initiated from 13:00 UTC to 16:30 UTC on March 18th, 2025, in Jira, Jira Service Management, and Confluence, execution will continue but may experience delays of up to one day. No action is required from users for these automations to be completed. We are closely monitoring the situation and will provide further updates as more information becomes available.

The delayed execution of automation rules is mitigated and recovery is in progress. We are now monitoring closely.

We are investigating cases of degraded performance regarding automation rules execution for Confluence, Jira Service Management, and Jira Cloud customers. We are applying mitigation to speed up rule execution. We will provide more details within the next hour.

We are investigating cases of degraded performance w.r.t automation rules execution for Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour.

Our team has identified the cause of this issue and has implemented a fix. This should now be mitigated for all users.

We are aware of an issue currently impacting users ability to open the marketplace due to a missing menu item within Confluence. Our team is currently looking into this issue.

Our team has identified the cause of this issue and has implemented a fix. This should now be mitigated for all users.

We are aware of an issue currently impacting users ability to open the marketplace due to a missing menu item within Confluence. Our team is currently looking into this issue.

Between 14:36 UTC to 16:15 UTC, we experienced performance degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

We are investigating cases of degraded performance for some Confluence, Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour.

Between 14:36 UTC to 16:15 UTC, we experienced performance degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

We are investigating cases of degraded performance for some Confluence, Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour.

A fix has been implemented and we have not seen any recurrences. This incident has been resolved for Confluence.

A fix has been implemented and we are monitoring the results.

We are investigating 'site maintenance' issue that is impacting some Confluence, Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour.

We are aware of some users experiencing a site maintenance window appearing instead of their site for Confluence. Our team is investigating this with urgency.

A fix has been implemented and we have not seen any recurrences. This incident has been resolved for Confluence.

A fix has been implemented and we are monitoring the results.

We are investigating 'site maintenance' issue that is impacting some Confluence, Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour.

We are aware of some users experiencing a site maintenance window appearing instead of their site for Confluence. Our team is investigating this with urgency.

Between 13:00 UTC to 16:30 UTC, we experienced delays in automation processing across Confluence, Jira Service Management, and Jira, which was causing rules to appear stuck.The issue has been resolved and we expect new automations to continue processing without delay.For automation processes initiated before 16:30 UTC, they may take until 08:00 UTC March 19th, 2025, however, we anticipate processing to be completed quicker. No action is required from users for these automations to be completed.

We have successfully identified and mitigated the issue affecting all automation customers, which was causing rules to appear stuck. New automations should now process as expected without delay.For automation processes initiated from 13:00 UTC to 16:30 UTC on March 18th, 2025, in Jira, Jira Service Management, and Confluence, execution will continue but may experience delays of up to one day. No action is required from users for these automations to be completed. We are closely monitoring the situation and will provide further updates as more information becomes available.

The delayed execution of automation rules is mitigated and recovery is in progress. We are now monitoring closely.

We are investigating cases of degraded performance regarding automation rules execution for Confluence, Jira Service Management, and Jira Cloud customers. We are applying mitigation to speed up rule execution. We will provide more details within the next hour.

We are investigating cases of degraded performance w.r.t automation rules execution for Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details within the next hour.

Between 05:30 UTC and 10:00 UTC, we experienced increased rates of Forge app installation, upgrade and uninstallation for Confluence and Jira. The issue has been resolved and the service is operating normally.

We have identified the root cause of the increased errors and have mitigated the problem. We are now monitoring closely.

We are investigating reports of intermittent errors for <SOME/ALL> Confluence, Jira, and Atlassian Developer Cloud customers. We will provide more details once we identify the root cause.

Between 05:30 UTC and 10:00 UTC, we experienced increased rates of Forge app installation, upgrade and uninstallation for Confluence and Jira. The issue has been resolved and the service is operating normally.

We have identified the root cause of the increased errors and have mitigated the problem. We are now monitoring closely.

We are investigating reports of intermittent errors for Confluence, Jira, and Atlassian Developer Cloud customers. We will provide more details once we identify the root cause.

Until the end of May 2025, Atlassian plans to perform maintenance on the infrastructure supporting the Jira and Confluence platforms.This maintenance will result in a temporary service outage for Free edition users located in Singapore and Northern California, with a total duration of no more than 120 minutes per customer. The maintenance will be performed during regular business hours in the specified regions.To learn more, please refer to this community post https://community.atlassian.com/forums/Announcement-articles/Upcoming-Maintenance-Notification-for-Jira-and-Confluence/ba-p/2973795#M6870

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Between 09:43 UTC to 15:55 UTC, we experienced delays in automation processing across Confluence, Jira Service Management, and Jira, which was causing rules to appear stuck. The issue has been resolved and we expect new automations to continue processing without delay. For automation processes initiated before 15:55 UTC, we anticipate processing to be completed by 08:00 UTC March 18th, 2025. No action is required from users for these automations to be completed.

We have successfully identified and mitigated the issue affecting all automation customers, which was causing rules to appear stuck. New automations should now process as expected without delay. For automation processes initiated before 15:55 UTC on March 17th, 2025, in Jira, Jira Service Management, and Confluence, execution will continue but may experience delays of up to one day. No action is required from users for these automations to be completed. We are closely monitoring the situation and will provide further updates as more information becomes available.

Following our previous update, we continue to experience delays in automation processing across Jira, Jira Service Management, and Confluence. The issue persists, affecting all automation customers and causing rules to appear stuck. Our team is actively working to resolve the situation and restore normal service levels as quickly as possible. We appreciate your patience and will provide further updates as more information becomes available.

We are currently experiencing delays in automation processing across Jira, Jira Service Management, and Confluence due to high traffic. While rules are firing, execution is delayed. Rules triggered in the last 2.5 hours will be processed, but this may take up to a day. New events should process normally following adjustments made at 12:13 PM UTC to prioritize them. We will provide an update in the next hour. Thank you for your patience.

Between 09:43 UTC to 15:55 UTC, we experienced delays in automation processing across Confluence, Jira Service Management, and Jira, which was causing rules to appear stuck. The issue has been resolved and we expect new automations to continue processing without delay.For automation processes initiated before 15:55 UTC, we anticipate processing to be completed by 08:00 UTC March 18th, 2025. No action is required from users for these automations to be completed.

We have successfully identified and mitigated the issue affecting all automation customers, which was causing rules to appear stuck. New automations should now process as expected without delay.For automation processes initiated before 15:55 UTC on March 17th, 2025, in Jira, Jira Service Management, and Confluence, execution will continue but may experience delays of up to one day. No action is required from users for these automations to be completed. We are closely monitoring the situation and will provide further updates as more information becomes available.

Following our previous update, we continue to experience delays in automation processing across Jira, Jira Service Management, and Confluence. The issue persists, affecting all automation customers and causing rules to appear stuck. Our team is actively working to resolve the situation and restore normal service levels as quickly as possible. We appreciate your patience and will provide further updates as more information becomes available.

We are currently experiencing delays in automation processing across Jira, Jira Service Management, and Confluence due to high traffic. While rules are firing, execution is delayed. Rules triggered in the last 2.5 hours will be processed, but this may take up to a day. New events should process normally following adjustments made at 12:13 PM UTC to prioritize them. We will provide an update in the next hour. Thank you for your patience.

On March 14th, 2025, between 09:00 and 19:14 UTC, some customers experienced issues creating new sites. The errors occurring for some users during new site creation should now be resolved.

We are investigating cases of errors for some users creating new sites. We will provide more details within the next hour.

Searches within Confluence and Compass should now be operating as normal. This issue will now be resolved.

Issues causing error messages when users were attempting to search within Confluence and Compass should now be resolved. Our team is monitoring ongoing performance at this time.

We are aware that some users of Confluence and Compass are currently experiencing errors when attempting to search. Our team is investigating this issue with urgency and will provide an update when available.

We recently identified and addressed an issue causing delays in document publishing. A change that led to delays of up to 6 seconds has been reverted, improving performance. With the issue now mitigated, we are resolving this incident while continuing to work internally on a permanent fix.

We are currently investigating this issue.

We are aware of an issue that was impacting user authentication to Atlassian services between 6:10AM Tuesday 4th March UTC and 6:35AM Tuesday 4th March UTC. Users that were already logged in would not have been impacted by this issue. A deployment suspected of causing this issue was rolled back and the problem was subsequently resolved.

On February 28, 2025, between 14:47 and 20:30 UTC, some customers experienced issues impacting search results. The issue has been resolved and search is now operating normally.

We are continuing to investigate this issue. We will provide more details once we identify the root cause.

We are investigating reports of intermittent errors for some Confluence Cloud customers. We will provide more details once we identify the root cause.

We are pleased to inform you that a new version of our app is now available on the Apple App Store. Please update your app to the latest version to resolve the issue.

We are currently aware of an issue impacting users of iOS devices where pages will present a 403 error to the user if IP Allowlist and a Mobile App policy with Allow access from any IP address are configured. A fix has been submitted to the AppStore for review and is expected to become available before the end of this week to resolve this issue. Users can use a mobile device running the Android operating system as a workaround to this problem until the release is available. For more information on IP Allowlists please see https://support.atlassian.com/security-and-access-policies/docs/specify-ip-addresses-for-product-access/ For more information on Mobile App policies please see https://support.atlassian.com/security-and-access-policies/docs/mobile-policy-mam-security-controls-and-supported-apps/

We are currently aware of an issue impacting users of iOS devices where pages will present a 403 error to the user if IP Allowlist and App Trust Mobile Bypass are both enabled. A fix has been submitted to the AppStore for review and is expected to become available before the end of this week to resolve this issue. Users can use a mobile device running on Android operating system as a workaround to this problem until the release is available.

On February 27, 2025, between 03:00 and 20:40 UTC, some customers experienced intermittent issues impacting Confluence search results. The issue has been resolved and search is operating normally.

We are investigating reports of intermittent errors for some Confluence Cloud customers. We will provide more details once we identify the root cause.

Between 7:59 UTC to 22:03 UTC, some customers experienced anonymous access search for Confluence. The root cause was a faulty change in authorization rules that caused an error response. 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're actively working on a permanent fix. The issue has been resolved and the service is operating normally.

We continue to work on resolving the anonymous access search for Confluence. We have identified the root cause and expect recovery shortly.

We are investigating reports of intermittent errors for some Confluence Cloud customers. We will provide more details once we identify the root cause.

### Summary On February 10, 2025, between 16:10 and 18:35 UTC, Atlassian customers in Brazil experienced intermittent failures accessing and using Jira and Confluence Cloud. This disruption was due to our Content Delivery Network \(CDN\) not having sufficient capacity in Brazil under a certain network configuration. Changes in the lead-up to the incident included enabling CDN for Jira and Confluence in Brazil between January 20th and February 6th to improve performance and security. Jira and Confluence experience success rate monitoring detected the incident within 50 minutes. The incident was mitigated by temporarily disabling CDN in Brazil, which put Atlassian systems into a known good state. The total time to resolution was two hours and 25 minutes. ### **IMPACT** The overall impact was on February 10, 2025, between 16:10 and 18:35 UTC to Jira and Confluence Cloud_._ The incident caused service disruption to Brazilian customers when they attempted to access or use any feature of those products. Customers observed a generic error page or “HTTP 500” error presented by our CDN provider for up to a third of all requests at peak. ### **ROOT CAUSE** Our CDN is configured to present Jira and Confluence Cloud from static IP ranges dedicated to Atlassian. This configuration limited the number of edge locations servicing customer requests, causing a high concentration of connections in the Brazilian region on one edge location in particular. When daily traffic volumes in Brazil peaked on February 10, connections through the edge location to our servers encountered a capacity limit and were rejected with a HTTP 500 error. ### **REMEDIAL ACTION PLAN & NEXT STEPS** We understand that outages impact your productivity. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Along with our CDN provider, we have already taken the following actions to avoid repeating this type of incident: * Our CDN provider has completed the rollout of the static, dedicated IP feature to all their edge locations and enabled Jira and Confluence Cloud to be served from all of them, thus moving to the intended configuration that will provide full network capacity. * We are working with our CDN provider to perform more rigorous checks of capacity and configuration for Jira and Confluence Cloud. * Our CDN provider increased the server connection limit for Jira and Confluence Cloud in all locations, further increasing capacity. * Based on the observed failure patterns, we have created additional monitoring and alerting configurations, so we will be alerted immediately if the issue reoccurs. Additionally, we are prioritizing actions to improve the detection of failures that affect a specific region. Thanks, Atlassian Customer Support

Between February 10, 2025, at 17:04 UTC and 18:32 UTC, some customers for Jira Work Management, Jira Service Management, Jira, Jira Product Discovery Cloud and Confluence experienced degraded performance and 500 errors. We found that cloud products in Brazil encountered an internal limit with our cloud service provider. We redistributed traffic to mitigate this issue and are working with our cloud provider to address this issue in the future. The issue has been resolved and all the services are operating normally.

We are investigating cases of degraded performance for Jira Work Management, Jira Service Management,Jira Cloud and confluence customers. We are currently investigating it and will provide more details within the next hour.

On February 13, 2025, between 21:47 UTC and 22:15 UTC, some customers for Confluence Cloud in the Asia Pacific region experienced degraded performance and 500 errors. The issue was caused by a sudden surge in traffic and was resolved within 28 minutes.

### Summary On January 28, 2025, between 13:35 and 15:10 UTC, Atlassian customers using Confluence Cloud experienced difficulties viewing, editing and creating pages. This disruption was caused by a faulty version of a third-party app which caused a grey overlay that obscured fully loaded Confluence pages, affecting customers who had the app installed. Customers reported the issue, and the Atlassian team began their investigation within 10 minutes after receiving the support tickets. **Timeline of events** * The app vendor released version \(1.3.39-AC\) of the app on January 28, 2025, 13:35 UTC. * Atlassian team got notified of the incident on January 28, 2025, 14:02 UTC, tried to reproduce the issue and involved the on-call teams. * The app vendor released version \(1.3.41-AC\) of the app on January 28, 2025 14:35 UTC . * Atlassian team notified customers to update the app to the latest version \(1.3.41-AC\) through our Statuspage on January 28, 2025, 15:06 UTC. * The app vendor released a hot-fix for the existing faulty version \(1.3.39-AC\) of the app on January 28, 2025, 15:10 UTC. This helped mitigate the incident in one hour and 35 minutes. Furthermore, the Atlassian team initiated a mandatory update to the latest version \(1.3.41-AC\) for all customers of the app on January 28, 2025, 16:37 UTC. ### **IMPACT** The overall impact was between January 28, 2025, 13: 35 UTC and 15:10 PM UTC on Confluence Cloud. The incident caused service disruption to customers having the third-party app installed, where they were unable to view, edit, or create pages on Confluence Cloud. ### **ROOT CAUSE** The issue arose from a problematic version release of a third-party app. **How it started?** The app vendor uploaded a new version of their app \(1.3.39-AC\) to the marketplace, making it available for automatic updates. Customer sites check for new minor app versions and update automatically within a rolling 24-hour period. However, an issue arose when the vendor deployed new frontend code that relied on a specific component available only in the latest app version. This created a dependency mismatch, leading to an error. The app’s frontend code is delivered through the vendor's CDN, and during testing, no issues were detected. However, when the updated JavaScript code was deployed to the CDN, it assumed the presence of the new component. Unfortunately, not all customers were updated to the latest app version because of our progressive updates, resulting in some using older app descriptors that lacked the required component. This mismatch triggered Confluence to display a full-screen dialog on every page load. The Confluence frontend rendered the dialog, which included an iframe to load the app’s code. Since the app had not been updated on some customer sites, the required component’s data could not be loaded, causing a grey overlay with error message to appear on the users’ screens. The Confluence frontend provided functionality to close the dialog using the escape key. However, because the app failed to load the necessary data, the dialog displayed a generic error message overlaid with a grey opaque screen. Customers were unaware of the escape key workaround, leaving them unable to dismiss the dialog easily. **How was it mitigated?** * The app vendor deployed a new version \(1.3.41-AC\) of the descriptor. * Atlassian team notified customers to update to the \(1.3.41-AC\) on StatusPage * The app vendor released a hotfix for \(1.3.39-AC\) which removed the reference to the new component. The issue was resolved in one hour and 35 minutes. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific issue wasn’t identified because the third-party app created an overlay on our loaded pages and that was not picked up by our monitoring systems. We are working to improve the monitoring and detection of such app triggered failures. To prevent the recurrence of this type of incident, and detect such incidents faster, we are prioritizing the following improvement actions: * We are developing a solution in our UX components to be resilient to app errors. * We are also developing a solution where we can have clear messaging to exit from overlays that are taking the whole screen. * We are working on improving our monitoring for this specific scenario. We are collaborating with app vendors to share guidance on dependency component versioning. Therefore, the app vendors need to make changes in a more backward compatible manner. 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

Between 28/Jan/25 2:02 PM UTC and 28/Jan/25 6:32 PM UTC, customers experienced issues in loading pages in Confluence due to a third party app. We have triggered an automatic update to a working version of the app for all impacted customers. This process has completed, and all customers using the third party app should once again be able to access Confluence as usual. The issue has been resolved and the service is operating normally.

We are continuing to work on a fix for this issue.

We are actively working on identifying a solution to address the issue. Workaround: We advise all customers experiencing this issue to upgrade the Table Filter, Charts, and Spreadsheets for the Confluence app. Please see this page https://confluence.atlassian.com/upm/updating-apps-273875710.html for instructions. We have received confirmation from customers that applying this workaround resolves the issue. Our teams are closely monitoring the situation to ensure consistent results and continue to validate the effectiveness of this solution.

We have identified that the issue affects customers using a third-party plugin. We recommend customers to upgrade the Table Filter, Charts & Spreadsheets for Confluence plugin and will continue to monitor the situation.

We are investigating issues with users who cannot access Confluence and will provide updates here soon.

Between 30 January 2025, 23:05 UTC, and 31 January 2025, 01:40 UTC, some customers for Confluence and Jira Service Management experienced errors viewing Confluence content either directly on Confluence or on Jira Service Management Portal as Knowledge base articles. The root cause was the custom domain configured for Confluence, which caused a 'Forbidden Client' error. We have deployed a fix to mitigate the issue and verified that the services have recovered. The issue has been resolved and the service is operating normally.

We have identified the root cause of the Confluence pages that can't be accessed and are not loaded in JIRA Service Management knowledge-based. We have mitigated the problem, and now we are monitoring it closely.

We are investigating an issue with being unable to access Confluence pages that are impacting Confluence and JIRA Service Management Cloud customers. We will provide more details within the next hour.

We experienced issues with linking Confluence spaces to Jira projects. The impact has been confirmed to only impact Jira Cloud.

We are investigating issues linking Confluence spaces to Jira projects affecting some Confluence and Jira Cloud customers. We will provide more details within the next hour.

Between 5:53 PM UTC and 6:30 PM UTC, we experienced 400 Bad Request errors during advanced search operations in Confluence Cloud. The issue has been resolved, and the service is operating normally.

We are investigating an issue with Search functionality that is impacting Confluence. We will provide more details within the next hour.

Between 13 Jan, 11:45 PM UTC to 14 Jan 07:10 AM UTC, we experienced intermittent login failures for Confluence, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

We are investigating reports of intermittent login errors for Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details once we identify the root cause.

This incident has been resolved.

Between 17/Dec/24 8:00 PM UTC to 23/Dec/24 7:26 PM UTC, we experienced a problem that prevented users from managing permissions within the Apps section of Space Settings. The issue has been resolved and the service is operating normally.

We are investigating an issue with managing user permissions that is impacting Confluence Cloud customers. Once we identify the root cause, we will provide more details.

Between 11:28:00 UTC on 22/Dec/24 to 16:41:00 UTC on 23/Dec/24, we experienced a problem when running Automation rules for Confluence, Jira Service Management, and Jira that prevented rules that contained a Send Web Request action with Smart Values from completing successfully. The issue has been resolved and the service is operating normally.

We are investigating reports of intermittent errors for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details once we identify the root cause.

This incident has been resolved.

A fix has been implemented and we are monitoring the result.

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

We have identified the issue and we are working to fix the issue.

Between 3:16pm PST and 7:38pm PST, we experienced an outage for Rovo and all AI features across Atlassian Products. The issue has been resolved and the service is operating normally

We are witnessing significant recovery in the services. We will continue to monitor the situation closely.

We are actively communicating with the affected AI Service provider and closely monitoring the ongoing outage situation. While we have observed some signs of recovery, the majority of API calls are still resulting in errors. We have successfully restored the Smart Answers in Search feature by rerouting requests to an alternative model. All other Atlassian Intelligence capabilities and Rovo remain unavailable at this time due to the ongoing AI Service provider outage.

The fix for this issue has been rolled out at 1PM 5th Dec UTC and this issue has now been resolved. If you have experienced issues updating your apps or if you notice any missing apps please attempt to reinstall the app. If you experience problems reinstalling an app, please raise a request with Atlassian support.

We have identified an intermittent issue since Mon, 18 Nov 2024 14:56 GMT where attempting to update a third party app that makes use of translation packs can result in that app being uninstalled instead, with subsequent attempts to reinstall the app also failing in some cases. The error message displayed for both failed upgrades and failed uninstalls is as follows 'Unfortunately, we're unable to process your request. Please retry again in some time. draw.io is known to be affected by this issue.' We're in the process of rolling out a fix and this should be rolled out by 6 December UTC. We recommend holding off updating your apps for now, but if you update an app and experience this issue, please attempt to reinstall the app. If you experience problems reinstalling the app, please raise a request with Atlassian support. We apologize for the inconvenience. We will monitor the resolution and will provide an update at 11pm UTC, 5th December.

Between 12:13 AM UTC to 01:30 AM UTC, we experienced a degraded experience for AI features in Confluence, Jira Service Management, Jira, and Rovo. The issue has been resolved and the service is operating normally.

We are investigating an issue with AI features that is impacting all Rovo and Enterprise and Premium Confluence, Jira Service Management and Jira customers. We will provide more details within the next hour.

Between 24/11/2024 09:46 PM UTC to 27/11/2024 5:58PM UTC, we experienced an issue where Automation match() smart values with regex are not working as expected for Confluence, Jira Service Management, and Jira. This issue has now been resolved, and automation rules are functioning as expected.

We have identified an issue with Automation match() smart values with regex that is impacting all Jira products and Confluence Cloud. We have identified the root cause and have stopped it from reoccurring.

Here is the root cause analysis of the incident. On November 21, 2024 9:11pm UTC, we deployed a production release of a Confluence service to one of the regions, using a new rollout technology. During the deployment, the team encountered an issue that necessitated a manual rollback. The rollback reverted the region to use the previous nodes, which weren’t pre-scaled to handle existing traffic at the time. Consequently, this caused stress on the service. In response, the team immediately scaled up the nodes in the region. By 9:24 PM UTC, the service was fully restored, resulting in an outage that lasted for 13 minutes. Atlassian is conducting an internal post-incident review and will take the required actions to prevent this kind of incident from happening again. We sincerely apologize for the inconvenience.

There was Confluence outage in one of the regions on November 21, 2024 9:11pm UTC. By 9:24 PM UTC, the service was fully restored, resulting in an outage that lasted for 13 minutes.

Between 07:50 UTC to 11:31 UTC, some customers experienced previews of attachments unavailable for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. 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're actively working on a permanent fix. The issue has been resolved and the service is operating normally.

We have identified the root cause of the issue of previews not being available for some attachments and mitigated the problem for new uploads and frequently viewed files that were affected by this issue. The rest of the previews are gradually being regenerated. We are now monitoring this closely.

We continue to work on resolving the previews unavailability for Confluence and Jira attachments. We have identified the root cause and expect recovery shortly. The issue will not be seen (ie., preview will be available) for new attachment uploads. We are working on remediating the impacted previews.

We are investigating reports of intermittent errors for some Confluence and Jira Cloud customers where attachment previews are not loading. The attachments are available for download. We will provide more details once we identify the root cause.

We have identified the root cause of the issue and the problem is now resolved.

We have identified an issue where, after modifying a macro's content and saving the page, the macro shows as empty or old content. Performing a hard reload of the page will restore the macro's content.

Between 11/20 19:40 UTC and 11/21 02:00 UTC, we experienced Jira issue macros failing to load the table view for Confluence Cloud. The issue has been resolved and the service is operating normally.

We continue to work on resolving the Jira issue macro (legacy) failing to load the table view for Confluence cloud customers. We have identified the root cause and expect recovery shortly.

We have identified an issue with Confluence Jira Legacy macro which causes the table view to not display, affecting all cloud customers. We are deploying a fix that should resolve this issue and will provide more details within the next hour.

We have fixed the Auth issue which Confluence License API partial outage for Marketplace apps.

We have identified an issue with Confluence License API which will cause issue for apps to fetch license information. We are working on the fix which should be deployed soon.

Between 06/Nov/24 12:00 AM UTC to 06/Nov/24 9:22 AM UTC, we experienced Automation Audit Logs not loading for customers intermittently for Confluence, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally.

We are investigating cases of degraded performance with the Automation logs for Confluence, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. However, automation rule runs are not impacted. We will provide more details within the next hour.

Between 08:00 UTC to 11:54 UTC, we experienced problems with the invitation of new users for Cloud customers on admin.atlassian.com. The issue has been resolved and the service is operating normally.

We continue to work on resolving the invitation workflow in admin.atlassian.com We have identified the root cause and performed changes in the environment to mitigate the issue.

We are investigating reports of intermittent errors for some Atlassian customers when they are trying to invite users using their admin panels (admin.atlassian.com) We will provide more details once we identify the root cause.

Between 07:30 UTC to 09:X30 UTC, we experienced issues with user mentions for Confluence, and Team fields and User Picker in Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

We are investigating issues with Team Fields, which does not provide existing options to be updated, and also User Picker functionality not working. We will provide updates here soon.

Between 2024-10-23, 15:09 UTC and 2024-10-23, 17:06 UTC, we identified an issue that affected tenant provisioning and user management actions at Atlassian Cloud, causing a delay in performing actions related to these two topics. We have identified the root cause and the issue has been mitigated.

Between 2024-10-18 05:40 UTC-7 to 2024-10-18 08:40 UTC-7, we experienced an outage affecting user/group memberships in AdminHub for Confluence, Jira Work Management, Jira Service Management, Jira, and Guard. The issue has been resolved and the service is operating normally.

We have received reports of intermittent errors for some Cloud customers, specifically admins who are unable to see group memberships in AdminHub. We have identified the root cause and expect recovery shortly.

Between 6 AM UTC to 10 AM UTC on October 7th, we experienced issues with automation rules and scheduled rules for Confluence, Jira Work Management, Jira Service Management, and Jira. We have implemented and monitored the fix, and the issue has been resolved. The service is operating normally.

We are observing a recovery on our monitoring dashboards. The affected rules will be executed in the next few hours, if they haven't been processed already. We will keep monitoring the situation during this time before marking the incident as 'Resolved'.

We identified that automation rules running between 6 AM UTC and 10 AM UTC may have been impacted by the incident. Additionally, all scheduled rules during this window were affected. We have taken action to mitigate this issue, and we are currently working on recovery. We know what the fix is and are implementing it now. The affected rules will run once the fix is applied.

We are investigating issues with scheduled automated rules and will provide updates here soon.

Between 2024-10-03 06:00PM CDT to 2024-10-04 05:00PM CDT, we experienced PDF page and space exports issues for Confluence Cloud. The issue has been resolved and the service is operating normally.

We have identified an issue impacting the PDF Export v2 functionality. As a corrective measure, we have temporarily reverted the PDF export process to the v1 exporter. We are observing signs of recovery and will continue to monitor the situation closely. We will provide more details by early next week.

We are continuing to investigate this issue.

Confluence Cloud PDF page and space exports are currently failing to export. We are currently investigating the impact and working to resolve the issue.