Company Logo

Is there an Atlassian Statuspage outage?

Atlassian Statuspage status: Systems Active

Last checked: 6 minutes ago

Get notified about any outages, downtime or incidents for Atlassian Statuspage and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Atlassian Statuspage outages and incidents

Outage and incident data over the last 30 days for Atlassian Statuspage.

There have been 1 outages or incidents for Atlassian Statuspage in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Atlassian Statuspage

Outlogger tracks the status of these components for Xero:

Signup Active
Admin Google Auth Active
Admin SAML 2.0 Active
Admin User+Pass Active
Page Access Users Active
Page Google Auth Active
Page IP Restriction Active
Page SAML 2.0 Active
Generic Email Active
Jira Software Integration Active
New Relic Email Active
PagerDuty Webhook Active
Pingdom Email Active
Slack Active
HTTP Pages Active
HTTPS Pages Active
Public API Active
Shortlinks Active
SMS Subscription Active
Status Embed Widget Active
Authenticated API Active
Billing Active
DNS Validation Active
SSL Provisioning Active
Web Portal Active
Email Active
SMS Active
Twitter Active
Webhook Active
API Documentation Active
Knowledge Base Active
Marketing Site (www.statuspage.io) Active
Metastatuspage Active
Ticketing Active
Custom Integration Active
Datadog Integration Active
Librato Integration Active
New Relic Integration Active
Pingdom Integration Active
External Active
Statuspage Active
Component Status
Signup Active
Active
Admin Google Auth Active
Admin SAML 2.0 Active
Admin User+Pass Active
Page Access Users Active
Page Google Auth Active
Page IP Restriction Active
Page SAML 2.0 Active
Active
Generic Email Active
Jira Software Integration Active
New Relic Email Active
PagerDuty Webhook Active
Pingdom Email Active
Active
Slack Active
Active
HTTP Pages Active
HTTPS Pages Active
Public API Active
Shortlinks Active
SMS Subscription Active
Status Embed Widget Active
Active
Authenticated API Active
Billing Active
DNS Validation Active
SSL Provisioning Active
Web Portal Active
Active
Email Active
SMS Active
Twitter Active
Webhook Active
Active
API Documentation Active
Knowledge Base Active
Marketing Site (www.statuspage.io) Active
Metastatuspage Active
Ticketing Active
Active
Custom Integration Active
Datadog Integration Active
Librato Integration Active
New Relic Integration Active
Pingdom Integration Active
Active
External Active
Statuspage Active

Latest Atlassian Statuspage outages and incidents.

View the latest incidents for Atlassian Statuspage and check for official updates:

