All Systems Operational
atlassian.com   ? Operational
aug.atlassian.com   ? Operational
aui-cdn.atlassian.com   ? Operational
Bitbucket Operational
Atlassian Bitbucket API   Operational
Atlassian Bitbucket Git via HTTPS   Operational
Atlassian Bitbucket Mercurial via HTTPS   Operational
Atlassian Bitbucket Source downloads   Operational
Atlassian Bitbucket SSH   Operational
Atlassian Bitbucket Webhooks   Operational
Atlassian Bitbucket Website   Operational
bitbucket.org   ? Operational
community.atlassian.com   Operational
Confluence Cloud   Operational
confluence.atlassian.com   ? Operational
developer.atlassian.com   ? Operational
Ecosystem Operational
community.developer.atlassian.com   ? Operational
getsupport.atlassian.com   ? Operational
HipChat Operational
Login   Operational
Receive message   Operational
Send message   Operational
id.atlassian.com   Operational
JIRA Cloud   Operational
jira.atlassian.com   ? Operational
marketplace.atlassian.com Operational
Atlassian Marketplace Add-on Listing Pages   Operational
Atlassian Marketplace Add-on Pricing Details   Operational
Atlassian Marketplace Sales API   Operational
Atlassian Marketplace UPM Connectivity   Operational
Atlassian Marketplace Search   Operational
Atlassian Marketplace Marketplace Homepage   Operational
maven.atlassian.com   ? Operational
my.atlassian.com   ? Operational
partners.atlassian.com   ? Operational
partners-jira.atlassian.com   Operational
profile.atlassian.com   Operational
StatusPage.io Operational
API   Operational
Chat Integrations   Operational
Component Alert Parsing   Operational
Email Notifications   Operational
Hosted Pages   Operational
Management Portal   Operational
Public Metrics   Operational
SMS Notifications   Operational
Third Party Components   Operational
Support Email Handling   ? Operational
support.atlassian.com   ? Operational
translations.atlassian.com   ? Operational
Trello   Operational
university.atlassian.com   ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
GSAC will be upgraded to address known bugs and performance issues prior to the seasonally high support load of spring.

During this time the service will not be available. Customers will be able to create support cases at http://support.atlassian.com/ and they will be entered in the support system when it is back online.

Customers with weekend support products should utilize phone support and other channels to get help during the maintenance window.
Posted on Jan 17, 15:05 UTC
Past Incidents
Jan 18, 2018

No incidents reported today.

Jan 17, 2018
Resolved - The systems are back to normal operation and the engineering team is declaring this incident resolved.
Jan 17, 22:28 UTC
Monitoring - We are seeing the systems return to normal operations. We will continue to monitor for a bit before resolving the incident. Thank you again for your patience.
Jan 17, 21:56 UTC
Identified - The engineering teams identified the issue and have put mitigations in place. We will continue to monitor the systems to confirm systems return to normal operations. Thank you for your patience.
Jan 17, 21:41 UTC
Investigating - We have received reports of customers having issues connecting to Atlassian Identity services and thus affecting logins to other Atlassian properties such as Atlassian Community, Jira, Stride, and Confluence. The engineering teams are currently investigating the issue.
Jan 17, 21:30 UTC
HOT-82838 - Issue with processing emails sent to default email handler was caused by recent code change. Rollback to previous version solved the problem and as of now, Jira is responding normally.
Jan 17, 14:17 UTC
Resolved - This issue is now resolved.
Jan 17, 10:55 UTC
Investigating - confluence.atlassian.com is down at the moment. We are actively working to bring it up again
Jan 17, 10:30 UTC
Jan 16, 2018

No incidents reported.

Jan 15, 2018

No incidents reported.

Jan 14, 2018

No incidents reported.

Jan 13, 2018

No incidents reported.

Jan 12, 2018
Resolved - We have successfully returned Bitbucket Cloud to normal response times and will no longer be providing status updates about the recent performance degradation. We want to thank all customers for your patience as we worked on resolving the issue. We know that you rely on Bitbucket to keep your teams working and your businesses running, and apologize for the disruption this has caused.

We will be publishing a post-mortem next week on this Statuspage.

If you have a specific question about your repository, you can raise an issue with our support team here: https://support.atlassian.com/contact
Jan 12, 19:12 UTC
Update - The effort to repair Bitbucket Cloud's affected storage volumes is approximately 50% complete and we are continuing to target Saturday, Jan 13 for completion of this process. We will provide status updates every 12 hours to communicate our progress.
Jan 12, 06:57 UTC
Update - The effort to repair Bitbucket Cloud's affected storage volumes is approximately 40% complete and we are continuing to target Saturday, Jan 13 for completion of this process. We will provide status updates every 12 hours to communicate our progress.
Jan 11, 18:47 UTC
Update - As communicated previously, we are continuing the maintenance process to return Bitbucket Cloud to normal performance after an issue with our storage system. There was no data loss associated with this incident.

