Historique des pannes de Confluence

1. 27 août 2026 à 04:22 UTCinvestigating

   Nos équipes ont identifié ce problème a également une incidence sur Jira Service Management. Nous procéderons à une mise à jour dans les plus brefs délais.

2. 27 août 2026 à 04:25 UTCinvestigating

   Nous enquêtons sur un problème d'accès aux produits qui affecte les clients de Confluence, Jira Cloud et Jira Serivce Management. Notre équipe enquête d'urgence sur cette question et nous fournirons plus de détails dans une heure ou plus tôt si des informations sont disponibles.

3. 27 août 2026 à 04:33 UTCidentified

   Nos équipes ont identifié une solution possible pour les problèmes touchant Jira Cloud, Jira Service Management et Confluence. Ce programme est maintenant mis en oeuvre dans les régions touchées et nous le mettrons à jour dans une heure, ou plus tôt si d'autres renseignements sont disponibles.

4. 27 août 2026 à 04:51 UTCmonitoring

   Les questions relatives au chargement de Jira Cloud, Jira Service Management et Confluence sont maintenant en cours de récupération. Nous continuerons à surveiller de près pour confirmer la stabilité et fournir une mise à jour dans une heure, ou plus tôt à mesure que plus d'informations seront disponibles.

5. 27 août 2026 à 05:16 UTCresolved

   Le 27 août 2026 UTC, les produits Atlassian, dont Jira Cloud, Jira Service Management et Confluence, ont connu une perturbation et les services n'ont pas été offerts aux utilisateurs touchés. Le problème a maintenant été résolu et le service fonctionne normalement pour tous les clients touchés. Un postmortem public pour cet incident sera disponible sur cette page lorsque notre enquête complète sur l'incident aura été terminée.

6. 7 septembre 2026 à 02:53 UTCpostmortem

   **SOMMAIRE** Le 27 août 2026, entre 03:51 et 04:35 UTC, les clients atlasiens des régions de l'Europe occidentale et du sud-est de l'APAC n'ont pas pu atteindre les produits Atlassian Cloud, y compris Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo Search et Talent. L'événement a été déclenché par un changement de code défectueux à la couche de routage d'une de nos flottes mandataires. Cela a conduit à des erreurs HTTP 404 servies à tous les trafics clients via ces flottes proxy en Europe occidentale et dans les régions APAC du Sud-Est. L'incident a été détecté en moins d'une minute par nos systèmes automatisés de surveillance, et atténué par le retour à la version précédente de configuration, qui a mis la flotte proxy dans un bon état connu. Après la récupération de la flotte proxy, certains clients Jira et Confluence (quel que soit leur emplacement) ont reçu des erreurs HTTP 503 entre 04:33 et 04:53 UTC en tant que flottes de serveurs ajustées à l'afflux de trafic. ** IMPACT** L'impact global a été divisé en deux périodes distinctes: - D'abord, le 27 août 2026, entre 03:51 et 04:35 UTC sur Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo Search et Talent. L'incident a causé une perturbation du trafic client en provenance des régions de l'Europe occidentale et du sud-est de l'APAC, les erreurs HTTP 404 étant retournées. Il n'y a eu aucun impact sur le trafic client API, quel que soit l'emplacement d'origine. - Deuxièmement, le 27 août 2026, entre 04:33 et 04:53 UTC, certains clients Jira et Confluence ont reçu des erreurs HTTP 503 après la résolution des erreurs HTTP 404 : ~32% des demandes dans ap-sud-est-2, ~4% des demandes dans eu-ouest-1, ~2,5% des demandes dans us-ouest-2 et ap-sud-est-1, et <1% des demandes dans toutes les autres régions mondiales. ** CAUSE DE ROOT** L'événement a été déclenché par un changement de code à une de nos flottes mandataires. Cependant, il y avait un défaut dans le code déployé qui n'a pas été détecté par des tests manuels et automatisés. Cela a conduit à une mauvaise configuration d'une fonctionnalité de recherche de locataire dans le niveau proxy, ce qui a conduit au trafic n'ayant pas de chemin de réseau valide, ce qui a conduit à des erreurs HTTP 404 servies à tous les trafics clients à travers ces flottes proxy en Europe occidentale et dans les régions APAC du Sud-Est. Après la récupération de l'impact de niveau de remplacement, une deuxième période d'impact a été causée à certains clients de Jira et de Confluence. En raison de la réduction du trafic desservi par Jira et Confluence par la flotte proxy, les niveaux de service Jira et Confluence avaient automatiquement augmenté dans le nombre de serveurs desservant le trafic client. Une fois que la fonctionnalité de flotte proxy a été rétablie, la surtension du trafic a dépassé le niveau de service Jira, qui a renvoyé un taux élevé de HTTP 503s jusqu'à ce qu'il ait automatiquement réévalué. ** PLAN D'ACTION ET PROCHAINES ÉTAPES** Nous savons que les pannes affectent votre productivité. Bien que nous ayons un certain nombre de processus de test et de prévention en place, ce problème précis n'a pas été identifié parce que le changement était lié à un type très spécifique de cas de bord qui n'a pas été repris par nos suites de déploiement continu automatisé et scripts de test manuel. Nous priorisons les mesures d'amélioration suivantes pour éviter de répéter ce type d'incident : - ** Ajouter de nouvelles garanties de déploiement :** Le pipeline de déploiement pour la configuration du niveau de proxy impacté utilisait un système existant et n'avait pas les fonctionnalités de déploiement régional lent appropriées configurées correctement. Nous avons déjà ajouté les garanties correctes, et nous sommes en train de transférer ce pipeline de déploiement standard de notre entreprise qui inclut tous nos contrôles de sécurité activés par défaut. Nous vérifions également tous les services de réseautage pour confirmer qu'ils sont tous sur le nouveau service standard de déploiement de pipelines. - **Améliorer les politiques d'échelle de la flotte de services :** La configuration d'échelle automatique de nos flottes de services Jira et Confluence a été configurée pour s'adapter à une échelle trop agressive. Nous sommes en train d'examiner et de mettre à jour en profondeur toutes les politiques complexes de jira et de confluence pour nous assurer que cela ne se reproduise pas. Nous nous excusons auprès des clients dont les services ont été touchés pendant cet incident; nous prenons des mesures immédiates pour améliorer la performance et la disponibilité de la plateforme. Merci, Assistance client Atlassian

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 25 août 2026 à 08:42 UTCinvestigating

   Nous enquêtons activement sur les rapports de dégradation de la performance qui se traduisent par une latence accrue pour les notifications par courriel, par mobile et par défaut pour Jira, JSM et Confluence. Nos équipes enquêtent sur la question et plus d'informations seront partagées dans les 1 prochaines heures.

