Atlassian Outage History

Atlassian is up right now

Pingoru has recorded 1,025 incidents for Atlassian: 401 in the last 12 months and 71 in the last 90 days.

Source: status.atlassian.com · Aggregated across Atlassian products

1,025incidents recorded
401last 12 months
71last 90 days
10 hourstypical duration
Incidents per month
050100AprMayJunJulAugSepOct18
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct3%
Pingoru began tracking Atlassian in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20263765 of 720 (9%)
May 202683286 of 744 (38%)
June 202634267 of 720 (37%)
July 202617130 of 744 (17%)
August 202627131 of 744 (18%)
September 20262577 of 720 (11%)
October 20261817 of 598 (3%)

Incidents, newest first

Critical April 28, 2025 Management of Apps is partially unavailable on different platforms 4h 13m via Atlassian Migrations· Jira: Cloud to Cloud Migrations - Copy Product Data, Jira: Server / Data Center to Cloud Migrations, Jira: Backup, Restore, Import & Export, Jira: Sandbox and 7 more

Started Apr 28, 2025, 11:59 AM UTC· resolved Apr 28, 2025, 04:12 PM UTC

  1. investigating Apr 28, 2025, 11:59 AM UTC

    We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms. Such as apps lifecycle (installation, removals), developer console usage (including tunnelling), and the creation and deployment of Forge apps. Our team is working diligently to resolve this issue and restore services quickly. We are in the process of identifying the root cause and implementing the necessary fixes. Next updates in 1 hour.

  2. identified Apr 28, 2025, 12:55 PM UTC

    We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms, such as apps lifecycle (installation, removals), developer console usage (including tunneling), and the creation and deployment of Forge apps. We have identified the root cause and are in the process of mitigating the impact. We'll keep you posted with further updates. Next updates in 1 hour.

  3. monitoring Apr 28, 2025, 01:42 PM UTC

    The issues causing the unavailability of related Forge apps capabilities on multiple Atlassian platforms have been resolved, and services are now operating normally for all impacted customers. We will continue to closely monitor for stability.

  4. resolved Apr 28, 2025, 04:12 PM UTC

    Between 10:55 AM UTC to 13:15 PM UTC on April 28, 2025, we experienced partial unavailability in managing Forge apps; Such as lifecycle developer console usage, and the creation and deployment of Forge apps for Atlassian Partners, Jira Work Management, Jira, Atlassian Developer, Jira Product Discovery, Compass, and Atlassian Migrations. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the bug have been addressed and we're actively working on a permanent fix. The issue has been resolved and the service is operating normally.

Read the full incident report →

Critical April 25, 2025 Trello is slow or unavailable 32m via Trello· Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing and 1 more

Started Apr 25, 2025, 06:39 PM UTC· resolved Apr 25, 2025, 07:12 PM UTC

  1. monitoring Apr 25, 2025, 06:39 PM UTC

    Trello was slow or unavailable. Our engineering team is actively investigating this incident to determine root cause. Users affected by this incident may have noticeed that Trello was slow or completely unavailable in both the web and mobile apps. Trello operations have recovered. We will update this page as we have additional information.

  2. resolved Apr 25, 2025, 07:12 PM UTC

    Between 18:18 UTC to 18:33 UTC, we experienced an outage for Trello. The issue has been resolved and the service is operating normally. Our teams are investigating and will publish the root cause as soon as available.

  3. postmortem May 16, 2025, 06:16 PM UTC

    ### **SUMMARY** On April 25, 2025, between 18:18 and 18:33 UTC, Atlassian customers using Trello may have experienced service interruptions. The event was triggered by temporarily reduced capacity following a rollback deployment, with insufficient nodes to handle the load. Automated monitoring systems detected the incident within one minute and mitigated it by scaling up the deployment, which put Atlassian systems into a known-good state. The total time to resolution was about 15 minutes. ### **IMPACT** The overall impact was on April 25, 2025, between 18:18 and 18:33 UTC, on Trello. The incident caused service disruption to Trello users, resulting in reduced functionality, slower response times, and errors when performing key actions such as loading boards and cards. ### **ROOT CAUSE** The root cause of the incident was a failure to scale our nodes to optimal capacity caused by a release rollback. If an issue is found during a deployment, we can roll back to a previous release. In this case, a rollback was executed to a previous release that had already undergone a scaling-down process. As that rollback happened, more compute nodes needed to be available to handle the high traffic. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity and strive to avoid incidents like these. We are prioritizing the following efforts as next steps: * Improvements to rollback tooling including UX upgrades and pre-scaling * Conduct an updated incident response training focused on rollback tooling and best practices We apologize to customers whose services were impacted during this incident; we are taking steps designed to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Minor April 23, 2025 Automation Rule execution is delayed 9h 16m via Jira Core· Viewing content, Create and edit, Authentication and User Management, Search and 7 more

