- Detected by Pingoru
- Mar 12, 2026, 11:42 AM UTC
- Resolved
- Mar 13, 2026, 12:26 AM UTC
- Duration
- 12h 43m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQL
Timeline · 4 updates
-
investigating Mar 12, 2026, 11:42 AM UTC
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.
-
investigating Mar 12, 2026, 01:38 PM UTC
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.
-
identified Mar 12, 2026, 01:38 PM UTC
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.
-
resolved Mar 13, 2026, 12:26 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 08:48 AM UTC
- Resolved
- Mar 12, 2026, 12:33 PM UTC
- Duration
- 3h 45m
Affected: WebsiteAPIGit via SSHAuthentication and user managementGit via HTTPSWebhooksSource downloadsPipelinesGit LFSEmail deliveryPurchasing & LicensingSignup
Timeline · 5 updates
-
investigating Mar 12, 2026, 08:48 AM UTC
We are actively investigating a service disruption impacting Bitbucket for some customers. We'll share updates here as more information is available.
-
investigating Mar 12, 2026, 09:40 AM UTC
We are actively investigating reports of a service disruption affecting Bitbucket Cloud. We'll share updates here within the next hour or as more information is available.
-
investigating Mar 12, 2026, 10:52 AM UTC
Our engineers are actively working to resolve the Bitbucket Cloud disruption. No new updates at this moment. We will share more details within the next hour or as soon as we more information is available.
-
investigating Mar 12, 2026, 12:05 PM UTC
Our engineers continue to work actively to identify the root cause. Meanwhile, the affected service is now stable and the error rate has decreased. We will share more details within the next hour, or sooner if more information becomes available.
-
resolved Mar 12, 2026, 12:33 PM UTC
We have successfully mitigated the incident, and the affected service is now fully operational. Our teams have verified that normal functionality has been restored and the service is performing as expected.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 12:15 AM UTC
- Resolved
- Mar 10, 2026, 12:59 AM UTC
- Duration
- 43m
Affected: View ContentiOS AppCreate and EditAndroid AppCommentsAuthentication and User ManagementSearchAdministrationNotificationsMarketplace AppsPurchasing & LicensingSignupConfluence AutomationsCloud to Cloud Migrations - Copy Product DataServer to Cloud Migrations - Copy Product Data
Timeline · 4 updates
-
investigating Mar 10, 2026, 12:15 AM UTC
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.
-
identified Mar 10, 2026, 12:15 AM UTC
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.
-
monitoring Mar 10, 2026, 12:51 AM UTC
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.
-
resolved Mar 10, 2026, 12:59 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 12:06 AM UTC
- Resolved
- Mar 10, 2026, 12:59 AM UTC
- Duration
- 52m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
-
investigating Mar 10, 2026, 12:06 AM UTC
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.
-
identified Mar 10, 2026, 12:15 AM UTC
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.
-
monitoring Mar 10, 2026, 12:51 AM UTC
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.
-
resolved Mar 10, 2026, 12:59 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 12:06 AM UTC
- Resolved
- Mar 10, 2026, 12:59 AM UTC
- Duration
- 52m
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssist
Timeline · 4 updates
-
investigating Mar 10, 2026, 12:06 AM UTC
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.
-
identified Mar 10, 2026, 12:15 AM UTC
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.
-
monitoring Mar 10, 2026, 12:51 AM UTC
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.
-
resolved Mar 10, 2026, 12:59 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 12:06 AM UTC
- Resolved
- Mar 10, 2026, 12:59 AM UTC
- Duration
- 52m
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssist
Timeline · 4 updates
-
investigating Mar 10, 2026, 12:06 AM UTC
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.
-
identified Mar 10, 2026, 12:15 AM UTC
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.
-
monitoring Mar 10, 2026, 12:51 AM UTC
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.
-
resolved Mar 10, 2026, 12:59 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 12:06 AM UTC
- Resolved
- Mar 10, 2026, 12:59 AM UTC
- Duration
- 52m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
-
investigating Mar 10, 2026, 12:06 AM UTC
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.
-
identified Mar 10, 2026, 12:15 AM UTC
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.
-
monitoring Mar 10, 2026, 12:51 AM UTC
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.
-
resolved Mar 10, 2026, 12:59 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 12:06 AM UTC
- Resolved
- Mar 10, 2026, 12:59 AM UTC
- Duration
- 52m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
-
investigating Mar 10, 2026, 12:06 AM UTC
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.
-
identified Mar 10, 2026, 12:15 AM UTC
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.
-
monitoring Mar 10, 2026, 12:51 AM UTC
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.
-
resolved Mar 10, 2026, 12:59 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 10, 2026, 12:06 AM UTC
- Resolved
- Mar 10, 2026, 12:59 AM UTC
- Duration
- 52m
Affected: Open projectsCreate and delete fieldsAdd/view data points ("Capture")
Timeline · 4 updates
-
investigating Mar 10, 2026, 12:06 AM UTC
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.
-
identified Mar 10, 2026, 12:15 AM UTC
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.
-
monitoring Mar 10, 2026, 12:51 AM UTC
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.
-
resolved Mar 10, 2026, 12:59 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 02:44 AM UTC
- Resolved
- Mar 06, 2026, 05:11 AM UTC
- Duration
- 2h 27m
Affected: WebsiteAPIGit via SSHAuthentication and user managementGit via HTTPSWebhooksSource downloadsPipelinesGit LFSEmail deliveryPurchasing & LicensingSignup
Timeline · 6 updates
-
investigating Mar 06, 2026, 02:44 AM UTC
We are actively investigating a service disruption impacting Bitbucket for some customers. We'll share updates here as more information is available.
-
identified Mar 06, 2026, 03:10 AM UTC
We have identified the cause of the issue, and our teams are diligently working on a mitigation. Affected users will experience Bitbucket being unavailable. We'll continue to share additional updates here as more information is available, with our next update to be posted within 1 hour.
-
identified Mar 06, 2026, 04:04 AM UTC
As restoration activities continue, we are now starting to see services recover for customers for Bitbucket Web and for Git HTTPS. We are continuing to work on mitigation across all remaining Bitbucket services. Our next update will be provided within one hour or if full recovery is seen prior to that time.
-
identified Mar 06, 2026, 05:00 AM UTC
Our team has now put mitigations in place across the majority of Bitbucket services and all are now actively recovering except for Pipelines, which is still being actively investigated. We are continuing to monitor these services and we will provide further update within 1 hour or when services have fully recovered.
-
resolved Mar 06, 2026, 05:11 AM UTC
On 06 March 2026 UTC, Bitbucket experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
-
postmortem Mar 26, 2026, 05:09 PM UTC
### Summary On March 6, 2026, between 02:19 UTC and 04:00 UTC, Bitbucket Cloud experienced an incident impacting the web app, API, CLI, and Pipelines operations. This was caused by the Bitbucket application hitting a regional provisioning API rate limit with our hosting provider, preventing application workers from handling website traffic. The incident was detected within 1 minute by automated monitoring and mitigated by scaling systems down and then back up to full capacity which put Atlassian systems into a known good state. ### **IMPACT** The incident resulted in a Bitbucket Cloud services being unavailable for 1 hour and 6 minutes on March 6, 2026 between 02:19 UTC and 03:25 UTC, followed by degraded website performance until 04:00 UTC. During this time, customers were unable to access Bitbucket services including the web app, Git operations \(clone, push, pull over HTTPS and SSH\), API, and running builds in Pipelines. ### **ROOT CAUSE** The issue stemmed from a change to an internal deployment system that increased use of a platform credential service, hitting a quota with our hosting provider. This blocked Bitbucket services from deploying additional capacity because new application nodes request the credential service on startup and were rate limited. This caused degradation of Bitbucket experiences and more failed requests to Bitbucket Cloud’s website and public APIs. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** The incident response team manually scaled down Bitbucket services, then gradually scaled them back up while closely monitoring our quota. We simultaneously engaged with our hosting provider to temporarily increasing this limit to unblock bringing more Bitbucket service capacity online. We know that outages impact your productivity. While we have a number of testing and preventative processes in place, Bitbucket services lacked necessary boundaries to be resilient to upstream platform system changes. To help minimise the impact of breaking changes to our environments, we will implement additional preventative measures such as: * Improve monitoring of shared Atlassian platform resources. * Update Bitbucket application bootstrapping to prevent new capacity from failing during resource contention of shared platform services. * Reduce Bitbucket’s dependency on shared hosting provider services. * Deploy Bitbucket services across multiple regions to reduce single-region failure risk. 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
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 04:15 PM UTC
- Resolved
- Mar 04, 2026, 03:04 AM UTC
- Duration
- 1d 10h
Affected: App listingsReporting APIs and dashboardsSearch
Timeline · 3 updates
-
monitoring Mar 02, 2026, 04:15 PM UTC
Since Feb 27, 2026 some Marketplace Partners may see incorrect install counts in their Marketplace Partner Portal and listing for their apps. The Marketplace team has identified the bug and is working to correct the same. Please note, the actual customer installs for these apps remain unaffected. As next Steps, the Marketplace team is working on a fix and expects to restore accurate install counts by Mar 3, 2026, EOD.
-
monitoring Mar 03, 2026, 05:06 PM UTC
We are providing an update regarding the install count discrepancy that some partners may have observed for some apps since Feb 27, 2026. - The install counts displayed on app listings are now accurate for the impacted apps. - The Active Installations tab in the Marketplace Partner Portal may still reflect incorrect counts for some apps; this will be corrected following tonight's scheduled update at 12:00 AM UTC on Mar 4, 2026. - Please note that actual customer installs were not impacted; only the reported counts displayed in the Partner Portal and on app listings were affected for some apps. We will share another update once the Partner Portal Active Installations tab has been fully corrected and validated. Thank you for your patience and understanding.
-
resolved Mar 04, 2026, 03:04 AM UTC
We are providing a further update regarding the install count discrepancy that some partners may have observed for some apps since Feb 27, 2026. - The Active Installations tab in the Marketplace Partner Portal is now showing accurate install counts for impacted apps from Mar 3, 2026 onward. - The install counts displayed on app listings remain accurate for impacted apps. - Please note that data from Mar 3, 2026 onward will remain accurate going forward. - You may notice a temporary dip in install counts for Mar 2, 2026. We are backfilling the data, and counts for that date will be restored once complete. - Actual customer installs were not impacted; only the reported counts displayed in the Partner Portal and on app listings were affected for some apps, and this is now fully functional. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 01:22 PM UTC
- Resolved
- Feb 26, 2026, 06:55 PM UTC
- Duration
- 5h 33m
Affected: Assist
Timeline · 6 updates
-
investigating Feb 26, 2026, 01:22 PM UTC
Atlassian Assist in Jira Service Management is currently unavailable. We are actively investigating the problem. We will share updates here as more information in next 60 mins or sooner.
-
investigating Feb 26, 2026, 02:25 PM UTC
We are still actively investigating this issue and working to restore Atlassian Assist in Jira Service Management. We will share another update here within the next 2 hours or sooner.
-
investigating Feb 26, 2026, 04:21 PM UTC
We continue to investigate the issue, and will share an update within next 2 hours or sooner.
-
identified Feb 26, 2026, 06:05 PM UTC
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience Atlassian Assist unavailability in JSM. We will continue to share additional updates here as more information is available.
-
monitoring Feb 26, 2026, 06:33 PM UTC
The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
-
resolved Feb 26, 2026, 06:55 PM UTC
On February 26, 2026, JSM experienced a disruption, and Atlassian Assist service was unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2026, 01:22 PM UTC
- Resolved
- Feb 26, 2026, 06:55 PM UTC
- Duration
- 5h 33m
Affected: Assist
Timeline · 6 updates
-
investigating Feb 26, 2026, 01:22 PM UTC
Atlassian Assist in Jira Service Management is currently unavailable. We are actively investigating the problem. We will share updates here as more information in next 60 mins or sooner.
-
investigating Feb 26, 2026, 02:25 PM UTC
We are still actively investigating this issue and working to restore Atlassian Assist in Jira Service Management. We will share another update here within the next 2 hours or sooner.
-
investigating Feb 26, 2026, 04:21 PM UTC
We continue to investigate the issue, and will share an update within next 2 hours or sooner.
-
identified Feb 26, 2026, 06:05 PM UTC
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience Atlassian Assist unavailability in JSM. We will continue to share additional updates here as more information is available.
-
monitoring Feb 26, 2026, 06:33 PM UTC
The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
-
resolved Feb 26, 2026, 06:55 PM UTC
On February 26, 2026, JSM experienced a disruption, and Atlassian Assist service was unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
Read the full incident report →
- Detected by Pingoru
- Feb 21, 2026, 03:32 PM UTC
- Resolved
- Feb 21, 2026, 03:32 PM UTC
- Duration
- 1s
Affected: Trello.comAPIAtlassian Support - Support PortalAtlassian Support TicketingAtlassian Support Knowledge Base
Timeline · 2 updates
-
investigating Feb 21, 2026, 03:32 PM UTC
Impact Trello users are experiencing issues with websocket connections, leading to difficulties in maintaining active sessions. Affected users may notice disruptions in service as connections are intermittently dropping. Current Status Efforts are underway to restore normal service. Teams are actively engaged in identifying the best path to full resolution. Next Steps The incident team is focusing on pinpointing the root cause and implementing necessary fixes. The next communication will be shared in 30 minutes.
-
resolved Feb 21, 2026, 03:32 PM UTC
Impact Trello users are experiencing issues with websocket connections, leading to difficulties in maintaining active sessions. Affected users may notice disruptions in service as connections are intermittently dropping. Current Status Efforts are underway to restore normal service. Teams are actively engaged in identifying the best path to full resolution. Next Steps The incident team is focusing on pinpointing the root cause and implementing necessary fixes. The next communication will be shared in 30 minutes.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 07:13 AM UTC
- Resolved
- Feb 20, 2026, 12:26 PM UTC
- Duration
- 5h 12m
Affected: Customer experienceCustomer Service Management AI agentSupport websiteEmail requestCustomer Service Management spacesCustomer profilesAutomation for Jira
Timeline · 3 updates
-
identified Feb 20, 2026, 07:13 AM UTC
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.
-
identified Feb 20, 2026, 12:26 PM UTC
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.
-
resolved Feb 20, 2026, 12:26 PM UTC
This issue has been resolved and all services are functional.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 04:14 AM UTC
- Resolved
- Feb 20, 2026, 12:26 PM UTC
- Duration
- 8h 11m
Affected: View ContentiOS AppCreate and EditAndroid AppCommentsAuthentication and User ManagementSearchAdministrationNotificationsMarketplace AppsPurchasing & LicensingSignupConfluence AutomationsCloud to Cloud Migrations - Copy Product DataServer to Cloud Migrations - Copy Product Data
Timeline · 4 updates
-
identified Feb 20, 2026, 04:14 AM UTC
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.
-
identified Feb 20, 2026, 07:13 AM UTC
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.
-
identified Feb 20, 2026, 12:26 PM UTC
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.
-
resolved Feb 20, 2026, 12:26 PM UTC
This issue has been resolved and all services are functional.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 02:52 AM UTC
- Resolved
- Feb 20, 2026, 12:26 PM UTC
- Duration
- 9h 33m
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssist
Timeline · 5 updates
-
identified Feb 20, 2026, 02:52 AM UTC
Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately. We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue. Feb 20, 2026 - 02:52 UTC Please see prior notifications relating to this incident below: Update - Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites. We anticipate next update to be posted in approximately 8 hours. Feb 19, 2026 - 21:04 UTC Update - We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available. Feb 19, 2026 - 18:56 UTC Identified - Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. Feb 19, 2026 - 17:34 UTC Update - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available. Feb 19, 2026 - 17:14 UTC Investigating - We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites. We will share updates here as more information is available. Feb 19, 2026 - 16:44 UTC
-
identified Feb 20, 2026, 04:14 AM UTC
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.
-
identified Feb 20, 2026, 07:13 AM UTC
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.
-
identified Feb 20, 2026, 12:26 PM UTC
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.
-
resolved Feb 20, 2026, 12:26 PM UTC
This issue has been resolved and all services are functional.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 02:52 AM UTC
- Resolved
- Feb 20, 2026, 12:26 PM UTC
- Duration
- 9h 33m
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssist
Timeline · 5 updates
-
identified Feb 20, 2026, 02:52 AM UTC
Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately. We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue. Feb 20, 2026 - 02:52 UTC Please see prior notifications relating to this incident below: Update - Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites. We anticipate next update to be posted in approximately 8 hours. Feb 19, 2026 - 21:04 UTC Update - We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available. Feb 19, 2026 - 18:56 UTC Identified - Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. Feb 19, 2026 - 17:34 UTC Update - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available. Feb 19, 2026 - 17:14 UTC Investigating - We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites. We will share updates here as more information is available. Feb 19, 2026 - 16:44 UTC
-
identified Feb 20, 2026, 04:14 AM UTC
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.
-
identified Feb 20, 2026, 07:13 AM UTC
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.
-
identified Feb 20, 2026, 12:26 PM UTC
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.
-
resolved Feb 20, 2026, 12:26 PM UTC
This issue has been resolved and all services are functional.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 04:44 PM UTC
- Resolved
- Feb 20, 2026, 12:26 PM UTC
- Duration
- 19h 41m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 10 updates
-
investigating Feb 19, 2026, 04:44 PM UTC
We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites. We will share updates here as more information is available.
-
investigating Feb 19, 2026, 05:14 PM UTC
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available.
-
identified Feb 19, 2026, 05:34 PM UTC
Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites.
-
identified Feb 19, 2026, 06:56 PM UTC
We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available.
-
identified Feb 19, 2026, 09:04 PM UTC
Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites. We anticipate next update to be posted in approximately 8 hours.
-
identified Feb 20, 2026, 02:52 AM UTC
Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately. We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue.
-
identified Feb 20, 2026, 04:14 AM UTC
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.
-
identified Feb 20, 2026, 07:13 AM UTC
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.
-
identified Feb 20, 2026, 12:26 PM UTC
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.
-
resolved Feb 20, 2026, 12:26 PM UTC
This issue has been resolved and all services are functional.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 03:44 PM UTC
- Resolved
- Feb 19, 2026, 05:47 PM UTC
- Duration
- 2h 2m
Affected: View Content
Timeline · 2 updates
-
monitoring Feb 19, 2026, 03:44 PM UTC
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.
-
resolved Feb 19, 2026, 05:47 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Feb 19, 2026, 03:06 PM UTC
- Resolved
- Feb 19, 2026, 03:22 PM UTC
- Duration
- 15m
Affected: Trello.comAPIAtlassian Support - Support PortalAtlassian Support TicketingAtlassian Support Knowledge Base
Timeline · 3 updates
-
investigating Feb 19, 2026, 03:06 PM UTC
We are actively investigating reports of performance degradation affecting Trello. We will share updates here as more information is available.
-
monitoring Feb 19, 2026, 03:10 PM UTC
The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.
-
resolved Feb 19, 2026, 03:22 PM UTC
On February 19, 2026, Trello users may have experienced performance degradation. The issue has now been resolved, and the service is operating normally for all affected customers.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 11:28 AM UTC
- Resolved
- Feb 18, 2026, 11:30 AM UTC
- Duration
- 2m
Affected: Domain ClaimsData ClassificationSAML-based SSOData Security PoliciesUser ProvisioningGuard DetectAccount ManagementAudit LogsSignupAPI tokens
Timeline · 2 updates
-
monitoring Feb 18, 2026, 11:28 AM UTC
We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.
-
resolved Feb 18, 2026, 11:30 AM UTC
We have implemented the fix and the group page in the Admin Hub is now functioning as expected.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 11:28 AM UTC
- Resolved
- Feb 18, 2026, 11:30 AM UTC
- Duration
- 2m
Affected: Domain ClaimsData ClassificationSAML-based SSOData Security PoliciesUser ProvisioningGuard DetectAccount ManagementAudit LogsSignupAPI tokens
Timeline · 2 updates
-
monitoring Feb 18, 2026, 11:28 AM UTC
We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.
-
resolved Feb 18, 2026, 11:30 AM UTC
We have implemented the fix and the group page in the Admin Hub is now functioning as expected.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 10:57 AM UTC
- Resolved
- Feb 18, 2026, 11:30 AM UTC
- Duration
- 32m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 3 updates
-
investigating Feb 18, 2026, 10:57 AM UTC
Org Admins are unable to click on any group from Groups page in Atlassian administration (admin.atlassian.com). Admins are unable to adding/removing users and app access from the groups while accessing from admin.atlassian.com. We are currently investigating the problem. Next update will be shared in 60 mins or sooner.
-
monitoring Feb 18, 2026, 11:28 AM UTC
We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.
-
resolved Feb 18, 2026, 11:30 AM UTC
We have implemented the fix and the group page in the Admin Hub is now functioning as expected.
Read the full incident report →
- Detected by Pingoru
- Feb 18, 2026, 10:57 AM UTC
- Resolved
- Feb 18, 2026, 11:30 AM UTC
- Duration
- 32m
Affected: View ContentiOS AppCreate and EditAndroid AppCommentsAuthentication and User ManagementSearchAdministrationNotificationsMarketplace AppsPurchasing & LicensingSignupConfluence AutomationsCloud to Cloud Migrations - Copy Product DataServer to Cloud Migrations - Copy Product Data
Timeline · 3 updates
-
investigating Feb 18, 2026, 10:57 AM UTC
Org Admins are unable to click on any group from Groups page in Atlassian administration (admin.atlassian.com). Admins are unable to adding/removing users and app access from the groups while accessing from admin.atlassian.com. We are currently investigating the problem. Next update will be shared in 60 mins or sooner.
-
monitoring Feb 18, 2026, 11:28 AM UTC
We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.
-
resolved Feb 18, 2026, 11:30 AM UTC
We have implemented the fix and the group page in the Admin Hub is now functioning as expected.
Read the full incident report →