Updates:

  • Time: April 29, 2022, 8:34 p.m.
    Status: Postmortem
    Update: Earlier this month, several hundred Atlassian customers were impacted by a site outage. We have published a Post-Incident Review which includes a technical deep dive on what happened, details on how we restored customers sites, and the immediate actions we’ve taken to improve our operations and approach to incident management. [https://www.atlassian.com/engineering/post-incident-review-april-2022-outage](https://www.atlassian.com/engineering/post-incident-review-april-2022-outage)
  • Time: April 17, 2022, 10:06 p.m.
    Status: Resolved
    Update: We have restored impacted Statuspage customer sites and the service is operating normally. If you need assistance, please reply to your support ticket so that our engineers can work with you. If you have any trouble accessing your support ticket, contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu) Our teams will be working on a detailed Post Incident Report to share publicly by the end of April.
  • Time: April 17, 2022, 7:12 p.m.
    Status: Monitoring
    Update: We have restored impacted Statuspage customer sites and the service is operating normally. If you need assistance, please reply to your support ticket so that our engineers can work with you. If you have any trouble accessing your support ticket, contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 17, 2022, 4:19 a.m.
    Status: Identified
    Update: We have now restored 99% of users impacted by the outage and have reached out to all affected customers. Our teams are available to help customers with any concerns. If you need assistance, please reply to your support ticket so that our engineers can work with you. If you have any trouble accessing your support ticket, contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 16, 2022, 8:12 p.m.
    Status: Identified
    Update: We have now restored 85% of users impacted by the outage and will continue to get sites back to customers for validation, over the weekend. As we hand your restored site over to you for validation, please reach out to our teams should you find any issues so that our support engineers can work to get you fully operational. You can contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 16, 2022, 1:42 a.m.
    Status: Identified
    Update: We have now restored 78% of users impacted by the outage as we continue to move with more speed and accuracy. Our teams will continue to restore sites through the weekend, and we expect to have all sites restored no later than end of day Tuesday, April 19th PT. As we restore your site and hand it over to you for validation, please reach out to our teams should you find any issues so that our support engineers can work to get you fully restored. You can contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 15, 2022, 8:13 p.m.
    Status: Identified
    Update: We have made significant progress over the last 24 hours and have now restored functionality for 62% of users impacted by the outage. We have also doubled the size of the batches we are pushing through the restoration process, which was a result of optimizing automated processes as well as accelerating our restoration speed. Our global engineering teams continue to work 24/7, and we expect to progress quickly through technical restoration of remaining customer sites over the weekend. If you do not have access to your open ticket, please contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 15, 2022, 3:06 a.m.
    Status: Identified
    Update: We have now restored functionality for 55% of users impacted by the outage. With automation in full effect, we have significantly increased the pace at which we are conducting technical restoration of affected customer sites, and we have reduced the time required for the validation of restored sites by half. If you are still experiencing an outage and do not have access to your open ticket, please contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 14, 2022, 8:14 p.m.
    Status: Identified
    Update: We have now restored functionality for 53% of users impacted by the outage. As outlined in yesterday’s update, we are restoring affected customers using a three step process: 1. Technical restoration of affected sites 2. Internal validation of restored sites 3. Validating with affected customers before enabling their users By automating some of our validation steps, we have now reduced time for internal validation of restored sites by half, which allows our support engineers to more quickly engage restored customers for validation and full site handover. If you are still experiencing an outage and do not have access to your open ticket, please contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 14, 2022, 3:53 p.m.
    Status: Identified
    Update: We have restored functionality for 49% of users impacted by the outage. We are taking a batch-based approach to restoring customers, and to-date, this process has been semi-automated. We are beginning to shift towards a more automated process to restore sites. That said, there are still a number of steps required before we hand a site to customers for review and acceptance. We are restoring affected customers identified by a mix of multiple variables including site size, complexity, edition, tenure, and several other factors in groups of up to 60 at a time. The full restoration process involves our engineering teams, our customer support teams, and our customer, and has three steps: 1. Technical restoration involving meta-data recovery, data restores across a number of services, and ensuring the data across the different systems is working correctly for product and ecosystem apps 2. Verification of site functionality to ensure the technical restoration has worked as expected 3. Lastly, working directly with the affected customer to enable them to verify their data and functionality before enabling for their users We have also contacted all customers who are *up next* for step 3 in the site restoration process described above. These customers are aware that they are next in queue through their support ticket and/or via a support engineer. We have proactively reached out to technical contacts and system admins at all impacted customers, and opened support tickets for each of them. However, we learned that some customers have not yet heard from us or engaged with our support team. If you are experiencing an outage and do not have access to your open ticket, please contact us through our (choose the Billing, Payments, & Pricing options from the drop down menu): https://support.atlassian.com/contact/#/ For more information from our engineering team, please read our update from our CTO, Sri Viswanath: https://www.atlassian.com/engineering/april-2022-outage-update
  • Time: April 12, 2022, 1:48 p.m.
    Status: Identified
    Update: The team is moving through the restoration process this week and is accelerating toward recovery. Functionality for 40% of impacted users has been restored.
  • Time: April 11, 2022, 4:04 p.m.
    Status: Identified
    Update: A small number of Atlassian customers continue to experience service outages and are unable to access their sites. Our global engineering teams are working 24/7 to make progress on this incident. At this time, we have rebuilt functionality for over 35% of the users who are impacted by the service outage, with no reported data loss. The rebuild stage is particularly complex due to several steps that are required to validate sites and verify data. These steps require extra time, but are critical to ensuring the integrity of rebuilt sites. We apologize for the length and severity of this incident and have taken steps to avoid a recurrence in the future.
  • Time: April 11, 2022, 12:11 p.m.
    Status: Identified
    Update: A small number of Atlassian customers continue to experience service outages and are unable to access their sites. Our global engineering teams are working 24/7 to make progress on this incident. At this time, we have rebuilt functionality for over 35% of the users who are impacted by the service outage, with no reported data loss. The rebuild stage is particularly complex due to several steps that are required to validate sites and verify data. These steps require extra time, but are critical to ensuring the integrity of rebuilt sites. We apologize for the length and severity of this incident and have taken steps to avoid a recurrence in the future.
  • Time: April 11, 2022, 9:01 a.m.
    Status: Identified
    Update: A small number of Atlassian customers continue to experience service outages and are unable to access their sites. Our global engineering teams are working 24/7 to make progress on this incident. At this time, we have rebuilt functionality for over 35% of the users who are impacted by the service outage, with no reported data loss. The rebuild stage is particularly complex due to several steps that are required to validate sites and verify data. These steps require extra time, but are critical to ensuring the integrity of rebuilt sites. We apologize for the length and severity of this incident and have taken steps to avoid a recurrence in the future.
  • Time: April 11, 2022, 12:50 a.m.
    Status: Identified
    Update: A dedicated team continue to work 24/7 to expedite service recovery. Restoration of all customers remains our top priority. We hear and appreciate all the feedback from our valued customers and are taking every necessary step to both restore full service and ensure site integrity as soon as possible.
  • Time: April 10, 2022, 7:45 p.m.
    Status: Identified
    Update: We are still working 24/7 to restore service to affected customers. We have restored partial access for some customers and will be continuing to restore access into next week.
  • Time: April 10, 2022, 1:14 p.m.
    Status: Identified
    Update: We continue to work 24/7 to restore service to affected customers. We have restored partial access for some customers and will be continuing to restore access into next week.
  • Time: April 10, 2022, 9:35 a.m.
    Status: Identified
    Update: Our teams are committed to restoring each customer’s service as soon as possible and are working through the weekend toward recovery.
  • Time: April 10, 2022, 4:05 a.m.
    Status: Identified
    Update: Our teams are committed to restoring each customer’s service as soon as possible and are working through the weekend toward recovery.
  • Time: April 9, 2022, 10:23 p.m.
    Status: Identified
    Update: The restoration process is underway. At this time we have no new significant updates, but the team continues to work around the clock to bring our customers back online.
  • Time: April 9, 2022, 6:25 p.m.
    Status: Identified
    Update: The restoration process is underway. At this time we have no new significant updates, but the team continues to work around the clock to bring our customers back online.
  • Time: April 9, 2022, 2:33 p.m.
    Status: Identified
    Update: Our team is working 24/7 to progress through site restoration work. Core functionality has been restored across a number of sites. We are continuously improving the process with the aim of accelerating the restoration process from here.
  • Time: April 9, 2022, 10:52 a.m.
    Status: Identified
    Update: Our team is working 24/7 to progress through site restoration work. Core functionality has been restored across a number of sites. We are continuously improving the process with the aim of accelerating the restoration process from here.
  • Time: April 9, 2022, 1:36 a.m.
    Status: Identified
    Update: The team is continuing the restoration process through the weekend and working toward recovery. We are continuously improving the process based on customer feedback and applying those learnings as we bring more customers online.
  • Time: April 8, 2022, 8:28 p.m.
    Status: Identified
    Update: Restoration work to restore sites is underway and will continue into the weekend. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of these site restorations.
  • Time: April 8, 2022, 5:11 p.m.
    Status: Identified
    Update: Restoration work to restore sites is underway and will continue into the weekend. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of these site restorations.
  • Time: April 8, 2022, 3:30 p.m.
    Status: Identified
    Update: We have started successfully restoring sites and continue to work on restoration to a wider cohort of customers. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of these site restorations.
  • Time: April 8, 2022, 10:59 a.m.
    Status: Identified
    Update: We have started successfully restoring sites and continue to work on restoration to a wider cohort of customers. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of this first round of restorations remains the same from our last update.
  • Time: April 8, 2022, 7:53 a.m.
    Status: Identified
    Update: We have started successfully restoring sites and continue to work on restoration to a wider cohort of customers. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of this first round of restorations remains the same from our last update.
  • Time: April 8, 2022, 1:27 a.m.
    Status: Identified
    Update: We continue to work on partial restoration to a cohort of customers. The plan is to take a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of this first round of restorations remains the same from our last update
  • Time: April 7, 2022, 9:51 p.m.
    Status: Identified
    Update: We continue to work on partial restoration to the first cohort of customers. The plan to take a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of this first round of restorations remains the same from our last update.
  • Time: April 7, 2022, 6:43 p.m.
    Status: Identified
    Update: We are beginning partial restoration to a cohort of customers. The early stages of this process will be controlled and hands-on, as we work with customers live to get feedback and ensure that restoration is working correctly before we accelerate the process for the next cohort. We will continue to post updates here as we move the process along.
  • Time: April 7, 2022, 12:26 p.m.
    Status: Identified
    Update: We are continuing work in the verification stage on a subset of instances. Once reenabled, support will update accounts via opened incident tickets. Restoration of customer sites remains our first priority and we are coordinating with teams globally to ensure that work continues 24/7 until all instances are restored.
  • Time: April 7, 2022, 9:34 a.m.
    Status: Identified
    Update: We are continuing work in the verification stage on a subset of instances. Once reenabled, support will update accounts via opened incident tickets. Restoration of customer sites remains our first priority and we are coordinating with teams globally to ensure that work continues 24/7 until all instances are restored.
  • Time: April 7, 2022, 4:19 a.m.
    Status: Identified
    Update: We are continuing work in the verification stage on a subset of instances. Once reenabled, support will update accounts via opened incident tickets. Restoration of customer sites remains our first priority and we are coordinating with teams globally to ensure that work continues 24/7 until all instances are restored.
  • Time: April 6, 2022, 9:26 p.m.
    Status: Identified
    Update: We are continuing to work on the resolution of the incidents for some Statuspage, Jira Work Management, Jira Service Management, Confluence, Jira Software, Atlassian Access, Jira Product Discovery, and Opsgenie Cloud customers.
  • Time: April 5, 2022, 9:11 p.m.
    Status: Identified
    Update: We have partially reactivated the Statuspages of affected customers. The hosted pages should be up, and the API capabilities have been restored so affected customers can use this to manage their pages while work is done to restore access to the manage portal. We have defined two processes to resolution of the issues impacting some customers. These processes each involve multiple stages of work. We are currently working on one of the processes and we will provide more detail as we progress through resolution.
  • Time: April 5, 2022, 1:45 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.