2. 25 août 2026 à 09:44 UTCinvestigating

   Nos équipes ont identifié les régions touchées et s'emploient activement à atténuer le problème. Nous fournirons d'autres mises à jour dans une heure, ou plus tôt si nous avons des progrès importants à partager.

3. 25 août 2026 à 10:49 UTCinvestigating

   Nos équipes ont pris peu de mesures correctives pour atténuer le problème dans l'une des régions touchées et observent certaines améliorations. Nous continuons de surveiller la situation et nous prendrons les mesures nécessaires jusqu'à ce que l'incident soit complètement rétabli. Nous fournirons d'autres mises à jour dans les deux prochaines heures, ou plus tôt si nous avons des progrès importants à partager.

4. 25 août 2026 à 13:01 UTCmonitoring

   Nos équipes continuent d'atténuer le problème et observent certaines améliorations. Nous continuons de surveiller la situation et nous prendrons les mesures nécessaires jusqu'à ce que l'incident soit complètement rétabli. Nous fournirons d'autres mises à jour dans les deux prochaines heures, ou plus tôt si nous avons des progrès importants à partager.

5. 25 août 2026 à 14:33 UTCresolved

   Le 25 août 2026, certains utilisateurs ont peut-être connu une latence accrue dans les notifications par courriel, par téléphone mobile et par la suite. Le problème a maintenant été résolu et le service fonctionne normalement pour tous les clients.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 24 août 2026 à 19:22 UTCinvestigating

   Nous enquêtons activement sur les rapports de dégradation des performances qui ont entraîné une latence accrue pour les notifications par courriel, mobile et Slack pour JIRA, JSM et Confluence. Nous partagerons les mises à jour ici car plus d'informations sont disponibles.

2. 24 août 2026 à 20:25 UTCinvestigating

   Nos équipes ont identifié trois régions touchées et continuent d'étudier l'augmentation de la latence touchant les notifications par courriel, par téléphone mobile et par Slack pour JIRA, JSM et Confluence.

3. 24 août 2026 à 21:30 UTCidentified

   Nous avons identifié la cause probable du problème, et nos équipes travaillent avec diligence à une atténuation. Les utilisateurs touchés peuvent éprouver une latence accrue dans les notifications par courriel, mobile et Slack pour JIRA, JSM et Confluence. Nous continuerons de partager des mises à jour supplémentaires ici, car plus d'information est disponible.

4. 24 août 2026 à 23:15 UTCresolved

   Le 24 août 2026, certains utilisateurs de JIRA, de JSM et de Confluence ont peut-être subi une dégradation des performances entraînant une latence accrue dans les notifications par courriel, mobile et Slack. Le problème a été résolu pour les notifications nouvellement créées, et le service fonctionne normalement. Il peut y avoir des notifications plus anciennes qui sont en cours de traitement, et nous nous attendons à ce qu'elles soient complétées dans les prochaines heures.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 21 août 2026 à 07:16 UTCidentified

   Nous avons identifié la cause fondamentale d'un problème ayant une incidence sur les macros de l'application Marketplace dans Confluence. Les utilisateurs peuvent voir des macros ne pas rendre correctement ou afficher des erreurs. Notre équipe d'ingénierie a identifié la cause fondamentale et l'assainissement est en cours. Nous fournirons d'autres mises à jour dans les 60 prochaines minutes.

2. 21 août 2026 à 08:15 UTCidentified

   Un correctif a été identifié et est en cours de déploiement. Les utilisateurs devraient commencer à voir l'application MarketPlace impactée - Connectez les macros pour commencer à rendre correctement, une fois que la correction a été entièrement propagée. Nous fournirons d'autres mises à jour dans les 2 prochaines heures.

3. 21 août 2026 à 10:10 UTCresolved

   Le 21 août 2026, entre 04:26 UTC et 09:33 UTC, certains utilisateurs peuvent avoir éprouvé des problèmes avec les macros ne rendant pas correctement dans Confluence. Le problème a maintenant été résolu et le service fonctionne normalement pour tous les clients.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 12 août 2026 à 20:11 UTCidentified

   Some Confluence Cloud users visiting public links saw a Something went wrong error page. The issue affected anonymous access paths for public links, and some related Confluence areas could also show the same error message.

2. 12 août 2026 à 22:13 UTCresolved

   On August 12, 2026 some Confluence users utilizing anonymous access via public links, may have experienced a 'Something went wrong' error message. The issue has now been resolved, and the service is operating normally for all affected customers.

1. 6 juillet 2026 à 09:23 UTCinvestigating

   Nous enquêtons sur des questions touchant vos services. Nous travaillons activement à identifier la cause et à résoudre le problème. Nous fournirons d'autres mises à jour dans une heure.

