Atlassian Developer Status - Incident History

Confluence Webhooks are not being delivered

Wed, 22 Oct 2025 22:09:20 +0000

Oct 22, 22:09 UTC
Resolved - Between 01:00 and 20:47 UTC on October 22, 2025, App Developers experienced an issue where Confluence webhooks were not being delivered. We have deployed a fix to mitigate the problem, and the service is now operating normally.

This outage did not affect Forge events. However, it did impact:
1) All Connect Apps
2) Forge apps that use webhooks via connectModules

Please note: Atlassian cannot replay or resend the missed webhook events. As a result, these events are permanently lost.

Recommended Action:
To recover, we recommend that all affected apps use their resynchronization (resync) mechanisms to fetch the latest data directly from Confluence. This will help ensure your app’s data is up to date and that any information missed during the outage is restored.

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 to prevent this from happening again in the future.

Oct 22, 20:07 UTC
Update - We have identified the issue causing Confluence Webhooks to not be delivered. We are currently testing a fix internally. We will provide another update at 22:00 UTC, or sooner if the fix is applied or new information becomes available.

Oct 22, 19:09 UTC
Identified - We have identified the issue causing Confluence Webhooks to not be delivered and are in the process of applying mitigations. We will provide another update at 20:00 UTC, or sooner if the mitigation is applied or new information becomes available.

Oct 22, 16:16 UTC
Update - We are continuing to investigate the issue causing Confluence Webhooks to not be delivered. While we have not yet identified the root cause, our team is making progress. We will provide another update at 18:20 UTC, or sooner as new information becomes available.

Oct 22, 14:20 UTC
Update - We are continuing our investigation. We will provide the next update within two hours or sooner.

Oct 22, 13:14 UTC
Update - Our team continues to investigate this issue. We will provide the next update within one hour or sooner.

Oct 22, 12:15 UTC
Investigating - We are aware that Confluence Webhooks are not being delivered and our team is actively investigating the same. We shall provide next update in one hour, if not sooner.

Atlassian Cloud Services impacted

Tue, 21 Oct 2025 05:24:25 +0000

Oct 21, 05:24 UTC
Resolved - Our team is now able to see full recovery across the vast majority of Atlassian products.

We are aware of some ongoing issues with specific components such as migrations and JSM virtual service agents, and our team is continuing to investigate with urgency.

We apologise for the inconvenience that this incident has caused and we will provide further information when the Post Incident Investigation has been completed.

Oct 21, 03:24 UTC
Update - The issue relating to the Atlassian Support portal displaying a message to customers to use our temporary support channel has now been resolved. The Atlassian Support portal is fully functional for any ongoing support issues.

With regards to other Atlassian products, we continue to see recovery continuing across all impacted products and our teams are continuing to monitor as the recovery continues.

We will provide further update on our recovery status within two hours.

Oct 21, 01:07 UTC
Update - We continue to see recovery progressing across all impacted products as backlogged items continue to be processed.

The Atlassian Support portal is currently displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message.

We will provide further update on our recovery status in two hours.

Oct 21, 00:03 UTC
Update - Our team is now seeing recovery across all impacted Atlassian products. We are continuing to monitor for individual products that may still be processing backlogged items now that services are restored.

The Atlassian Support portal is currently still displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message.

We will provide further update on our recovery status in one hour.

Oct 20, 22:58 UTC
Update - Our teams are continuing to monitor the recovery of systems across Atlassian products. This update is to inform that the Atlassian Support portal is fully operational at this time for customers that wish to contact support.

Oct 20, 21:26 UTC
Update - Monitoring - We've started seeing continued product experience improvement.

While we still have a backlog of event processing, we are seeing improvements in systems operational capabilities across all products. We estimate a significant improvement with the next few hours and will continue to monitor the health of AWS services and the effects on Atlassian customers. We appreciate your continued patience and remain committed to full resolution as we work through this situation. We will post our next update in two hours.

Oct 20, 18:38 UTC
Monitoring - There have been no changes since our last update. We will provide our next updated by 9:00PM UTC or sooner as new information becomes available.

We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation.

Oct 20, 17:43 UTC
Update - We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.