Updates:

  • Time: April 29, 2022, 8:34 p.m.
    Status: Postmortem
    Update: Earlier this month, several hundred Atlassian customers were impacted by a site outage. We have published a Post-Incident Review which includes a technical deep dive on what happened, details on how we restored customers sites, and the immediate actions we’ve taken to improve our operations and approach to incident management. [https://www.atlassian.com/engineering/post-incident-review-april-2022-outage](https://www.atlassian.com/engineering/post-incident-review-april-2022-outage)
  • Time: April 17, 2022, 10:06 p.m.
    Status: Resolved
    Update: We have restored impacted Statuspage customer sites and the service is operating normally. If you need assistance, please reply to your support ticket so that our engineers can work with you. If you have any trouble accessing your support ticket, contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu) Our teams will be working on a detailed Post Incident Report to share publicly by the end of April.
  • Time: April 17, 2022, 7:12 p.m.
    Status: Monitoring
    Update: We have restored impacted Statuspage customer sites and the service is operating normally. If you need assistance, please reply to your support ticket so that our engineers can work with you. If you have any trouble accessing your support ticket, contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 17, 2022, 4:19 a.m.
    Status: Identified
    Update: We have now restored 99% of users impacted by the outage and have reached out to all affected customers. Our teams are available to help customers with any concerns. If you need assistance, please reply to your support ticket so that our engineers can work with you. If you have any trouble accessing your support ticket, contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 16, 2022, 8:12 p.m.
    Status: Identified
    Update: We have now restored 85% of users impacted by the outage and will continue to get sites back to customers for validation, over the weekend. As we hand your restored site over to you for validation, please reach out to our teams should you find any issues so that our support engineers can work to get you fully operational. You can contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 16, 2022, 1:42 a.m.
    Status: Identified
    Update: We have now restored 78% of users impacted by the outage as we continue to move with more speed and accuracy. Our teams will continue to restore sites through the weekend, and we expect to have all sites restored no later than end of day Tuesday, April 19th PT. As we restore your site and hand it over to you for validation, please reach out to our teams should you find any issues so that our support engineers can work to get you fully restored. You can contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 15, 2022, 8:13 p.m.
    Status: Identified
    Update: We have made significant progress over the last 24 hours and have now restored functionality for 62% of users impacted by the outage. We have also doubled the size of the batches we are pushing through the restoration process, which was a result of optimizing automated processes as well as accelerating our restoration speed. Our global engineering teams continue to work 24/7, and we expect to progress quickly through technical restoration of remaining customer sites over the weekend. If you do not have access to your open ticket, please contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 15, 2022, 3:06 a.m.
    Status: Identified
    Update: We have now restored functionality for 55% of users impacted by the outage. With automation in full effect, we have significantly increased the pace at which we are conducting technical restoration of affected customer sites, and we have reduced the time required for the validation of restored sites by half. If you are still experiencing an outage and do not have access to your open ticket, please contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 14, 2022, 8:14 p.m.
    Status: Identified
    Update: We have now restored functionality for 53% of users impacted by the outage. As outlined in yesterday’s update, we are restoring affected customers using a three step process: 1. Technical restoration of affected sites 2. Internal validation of restored sites 3. Validating with affected customers before enabling their users By automating some of our validation steps, we have now reduced time for internal validation of restored sites by half, which allows our support engineers to more quickly engage restored customers for validation and full site handover. If you are still experiencing an outage and do not have access to your open ticket, please contact us at https://support.atlassian.com/contact/#/ (choose the Billing, Payments, & Pricing options from the drop down menu).
  • Time: April 14, 2022, 3:53 p.m.
    Status: Identified
    Update: We have restored functionality for 49% of users impacted by the outage. We are taking a batch-based approach to restoring customers, and to-date, this process has been semi-automated. We are beginning to shift towards a more automated process to restore sites. That said, there are still a number of steps required before we hand a site to customers for review and acceptance. We are restoring affected customers identified by a mix of multiple variables including site size, complexity, edition, tenure, and several other factors in groups of up to 60 at a time. The full restoration process involves our engineering teams, our customer support teams, and our customer, and has three steps: 1. Technical restoration involving meta-data recovery, data restores across a number of services, and ensuring the data across the different systems is working correctly for product and ecosystem apps 2. Verification of site functionality to ensure the technical restoration has worked as expected 3. Lastly, working directly with the affected customer to enable them to verify their data and functionality before enabling for their users We have also contacted all customers who are *up next* for step 3 in the site restoration process described above. These customers are aware that they are next in queue through their support ticket and/or via a support engineer. We have proactively reached out to technical contacts and system admins at all impacted customers, and opened support tickets for each of them. However, we learned that some customers have not yet heard from us or engaged with our support team. If you are experiencing an outage and do not have access to your open ticket, please contact us through our (choose the Billing, Payments, & Pricing options from the drop down menu): https://support.atlassian.com/contact/#/ For more information from our engineering team, please read our update from our CTO, Sri Viswanath: https://www.atlassian.com/engineering/april-2022-outage-update
  • Time: April 12, 2022, 1:48 p.m.
    Status: Identified
    Update: The team is moving through the restoration process this week and is accelerating toward recovery. Functionality for 40% of impacted users has been restored.
  • Time: April 11, 2022, 4:04 p.m.
    Status: Identified
    Update: A small number of Atlassian customers continue to experience service outages and are unable to access their sites. Our global engineering teams are working 24/7 to make progress on this incident. At this time, we have rebuilt functionality for over 35% of the users who are impacted by the service outage, with no reported data loss. The rebuild stage is particularly complex due to several steps that are required to validate sites and verify data. These steps require extra time, but are critical to ensuring the integrity of rebuilt sites. We apologize for the length and severity of this incident and have taken steps to avoid a recurrence in the future.
  • Time: April 11, 2022, 12:11 p.m.
    Status: Identified
    Update: A small number of Atlassian customers continue to experience service outages and are unable to access their sites. Our global engineering teams are working 24/7 to make progress on this incident. At this time, we have rebuilt functionality for over 35% of the users who are impacted by the service outage, with no reported data loss. The rebuild stage is particularly complex due to several steps that are required to validate sites and verify data. These steps require extra time, but are critical to ensuring the integrity of rebuilt sites. We apologize for the length and severity of this incident and have taken steps to avoid a recurrence in the future.
  • Time: April 11, 2022, 9:01 a.m.
    Status: Identified
    Update: A small number of Atlassian customers continue to experience service outages and are unable to access their sites. Our global engineering teams are working 24/7 to make progress on this incident. At this time, we have rebuilt functionality for over 35% of the users who are impacted by the service outage, with no reported data loss. The rebuild stage is particularly complex due to several steps that are required to validate sites and verify data. These steps require extra time, but are critical to ensuring the integrity of rebuilt sites. We apologize for the length and severity of this incident and have taken steps to avoid a recurrence in the future.
  • Time: April 11, 2022, 12:50 a.m.
    Status: Identified
    Update: A dedicated team continue to work 24/7 to expedite service recovery. Restoration of all customers remains our top priority. We hear and appreciate all the feedback from our valued customers and are taking every necessary step to both restore full service and ensure site integrity as soon as possible.
  • Time: April 10, 2022, 7:45 p.m.
    Status: Identified
    Update: We are still working 24/7 to restore service to affected customers. We have restored partial access for some customers and will be continuing to restore access into next week.
  • Time: April 10, 2022, 1:14 p.m.
    Status: Identified
    Update: We continue to work 24/7 to restore service to affected customers. We have restored partial access for some customers and will be continuing to restore access into next week.
  • Time: April 10, 2022, 9:35 a.m.
    Status: Identified
    Update: Our teams are committed to restoring each customer’s service as soon as possible and are working through the weekend toward recovery.
  • Time: April 10, 2022, 4:05 a.m.
    Status: Identified
    Update: Our teams are committed to restoring each customer’s service as soon as possible and are working through the weekend toward recovery.
  • Time: April 9, 2022, 10:23 p.m.
    Status: Identified
    Update: The restoration process is underway. At this time we have no new significant updates, but the team continues to work around the clock to bring our customers back online.
  • Time: April 9, 2022, 6:25 p.m.
    Status: Identified
    Update: The restoration process is underway. At this time we have no new significant updates, but the team continues to work around the clock to bring our customers back online.
  • Time: April 9, 2022, 2:33 p.m.
    Status: Identified
    Update: Our team is working 24/7 to progress through site restoration work. Core functionality has been restored across a number of sites. We are continuously improving the process with the aim of accelerating the restoration process from here.
  • Time: April 9, 2022, 10:52 a.m.
    Status: Identified
    Update: Our team is working 24/7 to progress through site restoration work. Core functionality has been restored across a number of sites. We are continuously improving the process with the aim of accelerating the restoration process from here.
  • Time: April 9, 2022, 1:36 a.m.
    Status: Identified
    Update: The team is continuing the restoration process through the weekend and working toward recovery. We are continuously improving the process based on customer feedback and applying those learnings as we bring more customers online.
  • Time: April 8, 2022, 8:28 p.m.
    Status: Identified
    Update: Restoration work to restore sites is underway and will continue into the weekend. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of these site restorations.
  • Time: April 8, 2022, 5:11 p.m.
    Status: Identified
    Update: Restoration work to restore sites is underway and will continue into the weekend. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of these site restorations.
  • Time: April 8, 2022, 3:30 p.m.
    Status: Identified
    Update: We have started successfully restoring sites and continue to work on restoration to a wider cohort of customers. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of these site restorations.
  • Time: April 8, 2022, 10:59 a.m.
    Status: Identified
    Update: We have started successfully restoring sites and continue to work on restoration to a wider cohort of customers. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of this first round of restorations remains the same from our last update.
  • Time: April 8, 2022, 7:53 a.m.
    Status: Identified
    Update: We have started successfully restoring sites and continue to work on restoration to a wider cohort of customers. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of this first round of restorations remains the same from our last update.
  • Time: April 8, 2022, 1:27 a.m.
    Status: Identified
    Update: We continue to work on partial restoration to a cohort of customers. The plan is to take a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of this first round of restorations remains the same from our last update
  • Time: April 7, 2022, 9:51 p.m.
    Status: Identified
    Update: We continue to work on partial restoration to the first cohort of customers. The plan to take a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of this first round of restorations remains the same from our last update.
  • Time: April 7, 2022, 6:43 p.m.
    Status: Identified
    Update: We are beginning partial restoration to a cohort of customers. The early stages of this process will be controlled and hands-on, as we work with customers live to get feedback and ensure that restoration is working correctly before we accelerate the process for the next cohort. We will continue to post updates here as we move the process along.
  • Time: April 7, 2022, 12:26 p.m.
    Status: Identified
    Update: We are continuing work in the verification stage on a subset of instances. Once reenabled, support will update accounts via opened incident tickets. Restoration of customer sites remains our first priority and we are coordinating with teams globally to ensure that work continues 24/7 until all instances are restored.
  • Time: April 7, 2022, 9:34 a.m.
    Status: Identified
    Update: We are continuing work in the verification stage on a subset of instances. Once reenabled, support will update accounts via opened incident tickets. Restoration of customer sites remains our first priority and we are coordinating with teams globally to ensure that work continues 24/7 until all instances are restored.
  • Time: April 7, 2022, 4:19 a.m.
    Status: Identified
    Update: We are continuing work in the verification stage on a subset of instances. Once reenabled, support will update accounts via opened incident tickets. Restoration of customer sites remains our first priority and we are coordinating with teams globally to ensure that work continues 24/7 until all instances are restored.
  • Time: April 6, 2022, 9:26 p.m.
    Status: Identified
    Update: We are continuing to work on the resolution of the incidents for some Statuspage, Jira Work Management, Jira Service Management, Confluence, Jira Software, Atlassian Access, Jira Product Discovery, and Opsgenie Cloud customers.
  • Time: April 5, 2022, 9:11 p.m.
    Status: Identified
    Update: We have partially reactivated the Statuspages of affected customers. The hosted pages should be up, and the API capabilities have been restored so affected customers can use this to manage their pages while work is done to restore access to the manage portal. We have defined two processes to resolution of the issues impacting some customers. These processes each involve multiple stages of work. We are currently working on one of the processes and we will provide more detail as we progress through resolution.
  • Time: April 5, 2022, 1:45 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.

