Get email notifications whenever Jira creates, updates or resolves an incident.
Get text message notifications whenever Jira creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever Jira creates an incident, updates an incident, resolves an incident or changes a component status.
All Systems Operational
About This Site
Here we will post updates about Jira's service availability. For status information about other Atlassian products or services, please visit the Atlassian status page.
Viewing content
?
Operational
Create and edit
?
Operational
Authentication and User Management
Operational
Search
?
Operational
Notifications
?
Operational
Administration
?
Operational
Marketplace
?
Operational
Mobile
?
Operational
Purchasing & Licensing
Operational
Signup
Operational
Automation for Jira
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Oct 14, 2024
No incidents reported today.
Oct 13, 2024
No incidents reported.
Oct 12, 2024
No incidents reported.
Oct 11, 2024
No incidents reported.
Oct 10, 2024
No incidents reported.
Oct 9, 2024
No incidents reported.
Oct 8, 2024
Resolved -
Between 6 AM UTC to 10 AM UTC on October 7th, we experienced issues with automation rules and scheduled rules for Confluence, Jira Work Management, Jira Service Management, and Jira. We have implemented and monitored the fix, and the issue has been resolved. The service is operating normally.
Oct 8, 06:56 UTC
Oct 8, 06:56 UTC
Monitoring -
We are observing a recovery on our monitoring dashboards. The affected rules will be executed in the next few hours, if they haven't been processed already. We will keep monitoring the situation during this time before marking the incident as 'Resolved'.
Oct 7, 11:42 UTC
Oct 7, 11:42 UTC
Identified -
We identified that automation rules running between 6 AM UTC and 10 AM UTC may have been impacted by the incident. Additionally, all scheduled rules during this window were affected. We have taken action to mitigate this issue, and we are currently working on recovery. We know what the fix is and are implementing it now. The affected rules will run once the fix is applied.
Oct 7, 10:31 UTC
Oct 7, 10:31 UTC
Investigating -
We are investigating issues with scheduled automated rules and will provide updates here soon.
Oct 7, 10:08 UTC
Oct 7, 10:08 UTC
Oct 7, 2024
Resolved -
Between 07/Oct/24 8:27 AM CEST to 07/Oct/24 8:28 PM CEST, we experienced the error "Something went wrong on our end" for Jira Software and Jira Service Management. The issue has been resolved and the service is operating normally.
Oct 7, 19:17 UTC
Oct 7, 19:17 UTC
Investigating -
We are investigating issues where the customers faces the error "Something went wrong on our end" and will provide updates here soon.
The issue occurs specifically with browsers with Ad block and the Brave browser.
Oct 7, 17:37 UTC
The issue occurs specifically with browsers with Ad block and the Brave browser.
Oct 7, 17:37 UTC
Resolved -
We have identified that the issue is related to a recent update on the Brave browser (https://brave.com/latest/), which is causing some cookie-related problems for users. As a temporary workaround, we recommend using one of our supported browsers: https://support.atlassian.com/atlassian-account/docs/supported-browsers-for-atlassian-cloud-products/.
We understand that many users prefer Brave, and our engineering team will continue to investigate this issue and work towards a resolution on a best-effort basis.
Oct 7, 09:19 UTC
We understand that many users prefer Brave, and our engineering team will continue to investigate this issue and work towards a resolution on a best-effort basis.
Oct 7, 09:19 UTC
Investigating -
We are investigating an issue with accessing Jira content that is impacting some Jira Cloud customers. We will provide more details within the next hour.
Oct 7, 06:26 UTC
Oct 7, 06:26 UTC
Oct 6, 2024
No incidents reported.
Oct 5, 2024
No incidents reported.
Oct 4, 2024
Resolved -
Between 24/9/24 04:30am UTC to 4/10/24 11:00am UTC, we experienced an issue that prevented automatic minor version upgrades for Connect on Confluence and Jira. The issue has been resolved and the service is operating normally.
Oct 4, 11:01 UTC
Oct 4, 11:01 UTC
Identified -
We continue to work on resolving the minor version update issue for Confluence and Jira.
We have identified the root cause and resolved the issue for Connect Jira Apps.
Minor version updates will be processed over the next 24 hours.
We are working through a fix for Confluence and expect recovery over the coming hours.
Oct 4, 05:30 UTC
We have identified the root cause and resolved the issue for Connect Jira Apps.
Minor version updates will be processed over the next 24 hours.
We are working through a fix for Confluence and expect recovery over the coming hours.
Oct 4, 05:30 UTC
Investigating -
We are investigating reports of automatic minor version upgrades for Atlassian Connect not running successfully. We will provide more details once we identify the root cause.
Oct 4, 02:49 UTC
Oct 4, 02:49 UTC
Resolved -
Syncing times for development information have returned to normal - we have scaled up systems to clear the backlog and will continue monitoring
Oct 4, 02:35 UTC
Oct 4, 02:35 UTC
Update -
We are aware of delays in syncing development information (from Bitbucket, Github, Gitlab) where information may take up to an hour to appear in Jira.
We are scaling up our services to deal with the load and reduce processing times.
Backfilling for Github (and Bitbucket) are impacted with sync times of up to 20 hours - but new commits, branches, prs should sync within 1 hour.
Oct 2, 21:20 UTC
We are scaling up our services to deal with the load and reduce processing times.
Backfilling for Github (and Bitbucket) are impacted with sync times of up to 20 hours - but new commits, branches, prs should sync within 1 hour.
Oct 2, 21:20 UTC
Investigating -
Development Info takes hours time to sync data from Bitbucket to Jira.
Oct 2, 18:13 UTC
Oct 2, 18:13 UTC
Oct 3, 2024
Resolved -
Between 2024-10-02 22:00 UTC to 2024-10-03 22:50 UTC we experienced UI glitch preventing users from using parts of Jira Advanced Roadmaps. The issue has been resolved and the service is operating normally.
Oct 3, 23:04 UTC
Oct 3, 23:04 UTC
Monitoring -
We have identified a fix for the issue and we are working to deploy it to all the affected regions.
Oct 3, 22:33 UTC
Oct 3, 22:33 UTC
Update -
We have identified the root cause and we continue to work on resolving the issue affecting the Jira Plans UI.
Oct 3, 21:13 UTC
Oct 3, 21:13 UTC
Identified -
We are currently experiencing an issue where there is unexpected whitespace on the right side when navigating to Jira Plans.
Oct 3, 19:48 UTC
Oct 3, 19:48 UTC
Resolved -
The issue has been resolved and the service is now operating normally.
Oct 3, 06:04 UTC
Oct 3, 06:04 UTC
Investigating -
Some customers may be experiencing an error showing on the project sidebar, which is impacting their ability to navigate within the project.
We have started to investigate the issue and will provide further updates.
Oct 3, 02:49 UTC
We have started to investigate the issue and will provide further updates.
Oct 3, 02:49 UTC
Oct 2, 2024
Oct 1, 2024
Resolved -
The issue is resolved, customers can now submit new migrations.
Oct 1, 14:55 UTC
Oct 1, 14:55 UTC
Identified -
The issue has been identified and a fix is being implemented.
Sep 30, 13:18 UTC
Sep 30, 13:18 UTC
Investigating -
Server to Cloud and Cloud to Cloud migrations for Jira for those customers in US East are currently not progressing. Migrations will be stuck at the last task that completed, or it will be showing the migration in the ready state if it has not already started.
We are working on a fix and expect to share an update in approximately 60 minutes.
Once the issue is resolved, we expect migrations to continue from the point that they were waiting.
Submitting new migrations at this point will queue, so we advise waiting on the original jobs to complete.
Sep 30, 13:17 UTC
We are working on a fix and expect to share an update in approximately 60 minutes.
Once the issue is resolved, we expect migrations to continue from the point that they were waiting.
Submitting new migrations at this point will queue, so we advise waiting on the original jobs to complete.
Sep 30, 13:17 UTC
Sep 30, 2024
Resolved -
Between 07:55 UTC to 17:10 UTC, we experienced errors for specific status changes in Jira Service Management and Jira Cloud using the Safari browser. The issue has been resolved and the service is operating normally.
Sep 30, 17:15 UTC
Sep 30, 17:15 UTC
Monitoring -
We have identified the root cause of the errors for specific status changes in Jira Service Management and Jira Cloud using the Safari browser. We are now monitoring closely.
Sep 30, 16:54 UTC
Sep 30, 16:54 UTC
Identified -
We are investigating reports of intermittent errors for specific status changes in Jira Service Management and Jira Cloud customers using the Safari browser which are reflected by the display of the error: Unable to update status. Check your network connection and try reloading the problem.
If possible, please use an alternative browser, such as Chrome or Firefox, as a temporary workaround. We will provide more details once we identify the root cause.
Sep 30, 11:55 UTC
If possible, please use an alternative browser, such as Chrome or Firefox, as a temporary workaround. We will provide more details once we identify the root cause.
Sep 30, 11:55 UTC