Oct 20, 17:27 UTC
Update - Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.

Oct 20, 16:36 UTC
Update - Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and while we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will be providing hourly updates on this issue.

Oct 20, 16:35 UTC
Update - Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and while we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will be providing hourly updates on this issue.

Oct 20, 15:21 UTC
Update - Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.

Oct 20, 15:20 UTC
Update - Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.

Oct 20, 14:02 UTC
Update - We understand your pain and mitigating or fixing this issue is of utmost importance. Our public cloud provider is actively working to mitigate this issue on priority. We have been seeing partial operational success. We appreciate your patience and will continue to provide updates every hour or sooner.

Oct 20, 13:58 UTC
Update - Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

Oct 20, 13:56 UTC
Update - Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

Oct 20, 13:07 UTC
Update - Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

Oct 20, 12:06 UTC
Update - Atlassian team is actively engaged and continues to work with our public cloud provider to mitigate this issue at the earliest. We are starting to see partial operations succeed. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

Oct 20, 11:06 UTC
Update - We continue to work with our public cloud provider towards mitigating the issue at the earliest. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

Oct 20, 09:58 UTC
Identified - We understand that our public cloud provider has identified the cause of the issue. We are starting to see some recovery and is working towards mitigation. We appreciate your patience.
We shall continue to share updates every hour, if not sooner.

Oct 20, 09:24 UTC
Update - We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment.
We shall continue to share updates every hour, if not sooner.

Oct 20, 09:23 UTC
Update - We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment.
We shall continue to share updates every hour, if not sooner.

Oct 20, 08:24 UTC
Update - Atlassian Cloud services are impacted and we are aware that our customers might not be able to create support tickets. Our teams are actively investigating the same.
We shall keep you informed of the progress every hour.

Oct 20, 07:56 UTC
Investigating - We have noticed that Atlassian Cloud services are impacted and our teams are actively investigating the same.
We shall keep you informed of the progress every hour.

Forge authenticated egress intermittent failure

Sun, 12 Oct 2025 19:25:16 +0000

Oct 12, 19:25 UTC
Resolved - Between 06:58 12 Oct UTC to 18:30 12 Oct UTC, we experienced calls from a some forge apps to external services (outside of Atlassian) intermittently fail. The issue has been resolved and the service is operating normally.

Oct 12, 18:33 UTC
Monitoring - We have identified the root cause of the intermittent errors and have mitigated the problem by putting in a temporary measure.

We are now monitoring closely.

Oct 12, 17:19 UTC
Update - We are deploying a fix that will alleviate some of the issues.
We are still investigating the root cause behind the intermittent failures.
Our team continues to closely monitor the errors and explore additional mitigations to ensure stability.

Oct 12, 15:25 UTC
Investigating - Impact
The issue is affecting Forge Egress within the Ecosystem, leading to intermittent failures in authenticated egress calls.
This has impacted functionalities such as Jira Incoming Mail, causing delays in fetching emails from providers like Gmail and Microsoft, and consequently affecting work item creation.
Additionally, Forge Compass apps are currently failing to send data to Compass.

Current Status
We have identified the root cause and are in the process of deploying a fix.

Next Steps
Post-deployment, we will continue to closely monitor the fix to ensure stability.
The next update will be provided in 60 minutes.

Forge authenticated egress intermittent failure

Sun, 12 Oct 2025 09:14:40 +0000

Oct 12, 09:14 UTC
Resolved - Between 06:30 12th Oct, 2025 UTC to 08:33 12th Oct, 2025 UTC, we experienced a degradation in us-east and ca-central regions affecting authenticated egress calls from Forge functions and from Forge bridge.

The issue has been resolved and the service is operating normally.

Oct 12, 08:51 UTC
Monitoring - The errors have gone down and not occurred in the last 30 minutes. The issue has been mitigated and we are continuing to monitor the situation closely.

Oct 12, 07:29 UTC
Investigating - We are aware of an intermittent issue affecting some authenticated egress calls from Forge functions and from Forge bridge (including product API calls).

The issue is primarily affecting invocations in the us-east and ca-central regions.

We are investigating the root cause and will provide an update in 1 hour.

