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

We are investigating reports of intermittent failures in forge app deployments. We will provide next update within an hour.

Between 18:19 UTC and 20:32 UTC, developers experienced intermittent outages when using the 'forge tunnel' CLI command. This was caused by to a service outage with our service provider, Cloudflare. Cloudflare have resolved the issue, and we have confirmed that forge tunneling has been restored. For more details, please refer to cloudflare status: https://www.cloudflarestatus.com/incidents/25r9t0vz99rp

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.

At 1:30 p.m. UTC, we completed the process of fixing apps affected by the incident. We don't observe any further impact on any production app.

Our team has identified a fix for this issue and is progressing through updating this for all impacted apps. Re-deploying your app in the meantime may still resolve this issue for your app immediately. We will provide further update when the rollout of the fix has been completed.

We are aware of an issue currently impacting some Forge apps where users may see a 'Not Found' error message when attempting to load the app. Re-deploying an app may resolve this issue. Our team is continuing to investigate with urgency and will provide an update when available.

We are aware of an issue currently impacting some Forge apps where users may see a 'Not Found' error message when attempting to load the app. Re-deploying an app may resolve this issue. Our team is continuing to investigate with urgency and will provide an update when available.

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.

Scopes information was not present in app details page and during installation experience for forge apps. This was caused due to a recent change which has now been rolled back. It has also been assessed that this issue had no impact on the app functionalities in existing installations. Post issue mitigation, we have verified that scopes information is visible as expected.

Scopes information was not present in app details page and during installation experience for forge apps. This was caused due to a recent change which has now been rolled back. It has also been assessed that this issue had no impact on the app functionalities in existing installations. Post issue mitigation, we have verified that scopes information is visible as expected.

The incident is resolved and impact is mitigated

We have identified an issue where Marketplace reports were not accessible to partners for around 11 hours. We have identified and addressed the issue, and we will continue to monitor. Apologies on the inconvenience caused

We have identified an issue where Marketplace reports were not accessible to partners for around 11 hours. We have identified and addressed the issue, and we will continue to monitor. Apologies on the inconvenience caused

Between 20:00 UTC May 19th to 07:55 UTC May 20th, some apps using Connect on Forge were experiencing installation failures. The issue has been resolved and the service is operating normally.

A fix for an issue relating to problems installing Connect on Forge apps in some cases has been identified and is currently underway to mitigate this issue. We will provide further update when this issue has been resolved.

We are aware of some users having issues installing Connect on Forge apps. Our team is investigating with urgency and will provide an update when available.

We are aware of some users having issues installing Connect on Forge apps. Our team is investigating with urgency and will provide an update when available.

The root cause of this issue with our service provider has now been resolved and this should no longer be impacting any customers.

The majority of app re-deployments have been completed and intermittent invocation errors should now be mitigated. Our team continues to work with our service provider on the small percentage of remaining apps and we will update once this issue has been resolved.

We identified 38 app deployments which might still be affected with the issue (intermittent invocation failures). These would be redeployed in next 24hours. No new app deployments should be affected by the issue. Next update ~5AM UTC

The apps which had the error were redeployed by the team. We will monitor if we observe any issues for them. In case you are still experiencing Forge invocations 'unhandled exception error' in the Developer Console, please re-deploy your apps which would rectify the issue.

We are working on the fix. We are currently redeploying the apps which had the error. In the meantime if you are experiencing Forge invocations 'unhandled exception error' in the Developer Console, please re-deploy your apps which should rectify the issue.

Our team has identified the cause of this issue and is working towards a resolution. If you are experiencing Forge invocations 'unhandled exception error' in the Developer Console, please re-deploy your apps which should rectify the issue in the meantime.

We are aware of some users experiencing a low percentage of Forge invocation errors in their apps in EU Central and CA Central regions. Our team is investigating this with urgency and an update will be provided when available.

We are working on the fix. We are currently redeploying the apps which had the error. In the meantime if you are experiencing Forge invocations 'unhandled exception error' in the Developer Console, please re-deploy your apps which should rectify the issue in the meantime.

Our team has identified the cause of this issue and is working towards a resolution.If you are experiencing Forge invocations 'unhandled exception error' in the Developer Console, please re-deploy your apps which should rectify the issue in the meantime.