Started Apr 23, 2025, 02:18 PM UTC· resolved Apr 23, 2025, 11:35 PM UTC

  1. investigating Apr 23, 2025, 02:18 PM UTC

    We are investigating cases of degraded performance for automation rules for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We will provide more details within the next hour.

  2. investigating Apr 23, 2025, 03:56 PM UTC

    We are investigating automation rule execution delays that are impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We have applied a temporary mitigation and are continuing to investigate for root cause. We will provide more details within the next hour.

  3. investigating Apr 23, 2025, 04:56 PM UTC

    We are still investigating automation rule delays that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. Previous mitigations have decreased the average delays across executions, however some customers may be still be experiencing delays. We are applying more mitigations and will provide more details within the next hour.

  4. investigating Apr 23, 2025, 06:01 PM UTC

    We are still investigating automation rule delays that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. The backlog of previous mitigations has decreased and continues to decrease, however some customers may be still be experiencing delays. The backlog of automations is being processed as we continue to apply mitigations and will provide more details within the next hour.

  5. monitoring Apr 23, 2025, 07:17 PM UTC

    We have applied significant mitigations and the majority of delayed automation executions should be completed within 2 hours. Some customers may experience some delay in some executions during the 2 hours following. Rule execution delays should be mitigated in 4 hours. We will continue to monitor the progress and provide an update within the next hour.

  6. monitoring Apr 23, 2025, 08:12 PM UTC

    A majority of new automation executions are running without delay. Remaining delayed automation executions should be completed within 3 hours. We will continue to monitor the progress and provide an update within the next hour.

  7. monitoring Apr 23, 2025, 09:09 PM UTC

    New executions are running without delay. Remaining delayed executions will complete in the next 2 hours. We will continue to monitor the progress and provide an update within the next hour.

  8. monitoring Apr 23, 2025, 10:11 PM UTC

    New executions are continuing to run without delay. Remaining delayed executions will complete in approximately one hour. We will continue to monitor the progress and provide an update within the next hour.

  9. resolved Apr 23, 2025, 11:35 PM UTC

    Between 13:00 UTC to 23:00 UTC on April 23, 2025, we experienced automation rule execution delays for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally. For some high volume customers who regularly have rule throttling, there may be an extended period to clear full backlogs. For those high volume customers we expect any extended period rule throttling to be resolved by 07:00 UTC on April 24, 2025.

Read the full incident report →

Minor April 23, 2025 Automation Rule execution is delayed 9h 16m via Jira Work Management· Viewing content, Create and edit, Authentication and User Management, Search and 7 more