2. 6 juillet 2026 à 10:04 UTCmonitoring

   Nous avons appliqué la solution avec succès et nous voyons la récupération. Les capacités d'automatisation sont rétablies et devraient fonctionner normalement. Les demandes de traitement de données soumises pendant la période de panne n'ont pas été traitées en raison de l'indisponibilité du service. Nous continuons de surveiller la situation et nous nous attendons à un rétablissement complet d'ici l'heure suivante. Nous fournirons des mises à jour supplémentaires dans la prochaine heure ou plus tôt.

3. 6 juillet 2026 à 11:46 UTCinvestigating

   Nous assistons encore à des problèmes de recherche des utilisateurs, de recherche des utilisateurs et d'atouts avec la région de l'UE. Nous continuons d'enquêter sur la situation et fournirons des mises à jour supplémentaires dans la prochaine heure ou plus tôt.

4. 6 juillet 2026 à 12:25 UTCmonitoring

   Nous avons appliqué le correctif pour atténuer le problème et nous voyons le rétablissement. Nous continuons à surveiller la situation et nous devrions la retrouver rapidement. Nous devrions être en mesure de fournir plus de mises à jour dans la prochaine heure ou plus tôt.

5. 6 juillet 2026 à 13:04 UTCresolved

   Le 6 juillet 2026, entre 06h51 UTC et 09h39 UTC, certains utilisateurs ont peut-être eu des problèmes liés à l'automatisation, et entre 08h10 UTC et 11h50 UTC, certains utilisateurs ont peut-être eu des problèmes liés à la recherche d'utilisateurs, à la recherche d'utilisateurs et aux actifs dans la région de l'UE. Les problèmes ont maintenant été résolus et les services fonctionnent normalement pour tous les clients.

6. 17 juillet 2026 à 16:59 UTCpostmortem

   Résumé Le 6 juillet 2026, entre 06:51 et 20:17 UTC, les clients atlassiens utilisant des produits cloud dans les régions européennes (UE) ont connu des perturbations de service affectant l'exécution des règles d'automatisation, la recherche des utilisateurs, le sélectionneur d'utilisateurs et les flux de travail connexes. L'incident a commencé quand un service d'identité de base a connu une saturation de la base de données dans les régions de l'UE, augmentant les taux de latence et d'erreur. Bien que les intervenants aient travaillé à rétablir la capacité, une atténuation d'urgence a été appliquée qui a empêché les règles d'automatisation d'accéder au paramètre d'identité. En parallèle, l'augmentation de la latence identitaire a contribué à une défaillance en cascade d'un service de recherche d'utilisateurs en aval, à une recherche d'utilisateurs dégradante et à des expériences de sélection d'utilisateurs sur plusieurs produits. Le service a été progressivement rétabli après l'ajout d'une capacité supplémentaire de lecture de la base de données, le bloc d'urgence a été supprimé et le service de recherche des utilisateurs a été augmenté manuellement. Impact L'incident a touché des clients de plusieurs produits atlassiens dans les régions de l'UE le 6 juillet 2026 entre 06:51 et 20:17 UTC. - **Dégradation du service d'identité de base:** des taux d'accès intermittents élevés ont été observés dans les produits des régions de l'UE. - **Défauts d'exécution des règles d'automatisation:** Les règles d'automatisation utilisant l'utilisateur par défaut (Automation pour Jira) dans Jira, Jira Service Management et Jira Product Discovery dans les régions de l'UE ont échoué avec une erreur d'autorisation. - **Défauts de recherche et de sélection d'utilisateurs:** Les taux de succès de recherche d'utilisateurs ont considérablement baissé dans les régions de l'UE, la capacité de sélection d'utilisateurs étant largement indisponible pour tous les produits. La cause profonde L'incident provient d'un changement de configuration récent qui a réduit la durée de vie du cache pour un service d'identité de base. Au fur et à mesure que le trafic de la journée de travail de l'UE a augmenté le 6 juillet 2026, une plus grande partie des demandes ont commencé à parvenir directement à la base de données d'appui plutôt que d'être desservies par cache. Les bases de données de l'UE ne disposaient pas d'une capacité régionale suffisante pour absorber l'augmentation de la charge, et le processeur de la base de données a atteint la saturation, ce qui a entraîné des taux d'accès intermittents élevés. Dans le cadre de l'atténuation, un bloc d'urgence a été appliqué afin de réduire la charge sur la base de données des services d'identité saturés et de prioriser la restauration du service d'identité de base. Cela empêchait par inadvertance les règles d'automatisation de passer leurs contrôles d'autorisation avant l'exécution, ce qui les faisait échouer. La durée prolongée était principalement due à une vague secondaire d'échecs des règles d'automatisation causée par la limite de traitement du grottling. Parallèlement, la dégradation soutenue a entraîné une augmentation de la latence et des défaillances intermittentes entre les produits qui dépendent de ces vérifications et a contribué à une défaillance en cascade dans un service de recherche d'utilisateurs en aval. En conséquence, les expériences de recherche et de sélection d'utilisateurs sont devenues largement indisponibles dans les régions de l'UE jusqu'à ce que le service des autorisations se rétablisse et que le service de recherche d'utilisateurs soit étendu pour rétablir la capacité. ## Plan d'actions correctives et prochaines étapes Nous savons que les pannes affectent la productivité des clients. Atlassian donne la priorité aux mesures suivantes pour aider à prévenir des incidents similaires à l'avenir : - **Améliorer les garanties pour les mesures d'atténuation d'urgence à impact élevé :** Pour durcir l'outillage opérationnel, il faut procéder à des étapes d'atténuation qui pourraient désactiver les flux de travail orientés vers le client. - **Renforcer la capacité de l'infrastructure d'identité et changer la sécurité :** Examiner la taille de la base de données régionale et la salle de tête de capacité afin de réduire le risque de saturation pendant les périodes de pointe et affiner le processus d'évaluation des changements de configuration de sorte que l'impact en aval de la charge soit évalué avant le déploiement de la production. - **Renforcer la résilience contre les défaillances en cascade résultant de la dégradation en amont :** Audit de la gestion de la contre-pression, de la configuration des disjoncteurs et du comportement d'étalonnage automatique dans les services, de sorte que la dégradation en amont ne cause pas d'impact plus large sur les produits dans la recherche des utilisateurs, le sélectionneur d'utilisateurs et les expériences connexes. - ** Mécanismes de replay Harden pour les défaillances de la règle d'automatisation :** Accroître la résilience des règles d'automatisation afin de réduire l'impact associé aux incidents survenant dans les dépendances. Nous reconnaissons à quel point les flux de travail fiables des produits sont critiques pour nos clients, et nous nous excusons auprès des clients qui ont été touchés par cet incident. Merci, Assistance client Atlassian

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 16 juin 2026 à 13:46 UTCinvestigating

   Our team is investigating degraded performance affecting your service. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.