We are aware of some users experiencing a low percentage of Forge invocation errors in their apps in EU Central and CA Central regions. Our team is investigating this with urgency and an update will be provided when available.

We are aware of some users experiencing a low percentage of Forge innovation errors in their apps in EU Central and CA Central regions. Our team is investigating this with urgency and an update will be provided when available.

The data in the impacted app versions has been fixed for fields scopes, release notes and release summary, successfully.

App versions data has been fixed to add the scopes from descriptor file. Correct values are appearing in all the impacted places for Customers. The impacted versions are not editable at the moment, we're fixing the issue. And fixing the version release notes as well to remove the comment about removing scopes. Please expect the next update in 3 hours.

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

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

The issue was caused due to a recent change which has now been rolled back. It has also been assessed that this issue has had no impact on the app functionalities in existing installations. For the versions already created in which scopes is missing, team is working to fix this.

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

The issue was caused due to a recent change which has now been rolled back. It has also been assessed that this issue has had no impact on the app functionalities in existing installations.For the versions already created in which scopes is missing, team is working to fix this.

HTTP calls to Forge Web Triggers were failing with code 503. This was impacting all Forge apps that use web triggers. The issue has now been resolved. - Incident started at 01:52 UTC - Incident was fixed at 03:17 UTC

We are investigating an error with Forge web triggers returning HTTP 503 errors. Any apps using web triggers may be experiencing failures

We are investigating an error with Forge web triggers returning HTTP 503 errors. Any apps using web triggers may be experiencing failures

Between 16:49 UTC to 17:29 UTC on May 7, 2025, we experienced a brief outage for the developer console. The issue has been resolved and the service is operating normally.

Between 16:49 UTC to 17:29 UTC on May 7, 2025, we experienced a brief outage for the developer console. The issue has been resolved and the service is operating normally.

Between 10:55 AM UTC to 13:15 PM UTC on April 28, 2025, we experienced partial unavailability in managing Forge apps; Such as lifecycle developer console usage, and the creation and deployment of Forge apps for Atlassian Partners, Jira Work Management, Jira, Atlassian Developer, Jira Product Discovery, Compass, and Atlassian Migrations. 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.

The issues causing the unavailability of related Forge apps capabilities on multiple Atlassian platforms have been resolved, and services are now operating normally for all impacted customers. We will continue to closely monitor for stability.

We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms, such as apps lifecycle (installation, removals), developer console usage (including tunneling), and the creation and deployment of Forge apps. We have identified the root cause and are in the process of mitigating the impact. We'll keep you posted with further updates. Next updates in 1 hour.

We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms. Such as apps lifecycle (installation, removals), developer console usage (including tunnelling), and the creation and deployment of Forge apps. Our team is working diligently to resolve this issue and restore services quickly. We are in the process of identifying the root cause and implementing the necessary fixes. Next updates in 1 hour.

We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms. Such as apps lifecycle (installation, removals), developer console usage (including tunnelling), and the creation and deployment of Forge apps. Our team is working diligently to resolve this issue and restore services quickly. We are in the process of identifying the root cause and implementing the necessary fixes.Next updates in 1 hour.

The issue in the 3rd party dependency has been resolved. All reporting APIs are working as expected.

Marketplace reports are not working due to an issue in a 3rd party dependency. The 3rd party has identified the root cause and is fixing it. The issue started on 4th April at 10:50 pm UTC. We'll share an update in next one hour.

Marketplace reports are not working due to an issue in a 3rd party dependency. The 3rd party has identified the root cause and is fixing it. The issue started on 4th April at 10:50 pm UTC. We'll share an update in next one hour.

This incident is now resolved.

We are seeing delay in transaction reports . The cause has been identified and occurred due to configuration change in a dependant system . The team is working on getting the pipeline up and running as soon as possible. Estimated ETA is around 3-4 hours from now. We are keeping this thread open and will keep it updated on all significant updates.

This incident is now resolved.

We are seeing delay in transaction reports . The cause has been identified and occurred due to configuration change in a dependant system . The team is working on getting the pipeline up and running as soon as possible. Estimated ETA is around 3-4 hours from now. We are keeping this thread open and will keep it updated on all significant updates.

The APIs for the licensing details and aggregated evaluation details were failing, for 1.5 hours, due to an issue on the Databricks catalog side. The issue however has been resolved and the functionality is working as expected now.