Updates:

  • Time: April 1, 2022, 12:51 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: March 31, 2022, 11:18 p.m.
    Status: Monitoring
    Update: We have identified and resolved all issues with third-parties and we are now monitoring and continuing to process any delayed metrics.
  • Time: March 31, 2022, 7:18 p.m.
    Status: Identified
    Update: Based on additional reporting and investigation, we have found that System Metrics is experiencing delays between 5 to 30 minutes. We are continuing to work with our vendor to return the service to normal operations.
  • Time: March 31, 2022, 12:05 a.m.
    Status: Identified
    Update: We have identified the issue and we’re working with our vendor to return the service to normal operations.
  • Time: March 30, 2022, 10:07 p.m.
    Status: Investigating
    Update: System metrics is experiencing a delay of up to 5 to 10 minutes. We are currently investigating this issue.

Updates:

  • Time: April 1, 2022, 12:51 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: March 31, 2022, 11:18 p.m.
    Status: Monitoring
    Update: We have identified and resolved all issues with third-parties and we are now monitoring and continuing to process any delayed metrics.
  • Time: March 31, 2022, 7:18 p.m.
    Status: Identified
    Update: Based on additional reporting and investigation, we have found that System Metrics is experiencing delays between 5 to 30 minutes. We are continuing to work with our vendor to return the service to normal operations.
  • Time: March 31, 2022, 12:05 a.m.
    Status: Identified
    Update: We have identified the issue and we’re working with our vendor to return the service to normal operations.
  • Time: March 30, 2022, 10:07 p.m.
    Status: Investigating
    Update: System metrics is experiencing a delay of up to 5 to 10 minutes. We are currently investigating this issue.