2. 16 juin 2026 à 14:28 UTCidentified

   We have identified the source of degraded performance affecting some Confluence Cloud users. A subset of users may experience errors or slowness when viewing or editing pages. Our team has initiated a remediation and is actively monitoring recovery. We will provide another update within one hour or once the issue is fully resolved.

3. 16 juin 2026 à 14:53 UTCmonitoring

   We have been able to apply the fix to mitigate the issue and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.

4. 16 juin 2026 à 15:56 UTCresolved

   On June 16, 2026, Confluence Cloud users for some customers may have experienced performance degradation of view and edit page experiences. The issue has now been resolved, and the service is operating normally for all affected customers.

5. 23 juin 2026 à 18:25 UTCpostmortem

   ### Summary ### On Jun 12, 2026, between 07:04 and 12:10 UTC and on Jun 16, 2026, between 12:56 and 14:35 UTC, a subset of Atlassian customers using Confluence Cloud experienced errors and degraded performance when attempting to view or edit pages. The event was triggered when a database cluster within our infrastructure stopped responding to connection close requests. This caused idle connections to accumulate rather than be released — resulting in increased memory pressure and cascading errors for users. The incident was detected by our automated monitoring within 18 minutes and mitigated by scaling database resources and redeploying, which recycled the idle connections. A permanent fix has since been developed and deployed. ### IMPACT ### The overall impact was between Jun 12, 2026 07:04 and 12:10 UTC and Jun 16, 2026 12:56 and 14:35 UTC on Confluence Cloud. The June 12 incident caused service disruption to a subset of customers in the EU region while the June 16 incident caused service disruption to a subset of customers in the US region. Impacted users experienced errors or degraded performance when attempting to view, edit, or access Confluence content and spaces. ### ROOT CAUSE ### 1. A database cluster within our infrastructure stopped responding to connection close requests. 2. Idle connections accumulated across clusters rather than being closed, creating a connection leak and increasing memory pressure on the database layer. 3. Hitting max connections on the cluster degraded query performance. 4. Users attempting to view or edit Confluence content experienced errors and slow load times as a result. ### 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 design limitation in our connection cleanup process was not identified until it was triggered by an adverse infrastructure condition in production. We have already deployed the following fix: - Redesigned the database connection cleanup process to prevent unresponsive connections from impacting the closure of others. To minimize the impact of similar incidents in the future, we will implement additional preventative measures such as: - Monitoring and alerting for connection cleanup latency and failure rates, so that slowdowns in connection closure are detected early. - Enhanced safeguards on database connection creation to limit the blast radius of any future connection accumulation events. We apologize to customers whose services were impacted during this incident. We are taking immediate steps to improve the resilience of our platform_._ Thanks, Atlassian Customer Support

1. 12 juin 2026 à 07:39 UTCinvestigating

   Users are experiencing experiencing degraded performance in Confluence Cloud affecting view page and edit page functionality. Our teams are actively investigating and will be sharing more updates in next 1 hour or sooner.

2. 12 juin 2026 à 08:45 UTCinvestigating

   Users are experiencing degraded performance with view content, create and edit functionality on Confluence Cloud primarily in the EU region. Our teams are actively working to identify the root cause of the issue. We will share additional updates in next 2 hours or sooner as more information is available.

3. 12 juin 2026 à 10:29 UTCidentified

   Our teams have identified the root cause of this issue and implemented a fix. We are beginning to observe signs of recovery, with some affected users regaining access to view, create, and edit content on Confluence Cloud. We will provide a further update within one hour, or sooner if we confirm full recovery for all affected customers.

4. 12 juin 2026 à 11:15 UTCresolved

   On June 12th 2026, between 07:04 to 11:06 UTC, some Confluence users may have experienced service disruptions. The issue has now been resolved and the service is operating normally for all affected customers.