The repair effort for the affected storage volumes is approximately 30% complete and we are continuing to target Saturday, Jan 13 for completion of this process. We will provide status updates every 12 hours to communicate our progress.

If you have a specific question about your repository, you can raise an issue with our support team here: https://support.atlassian.com/contact
Jan 11, 06:57 UTC
Update - We are running a multi-day maintenance process to rebuild our storage volumes and return to normal performance. Bitbucket Cloud services and repositories are online and available for all users, however some will experience slower than normal response times until the maintenance completes. We are continuing to make improvements throughout the day to enhance performance in the interim.

We expect Bitbucket Cloud to return to normal response times by Saturday, January 13th, 2018, and will continue to provide status updates every 12 hours to communicate our progress.

If you have a specific question about your repository, you can raise an issue with our support team here: https://support.atlassian.com/contact/
Jan 10, 18:53 UTC
Monitoring - Our team continues to work around the clock to recover from an incident that involved a failure in Bitbucket's storage layer. Most services and repositories are functioning normally, albeit slower than usual while the storage layer repairs itself. No data has been lost, but we are continuing to run a maintenance process to bring everything back online at full capacity.
Jan 10, 02:21 UTC
Identified - All services and all repositories are back, but overall performance of the website and SSH/HTTPS transactions will continue to be slow.
We are still in the process of mitigating the performance issue and will be able to share additional information soon.
Thank you for your patience. Next update 1 hour.
Jan 9, 23:46 UTC
Update - All services and all repositories are back, but overall performance of the website, and SSH/HTTPS transactions will continue to be slow.

We are in the process of mitigating the performance issue, but cannot currently give an accurate eta for when this will be completed.

Thank you for your patience. Next update in three hours.
Jan 9, 20:23 UTC
Update - All services and all repositories are back, but overall performance of the website, and SSH/HTTPS transactions will continue to be slow.
We are in the process of fixing the overall issue with our vendor, but cannot currently give an accurate ETA for when this will be completed.

Thank you for your patience. Next update in an hour.
Jan 9, 19:15 UTC
Update - The team is working with our storage vendor to address performance issues. Thank you for your patience. Next update in an hour.
Jan 9, 18:13 UTC
Update - The team is continuing to investigate possible network and/or storage layer issues, thank you for your patience. Next update in an hour.
Jan 9, 16:57 UTC
Update - We are continuing to investigate and test potential fixes for this service degradation, thank you for your patience. Next update in 60 minutes or if there is a notable change in status.
Jan 9, 15:51 UTC
Update - We are continuing to investigate the service degradation and are testing out potential fixes. Thank you for your patience, the next update will be in 60 minutes.
Jan 9, 14:52 UTC
Update - We are continuing to investigate issues with BitBucket.org and apologize for any inconvenience. Next update in 60 minutes or if there is a material change in status.
Jan 9, 13:39 UTC
Investigating - We are investigating issues with BitBucket.org. We apologize for the disruption in service. Our next update will be posted within 60 minutes.
Jan 9, 12:35 UTC
Jan 11, 2018
Resolved - This incident has been resolved. If you still have any difficulties, please contact Atlassian Support.
Jan 11, 18:47 UTC
Monitoring - We have identified earlier today a surge of CPU usage across multiple instances causing outages. We've already applied a fix and are currently monitoring.
Jan 11, 17:09 UTC
Jan 8, 2018
Resolved - This incident has been resolved.
Jan 8, 15:12 UTC
Monitoring - Our engineering team have fully recovered the degraded performance and we will continue to monitor this situation.
Jan 8, 12:58 UTC
Identified - We have identified the root cause as unusual load and our engineering team implemented mitigation fix in place and there will be around 15 mins outage observed during the fix. We are still monitoring closely the stability of the fix to make sure the problem is resolved and will update back accordingly.
Jan 8, 12:21 UTC
Investigating - We have received reports of degraded performance affecting some customers in Jira. We are currently investigating and will provide further updates as they are available.
Jan 8, 10:04 UTC
Jan 7, 2018

No incidents reported.

Jan 6, 2018

No incidents reported.

Jan 5, 2018

No incidents reported.

Jan 4, 2018

No incidents reported.