Delay in the Marketplace invoice data
Investigating - We are currently experiencing a delay in Marketplace invoice data due to an unidentified issue with our upstream services. As of now, no new invoices have been processed since 3:30 am UTC. We are actively working to identify the root cause of this issue. We will provide an update by 8:30 am UTC
Apr 19, 2024 - 05:31 UTC
Forge Hosted Storage Scheduled Data Residency Rollout
In progress - We have started the rollout of data residency for Forge hosted storage, where data will be moving to the same location as the host product. We expect the rollout to be completed by Apr 30, 2024 00:00 UTC.

Please refer to https://developer.atlassian.com/platform/forge/changelog/#CHANGE-1556 for more information.
Mar 28, 2024 - 03:12 UTC
Scheduled - We will be commencing rollout of data residency for Forge hosted storage. As part of this rollout, we will be moving data to the location of the host product (e.g. if an app is installed in a Jira instance whose data is pinned to Singapore, Forge Hosted Storage data will be pinned to Singapore).

This will begin on Mar 28, 2024 00:00 UTC and we expect to be completed by Apr 30, 2024 00:00 UTC. There is no expected downtime during this migration. Once the migration is complete, Forge Hosted Storage data will stored in the same location as the host product for all new and existing Forge apps.

Action Required: In order to benefit from data residency and multi-region compute, you will need to redeploy your app, and may need to declare information in your app manifest regarding remote usage of data. Please see this changelog[https://developer.atlassian.com/platform/forge/changelog/#CHANGE-1556] and our data residency documentation[https://developer.atlassian.com/platform/forge/data-residency/] for more details.

If you notice any unexpected issues during this rollout, please report via the Developer and Marketplace Support service desk [https://ecosystem.atlassian.net/servicedesk/customer/portal/34/group/96/create/571].
Mar 28, 2024 00:00 - Apr 30, 2024 00:00 UTC

About This Site

This page is intended for Atlassian developers. Please visit https://status.atlassian.com for the status of end-user features and services.

Uptime over the past 90 days. View historical uptime.
APIs Operational
90 days ago
99.98 % uptime
Today
Bitbucket Cloud APIs Operational
90 days ago
100.0 % uptime
Today
Confluence Cloud APIs Operational
90 days ago
99.92 % uptime
Today
Jira Cloud APIs Operational
90 days ago
100.0 % uptime
Today
Product Events ? Operational
90 days ago
100.0 % uptime
Today
User APIs Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
Web Triggers Operational
90 days ago
100.0 % uptime
Today
Developer Operational
90 days ago
99.97 % uptime
Today
App Deployment Operational
90 days ago
100.0 % uptime
Today
Artifactory (Maven repository) ? Operational
90 days ago
100.0 % uptime
Today
Create and manage apps ? Operational
90 days ago
100.0 % uptime
Today
Developer documentation ? Operational
90 days ago
100.0 % uptime
Today
Forge App Installation ? Operational
90 days ago
100.0 % uptime
Today
Forge CDN (Custom UI) ? Operational
90 days ago
100.0 % uptime
Today
Forge Function Invocation Operational
90 days ago
99.72 % uptime
Today
aui-cdn.atlassian.com ? Operational
90 days ago
100.0 % uptime
Today
Forge App Logs ? Operational
90 days ago
100.0 % uptime
Today
Forge App Monitoring ? Operational
90 days ago
99.95 % uptime
Today
Developer console ? Operational
90 days ago
100.0 % uptime
Today
Forge direct app distribution ? Operational
90 days ago
100.0 % uptime
Today
Hosted storage ? Operational
90 days ago
99.95 % uptime
Today
Forge CLI Operational
90 days ago
100.0 % uptime
Today
End-user consent ? Operational
90 days ago
100.0 % uptime
Today
Forge App Alerts ? Operational
90 days ago
100.0 % uptime
Today
Marketplace ? Degraded Performance
90 days ago
99.9 % uptime
Today
App listing management ? Operational
90 days ago
99.94 % uptime
Today
App listings ? Operational
90 days ago
100.0 % uptime
Today
App pricing ? Operational
90 days ago
100.0 % uptime
Today
App submissions Operational
90 days ago
100.0 % uptime
Today
Category landing pages Operational
90 days ago
100.0 % uptime
Today
Evaluations and purchases Operational
90 days ago
100.0 % uptime
Today
In-product Marketplace and app installation (Cloud) ? Operational
90 days ago
99.94 % uptime
Today
In-product Marketplace and app installation (Server) ? Operational
90 days ago
99.94 % uptime
Today
Notifications ? Operational
90 days ago
100.0 % uptime
Today
Private listings Operational
90 days ago
99.01 % uptime
Today
Reporting APIs and dashboards ? Degraded Performance
90 days ago
99.86 % uptime
Today
Search Operational
90 days ago
100.0 % uptime
Today
Vendor management Operational
90 days ago
99.94 % uptime
Today
Vendor Home Page Operational
90 days ago
100.0 % uptime
Today
Authentication and user management Operational
90 days ago
99.71 % uptime
Today
Support Operational
90 days ago
100.0 % uptime
Today
Atlassian Support contact form Operational
Developer community ? Operational
90 days ago
100.0 % uptime
Today
Developer service desk ? Operational
Marketplace service desk ? Operational
Atlassian Support Operational
Vulnerability management [AMS] Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Past Incidents
Apr 19, 2024
Inconsistencies in Forge app observability metrics
Resolved - We have now resolved the issue where inflated metrics are being seen in the Developer console. This impact was witnessed between 16/Apr/24 05:00 UTC to 19/Apr/24 2:40 AM UTC.

Please note: your metrics between the impact period will continue to show inflated metrics.
Apr 19, 03:26 UTC
Investigating - We have identified inconsistencies in Forge app observability metrics. Some apps may be experiencing metrics showing an increased and inaccurate invocation count starting from 5 AM on April 16th UTC.

We have identified a potential root cause and are in the process of rolling this change back.

We will provide a further update within the next two hours.
Apr 19, 00:30 UTC
Apr 18, 2024
Intermittent Connect App Upgrade issue results in Apps in Disabled state
Resolved - The root cause has been identified and fixed, and all impacted Connect apps for Jira and Confluence have been re-enabled. Our monitoring has not observed reoccurrences of the problem.

In a previous update we advised caution in making descriptor updates as we investigated the issue and its underlying causes. Now that the problem has been resolved, you may safely proceed with making updates to marketplace apps.

[This message was updated at 2024-04-19 06:15 UTC to clarify that the underlying root cause had been addressed and that it is now safe to publish descriptor updates.]
Apr 18, 15:47 UTC
Monitoring - All identified disabled Connect apps for Jira and Confluence have been enabled. Major impact is mitigated as for now.

We will continue monitoring the situation. Will provide another update in 24 hours (by 2024-04-17 10:00 UTC).
Apr 16, 10:25 UTC
Update - We continue to investigate the intermittent enablement failures impacting some Connect apps. Concurrently, we are also exploring a pathway to re-enable impacted app installations, so that apps will be restored for customers.

We will post updates within the next 3 hours.
Apr 16, 07:02 UTC
Investigating - In response to some recent customer and partner support tickets which have been raised, we have identified that since 2024-04-08 there have been some Connect app installations and updates which have immediately entered a disabled state. This behaviour is affecting multiple apps and appears to be inconsistent in nature.

The impact relates to any new Connect app installation or any updates which occur to a Connect app. For this reason, we suggest that marketplace partners hold off on any descriptor updates until this incident is resolved.

For affected customers that are unable to re-enable these apps, the immediate workaround is to uninstall and reinstall the app, forcing the app to attempt enablement once again.

We do not yet have any expected resolution time or any other mitigations for apps or customers.

We will continue to investigate the cause of this incident and provide another update by 2024-04-16 07:00.
Apr 16, 05:39 UTC
Delay in Marketplace reporting data
Resolved - Marketplace reporting data was delayed by 1.5hrs due to issue in downstream services. Issue has been fixed and data flow is restored.
Apr 18, 02:00 UTC
Apr 17, 2024

No incidents reported.

Apr 16, 2024
Apr 15, 2024

No incidents reported.

Apr 14, 2024

No incidents reported.

Apr 13, 2024

No incidents reported.

Apr 12, 2024

No incidents reported.

Apr 11, 2024

No incidents reported.

Apr 10, 2024
Backfilling few missing licenses in licenses reporting APIs
Resolved - Missing licenses are backfilled and the incident is resolved.
Apr 10, 09:18 UTC
Identified - We have noticed around 12k inactive licenses were missing in licenses reporting APIs. We have identified the issue and deployed the fix. Pipeline run is in progress. We will send next update once the missing licenses are backfilled. We apologise for any inconvenience caused.
Apr 10, 05:42 UTC
Apr 9, 2024

No incidents reported.

Apr 8, 2024
Webhooks not dispatched to Atlassian Connect apps for content deleted during permanent space deletion
Resolved - Apps built on the Atlassian Connect platform can subscribe to webhooks notifying them when content is deleted in Confluence. Historically, these webhooks are sent individually when a user deletes a single piece of content, or in rapid succession for all content in a space if an administrator permanently deletes that space (as described in https://support.atlassian.com/confluence-cloud/docs/delete-a-space/#Permanently-delete-a-space).

Historically, permanent deletion has been slow and/or unreliable for spaces containing large amounts of content, resulting in frequent customer issues and support requests. In early March we rolled out some changes designed to improve the stability and performance of Confluence’s permanent space deletion functionality. These updates included shifting much of the deletion logic from the application layer into optimised bulk deletion SQL queries.

Unfortunately these changes had the unintended side-effect of preventing content deletion webhooks from being dispatched during permanent space deletions. While permanent deletions are infrequent, this change in webhook behaviour may have had an adverse impact on apps that are subscribed to them. Because of this, we have rolled back the change and have recommenced sending webhooks for content deletions that occur when a space is permanently deleted.

The problematic changes were progressively rolled out for all customers between March 7th at 20:10 UTC and March 11th at 18:20 UTC. The changes were rolled back on April 3rd at 06:27 UTC. Apps built on the Atlassian Connect framework will not have received the following webhooks for content deleted during a permanent space deletion on a site with the changes enabled:

- page_removed
- blog_removed
- attachment_removed
- comment_removed
- content_removed

Note that webhooks were delivered as normal for any content deletions that occurred outside of the context of a permanent space deletion.

We have reached out to all app developers whom we believe were impacted by this incident. If you believe you are impacted and have not been contacted via email or an ADDON issue, please submit a "Bugs" ticket at https://ecosystem.atlassian.net/servicedesk/customer/portal/34/group/106/create/567 and mention “confluence-webhooks-2024” in the ticket subject - we will endeavour to support you.

Our sincerest apologies for any inconvenience this has caused you or our mutual customers.
Apr 8, 06:24 UTC
Apr 7, 2024
Forge Storage Intermittently Blocking Some Apps to Forge Storage
Resolved - This incident has been resolved.
Apr 7, 22:59 UTC
Monitoring - Forge apps may have received intermittent errors when calling Forge Storage. This impacted approximately 0.5% of Storage read or write requests. In Forge logs, the error would read, "Request principal is not authorized to use storage resource". Forge apps that implement retries likely detect this as an increase in retries.

We observed an increase in errors beginning March 11.

The team believe they have identified the cause and have deployed a fix. Due to the intermittent nature and low volume of errors, we will continue to monitor to ensure the issue has been fully resolved.

We will update this issue with further information once we are confident the issue is fixed.
Mar 25, 06:50 UTC
Update - We continue to investigate the issue with a small number of requests to Forge Storage failing. We will provide another update in 3 hours or earlier if we have more information to share.
Mar 25, 02:34 UTC
Update - We continue to investigate the intermittent Forge Storage failures impacting some Forge apps. We will post updates within the next hour.
Mar 25, 01:10 UTC
Investigating - In response to some support tickets raised we have identified that since 2024-03-12 there has been a significant increase in failures for Forge apps calling the Forge Storage API. These failures are affecting multiple apps and appear to be inconsistant in nature. This impacts Forge Apps ability to retrieve and/or persist data using Forge Storage.

We do not yet have any expected resolution time or mitigation for apps or customers.

We will continue to investigate the cause of this incident and provide another update by 2024-03-25 01:00.
Mar 24, 23:39 UTC
Apr 6, 2024

No incidents reported.

Apr 5, 2024

No incidents reported.

← Incident History Powered by Atlassian Statuspage