The APIs for the licensing details and aggregated evaluation details were failing, for 1.5 hours, due to an issue on the Databricks catalog side. The issue however has been resolved and the functionality is working as expected now.

The scheduled maintenance has been completed.

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

Forge SQL cluster will be upgraded during a routine maintenance window. During this time, control plane operations, such as fresh installations or upgrade of an app that uses SQL capability, may fail intermittently. The upgrade will be applied between 21:00 and 21:30 (UTC) on 24th March, 2025.Data plane operations such as SQL queries will continue to work as normal.Other Forge storage capabilities will not be impacted during this maintenance window.

The incident has been resolved. Users who have not refreshed their pages since the fix was deployed may continue to experience the issue until they perform a refresh.

The fix has been deployed. We will monitor it for the next few hours.

Since 2:00 AM UTC on March 20, 2025, we have been observing failures of invoke API calls on the Jira Issue View. On the app developer side, errors related to schema validation can be observed. The root cause of the problem has been identified, and we are working on delivering a fix. You can expect the next update around 12:00 AM UTC.

The incident has been resolved. Users who have not refreshed their pages since the fix was deployed may continue to experience the issue until they perform a refresh.

The fix has been deployed. We will monitor it for the next few hours.

Since 2:00 AM UTC on March 20, 2025, we have been observing failures of invoke API calls on the Jira Issue View. On the app developer side, errors related to schema validation can be observed. The root cause of the problem has been identified, and we are working on delivering a fix.You can expect the next update around 12:00 AM UTC.

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.

The scheduled maintenance has been completed.

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

We will be undergoing scheduled maintenance during this time.

The issue is resolved now.

The Apps tab on Manage Vendor page - https://marketplace.atlassian.com/manage/vendors/{vendorId}/addons is not showing list of apps owned by the vendors. There is additionally an impact to the 1% customers using Marketplace website to search apps. We have identified the root cause of this issue and are working on fixing it. Please expect an update in the next 2 hours.

Issue has been addressed and incident is resolved. Discounts field is now populated as expected

The fix has been implemented and deployment is in progress. We will keep you updated on the progress

We have identified discounts array field is missing for transactions impacting transactions API, and we are working on the fix. We will keep you posted and share next update in around an hour.

Today between 14:25-16:00 UTC and 16:15-16:30 UTC portion (up to 17%) of Forge app invocations has failed due to degradation of service handling Forge function invocations. Affected customers observed errors while interacting with apps. The incident has been resolved - no further invocation failures are happening since 16:30 UTC.

We have recovered service and are closely monitoring it's operation - forge invocations should be function at the moment.

We are investigating incident where forge app invocations are failing. We will post update once more details are established. The Forge apps may observe failed invocations or increased latency.

Between 2025-02-21 5:20 UTC and 2025-02-26 12:20 UTC an incremental deployment of change in relation to dropdown buttons on Jira software boards introduced regression causing buttons provided by apps to not function correctly. The observed behavior on customer side was that clicking a button wasn't triggering any action, where it was expected that user should be redirected to app UI. This issue was only affecting actions which trigger page navigation - apps using modal dialog were not affected. This problem has been resolved at 12:20 UTC. Due to technical mechanism of release, a small portion of users may be still affected until board page is refreshed - please advice customers to reload page if the issue still persist.

We applied a fix and made adjustments to the statuses of the affected AMS tickets. This issue is now resolved.

We applied a hotfix and monitoring the change in production.

We have identified the issue of old Duplicate AMS tickets being reopened in AMS, and we are currently working on a fix.

The fix has been applied and rate limiting is not occurring anymore. The impact started around 2025-02-11 4:12 UTC with small amount of rate limit events and has grown up with the traffic until 2025-02-11 8:35 UTC when fix has been applied and rate limiting stopped completely. Web Triggers are fully operational. This incident is now resolved.

We have identified problem causing overly aggressive rate limiting of Forge Web Trigger invocations. The fix is being currently rolled out. We will post next update by 09:00 UTC.

This incident is now resolved. The Partners should be able to see the correct data for all the fields in the response.

The issue is identified and a fix is being implemented.

We're sending empty values intermittently in the Licenses and Transactions reports for the below fields: - partnerDetails.billingContact - partnerDetails.partnerName - partnerDetails.partnerType This would be impacting all the Marketplace Partners.

The issue has been resolved, and the App Listing functionality has been restored.