Started Apr 23, 2025, 02:18 PM UTC· resolved Apr 23, 2025, 11:35 PM UTC

  1. investigating Apr 23, 2025, 02:18 PM UTC

    We are investigating cases of degraded performance for automation rules for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We will provide more details within the next hour.

  2. investigating Apr 23, 2025, 03:56 PM UTC

    We are investigating automation rule execution delays that are impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We have applied a temporary mitigation and are continuing to investigate for root cause. We will provide more details within the next hour.

  3. investigating Apr 23, 2025, 04:56 PM UTC

    We are still investigating automation rule delays that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. Previous mitigations have decreased the average delays across executions, however some customers may be still be experiencing delays. We are applying more mitigations and will provide more details within the next hour.

  4. investigating Apr 23, 2025, 06:01 PM UTC

    We are still investigating automation rule delays that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. The backlog of previous mitigations has decreased and continues to decrease, however some customers may be still be experiencing delays. The backlog of automations is being processed as we continue to apply mitigations and will provide more details within the next hour.

  5. monitoring Apr 23, 2025, 07:17 PM UTC

    We have applied significant mitigations and the majority of delayed automation executions should be completed within 2 hours. Some customers may experience some delay in some executions during the 2 hours following. Rule execution delays should be mitigated in 4 hours. We will continue to monitor the progress and provide an update within the next hour.

  6. monitoring Apr 23, 2025, 08:12 PM UTC

    A majority of new automation executions are running without delay. Remaining delayed automation executions should be completed within 3 hours. We will continue to monitor the progress and provide an update within the next hour.

  7. monitoring Apr 23, 2025, 09:09 PM UTC

    New executions are running without delay. Remaining delayed executions will complete in the next 2 hours. We will continue to monitor the progress and provide an update within the next hour.

  8. monitoring Apr 23, 2025, 10:11 PM UTC

    New executions are continuing to run without delay. Remaining delayed executions will complete in approximately one hour. We will continue to monitor the progress and provide an update within the next hour.

  9. resolved Apr 23, 2025, 11:35 PM UTC

    Between 13:00 UTC to 23:00 UTC on April 23, 2025, we experienced automation rule execution delays for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally. For some high volume customers who regularly have rule throttling, there may be an extended period to clear full backlogs. For those high volume customers we expect any extended period rule throttling to be resolved by 07:00 UTC on April 24, 2025.

Read the full incident report →

Notice April 23, 2025 Automation Rule execution is delayed 9h 16m via Jira Product Discovery· Open projects, Create and delete fields, Add/view data points ("Capture")

Started Apr 23, 2025, 02:18 PM UTC· resolved Apr 23, 2025, 11:35 PM UTC

  1. investigating Apr 23, 2025, 02:18 PM UTC

    We are investigating cases of degraded performance for automation rules for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We will provide more details within the next hour.

  2. investigating Apr 23, 2025, 03:56 PM UTC

    We are investigating automation rule execution delays that are impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. We have applied a temporary mitigation and are continuing to investigate for root cause. We will provide more details within the next hour.

  3. investigating Apr 23, 2025, 04:56 PM UTC

    We are still investigating automation rule delays that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. Previous mitigations have decreased the average delays across executions, however some customers may be still be experiencing delays. We are applying more mitigations and will provide more details within the next hour.

  4. investigating Apr 23, 2025, 06:01 PM UTC

    We are still investigating automation rule delays that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. The backlog of previous mitigations has decreased and continues to decrease, however some customers may be still be experiencing delays. The backlog of automations is being processed as we continue to apply mitigations and will provide more details within the next hour.

  5. monitoring Apr 23, 2025, 07:17 PM UTC

    We have applied significant mitigations and the majority of delayed automation executions should be completed within 2 hours. Some customers may experience some delay in some executions during the 2 hours following. Rule execution delays should be mitigated in 4 hours. We will continue to monitor the progress and provide an update within the next hour.

  6. monitoring Apr 23, 2025, 08:12 PM UTC

    A majority of new automation executions are running without delay. Remaining delayed automation executions should be completed within 3 hours. We will continue to monitor the progress and provide an update within the next hour.

  7. monitoring Apr 23, 2025, 09:09 PM UTC

    New executions are running without delay. Remaining delayed executions will complete in the next 2 hours. We will continue to monitor the progress and provide an update within the next hour.

  8. monitoring Apr 23, 2025, 10:11 PM UTC

    New executions are continuing to run without delay. Remaining delayed executions will complete in approximately one hour. We will continue to monitor the progress and provide an update within the next hour.

  9. resolved Apr 23, 2025, 11:35 PM UTC

    Between 13:00 UTC to 23:00 UTC on April 23, 2025, we experienced automation rule execution delays for Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally. For some high volume customers who regularly have rule throttling, there may be an extended period to clear full backlogs. For those high volume customers we expect any extended period rule throttling to be resolved by 07:00 UTC on April 24, 2025.

Read the full incident report →

Major April 17, 2025 Intermittent Outage with Jira Align 6h 15m via Jira Align

