Update - We have identified an issue with the Forge Developer Console not displaying data on the Usage and Charges page. We are actively working to resolve this issue and will provide more details within the next hour.
Dec 16, 2025 - 05:47 UTC
Identified - We have identified an issue with the Forge Developer Console, which is not displaying data on the Usage and Charges page. We are actively working to resolve this issue and will provide more details within the next hour.
Dec 16, 2025 - 05:47 UTC
Resolved -
The rollback required to resolve this issue is now completed, and we have verified across the impacted products that App installation behaviour is now working as expected. We apologize for any inconvenience this may have caused.
Dec 11, 04:37 UTC
Identified -
Our team has identified a root cause for this issue, and have now commenced a rollback of the problematic change and verifying that this is resolved.
There should not be any impact to currently installed apps as a result of this incident. However, we are aware that cloud migrations including Confluence Apps may also currently be blocked by this issue.
We currently expect the rollback and validation of the fix to be completed within 3 hours. We will update further at that time with the latest status.
Dec 11, 02:08 UTC
Investigating -
We are aware that customers are currently experiencing installation failures when attempting to install Connect on Forge apps into Confluence. Our team is investigating with urgency and we will provide an update within the hour.
Dec 11, 01:08 UTC
Resolved -
Between Dec 8 05:30 UTC and Dec 9 05:30 UTC, new Forge app versions were not auto-published to Atlassian Marketplace. We’ve implemented a mitigation and auto-publish is operating normally.
Action required: If you deployed during this window, please manually publish those versions in Marketplace (or re-deploy your app with forge deploy).
We’re sorry for the inconvenience.
Dec 9, 08:14 UTC
Resolved -
The feature flag causing the issue has been reverted, fixing the problem. With that this incident is resolved.
Dec 5, 12:09 UTC
Update -
Customers continue to encounter a permission error when accessing tickets: No Access - You do not have permission to view this request.
Ticket creation works and created tickets are visible to the Atlassian teams.
The Atlassian team is engaged and continues investigation. However, the root cause remains unclear. We will provide next update in 3 hours or sooner.
Dec 5, 11:06 UTC
Update -
Customers encounter a permission error when accessing tickets: No Access - You do not have permission to view this request.
Ticket creation works and created tickets are visible to the Atlassian teams.
The Atlassian team continues investigating. The root cause remains unclear. We will provide next update in 60 minutes.
Dec 5, 09:56 UTC
Update -
Customers encounter a permission error when accessing tickets: No Access - You do not have permission to view this request.
Ticket creation works and created tickets are visible to the Atlassian teams.
The Atlassian team continues investigating. The root cause remains unclear.
We will provide next update in 60 minutes.
Dec 5, 09:23 UTC
Investigating -
We are aware that access to created Ecohelp support tickets is not available for some of our customers. Our team is investigating this issue.
Repeat creation of tickets is not required as the created tickets are visible to the Atlassian teams.
We will provide next update in 60 minutes.
Dec 5, 08:08 UTC