The issue has been identified, and the team is prioritising a hotfix rollout. The impact is primarily on Confluence trial customers, while Jira remains largely unaffected, as early mitigation prevented deployment to all shards.

This incident has been resolved.

We have fixed an issue in the Forge UI Bridge API that prevented subscribers from receiving events. This impacted Forge apps using the event.emit and event.on methods from the API in Jira and Confluence. Impact started: Confluence: 2025-01-17 05:00 UTC Jira: 2025-01-20 08:00 UTC The incident has been resolved in all regions as of 2025-01-23 08:40 UTC.

We have developed a fix to resolve the issue impacting Forge apps not receiving events via the Forge UI Bridge. We anticipate the deployment will occur over the next 2-3 hours. We will provide another update by 2021-01-23 08:00 UTC, in 2 hours from now

We have identified the issue impacting Forge apps not receiving events via the Forge UI Bridge. We are creating a fix and will deploy once ready. We will provide an update 2025-01-23 06:30 UTC in 2 hours from now

We have identified the issue preventing events being sent with the Forge UI bridge API in some apps. We are now working on a fix and will provide an update by 2025-01-23 03:30 UTC, in 2 hours from now.

We are investigating an issue where Forge apps my not receive events from the Forge UI Bridge. This will cause Forge apps to operate inconsistently or not at all. We will provide another update by 2025-01-23 01:30 UTC, in 2 hours from now.

This incident has been resolved. A fix was deployed on 2024-01-22 15:00 UTC which have mitigated the issue. Re-installation of the app will trigger the lifecycle hook which will allow app to complete installation process. This is final update for this incident.

We believe we have identified the root cause of this issue and are working on a solution. If you observe this error, retrying the installation may resolve the issue. We will provide another update once we have deployed the fix.

We have identified an intermittent problem installing some Forge apps on Confluence. This only impacts Forge apps that have migrated from Connect. The error message is "LIFECYCLE_HOOK_FAILED: Request to <<url>> failed. Check the app host is available and try again." If you observe this error, retrying the installation may resolve the issue. We are investigating the root cause and will provide an update once we have more information.

We've confirmed the issue no longer affect customers. Resolving he incident.

The fix was fully rolled out. We've verified internally service is now fully operational. We will monitor situation for next 1 hour and resolve the incident when confirmed with customers all is back to normal.

We've prepared a fix for the issue and are currently rolling it out. It should be fully rolled out ~1PM UTC. We will provide another update by 2025-01-21 13:30 UTC, in 4 hours from now.

We have identified a problem preventing customers from being able to update major versions of Forge or Connect to Forge apps in both UPM and Connected Apps. This only impacts Jira. Customers who attempt to update at this time will see an error message. 2025-01-15 07:30:00 UTC: impact start We have identified the root cause and are fixing the issue. We will provide another update by 2025-01-21 09:15 UTC, in 2 hours from now.

The incident has been resolved and the data pipelines were re-run. The reporting APIs and the UI are functioning as expected are fully operational. There has been no data loss due to this incident and all the 3 reported APIs and Marketplace reporting UI is fully operational.

The issue root cause of the incident has been identified and the fix is being worked upon. Next update will be provided at 06:15 UTC

Due to upstream service changes, the following Marketplace Reporting APIs are currently unavailable: Conversions: Get Cloud conversions Renewals: Get Cloud renewals Churn: Get Cloud churn Additionally, the Marketplace reporting UI for Cloud conversions, renewals, churn reports, and the app filter in other reports is impacted. The root cause is under investigation, with the next update scheduled for 2:30 PM UTC. We sincerely regret the inconvenience caused.

Between 14/Jan/25 5:30 AM UTC to 14/Jan/25 7:52 AM UTC, we experienced failures in installations for all paid apps on certain cloud sites, we have mitigated the problem and are now monitoring closely.

Due to changes in an upstream service of the reporting pipeline on December 18, 2024, the applicationKey field in the Marketplace reporting feedback APIs was incorrect. We have now fixed the issue and partners should be able to see the correct parent product value (e.g. "jira" or "confluence") in the API response. We deeply regret any inconvenience caused due to this issue.

Between 19/Dec/24 5:00 AM UTC to 20/Dec/24 12:00 AM UTC, we experienced an issue causing intermittent errors for Connect app history API for Jira. The issue has been resolved and the service is operating normally.

