Jira Align incident

Users experiencing issues accessing multiple Atlassian products

Critical Resolved View vendor source →

Jira Align experienced a critical incident on May 14, 2026 affecting Pod 1 and Pod 2 and 1 more component, lasting 1h 23m. The incident has been resolved; the full update timeline is below.

Started
May 14, 2026, 05:24 AM UTC
Resolved
May 14, 2026, 06:48 AM UTC
Duration
1h 23m
Detected by Pingoru
May 14, 2026, 05:24 AM UTC

Affected components

Pod 1Pod 2Pod 3Pod 4Pod 5Pod 6Pod 7Pod 8Pod 9Pod 10Pod 11Pod 12Pod 13Pod 14Pod 15Pod 16Pod 17Pod 18Pod 19Pod 20Pod 21Pod 22Pod 23Pod 24Pod 25Pod 26Pod 27Pod 28Pod 29Pod 30Pod 31Pod 32Pod 33Pod 34Pod 35Pod 36Pod 37Pod 38Pod 39Pod 40Pod 41Pod 42Pod 43Pod 44Pod 44Pod 45Pod 46Pod 47Pod 48Pod 49AWS ec2-us-east-2AWS ec2-eu-central-1AWS ec2-ap-southeast-2AWS rds-ap-southeast-2AWS rds-eu-central-1AWS rds-us-east-2AWS elb-ap-southeast-2AWS elb-eu-central-1AWS elb-us-east-2AWS glue-ap-southeast-2AWS glue-eu-central-1AWS glue-us-east-2AWS ses-ap-southeast-2AWS ses-eu-central-1AWS ses-us-east-1Cloudflare Network

Update timeline

  1. identified May 14, 2026, 05:24 AM UTC

    It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information. We will provide further update within one hour, or sooner as further information becomes available.

  2. identified May 14, 2026, 05:34 AM UTC

    Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products. At this time, Atlassian customers should also be able to once again raise support requests with our team. We will provide further update within an hour as we are able to progress mitigating this issue.

  3. monitoring May 14, 2026, 05:43 AM UTC

    Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

  4. monitoring May 14, 2026, 06:39 AM UTC

    We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

  5. monitoring May 14, 2026, 06:40 AM UTC

    We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

  6. resolved May 14, 2026, 06:48 AM UTC

    All products and services impacted by this incident should now be fully recovered, and this incident is resolved.