Started Apr 17, 2025, 10:58 PM UTC· resolved Apr 18, 2025, 05:14 AM UTC

  1. monitoring Apr 17, 2025, 10:58 PM UTC

    Jira Align was experiencing intermittent issues across multiple sites between 19:30 UTC and 22:12 UTC. The issue is resolved and the service is operating normally. If you continue to experience issues, please clear your browser cache and restart all open browser windows.

  2. resolved Apr 18, 2025, 05:14 AM UTC

    The issue has been resolved, service has been returned to operational status.

Read the full incident report →

Major April 17, 2025 Intermittent Outage 1h 7m via Jira Align

Started Apr 17, 2025, 09:17 PM UTC· resolved Apr 17, 2025, 10:24 PM UTC

  1. investigating Apr 17, 2025, 09:17 PM UTC

    Jira Align is experiencing intermittent outages across multiple sites. The team is currently investigating.

  2. investigating Apr 17, 2025, 09:33 PM UTC

    For customers experiencing issues, incognito mode in your browser can be used as a work around.

  3. investigating Apr 17, 2025, 10:06 PM UTC

    We have been able to reproduce the issue and are investigating the root cause.

  4. investigating Apr 17, 2025, 10:24 PM UTC

    The issue has been mitigated, service has been returned to operational status. If you continue to experience issues, clear cache and restart all open browser windows.

  5. resolved Apr 17, 2025, 10:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 16, 2025 Users experiencing issues loading some Dashboard widgets in Jira 11h 10m via Jira Product Discovery· Open projects, Create and delete fields, Add/view data points ("Capture")

Started Apr 16, 2025, 11:46 AM UTC· resolved Apr 16, 2025, 10:57 PM UTC

  1. investigating Apr 16, 2025, 11:46 AM UTC

    We are aware of users experiencing issues attempting to load Jira Dashboard widgets. Our team is investigating this issue with priority.

  2. identified Apr 16, 2025, 04:43 PM UTC

    We continue to work on resolving the issue with loading certain Jira Dashboard widgets for Jira Work Management, Jira Service Management, and Jira Product Discovery. We have identified the root cause and expect recovery shortly. We will provide another update at 19:00 UTC.

  3. identified Apr 16, 2025, 07:00 PM UTC

    We continue to work on resolving the issue with loading certain Jira Dashboard widgets for for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. We have identified the root cause and expect recovery shortly. We will provide another update at 22:00 UTC.

  4. identified Apr 16, 2025, 10:21 PM UTC

    We continue to work on resolving the issue with loading certain Jira Dashboard widgets for for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. We have identified the root cause and are currently deploying fixes. We expect to complete the deployments by 23:00 UTC.

  5. resolved Apr 16, 2025, 10:57 PM UTC

    Between 3:30 UTC to 23:00 UTC April 16, 2025, we experienced an issue with loading certain Jira Dashboard widgets for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally.

Read the full incident report →

Minor April 16, 2025 Users experiencing issues loading some Dashboard widgets in Jira 11h 10m via Jira Core· Viewing content, Create and edit, Authentication and User Management, Search and 7 more

Started Apr 16, 2025, 11:46 AM UTC· resolved Apr 16, 2025, 10:57 PM UTC

  1. investigating Apr 16, 2025, 11:46 AM UTC

    We are aware of users experiencing issues attempting to load Jira Dashboard widgets. Our team is investigating this issue with priority.

  2. identified Apr 16, 2025, 04:43 PM UTC

    We continue to work on resolving the issue with loading certain Jira Dashboard widgets for Jira Work Management, Jira Service Management, and Jira Product Discovery. We have identified the root cause and expect recovery shortly. We will provide another update at 19:00 UTC.

  3. identified Apr 16, 2025, 07:00 PM UTC

    We continue to work on resolving the issue with loading certain Jira Dashboard widgets for for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. We have identified the root cause and expect recovery shortly. We will provide another update at 22:00 UTC.

  4. identified Apr 16, 2025, 10:21 PM UTC

    We continue to work on resolving the issue with loading certain Jira Dashboard widgets for for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. We have identified the root cause and are currently deploying fixes. We expect to complete the deployments by 23:00 UTC.

  5. resolved Apr 16, 2025, 10:57 PM UTC

    Between 3:30 UTC to 23:00 UTC April 16, 2025, we experienced an issue with loading certain Jira Dashboard widgets for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally.