5. 23 juin 2026 à 18:28 UTCpostmortem

   ### Summary On Jun 12, 2026, between 07:04 and 12:10 UTC and on Jun 16, 2026, between 12:56 and 14:35 UTC, a subset of Atlassian customers using Confluence Cloud experienced errors and degraded performance when attempting to view or edit pages. The event was triggered when a database cluster within our infrastructure stopped responding to connection close requests. This caused idle connections to accumulate rather than be released — resulting in increased memory pressure and cascading errors for users. The incident was detected by our automated monitoring within 18 minutes and mitigated by scaling database resources and redeploying, which recycled the idle connections. A permanent fix has since been developed and deployed. ### IMPACT The overall impact was between Jun 12, 2026 07:04 and 12:10 UTC and Jun 16, 2026 12:56 and 14:35 UTC on Confluence Cloud. The June 12 incident caused service disruption to a subset of customers in the EU region while the June 16 incident caused service disruption to a subset of customers in the US region. Impacted users experienced errors or degraded performance when attempting to view, edit, or access Confluence content and spaces. ‌ ### ROOT CAUSE ‌ 1. A database cluster within our infrastructure stopped responding to connection close requests. 2. Idle connections accumulated across clusters rather than being closed, creating a connection leak and increasing memory pressure on the database layer. 3. Hitting max connections on the cluster degraded query performance. 4. Users attempting to view or edit Confluence content experienced errors and slow load times as a result. ‌ ### 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 design limitation in our connection cleanup process was not identified until it was triggered by an adverse infrastructure condition in production. ‌ We have already deployed the following fix: * Redesigned the database connection cleanup process to prevent unresponsive connections from impacting the closure of others. To minimize the impact of similar incidents in the future, we will implement additional preventative measures such as: * Monitoring and alerting for connection cleanup latency and failure rates, so that slowdowns in connection closure are detected early. * Enhanced safeguards on database connection creation to limit the blast radius of any future connection accumulation events. We apologize to customers whose services were impacted during this incident. We are taking immediate steps to improve the resilience of our platform_._ ‌ Thanks, Atlassian Customer Support

1. 10 juin 2026 à 06:14 UTCinvestigating

   We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

2. 10 juin 2026 à 06:14 UTCidentified

   Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

3. 10 juin 2026 à 06:14 UTCmonitoring

   Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

4. 10 juin 2026 à 06:31 UTCresolved

   We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

1. 27 mai 2026 à 06:03 UTCinvestigating

   We are investigating an issue where customers attempting to view Calendars receive an error message on Confluence Cloud pages. Our engineering team is actively investigating and working toward a resolution. We will provide an update within an hour or as more information becomes available.

2. 27 mai 2026 à 07:06 UTCidentified

   Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 1 hours, or sooner if we have any meaningful developments to report.

3. 27 mai 2026 à 07:48 UTCresolved

   Between 00:50 UTC and 07:30 UTC on 27 May 2026, some users were facing errors when attempting to view Calendars in Confluence. Our engineering team identified and resolved the underlying issue, and this incident has been fully restored.

1. 26 mai 2026 à 11:58 UTCinvestigating

   We are investigating an issue where some custom extensions may fail to load when editing Confluence Cloud pages. Affected users may see 'Error loading the extension!' messages or notice that certain macros are missing from the editor's extension selection menu. Viewing published pages is not affected. Our engineering team is actively investigating and working toward a resolution. We will provide an update within an hour or as more information becomes available.

2. 26 mai 2026 à 11:58 UTCinvestigating

   We are actively investigating an issue affecting the editing macros in Confluence Cloud editor. Our team is working to identify the root cause. We will provide an update within approximately one hour.

3. 26 mai 2026 à 13:55 UTCresolved

   Between 08:30 UTC and 13:51 UTC on 26 May 2026, some users were unable to load or edit certain macros in the Confluence Cloud page editor. Our engineering team identified and resolved the underlying issue, and macro functionality has been fully restored.

1. 14 mai 2026 à 04:54 UTCinvestigating

   We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more details within the next hour or sooner if further information becomes available

2. 14 mai 2026 à 05:03 UTCinvestigating

   We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

3. 14 mai 2026 à 05:11 UTCidentified

   Further confirmations of impacted products have now been added to the incident. Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

4. 14 mai 2026 à 05:24 UTCidentified

   It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information. We will provide further update within one hour, or sooner as further information becomes available.

5. 14 mai 2026 à 05:34 UTCidentified

   Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products. At this time, Atlassian customers should also be able to once again raise support requests with our team. We will provide further update within an hour as we are able to progress mitigating this issue.

6. 14 mai 2026 à 05:43 UTCmonitoring

   Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

7. 14 mai 2026 à 06:40 UTCmonitoring

   We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

8. 14 mai 2026 à 06:41 UTCmonitoring

   We are approaching full system recovery at this time, and are performing final confirmations that services are restored.

9. 14 mai 2026 à 06:48 UTCresolved

   All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

10. 19 mai 2026 à 19:04 UTCpostmortem

    ### Summary On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes. ### **IMPACT** During the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access services. Customers also experienced errors when accessing the support portal until Atlassian fell back to an alternate support method. This was caused by a core identity service in the us-east region becoming unavailable. Affected products included Atlassian Administration, Atlassian Analytics, Bitbucket, Compass, Confluence, Jira, Jira Product Discovery, Jira Service Management and Trello. Some users outside us-east may have been affected in certain scenarios. ### **ROOT CAUSE** The incident was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future: * **Refine deployment orchestration safeguards** * Harden our deployment platform to prevent similar race conditions or resulting capacity loss during a rollback operation. * Streamline mitigation steps when a service becomes unavailable in a region. * **Reduce cross-region impact** * Improve regional isolation and fallback handling so an issue affecting a single region is less likely to impact customers or product functionality in other regions. We recognise how critical reliable access to Atlassian products is for our customers' productivity, and we apologize to customers who were impacted by this incident. Thanks, Atlassian

1. 8 mai 2026 à 01:31 UTCinvestigating

   We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

2. 8 mai 2026 à 04:10 UTCidentified

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

3. 8 mai 2026 à 04:10 UTCidentified

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

4. 8 mai 2026 à 04:10 UTCidentified

   We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.

5. 8 mai 2026 à 05:53 UTCmonitoring

   The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

6. 8 mai 2026 à 08:03 UTCmonitoring

   We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