Scheduled Maintenance for systems impacting Forge app lifecycle

Sun, 12 Oct 2025 04:00:21 +0000

Oct 12, 04:00 UTC
Completed - The scheduled maintenance has been completed.

Oct 12, 03:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Oct 2, 01:47 UTC
Scheduled - Atlassian will be undergoing scheduled maintenance with up to 1 minute of downtime in the commercial perimeter on 2025-10-12 between 3am to 4am UTC.
During the write outage, you won’t be able to:
- Create/upgrade/delete apps
- Install/uninstall apps
- Upgrade installations
- Deploy app
- Grant/revoke access for apps
- Grant consent to apps
- Revoke consent to apps
Expect to see the above operations fail with 500 status code and you will need to retry the operations after maintenance is successfully completed.
We will continue to provide updates as we progress and when you can expect these services to be restored.

Forge app user OAuth consent prompt being shown unnecessarily

Fri, 03 Oct 2025 06:24:19 +0000

Oct 3, 06:24 UTC
Resolved - Between 29 Sep 2025 07:10 UTC and 03 Oct 2025 06:00 UTC, some customers experienced unexpected Allow access OAuth consent prompts when using the Forge app UI. The issue has been resolved, and the service is operating normally.

Oct 3, 06:04 UTC
Monitoring - We identified the root cause of the unexpected Allow access prompts in Forge app UI and have mitigated the problem. We are now monitoring closely.

Oct 3, 03:43 UTC
Identified - We are currently experiencing an issue where some Forge app users are seeing unexpected Allow access OAuth consent prompts when first using the app UI. There is no security impact; affected users can proceed by approving the prompt and continue using the app normally.
This primarily affects apps that use auto‑consent with UI, including newly installed apps and upgraded apps where permissions changed and the user does not already have a consent grant. Our engineering team has identified the cause and is deploying a fix. We will provide our next update by 06:00 UTC.
We apologize for the inconvenience and appreciate your patience.

Delays in Dev Console log delivery

Mon, 29 Sep 2025 17:07:09 +0000

Sep 29, 17:07 UTC
Resolved - Between 08:30 AM UTC to 16:30 UTC on September 29, 2025, some developers experienced delays of log delivery for the Dev Console. The root cause was an unexpected spike in volume that required updates to autoscaling configurations to address. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we’re actively working on a permanent fix. The issue has been resolved and the service is processing logs normally. We are currently processing the delayed logs and anticipate completion by 17:00 UTC today, September 29, 2025.

Sep 29, 15:32 UTC
Identified - We are investigating cases of degraded performance of log delivery for some app developers. We are working on implementing a fix. We will provide more details within the next hour.

Scheduled Maintenance for systems impacting Forge app lifecycle

Sun, 28 Sep 2025 05:00:21 +0000

Sep 28, 05:00 UTC
Completed - The scheduled maintenance has been completed.

Sep 28, 04:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Sep 19, 09:38 UTC
Scheduled - Atlassian will be undergoing scheduled maintenance with up to 1 minute of downtime in the commercial perimeter on 2025-09-28 between 4am to 5am UTC.

During the write outage, you won’t be able to:

- Create/upgrade/delete apps
- Install/uninstall apps
- Upgrade installations
- Deploy app
- Grant/revoke access for apps
- Grant consent to apps
- Revoke consent to apps

Expect to see the above operations fail with 500 status code and you will need to retry the operations after maintenance is successfully completed.
We will continue to provide updates as we progress and when you can expect these services to be restored.

Marketplace Reporting APIs and Partner Portal Disruption

Fri, 26 Sep 2025 10:45:55 +0000

Sep 26, 10:45 UTC
Resolved - Issues affecting Marketplace Reporting APIs and Partner Portal have been resolved. Both services are now back up and running normally. This incident has been resolved.

Sep 26, 10:28 UTC
Monitoring - A fix has been implemented and monitoring the fix.

Sep 26, 10:10 UTC
Update - We are continuing to work on a fix for this issue.