We have identified an issue causing intermittent errors for Connect app history API for Jira. Some Connect Apps relying on the history API may not be able to navigate between pages Impact Start Time: 2024-12-19 05:00 UTC We have deployed a fix, and are currently validating the solution.

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.

This incident was resolved by hotfix and rolled out to all environments by 2024-12-02 07:06 UTC. We apologize for any inconveniences this may have caused you, your team, and our mutual customers.

A hotfix is rolling out to all environments and expected to complete within the next 2 hours. We will continue to monitor the issue during this time and provide an update to confirm the impact is mitigated.

We have identified the root cause in a code path that processes the response from loading static macro content. A fix has been produced and is going through QA to ensure the issue is resolved before rolling out to all sites. We expect to resolve the issue across all Confluence sites by the end of the day.

We have identified a problem with Connect where Confluence macro rendering is degraded. We are investigating the root cause and will provide another update by 02:00 UTC.

At 2024-10-29 10:00 UTC users using the latest Forge CLI v10.8.0 would be facing issues including creating new Forge apps. Developers would receive the error: Error: The "path" argument must be of type string. Received undefined Users who installed the latest version need to downgrade the CLI to version 10.7.0 using npm install -g @forge/cli@10.7.0 for anyone who is on 10.8.0 version currently. You can know the current version you are in by executing the forge --version command The issue was mitigated at 2024-10-30 5:20 UTC where users using the latest Forge CLI ( npm install -g @forge/cli@latest) will automatically point to 10.7.0 The team apologies for inconvenience caused. There will be no further communications for this incident.

The incident has been resolved and monitoring did not identify any further issues.

The issue has been identified the the team is working on fixing the issue. The missing data has been restored for the reported apps so far. The team continue to identify any further impact - beyond the reported apps - and will take the corrective action, if needed. The issue remains under investigation and correction mode.

Some of the Marketplace apps are missing the categories and keywords information. The team is investigating the issue at the moment and will share the next update soon.

This incident has been resolved on 01-11-2024 5:00 am UTC 6:08 am

This incident has now been resolved. All deployments are now successful.

We are continuing to monitor for any further issues.

We are monitoring an issue where Forge app deployment failed during 01-11-2024 5:00 am UTC to 6:08 am with an error. If customers have tried to deploy during the time window and failed, re-deployment will fix the issue. This issue is resolved now and we are monitoring the fix.

This issue is now resolved and performance is back to normal. We recommend any apps deployed between 9:24 UTC on 2024-10-23 05:56 UTC 2024-10-25 to be re-deployed in case the app users identify any latency issues.

Between 08:59 UTC and 9:24 UTC on 2024-10-23 we have observed increased error rate on app deployments, similar to problem that happened on 2024-10-24. After investigation we found an condition in one of cells in EU region which was causing deployments to fail. We applied change to migrate new deployments off the impacted EU cell which mitigated impact. We are keeping this incident in monitoring state and will resolve it once underlying issue is resolved and deployments are resumed to the affected cell. From perspective of App developers this means that deployments of apps (new apps and updates to existing ones) will work correctly but may introduce minor performance degradation due to function being invoked from nearest EU cell when customer is located in the affected cell. Because of this we will post an update advising to re-deploy affected apps once this incident is resolved.

Deployments of Forge apps in all EU cells are confirmed to be proceeding normally. We are now setting this issue as resolved. Timeline 2024-10-22 08:58 UTC: deployments in one EU cell began to fail intermittently 2024-10-22 09:48 UTC: we moved deployments off the impacted cell, which resolved the issue 2024-10-23 00:25 UTC: all EU cells are confirmed to be operating normally If you deployed apps between 2024-10-22 08:55 UTC to 2024-10-23 00:25 UTC and require them to deploy to the eu-west-1 region, we recommend deploying those apps again.

Between 08:55 UTC and 9:50 UTC on 2024-10-22 we have observed increased error rate on app deployments. After investigation we found an condition in one of cells in EU region which was causing deployments to fail. We applied change to migrate new deployments off the impacted EU cell which mitigated impact - no new errors were since 9:50 UTC. We are keeping this incident in monitoring state and will resolve it once underlying issue is resolved and deployments are resumed to the affected cell. From perspective of App developers this means that deployments of apps (new apps and updates to existing ones) will work correctly but may introduce minor performance degradation due to function being invoked from nearest EU cell when customer is located in the affected cell. Because of this we will post an update advising to re-deploy affected apps once this incident is resolved.