Read the full incident report →

Minor April 16, 2025 Users experiencing issues loading some Dashboard widgets in Jira 11h 10m via Jira Work Management· Viewing content, Create and edit, Authentication and User Management, Search and 7 more

Started Apr 16, 2025, 11:46 AM UTC· resolved Apr 16, 2025, 10:57 PM UTC

  1. investigating Apr 16, 2025, 11:46 AM UTC

    We are aware of users experiencing issues attempting to load Jira Dashboard widgets. Our team is investigating this issue with priority.

  2. identified Apr 16, 2025, 04:43 PM UTC

    We continue to work on resolving the issue with loading certain Jira Dashboard widgets for Jira Work Management, Jira Service Management, and Jira Product Discovery. We have identified the root cause and expect recovery shortly. We will provide another update at 19:00 UTC.

  3. identified Apr 16, 2025, 07:00 PM UTC

    We continue to work on resolving the issue with loading certain Jira Dashboard widgets for for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. We have identified the root cause and expect recovery shortly. We will provide another update at 22:00 UTC.

  4. identified Apr 16, 2025, 10:21 PM UTC

    We continue to work on resolving the issue with loading certain Jira Dashboard widgets for for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. We have identified the root cause and are currently deploying fixes. We expect to complete the deployments by 23:00 UTC.

  5. resolved Apr 16, 2025, 10:57 PM UTC

    Between 3:30 UTC to 23:00 UTC April 16, 2025, we experienced an issue with loading certain Jira Dashboard widgets for Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery. The issue has been resolved and the service is operating normally.

Read the full incident report →

Major April 15, 2025 Some Cloud and Sandbox Migrations entering a stuck or failed status 1h 23m via Atlassian Migrations· Jira: Cloud to Cloud Migrations - Copy Product Data, Jira: Server / Data Center to Cloud Migrations, Jira: Sandbox, Confluence: Cloud to Cloud Migrations - Copy Product Data and 2 more

Started Apr 15, 2025, 06:00 AM UTC· resolved Apr 15, 2025, 07:23 AM UTC

  1. identified Apr 15, 2025, 06:00 AM UTC

    We are aware of some customers experiencing issues when attempting to run cloud or sandbox migrations that will cause them to enter a failed or stuck status. Our team is investigating these migrations and we will provide an update as soon as possible. If you are experiencing this issue, please reach out to Atlassian support.

  2. resolved Apr 15, 2025, 07:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 14, 2025 Customers unable to checkout with loom monthly plans 26m via Atlassian Loom

Started Apr 14, 2025, 07:07 PM UTC· resolved Apr 14, 2025, 07:34 PM UTC

  1. identified Apr 14, 2025, 07:07 PM UTC

    Customers are unable to choose a monthly plan when upgrading or purchasing from loom.com. We are investigating this issue.

  2. monitoring Apr 14, 2025, 07:30 PM UTC

    A fix has been implemented and we are monitoring the results

  3. resolved Apr 14, 2025, 07:34 PM UTC

    This issue is now resolved and customers can checkout as expected.

Read the full incident report →

Minor April 14, 2025 New goal links in dashboards have display chart error 5h 34m via Atlassian Focus· Data visualization

Started Apr 14, 2025, 03:59 PM UTC· resolved Apr 14, 2025, 09:33 PM UTC

  1. identified Apr 14, 2025, 03:59 PM UTC

    The issue has been identified and we're rolling out a fix.

  2. monitoring Apr 14, 2025, 04:49 PM UTC

    Fix is merged and we are monitoring its roll out

  3. resolved Apr 14, 2025, 09:33 PM UTC

    The incident has been resolved.

Read the full incident report →

Notice April 14, 2025 Issues loading Administration across Atlassian Products 52m via Atlassian Access· Account Management