Updates:

  • Time: March 22, 2022, 3:58 p.m.
    Status: Postmortem
    Update: ### **SUMMARY** On March 14, 2022, between 01:05pm and 01:47pm UTC, some Atlassian customers were unable to login to our products including Trello and Statuspage, and could not access some services including the ability to create support tickets. The underlying cause was a newly introduced configuration data store that did not scale up properly due to a misconfiguration of autoscaling. The incident was detected by Atlassian's automated monitoring system and mitigated by disabling the use of the new configuration datastore which put our systems into a known good state. The total time to resolution was approximately 42 minutes. ### **IMPACT** The overall impact was between March 14 2022, 01:05 PM UTC and March 14, 2022, 01:47 PM UTC across seven products and services. The bug impacted several of the key dependent services which resulted in an outage for end users, leading to failed logins across the following products and services: * [**getsupport.atlassian.com**](http://getsupport.atlassian.com) * [**confluence.atlassian.com**](http://confluence.atlassian.com) * [**jira.atlassian.com**](http://jira.atlassian.com) * [**partners-jira.atlassian.com**](http://partners-jira.atlassian.com) * [**community.atlassian.com**](http://community.atlassian.com) * [**manage.statuspage.io**](http://manage.statuspage.io) * [**trello.com**](http://trello.com) * [**university.atlassian.com**](http://university.atlassian.com) ### **ROOT CAUSE** The issue was caused by an underlying configuration data store based on AWS DynamoDB failing to scale up. During post-setup fine-tuning it was identified that initial values for the read capacity units \(RCUs\) and write capacity units \(RCUs\) were over-provisioned. As a result a decision was made to decrease them however the resulting values proved to be insufficient to handle the increased traffic in our system. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We're prioritizing the following improvement actions to avoid repeating this type of incident: * Fix the configuration so that the new configuration data store dynamically scales-up regardless of the size of the incoming traffic. * Conduct more thorough capacity planning and load testing. * Improve the resilience of the system by adding fallbacks to our secondary data store. 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
  • Time: March 14, 2022, 2:28 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: March 14, 2022, 2:28 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: March 14, 2022, 2:10 p.m.
    Status: Monitoring
    Update: We have identified and mitigated an issue with users logging in to Statuspage starting at 6:05am PST and ending at 6:46am PST and are monitoring the results.
  • Time: March 14, 2022, 2:10 p.m.
    Status: Monitoring
    Update: We have identified and mitigated an issue with users logging in to Statuspage starting at 6:05am PST and ending at 6:46am PST and are monitoring the results.

Check the status of similar companies and alternatives to Atlassian Statuspage

Discord
Discord

Systems Active

Aircall
Aircall

Systems Active

Sinch
Sinch

Systems Active

CallRail
CallRail

Systems Active

Phone.com
Phone.com

Systems Active

Mattermost
Mattermost

Systems Active

Dubber
Dubber

Systems Active

getstream.io
getstream.io

Systems Active

Netomi
Netomi

Systems Active

Convoso
Convoso

Systems Active

Plex
Plex

Systems Active

Helpshift
Helpshift

Systems Active

Frequently Asked Questions - Atlassian Statuspage

Is there a Atlassian Statuspage outage?
The current status of Atlassian Statuspage is: Systems Active
Where can I find the official status page of Atlassian Statuspage?
The official status page for Atlassian Statuspage is here
How can I get notified if Atlassian Statuspage is down or experiencing an outage?
To get notified of any status changes to Atlassian Statuspage, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Atlassian Statuspage every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Atlassian Statuspage do?
Statuspage is a reliable tool for communicating status and incidents to customers and employees, reducing support costs and building trust.

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free