7. 8 mai 2026 à 11:12 UTCmonitoring

   Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We apologise for the disruption and thank you for your patience.

8. 8 mai 2026 à 19:45 UTCresolved

   On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

9. 20 mai 2026 à 06:55 UTCpostmortem

   All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution. The incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15. ### **IMPACT** The primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Atlassian services and underpins background operations such as automation execution, search indexing, notifications, permission synchronisation. * Between 00:22 and 06:08, an infrastructure incident in our hosting provider triggered an ingestion failure in our event processing pipeline. * At 02:50, event ingestion was failed over to an unaffected availability zone, progressively restoring live event flows. * At 06:08, reliability for new ingestion in prod-east recovered to 100%. The remaining work was to drain the accumulated cross-region backlog of messages, which completed by 17:00. * By 18:48, Automation had processed their backlog of events that were created while processing **Automation** Between 00:22 and 02:50, customers with automation rules triggered by events originating from the prod-east region experienced a significant reduction in rule executions. During this window, event-triggered automation rules were not firing because the events that trigger them were not being delivered. Rule authoring, saving, and rules triggered manually, by schedules, or by webhooks were not affected. At 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of live events to Automation and allowing new event-triggered rules to begin executing normally. However, events generated during the impact window still needed to be replayed before delayed automations could be processed. Beginning at 08:28, upstream services replayed their queued events in a coordinated sequence, and all replayed events were processed by 18:48. During the replay window, customers may have experienced automation rules executing later than expected, a small number of rules reaching daily processing limits due to compressed replay, and time-sensitive rules not completing as expected if internal timeout thresholds were exceeded. **Jira and Jira Service Management** Between 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruption to Jira and Jira Service Management event-driven features like automation, along with a short period of elevated errors during infrastructure failover. Core Jira experiences, including issue view, boards, and project navigation, remained available throughout the incident. Jira event delivery was affected by the primary impact, preventing downstream services from receiving issue lifecycle events. This affected automation rules triggered by Jira events, AI agent orchestration in Jira, notifications for issue updates and transitions, search indexing for newly created or modified issues, and event-driven integrations between Jira and other Atlassian products. At 02:50, the event processing infrastructure failed over to an unaffected availability zone, restoring delivery of new events. All events generated during the impact window were retained in a recovery queue and required replaying. This began at 08:28 and completed at 12:00. During the replay window, customers may have experienced automation rules executing later than expected, delayed notifications arriving hours after the triggering action, temporary gaps in search results for content created or modified during the impact window, and AI agent workflows not completing as expected where internal timeout thresholds were exceeded. **Confluence** Between 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced disruptions to event-driven services in Confluence. This resulted in delays to search indexing, notifications, automation rule execution, and permission synchronisation. The underlying event processing infrastructure failed over to an unaffected availability zone, after which live Confluence operations resumed normally. However, events generated during the impact window were queued for replay, and some background services remained delayed until that replay and related validation work completed. Between 10:14 and 17:00, a bulk replay of all the queued tenant replay tasks was completed to restore data consistency. During and immediately after the replay window, customers may have experienced search results not reflecting content created or modified during the outage, delayed or missing notifications for page and comment activity, automation rules firing later than expected, and brief delays in permission synchronisation for tenants relying on incremental identity sync. **Bitbucket and Pipelines** Between 00:22 and 06:08, customers using Bitbucket and Pipelines experienced failures and degraded functionality across event-driven workflows. Core Git operations, including push, pull, and clone, were not affected and continued to operate normally throughout the incident. Automatic pipeline triggers initiated by push or pull request events were unavailable during the impact window. Merge queues, custom merge checks, Forge-based triggers, workspace permission changes, and some workspace provisioning flows were also affected. Customers using merge queues were unable to merge pull requests, and some pipeline steps failed because queued work contributed to elevated concurrency limits. At approximately 03:57, Pipelines was reconfigured to consume events through an alternative path, restoring automatic pipeline triggering. Merge queues, custom merge checks, Forge triggers, and other affected workflows were progressively restored as the underlying event processing infrastructure recovered. All Bitbucket and Pipelines services were confirmed fully operational by 06:08. After recovery, queued events were reviewed and replayed where safe to restore data consistency for billing, audit logging, and other background processes. **Identity Services** Between 00:22 and 02:50, customers with tenants hosted in the prod-east region experienced delays in the propagation of identity and group membership changes to downstream Atlassian products. Core identity operations, including authentication, login, and direct group management actions, were not affected and continued to function normally throughout the incident. The impact was limited to asynchronous, event-driven operations that depend on the event processing pipeline. This included delays in delivering group membership and user profile changes to products such as Jira and Confluence, which affected downstream permission synchronisation and crowd sync flows. A small number of SCIM-based identity synchronisation and site provisioning workflows also experienced temporary delays. After the event processing infrastructure recovered, backed-up identity and group directory events were replayed where required, restoring downstream consistency for affected products. No identity data was lost. Group membership changes, user profile updates, and provisioning-related events that occurred during the impact window were retained and processed after recovery. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know outages impact your productivity. While our monitoring and recovery processes helped us respond quickly, this incident highlighted opportunities to further strengthen resilience for event-driven services. We are prioritizing improvements that will: * **Enhance failover coverage** so critical event processing can recover more smoothly during infrastructure disruptions. * **Strengthen recovery handling** so replayed events can be processed more quickly. 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.

1. 14 avril 2026 à 12:25 UTCinvestigating

   We are actively investigating reports of a partial service disruption affecting Rovo, specifically for customers using automation rules that invoke Rovo agents. Some customers may find that these automations are not completing as expected. We'll share updates here as more information becomes available.

