Issues With Login

What to do

• Check whether you use Atlassian Statuspage Admin User+Pass. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 18m it lasted.

  Anything that failed between 2022-03-14 14:10 UTC and 2022-03-14 14:28 UTC may need a replay.

• Subscribe to Atlassian Statuspage's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=statuspage works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Atlassian Statuspage 3

1. monitoringMar 14, 2022, 2:10 PM UTC

   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.

   provider

2. resolvedMar 14, 2022, 2:28 PM UTC

   This incident has been resolved.

   provider

3. postmortemMar 22, 2022, 3:58 PM UTC

   ### **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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.