Cloud & service outages
Page 12
Wed, June 10
Resolved: Heroku Retroactive Feature Disruption
The issue is now resolved.
Tue, June 9
Incident: Some users unable to sign in
The issue affecting SMS-based two-factor authentication for users in EMEA has been resolved, and all services are now functioning as expected. We have adjusted configuration settings to restore normal service and will continue to monitor the situation to ensure stability. We apologize for how you and your business may have been affected by this. We will perform a full investigation of the incident, confirming the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Mon, June 8
Increased latency across multiple products
Jun 8 , 08:59 EDT Resolved - This incident has been resolved. Jun 8 , 08:21 EDT Update - We are continuing to monitor the fix deployed earlier. We will provide another update once the issue is fully resolved. Jun 8 , 07:21 EDT Monitoring - We have deployed a fix and we are monitoring the results. Jun 8 , 07:05 EDT Identified - We are investigating and have identified a fix for increased latency across multiple products. As a result of this issue, some users may see delays in data across the platform.
Users experiencing issues loading work items in Jira and JSM
Jun 8 , 02:56 UTC Resolved - On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely. Jun 8 , 02:36 UTC Identified - We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. Our engineering team is actively working on a re…
Sun, June 7
Users experiencing issues loading work items in Atlassian products
Jun 7 , 00:13 UTC Resolved - The issues relating to viewing and creating work items in Jira should now be fully resolved. Jun 7 , 00:07 UTC Monitoring - A fix has been implemented for the issues some customers have been experiencing with creating and viewing work items in Jira. We are now monitoring for this recovery and will update shortly with further confirmation. Jun 6 , 23:21 UTC Investigating - We are aware of users currently experiencing loading work items across Atlassian products in some regions. We are investigating with urgency and will provide update within one hour.
Thu, June 4
Incident: Administrators may experience errors in member management.
The Slack engineering team identified the cause as a recent update that introduced a code change which caused the invite modal to fail when accessed from the Admin page. We rolled back the change and have confirmed the fix is fully deployed and the issue is resolved.Some workspace Admins were unable to add new members to their workspaces via the Manage Members Admin page. In addition, some users attempting to invite people from this page may have encountered an error or been unable to run macros on their workspaces.Workspace Admins should now be able to add new members via the Manage Members…
Wed, June 3
Incident: Trouble connecting or loading Slack
This issue is now resolved for all users.Current status and recent actions taken: we've resolved the issue where some Slack users may have experienced message send failures and thread loading issues. We identified and addressed the root cause, and services have been fully restored.We apologize for any disruptions to your day.
Degraded performance of Jira and JSM automations in US East
Jun 2 , 16:51 UTC Resolved - On June 2, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Previously delayed automation rules are expected to be completed within 12 hours. Jun 2 , 15:32 UTC Investigating - We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. Some customers may experiences delays in rule execution. We'll provide an up…
Incident: Connectivity Issues Affecting Some Users in Europe
Current status: The Slack engineering team investigated connectivity issues that affected some users between approximately 13:30 and 14:00 UTC on June 2, 2026. The issue has been resolved and no further impact has been reported.Scope: Some users, primarily in Europe, may have experienced difficulty loading or sending Slack messages during this windowWe apologize for any inconvenience this may have caused.
Mon, June 1
For Jira-software viewIssues and viewBoard are degraded
Jun 1 , 13:23 UTC Resolved - This incident has been resolved. The issue causing degraded performance for Jira Software and Jira Service Management in the EU region has been fully mitigated. We have deployed a fix to prevent recurrence. If you continue to experience issues, please contact Atlassian Support. We apologise for the disruption and thank you for your patience. Jun 1 , 09:07 UTC Monitoring - We have implemented a fix for the issue causing degraded performance for Jira Software and Jira Service Management in the EU region. The impact has been mitigated, and we are actively monitoring…
Incident: Partial Degradation Impacting Usergroups
Our investigation has determined that the issue is isolated to a single customer environment and is not impacting the broader service. As a result, this incident will be removed from the status page and we will continue to work directly with the affected customer to address their issue.
Fri, May 29
Incident: Trouble with Slack - General Slack functionality issues
This issue is now resolved for all users.Current status and recent actions taken: We deployed a series of configuration adjustments and infrastructure fixes to restore services. Messaging, Workflows, Apps, and Connections were progressively restored over the last several hours. Some users continued to experience permissions-related issues, including inability to manage channels and Canvas edits not saving, as a result of residual stale cache data. Cache deployment activities completed at 14:13 UTC on May 28, 2026, fully resolving the issue. Scope: This issue affected Slack users globally.Prev…
Wed, May 27
Users facing errors when attempting to view Calendars in Confluence
May 27 , 07:48 UTC Resolved - 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. May 27 , 07:06 UTC Identified - 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. May 27 , 06:03 UTC Investigating - We are investigating an issue where customers attempting to view Calendars rec…
Tue, May 26
Some macros failing to load in the Confluence Cloud editor
May 26 , 13:55 UTC Resolved - 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. May 26 , 11:58 UTC Update - 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. May 26 , 11:58 UTC Update - We are investigating an issue where some custom extension…
Fri, May 22
Resolved: Heroku Retroactive Feature Disruption
The issue is now resolved.
Wed, May 20
Incident: Trouble uploading files and emojis in Slack
This issue is now resolved for all users.Current status and recent actions taken: The fix has successfully deployed, and our health metrics have stabilized. The issue is now fully resolved for all affected users. Scope: This wasn't affecting any specific region, but a percentage of users may have been affected globally.Previous impact to end users: Some users may have experienced slowness when uploading files and emojis in Slack. Attaching or sending files may have taken longer than expected — or failed to complete in a timely manner.Required resolution steps: No additional steps are required…
Mon, May 18
Incident: Huddle AI summaries not being generated
Some Slack users experienced issues where Huddle AI summaries weren't being generated. Users also appeared to be showing as in a huddle after it had ended.We've fixed both issues. Missing summaries were restored, and the system responsible for showing huddle statuses has been refreshed. If you still notice any users appearing stuck in a huddle, please contact Slack Support. We apologize for the inconvenience and any impact this may have had.
Sat, May 16
Azure Metrics Reporting
May 15 , 23:43 EDT Resolved - This incident has been resolved and Azure metrics are reporting as expected. May 15 , 23:27 EDT Monitoring - A fix has been implemented and we are monitoring the results. May 15 , 23:09 EDT Update - We are continuing to work on a fix for this issue. May 15 , 22:40 EDT Identified - The issue has been identified and a fix is being implemented. May 15 , 22:17 EDT Investigating - We are investigating an issue submitting Azure metrics.
Fri, May 15
Incident: Issues affecting file uploads, message edits, channel renames, and channel creations
The issue affecting multiple features, including file uploads, message edits, and channel management, has been resolved. A fix has been fully deployed, and all systems are functioning normally. If you are still experiencing any trouble, please perform a hard reload of Slack by pressing Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). Mobile users should fully close and relaunch the app. We sincerely apologize for the disruption to your day and appreciate your patience while we worked to sort this out.
Thu, May 14
Users experiencing issues accessing multiple Atlassian products
May 14 , 06:48 UTC Resolved - All products and services impacted by this incident should now be fully recovered, and this incident is resolved. May 14 , 06:41 UTC Update - We are approaching full system recovery at this time, and are performing final confirmations that services are restored. May 14 , 06:40 UTC Update - 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 vali…
Users experiencing issues accessing multiple Atlassian products
May 14 , 06:48 UTC Resolved - All products and services impacted by this incident should now be fully recovered, and this incident is resolved. May 14 , 06:41 UTC Update - We are approaching full system recovery at this time, and are performing final confirmations that services are restored. May 14 , 06:40 UTC Update - 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 vali…
Tue, May 12
Incident: EKM customers were previously experiencing issues with channel loading and message delivery
Users who rely on Enterprise Key Management (EKM) may have experienced elevated latency and errors across messaging, channel loading, workflows, and file operations starting around 5:55 AM PDT on May 11, 2026. Impact was mitigated and the incident was brought under control at 9:16 AM PDT on May 11, 2026.We've deployed fixes addressing the root cause of the elevated encryption key request load. If you continue to experience trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). We apologize for the disruption and thank you for your patience.
Sat, May 9
Multiple Atlassian services are experiencing issues
May 8 , 19:45 UTC Resolved - 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. May 8 , 11:12 UTC Update - 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 you…
Multiple Atlassian services are experiencing issues
May 8 , 19:45 UTC Resolved - 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. May 8 , 11:12 UTC Update - 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 you…
Incident: Scheduled Grid Migrations are experiencing extended downtime
This issue is now resolved.Current status and actions being taken: We identified database write throttling as the cause of the stalled grid migrations. We applied a drop rule for jobs that were stuck in a retry loop, which has restored normal migration processing. Scope: A small number of enterprise users undergoing grid migrations experienced extended delays in accessing Slack. Current impact to end users: Affected users may have experienced an inability to access Slack during their migration window. Known workarounds: No workarounds needed at this time.We apologize for how this incident aff…
Fri, May 8
Resolved: Heroku Service Disruption
We have successfully applied the fix to all remaining affected customers. Heroku databases and web applications are now fully operational for all customers. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.
Tue, May 5
Resolved: Heroku Feature Disruption
Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this.
Incident: Slow behaviour in Slack
This issue is now resolved for all users.Current status and recent actions taken: A fix has been deployed that resolved the underlying cause of this issue. Our health metrics have returned to normal levels and workflows are running as expected.Scope: Users in the EU region — primarily teams based in Central Europe — experienced elevated workflow failure rates.Previous impact to end users: Users may have experienced workflows failing to run, with the first step remaining stuck in an initialized state. Some users in the EU region may also have experienced general slowness when using Slack.Requi…
Fri, May 1
Incident: Slack Search Feature Disruption - Japan region
At 23:20 UTC, April 30, 2026, a feature disruption began affecting the Slack Search feature for a subset of customers in Japan region. As a result, users were unable to use Search functionality within Slack.We identified that infrastructure changes to our Search cluster caused a number of internal search nodes to become unavailable, which prevented Search queries from routing correctly. We implemented a series of remediation steps, including increasing cluster capacity and restoring affected search shards. We also blocked certain Search traffic to contain secondary impact while the cluster wa…
Thu, April 30
npm website issues
Apr 29 , 20:49 UTC Resolved - This incident has been resolved. Apr 29 , 20:49 UTC Update - We are continuing to investigate this issue. Apr 29 , 20:07 UTC Investigating - We are currently investigating this issue.
Degraded Performance in View Package and Login on npmjs.com
Apr 29 , 19:35 UTC Resolved - This incident has been resolved. Apr 29 , 18:47 UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr 29 , 16:48 UTC Investigating - We are currently investigating this issue.
Resolved: Heroku Retroactive Feature Disruption
The issue is now resolved.
Wed, April 29
npm website degraded service
Apr 28 , 22:24 UTC Resolved - This incident has been resolved. Apr 28 , 21:04 UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr 28 , 19:55 UTC Investigating - We are currently investigating this issue.
Tue, April 28
npm Website is unavailable
Apr 27 , 22:30 UTC Resolved - This incident has been resolved. Apr 27 , 22:28 UTC Update - We are continuing to investigate this issue. Apr 27 , 21:06 UTC Investigating - We are currently investigating this issue.
Incident: Users May Not Receive Notifications on Slack Thread Replies
We’ve successfully performed a rollback in the production environment, and all systems are now functioning as expected. Users should no longer experience any issues with thread replies not generating a notification banner.We apologize for any inconvenience and appreciate your patience.
Tue, April 21
Figma Make Service Disruption
Apr 20 , 15:50 UTC Resolved - This incident has been resolved at 9:39 am UTC Apr 20 , 07:08 UTC Monitoring - [Mitigated] A fix has been implemented and we're monitoring the results. Apr 20 , 06:42 UTC Investigating - We are investigating an increase in Figma Make error messages
Fri, April 17
Bitbucket Pipelines degraded performance
Apr 16 , 20:44 UTC Resolved - On April 16 at 8:00PM UTC Bitbucket Pipelines users may have experienced performance degradation running new pipelines. The issue has now been resolved, and the service is operating normally for all affected customers. Apr 16 , 20:44 UTC Update - We are investigating cases of degraded performance for Atlassian Bitbucket Pipelines customers. We mitigated an issue preventing new pipelines from starting, and have scaled up services are processing a backlog. Customers should see recovery shortly. Apr 16 , 20:23 UTC Monitoring - We are investigating cases of degraded…
Wed, April 15
Disrupted Rovo availability for Automation rules
Apr 14 , 16:11 UTC Resolved - 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. Apr 14 , 15:46 UTC Monitoring - The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability. Apr 14 , 14:11 UTC Identified - We have identified the issue, and our teams are working to resolve it and restore normal operations as quickly as possible. We w…
Mon, April 13
Users experiencing issues with login across Atlassian products
Apr 13 , 10:17 UTC Resolved - 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. Apr 13 , 08:33 UTC Update - 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. Apr 13 , 07:…
Users experiencing issues with login across Atlassian products
Apr 13 , 10:17 UTC Resolved - 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. Apr 13 , 08:33 UTC Update - 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. Apr 13 , 07:…
Sat, April 11
Figma Make Service Disruption
Apr 10 , 16:00 UTC Resolved - This incident has been resolved. Apr 9 , 22:33 UTC Monitoring - Some users on certain VPN providers may have experienced difficulty loading Figma Make files and published Sites. The issue has been resolved. We are monitoring to confirm full recovery. Apr 9 , 19:00 UTC Investigating - We are investigating an issue some users are experiencing while loading Figma Make files or published Sites.
Wed, April 8
Multiple products impacted by search failures
Apr 8 , 11:43 UTC Resolved - The issue has now been resolved, and the service is operating normally for all affected customers. Apr 8 , 09:03 UTC Monitoring - 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. Apr 8 , 09:03 UTC Update - We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards…
Wed, April 1
Increased errors in viewing packages and authentication on npmjs.com
Apr 1 , 13:12 UTC Resolved - This incident has been resolved. Apr 1 , 12:20 UTC Monitoring - A fix has been implemented and we are monitoring the results. Apr 1 , 10:05 UTC Investigating - We are observing increased errors in viewing packages and authentication on npmjs website. We are investigating this issue.
Degraded Performance in View Package and Login on npmjs.com
Mar 31 , 21:49 UTC Resolved - This incident has been resolved. Mar 31 , 21:12 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 31 , 20:42 UTC Update - We have implemented initial fixes and are continuing to investigate this issue Mar 31 , 19:12 UTC Investigating - We are seeing degraded performance in package viewing and authentication on npmjs website. We are currently investigating the issue.
Tue, March 31
delay and errors viewing packages and submitting web based authentication
Mar 30 , 19:17 UTC Resolved - This incident has been resolved. Mar 30 , 18:19 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 30 , 17:56 UTC Update - We have implemented some initial fixes. We are continuing to investigate the issue. Mar 30 , 16:41 UTC Investigating - We are currently investigating this issue.
delay and errors viewing packages and submitting web based authentication
Mar 30 , 15:59 UTC Resolved - This incident has been resolved. Mar 30 , 15:30 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 30 , 15:17 UTC Identified - The issue has been identified and a fix is being implemented. Mar 30 , 14:54 UTC Investigating - We are currently investigating this issue.
Thu, March 26
Issue with npm website and login.
Mar 25 , 23:26 UTC Resolved - This incident has been resolved. Mar 25 , 23:10 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 25 , 22:39 UTC Investigating - We are currently investigating this issue.
Fri, March 13
Static macro rendering is failing in Confluence Cloud
Mar 13 , 00:26 UTC Resolved - 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. Mar 12 , 13:38 UTC Identified - 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. Mar 12 , 13:38 UTC Update - Confluence Cloud users may experience errors when accessing certain Marketplace macros. Affected customers are seeing t…
Figma Make Publishing Disruption
Mar 12 , 22:11 UTC Resolved - From 12:45 to 4:50 PM UTC today, we experienced an issue that prevented some users from previewing and publishing Figma Make files. We have updated this from Monitoring to Resolved. Mar 12 , 15:19 UTC Monitoring - A fix has been implemented and we're monitoring the results. Mar 12 , 14:43 UTC Identified - We have identified the issue that is preventing some users from previewing and publishing Figma Make files. We are now working to fix it. Mar 12 , 14:00 UTC Investigating - We are investigating an issue loading previews and publishing Figma Make files.
Resolved: Heroku Feature Disruption
The issue is now resolved.