Started Apr 14, 2025, 12:40 AM UTC· resolved Apr 14, 2025, 01:33 AM UTC

  1. investigating Apr 14, 2025, 12:40 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 14, 2025, 01:33 AM UTC

    Between 00:00 UTC to 01:05 UTC 14 April, users attempting to load the Administration page for Atlassian products. The issue has been resolved and the service is operating normally.

Read the full incident report →

Notice April 14, 2025 Issues loading Administration across Atlassian Products 52m via Guard· Account Management

Started Apr 14, 2025, 12:40 AM UTC· resolved Apr 14, 2025, 01:33 AM UTC

  1. investigating Apr 14, 2025, 12:40 AM UTC

    We are currently investigating this issue.

  2. resolved Apr 14, 2025, 01:33 AM UTC

    Between 00:00 UTC to 01:05 UTC 14 April, users attempting to load the Administration page for Atlassian products. The issue has been resolved and the service is operating normally.

Read the full incident report →

Critical April 14, 2025 Issues loading Administration across Atlassian Products 55m via Jira Core· Administration

Started Apr 14, 2025, 12:37 AM UTC· resolved Apr 14, 2025, 01:33 AM UTC

  1. investigating Apr 14, 2025, 12:37 AM UTC

    We are aware of an issue where users attempting to load the Administration page are instead seeing a blank page. Our team is investigating with urgency and will provide further update as soon as possible.

  2. resolved Apr 14, 2025, 01:33 AM UTC

    Between 00:00 UTC to 01:05 UTC 14 April, users attempting to load the Administration page for Atlassian products. The issue has been resolved and the service is operating normally.

Read the full incident report →

Critical April 14, 2025 Issues loading Administration across Atlassian Products 55m via Jira Work Management· Administration

Started Apr 14, 2025, 12:37 AM UTC· resolved Apr 14, 2025, 01:33 AM UTC

  1. investigating Apr 14, 2025, 12:37 AM UTC

    We are aware of an issue where users attempting to load the Administration page are instead seeing a blank page. Our team is investigating with urgency and will provide further update as soon as possible.

  2. resolved Apr 14, 2025, 01:33 AM UTC

    Between 00:00 UTC to 01:05 UTC 14 April, users attempting to load the Administration page for Atlassian products. The issue has been resolved and the service is operating normally.

Read the full incident report →

Notice April 4, 2025 Schedule API are getting timed out 46m via OpsGenie

Started Apr 04, 2025, 10:05 AM UTC· resolved Apr 04, 2025, 10:52 AM UTC

  1. investigating Apr 04, 2025, 10:05 AM UTC

    We are investigating cases of degraded performance for Alert Schedules experiencing timeouts and slowness for Opsgenie Cloud customers. Requests have been taking more than 30s and some have been timing out. We will provide more details within the next hour.

  2. resolved Apr 04, 2025, 10:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 4, 2025 Issues accessing Jira and Confluence in some regions 3h 20m via Jira Core· Viewing content, Create and edit, Authentication and User Management, Search and 7 more