Sep 26, 10:09 UTC
Identified - We are currently experiencing technical difficulties with our internal data pipelines, resulting in 5XX errors for Marketplace Reporting APIs. Consequently, Marketplace partners are unable to access reporting APIs, and users of the Partner Portal may experience degraded performance. Our engineering team is actively investigating the issue and working diligently to resolve it as quickly as possible. We will provide regular updates as more information becomes available. We apologize for the inconvenience and appreciate your patience and understanding

JSM Assets API using connect authentications were disrupted

Thu, 25 Sep 2025 08:14:11 +0000

Sep 25, 08:14 UTC
Resolved - We experienced a disruption affecting all JSM assets APIs using Connect JWT and user impersonation for connect apps, starting on September 13th at 2:05 AM UTC and lasting until September 17th at 3:36 PM UTC. This issue was caused by an internal routing change within Atlassian systems. During this time, all Assets API calls using Connect authentications were disrupted. The issue has now been resolved, and all affected APIs are fully operational again. We sincerely apologise for any inconvenience caused and thank you for your patience and understanding.

Scheduled Maintenance of Forge FedRAMP services

Sun, 21 Sep 2025 07:00:24 +0000

Sep 21, 07:00 UTC
Completed - The scheduled maintenance has been completed.

Sep 21, 05:27 UTC
Verifying - Scheduled maintenance has been completed in the FedRAMP perimeter. Maintenance was performed on 2025-09-21 between 4am to 7am UTC.
You should now be able to:
- Create/upgrade/delete apps
- Install/uninstall apps
- Upgrade installations
- Deploy app
- Grant/revoke access for apps
- Grant consent to apps
- Revoke consent to apps
If you experienced problems with these operations during the maintenance window, please try again to determine if your issue is now resolved.
If you are experiencing ongoing issues with the above operations please contact your local Atlassian site administrator. If you need further help, please raise a support ticket at https://support.atlassian.com/#contact.

Sep 21, 04:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Sep 16, 07:06 UTC
Scheduled - Atlassian will be undergoing scheduled maintenance with ~1 hour of intermittent downtime in the FedRAMP perimeter on 2025-09-21 between 4am to 7am UTC.
During the write outage, you won’t be able to:
- Create/upgrade/delete apps
- Install/uninstall apps
- Upgrade installations
- Deploy app
- Grant/revoke access for apps
- Grant consent to apps
- Revoke consent to apps
Expect to see the above operations fail with 500 status code and you will need to retry the operations after maintenance is successfully completed.
We will continue to provide updates as we progress and when you can expect these services to be restored.

Intermittent failure on all app networking calls (including product apis, egress, storage and resolvers)

Fri, 19 Sep 2025 02:02:51 +0000

Sep 19, 02:02 UTC
Resolved - No customer impact has been observed seen since mitigation began. We are now closing this incident.

Sep 16, 00:07 UTC
Monitoring - We identified a networking issue that increased timeouts for fetch requests originating from Forge apps. A small portion (< 0.1%) of requests resulted in Connection Timeout errors. Other symptoms included timeouts in product API requests, storage calls and resolver executions.

Timeline:
2025-09-03 10:00 UTC: impact start
2025-09-15 16:56 UTC: impact mitigated

We will continue to monitor our mitigation and investigate the root cause.

Sep 15, 10:10 UTC
Update - We are continuing to investigate and mitigate the issue.
Upto 0.1% of all requests originating from Forge apps could result in Connection Timeout errors

We are continuing to diagnose the root cause and are attempting mitigation in affected regions. We will continue to monitor requests and report on any improvements.

Next Steps: We will apply the mitigation in other regions and continue to monitor. Next update will be within 4 hours.

Sep 15, 02:06 UTC
Investigating - We have identified a networking issue that is impacting fetch requests originating from forge apps. All forge-enabled products are impacted.

Impact start time: Thursday, September 4th

Symptoms include:
- product fetch call timeout
- egress fetch call timeout
- storage calls timeout
- resolver timeout

The following errors may be present in your app logs
- UND ERR CONNECT TIMEOUT
- ERR SOCKET TIMEOUT

We are currently investigating the root cause
- seeing evidence of unstable network connections between distributed infrastructure
- Packet loss
- TCP resends
- Eventual timeout on fetch operations