2. 14 avril 2026 à 12:25 UTCinvestigating

   We have identified that this incident also affects automation rules in Confluence that use Rovo agents. We are investigating and will provide updates as we learn more.

3. 14 avril 2026 à 14:11 UTCidentified

   We have identified the issue, and our teams are working to resolve it and restore normal operations as quickly as possible. We will provide further updates as they become available.

4. 14 avril 2026 à 15:46 UTCmonitoring

   The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability.

5. 14 avril 2026 à 16:11 UTCresolved

   On April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected customers.

1. 13 avril 2026 à 07:29 UTCmonitoring

   Our team is aware that some users were unable to log in to Atlassian products with their Atlassian accounts. While we believe this issue is now resolved, we are continuing to monitor all products and services for any ongoing impact. Our team is investigating with urgency, and we will provide an update within 1 hour.

2. 13 avril 2026 à 08:33 UTCmonitoring

   Atlassian account login services are now operating as expected, and we are not observing new errors. We continue to closely monitor our systems to ensure they remain stable. We will provide another update within 60 minutes or sooner if we detect a change in status.

3. 13 avril 2026 à 10:17 UTCresolved

   On April 13, 2026, between 05:49 a.m. and 06:25 a.m. UTC, some users were unable to log in to Atlassian products with their Atlassian accounts. The underlying issue has been addressed, and authentication services have remained stable with no new impact observed.

4. 21 avril 2026 à 02:33 UTCpostmortem

   ### Summary On April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed during the peak impact window, affecting users in the US East and EU regions. The incident was mitigated within 40 minutes through manual intervention, and full service was restored by 06:29 UTC. ### **IMPACT** * **Duration**: ~40 minutes \(05:49–06:29 UTC, April 13, 2026\) * **Affected regions**: US East and EU \(authentication infrastructure serves EU traffic from US East, with traffic primarily from EU at this time of day\). * **Affected products**: All Atlassian cloud products requiring authentication, including Jira, Confluence, Jira Service Management, and Trello. * **Customer experience**: Users attempting to log in, sign up, reset passwords, or complete MFA flows received errors. Users already logged in with active sessions were unaffected. ### **ROOT CAUSE** This incident had several contributing factors that combined to produce a failure that the system could not recover from without manual intervention. **The primary cause** was a recently enabled change that caused our authentication infrastructure to retry requests to a downstream identity service when those requests were slow to respond. This retry behaviour was rolled out to 100% of traffic earlier the same day. Under normal conditions this would be benign, but it meant that any slowness in the downstream service was amplified. Since multiple upstream services were also independently retrying their own failed requests, the amplification compounded further into a retry storm. **The trigger** was a burst of legitimate user traffic. A pattern of many parallel link preview requests for a single user caused a concentrated load spike on a downstream identity service, pushing its response times above the retry threshold. On its own, this kind of spike had occurred many times before and always recovered. With the retry amplification now in effect, the spike instead created a runaway feedback loop: slow responses caused retries, retries increased load, increased load caused slower responses, preventing recovery. The incident was mitigated by manually scaling up the downstream identity service to provide sufficient capacity to absorb the amplified load. Once scaled, the service recovered immediately, bringing authentication error rates to zero within one minute. **REMEDIAL ACTIONS PLAN & NEXT STEPS** We are taking the following actions designed to prevent recurrence and improve our resilience: 1. **Immediate**: The retry-on-timeout change has been disabled. 2. **Load shedding and self-healing**: We are adding load shedding capabilities to our authentication services so that they can automatically shed excess load and self-recover during traffic spikes, without requiring action before automatic scaling starts. 3. **Reducing request fan-out**: We are reviewing patterns where a single user action can generate many parallel downstream requests, and will introduce methods where possible to reduce the amplification potential. We apologize to customers whose services were interrupted by this incident and we are taking immediate steps to improve the platform’s reliability. Thanks, Atlassian Customer Support

1. 8 avril 2026 à 06:01 UTCinvestigating

   The impact of this incident is now understood to also be impacting search in Jira and Confluence, as well as additional downstream impacts to Rovo Chat, User Management, Administration and Guard. Our team is continuing to investigate with urgency and we will provide further update within 1 hour.

2. 8 avril 2026 à 06:25 UTCinvestigating

   Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.

3. 8 avril 2026 à 07:40 UTCidentified

   Confluence and Jira search reliability is improving, and we expect full recovery shortly; we will continue to closely monitor the services to ensure they remain stable.

4. 8 avril 2026 à 08:33 UTCidentified

   We have restored core search functionality and services are operating again, but some customers may still experience delays when searching for data changed within the last hour while new data continues to be indexed. We are actively working to complete reindexing and will update this page as performance fully recovers.

5. 8 avril 2026 à 09:03 UTCidentified

   We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution. We will provide further update within 1 hour.

6. 8 avril 2026 à 09:03 UTCmonitoring

   The issue has been resolved, and services are now operating normally. Some customers may still experience delays when searching for data changed within the last hour, while new data continues to be indexed. We'll continue to monitor closely to confirm stability.

7. 8 avril 2026 à 11:43 UTCresolved

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