This issue is now fixed.

We have observed that the Marketplace Search Words API is not showing latest data. We have identified the issue and are working towards fixing it. The next update will be provided as soon as we have more information.

We discovered an issue in our upstream service that affected discount data, resulting in missing values for the partnerDiscountAmount field in the transactions API for approximately 30,000 transactions (specifically refund transactions) across multiple partners. This issue has now been resolved, and partners will have access to accurate partnerDiscountAmount information for all relevant transactions.

This incident has been resolved

Issue in third party service has been mitigated, we will continue to monitor

Few reporting API calls are failing due to an issue in third party service. We are closely working with them and will share more updates in an hour

Between 24/9/24 04:30am UTC to 4/10/24 11:00am UTC, we experienced an issue that prevented automatic minor version upgrades for Connect on Confluence and Jira. The issue has been resolved and the service is operating normally.

We continue to work on resolving the minor version update issue for Confluence and Jira. We have identified the root cause and resolved the issue for Connect Jira Apps. Minor version updates will be processed over the next 24 hours. We are working through a fix for Confluence and expect recovery over the coming hours.

We are investigating reports of automatic minor version upgrades for Atlassian Connect not running successfully. We will provide more details once we identify the root cause.

We have monitored this issue and confirm that the issue is resolved.

We've identified the cause and have mitigated the impact. We're monitoring for changes to service behavior.

We're investigating reports of authentication issues for requests to Jira Service Management endpoints via Connect apps.

Between Oct 01, 2024 - 17:49 UTC and Oct 01, 2024 - 19:43 UTC we identified a temporary outage with Atlassian Developer products. All affected products are now back online and no further impact has been observed.

We are continuing to investigate this issue.

We are investigating issues with the Partner Support Portal and will provide updates here soon.

The issue has now been resolved.

The issue has been mitigated in the upstream dependency and is being monitored.

The issue has been identified in the upstream dependency and potential mitigation paths are being worked on.

The cause for the failures is due to an issue in the dependent upstream service and is being investigated.

This incident has been resolved.

We identified a bug because of which there was incorrect mapping for the current to previous transaction for few transactions which had caused the saleType update for few transactions recently. We are correcting them up and this would impact around 2500 records. We are actively working on deploying the changes.

We have identified and resolved a problem with Forge app installation functionality, where most installations on Jira Cloud and Confluence Cloud were failing with the message "Error performing sync with Connect". This affected installations performed via any mechanism. Here is the timeline of the impact: - 2024-09-14 10:27 UTC: impact start - 2024-09-15 12:55 UTC: impact resolved for Jira app installation - 2024-09-15 13:19 UTC: impact resolved for Confluence app installation Impact has already been resolved. Developers or end users can retry any installations that previously failed, and they will now succeed.

A change was rolled out to production 5 hours ago to mitigate a security risk which had the unintended consequence of disallowing apps from impersonating JSM Customers. This change has since been rolled back and impact is resolved now. For Partners: This incident is limited to Atlassian apps which use the Connect app framework.

We discovered a recent issue affecting apps that participated in the Dual Licensing program via the Marketplace UI toggle option, which may have resulted in the loss of migration data. This issue has not affected any migrating customers. The issue has been fixed, and we will contact the affected partners via ECOHELP tickets to provide guidance on re-entering the migration information. We apologise for any inconvenience this has caused.

This incident has been resolved. The impact time was on 5th September, between 17:40 and 19:20 UTC.

The situation has returned to normal. Nevertheless, we will keep monitoring the underlying services to prevent any potential recurrences and we will undertake a thorough root cause analysis.

Starting from 17:40 UTC 5th September developers may experience issues with creating apps and managing them via Developer Console and with use of Forge CLI. Similarly, the admin experience is affected and admins may experience difficulties with displaying connected apps. We are investigating the root cause of the issue. You can expect the next update around 21:00 UTC.

We are currently investigating an incident where Forge paid apps on some sites cannot be installed between 5th September 1 AM UTC to 9th September 5 PM UTC. This is caused by invalid data sent during the installation process - this is now fixed and the functionality is back to normal. All apps which failed installation, will need to be reinstalled.