We will provide another update at Sep 15 7:00 AM UTC

Intermittent 500 errors on Confluence endpoint /wiki/api/v2/spaces/properties

Fri, 12 Sep 2025 11:56:02 +0000

Sep 12, 11:56 UTC
Resolved - Changes have landed in production at 11:40 AM (UTC). The issue is resolved and the endpoint is now operating normally.

Sep 12, 10:44 UTC
Identified - We have produced a fix and are releasing the changes into production. Expected resolution in 1 hour.

Sep 12, 09:41 UTC
Update - We have potentially identified the issue but verification is still ongoing. We will provide another update in an hour.

Sep 12, 08:14 UTC
Investigating - We are aware of an issue affecting one of our Confluence API Endpoints /wiki/api/v2/spaces/properties , causing it to return a 500 status code.

Impact started on Thursday 11 September at 7.45 PM (UTC).

Our team is investigating this issue with urgency and will provide further updates throughout the investigation.

We will provide an update within the next hour.

Deploying a forge app using the forge CLI

Mon, 08 Sep 2025 13:46:29 +0000

Sep 8, 13:46 UTC
Resolved - Between 12:50 UTC to 13:20 UTC, we experienced partial failures for deploying forge apps via forge cli for Atlassian Developers.
The issue has been resolved and the service is operating normally.

Sep 8, 13:35 UTC
Monitoring - We have mitigated the intermittent errors affecting some Atlassian Developer Cloud customers when deploying apps via the Forge CLI.
We are continuing to monitor the systems closely to ensure there is no further deterioration

Forge App Invocations failing intermittently

Mon, 08 Sep 2025 10:05:53 +0000

Sep 8, 10:05 UTC
Resolved - This incident is resolved now. Between 6:30 AM and 8:35 AM UTC on September 8th, there was an issue with one of the dependent vendor services, due to which invocations were intermittently failing, primarily in the EU-CENTRAL-1 Region. This issue is fixed now.

Sep 8, 08:06 UTC
Monitoring - A Fix has been implemented and we are monitoring the results

Sep 8, 07:58 UTC
Identified - The issue has been identified and is being fixed.

Sep 8, 07:44 UTC
Investigating - We are investigating an issue where app invocations are intermittently failing primarily in Eu-Central at around 6:41 am UTC. Apps will not work correctly during this time. We will update once this issue is resolved.

Some marketplace apps being uninstalled unexpectedly

Fri, 05 Sep 2025 06:16:06 +0000

Sep 5, 06:16 UTC
Resolved - Atlassian is continuing to work with a small number of application partners that are still impacted by this incident to address any further installation issues.

Sep 4, 01:39 UTC
Monitoring - Our team has identified the root cause and taken steps to prevent any future apps from being impacted. The team has also successfully re-installed the majority of affected apps. Our team is continuing work to address the remaining apps.

Sep 3, 03:29 UTC
Investigating - We are aware of an issue that is currently impacting some customers where apps are being uninstalled unexpectedly.
Re-installing the impacted Apps should restore expected functionality.
For more information on how to install apps please see the following page: https://support.atlassian.com/organization-administration/docs/installing-and-managing-app-access/
Our team is investigating this issue with urgency and will provide further update when available.

Forge invocation and deployment issue

Tue, 02 Sep 2025 18:43:18 +0000

Sep 2, 18:43 UTC
Resolved - Between September 2, 2025 14:00 and 17:15 UTC we experienced an issue with Forge invocations and Deployment failures for some customers in the US West Region. The issue has now been resolved and the service is operating normally.

Sep 2, 17:10 UTC
Identified - We have identified the cause of the issue with Forge invocations and Deployments failing for some customers. We are currently working on a fix. We will provide another update either once the issue has been resolved or within the next hour, whichever comes first.

Sep 2, 16:13 UTC
Investigating - We are investigating an issue with Forge invocations and Deployments failing for some customers. We will post another update in an hour.

401 Authorisation Errors in Forge Apps

Fri, 29 Aug 2025 03:32:33 +0000