Started Apr 04, 2025, 09:56 AM UTC· resolved Apr 04, 2025, 01:16 PM UTC

  1. monitoring Apr 04, 2025, 09:56 AM UTC

    We are aware that some customers experienced access issues with their sites. We identified the root cause and have mitigated the problem. Systems are now stable, and we are monitoring closely to ensure no further issues arise. For those still having trouble accessing their sites, adding /wiki/ to the site URL can serve as a temporary workaround (for example https://site.atlassian.net/wiki/). Further updates will be provided as needed.

  2. resolved Apr 04, 2025, 01:16 PM UTC

    We identified a temporary access issue affecting some customers using several Atlassian Cloud products. All affected products are now back online, and no further impacts have been observed. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor April 4, 2025 Issues accessing Jira and Confluence in some regions 3h 20m via Jira Work Management· Viewing content, Create and edit, Authentication and User Management, Search and 7 more

Started Apr 04, 2025, 09:56 AM UTC· resolved Apr 04, 2025, 01:16 PM UTC

  1. monitoring Apr 04, 2025, 09:56 AM UTC

    We are aware that some customers experienced access issues with their sites. We identified the root cause and have mitigated the problem. Systems are now stable, and we are monitoring closely to ensure no further issues arise. For those still having trouble accessing their sites, adding /wiki/ to the site URL can serve as a temporary workaround (for example https://site.atlassian.net/wiki/). Further updates will be provided as needed.

  2. resolved Apr 04, 2025, 01:16 PM UTC

    We identified a temporary access issue affecting some customers using several Atlassian Cloud products. All affected products are now back online, and no further impacts have been observed. We apologize for any inconvenience this may have caused.

Read the full incident report →

Minor April 3, 2025 Dashboards in Focus not filtering by goals correctly 3h 10m via Atlassian Focus· Data visualization

Started Apr 03, 2025, 02:59 PM UTC· resolved Apr 03, 2025, 06:10 PM UTC

  1. investigating Apr 03, 2025, 02:59 PM UTC

    We're investigating an issue causing Focus dashboards not to filter correctly by goals linked to a focus area. We'll provide updates as we investigate the root cause.

  2. resolved Apr 03, 2025, 06:10 PM UTC

    We've identified the root cause of the issue and implemented a fix that has restored the correct filtering to Focus dashboards.

Read the full incident report →

Major March 24, 2025 Some customers are experiencing an issue viewing Team field in Jira issue view 48m via Jira Core· Viewing content, Create and edit, Authentication and User Management, Search and 7 more

Started Mar 24, 2025, 05:07 PM UTC· resolved Mar 24, 2025, 05:56 PM UTC

  1. investigating Mar 24, 2025, 05:07 PM UTC

    We are investigating reports of users being unable to view and assign the team field value from the issue view for some Jira Work Management, Jira Service Management, and Jira customers.

  2. resolved Mar 24, 2025, 05:56 PM UTC

    Between March 21, 2025 17:00 UTC and March 24, 2025 17:39 UTC, some customers were not able to view and assign the team field value from the issue view in Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

Read the full incident report →

Major March 24, 2025 Some customers are experiencing an issue viewing Team field in Jira issue view 48m via Jira Work Management· Viewing content, Create and edit, Authentication and User Management, Search and 7 more

Started Mar 24, 2025, 05:07 PM UTC· resolved Mar 24, 2025, 05:56 PM UTC

  1. investigating Mar 24, 2025, 05:07 PM UTC

    We are investigating reports of users being unable to view and assign the team field value from the issue view for some Jira Work Management, Jira Service Management, and Jira customers.

  2. resolved Mar 24, 2025, 05:56 PM UTC

    Between March 21, 2025 17:00 UTC and March 24, 2025 17:39 UTC, some customers were not able to view and assign the team field value from the issue view in Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally.

Read the full incident report →

Minor March 20, 2025 Search results not showing in Atlassian Focus 1h 45m via Atlassian Focus· Search

Started Mar 20, 2025, 08:25 PM UTC· resolved Mar 20, 2025, 10:11 PM UTC

  1. investigating Mar 20, 2025, 08:25 PM UTC

    We are investigating reports of search errors for all Atlassian Focus Cloud customers. We will provide more details once we identify the root cause.

  2. identified Mar 20, 2025, 09:26 PM UTC

    We continue to work on resolving the search functionality for Atlassian Focus. We have identified the root cause and are working on a resolution.

  3. resolved Mar 20, 2025, 10:11 PM UTC

    Between 19:35 UTC to 21:50 UTC, we experienced search functionality issues for Atlassian Focus. The issue has been resolved and the service is operating normally.

Read the full incident report →

Minor March 20, 2025 Bitbucket pipelines showing error when running a build. 49m via Bitbucket· Pipelines

Started Mar 20, 2025, 06:11 AM UTC· resolved Mar 20, 2025, 07:01 AM UTC

  1. investigating Mar 20, 2025, 06:11 AM UTC

    We are aware of an issue where users are receiving an error message when running a build. Although we believe builds are still running successfully our team is investigating with urgency and an update will be provided when available.

  2. resolved Mar 20, 2025, 07:01 AM UTC

    The issue where users running builds would receive an error message should now be resolved. This issue was impacting only those using self-hosted runners. It is expected that builds should have still run as expected despite this error message in the meantime.

Read the full incident report →