8. 17 avril 2026 à 16:24 UTCpostmortem

   ### Summary On April 8, 2026, between 04:46 UTC and 12:09 UTC, search functionality was unavailable or degraded across several Atlassian Cloud products, including Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and Atlassian Administration. A configuration change increased the resources reserved for a core system component that runs on nodes in our compute platform. On a subset of clusters configured for high‑density workloads, the increased reservations exceeded available node capacity interrupting search and related experiences for affected customers. The root cause was identified and a rollback was merged at 05:42 UTC with some systems seeing recovery by 07:33 UTC**.** Core search functionality was restored approximately by 08:55 UTC, and full downstream recovery completed by 12:09 UTC. ### **IMPACT** During the impact period, some customers experienced outages or degradation in search across Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and Atlassian Administration. Other experiences that rely on search such as quick find, navigation, AI assistants, dashboards, were also intermittently affected during this period. Impacted customers may have been unable to find pages or recordings and experienced degraded performance in finding issues; received empty or delayed search results; or experienced AI assistants and dashboards that could not retrieve relevant context. **Jira, Jira Service Management and Customer Service Management:** Search and experiences that depend on search like finding issues and agent responses in CSM remained available but with degraded performance in fallback mode. By 12:09 UTC, search indexes and search performance was fully restored from fallback to full capacity across all regions. **Guard Standard and Atlassian Administration:** Search functionality was unavailable for parts of the incident window. As a result, Domain Claims, usage tracking, and managed accounts were degraded for portions of the window. These services were restored to operational status by 07:33 UTC. Guard Premium was not impacted by this issue. **Confluence:** Search functionality was unavailable for parts of the incident window. Recovery began at 07:30 UTC as backend search clusters were restored. Full recovery, including search index replay, completed at 11:37 UTC. **Loom:** Search functionality and some experiences that rely on Confluence Search, such as sharing to spaces\) was unavailable for portions of the window and fully restored at 11:37 UTC. **Rovo and Rovo Dev:** Rovo agents remained responsive but experienced degraded functionality due to loss of search capabilities in underlying services. They were unable to reliably return context about work items or pages. Functionality was fully restored at 11:37 UTC. ### **ROOT CAUSE** Atlassian products rely on OpenSearch clusters to power their search capabilities including issue search, content search, and AI-powered search features. An infrastructure configuration change increased resource reservations \(CPU & Memory\) for a system component that runs across our compute platform. On a subset of clusters configured for high-density workloads, the increased reservations exceeded available node capacity. This caused search workloads to be evicted and, in some clusters, could not reschedule onto any available nodes impacting search functionality across affected products. The change was deployed across multiple production clusters in a short time frame, limiting the opportunity to detect the capacity conflict in a smaller subset of clusters before it reached the wider fleet. Automated scaling systems attempted to recover by provisioning additional capacity but in the worst‑affected clusters this led to runaway node scaling and exhaustion of available network resources, prolonging recovery time. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We understand that service disruptions impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritizing the following actions to help reduce the likelihood and impact of similar incidents in the future and to speed up recovery when issues occur: * **Enforce smaller deployment cohorts and larger soak for critical platform changes for these cluster types** Implement smaller deployment cohorts, mandatory soak periods between environments, and automated health gates so that changes are validated on a limited set of clusters before being promoted more broadly. * **Strengthen automated pre‑deploy validation for resource changes** Add validation checks to ensure resource changes for system components are compatible with node capacity and reserved headroom, preventing system workloads from crowding out customer workloads. * **Improve post‑deploy verification and alerting** Enhance monitoring and post‑deployment verification to detect patterns such as spikes in pending pods, runaway node scaling, and low pod‑IP headroom closely correlated with new configuration being rolled out. * **Align autoscaling behavior with capacity and safety limits** Align autoscaling capacity calculations with node reservations and introduce safeguards and circuit breakers to prevent runaway scaling and to enforce safe limits on node and pod IP counts. * **Enhance recovery automation** Improve automation and runbooks so we can safely disable autoscaling, remove empty nodes in bulk, and restore normal operations faster across multiple clusters in parallel. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability and to reduce the risk and impact of similar issues in future. Thanks, Atlassian Customer Support

1. 12 mars 2026 à 13:38 UTCinvestigating

   Confluence Cloud users may experience errors when accessing certain Marketplace macros. Affected customers are seeing the message Error rendering macro 'static-macro': Page loading failed. Our team is actively investigating this issue. We will provide another update within 2 hours, or sooner.

2. 12 mars 2026 à 13:38 UTCidentified

   Our team has identified the cause of this issue, and a fix is currently being deployed. We are monitoring the deployment, and we will provide another update within 2 hours, or sooner if needed.

3. 13 mars 2026 à 00:26 UTCresolved

   On March 12, 2026, affected Confluence Cloud users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

1. 10 mars 2026 à 00:15 UTCinvestigating

   We are aware of customers experiencing delays with their automations within Jira, Jira Service Management, Jira Work Management, Jira Product Discovery and Confluence. Our team is investigating with urgency and we will provide an update within one hour.

2. 10 mars 2026 à 00:15 UTCidentified

   Our team has now identified the cause of this issue relating to delayed automation events and has put a hotfix in place to help restore automation performance. We will continue to monitor performance as the backlog of issues is now being processed.

3. 10 mars 2026 à 00:51 UTCmonitoring

   The performance degradation of automations has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

4. 10 mars 2026 à 00:59 UTCresolved

   On 9 March UTC, Automation users in the APAC region may have experienced performance degradation within Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, Confluence. The issue has now been resolved, and the service is operating normally for all affected customers.

1. 20 février 2026 à 04:14 UTCidentified

   Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours as we continue our investigation.

2. 20 février 2026 à 12:26 UTCidentified

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

3. 20 février 2026 à 12:26 UTCresolved

   This issue has been resolved and all services are functional.

1. 19 février 2026 à 15:44 UTCmonitoring

   We have received and investigated reports of a partial service disruption affecting Confluence Cloud for some customers in AP South, APSE, APSE2, East, and Central. The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.

2. 19 février 2026 à 17:47 UTCresolved

   On February 19 2026, affected Confluence Cloud users may have experienced some service disruption in AP South, APSE, APSE2, East, and Central regions. The issue has now been resolved, and the service is operating normally for all affected customers.