Aug 29, 03:32 UTC
Resolved - We are aware of an issue that occurred between 00:30: UTC and 02:20 UTC on 29/08/2025, where Forge apps using Forge SQL capability may have experienced 401 authorisation errors in their apps. This issue is now mitigated.

Marketplace reporting export APIs returning the 403 error

Thu, 31 Jul 2025 06:30:00 +0000

Jul 31, 06:30 UTC
Resolved - On July 31st 06:30 AM UTC, a 403 Forbidden error was observed across all Reporting Export API requests. The issue was caused by an unintended impact from a code cleanup activity, which affected access to APIs such as Export Cloud License Events and Export Transactions.

The issue was resolved by 03:00 PM UTC on July 31st, and all Reporting Export APIs are now fully accessible to Marketplace partners.

Forge installations are not being assigned correct permissions

Tue, 29 Jul 2025 03:27:28 +0000

Jul 29, 03:27 UTC
Resolved - Our team was able to complete the resolution of this issue for all prior installations by July 24th. This incident is now resolved.

Jul 18, 04:36 UTC
Update - We have identified the cause of an issue affecting a small number of Forge app installations between July 10, 2025, and July 18, 2025, at 03:38 UTC. This issue meant that the app user was not granted the correct admin permissions during installation, resulting in failing calls to REST APIs that require the permission.

This issue will not impact new installations, and we are working on a fix for previously impacted installations.

Jul 18, 03:32 UTC
Identified - We have identified an issue where some Forge apps are receiving permission errors when calling REST endpoints that require admin permissions. We are investigating the root cause.

Jul 18, 02:49 UTC
Investigating - We are investigating an incident where app users associated with new Forge installations and Connect to Forge upgrades are not being added to Jira permission groups. We will post the next update in 30 minutes.

Forge CE Store scheduled maintenance

Sun, 27 Jul 2025 13:08:58 +0000

Jul 27, 13:08 UTC
Completed - The scheduled maintenance has been completed.

Jul 27, 11:36 UTC
Verifying - Verification is currently underway for the maintenance items.

Jul 27, 10:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Jul 27, 10:00 UTC
Update - We will be undergoing scheduled maintenance during this time.

Jul 24, 05:32 UTC
Scheduled - Forge will be migrating the Custom Entity Store metadata to a new data source. During this time, the following commands in the Forge CLI will fail for any apps that have storage:entities declared in their manifest:
* forge deploy
* forge storage entities indexes list

KVS and Custom Entity Store operations will continue to work as normal.

Forge Tunnel Outage

Tue, 22 Jul 2025 00:30:00 +0000

Jul 22, 00:30 UTC
Resolved - Between Jul 22, 2025 00:28 UTC and 01:13 UTC, developers in all regions are experiencing failures with tunnel creation in the Forge CLI.

We have investigated the issue and have identified the root cause as a temporary outage with an external vendor.

The issue has now been resolved. We are continuing to monitor the service.

Marketplace reporting data will be delayed by 8 hours on July 19, 2025

Sat, 19 Jul 2025 12:30:21 +0000

Jul 19, 12:30 UTC
Completed - The scheduled maintenance has been completed.

Jul 19, 04:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Jul 18, 07:40 UTC
Scheduled - There will be a scheduled maintenance during this time

App deployments and App invocations failed for approximately 45 mins and 100 mins respectively

Tue, 08 Jul 2025 12:30:05 +0000

Jul 8, 12:30 UTC
Resolved - Forge App deployments and invocations have experienced an outage for 45 minutes and 100 minutes approximately starting at 20250708T0934 UTC due to an infrastructure related issue
Both the services have recovered now and are working as expected

Rollout of Jira 100K user tier for the Marketplace Apps

Fri, 04 Jul 2025 15:30:21 +0000

Jul 4, 15:30 UTC
Completed - The scheduled maintenance has been completed.

Jul 4, 09:25 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Jul 4, 09:23 UTC
Scheduled - Marketplace is undergoing a rollout of Jira 100K user tier for all the apps. This upgrade will run for approximately 6 hours (till July 04 03:30 PM UTC) and during this period, the set pricing functionality of the apps will be frozen.

During this window of 6 hours of pricing freeze, new app submissions for approval will be blocked if there is a pricing change involved.