Jira Align Outage History

Jira Align is up right now

Jira Align had 18 outages in the last 2 years totaling 226h 45m of downtime — averaging 0.7 incidents per month.

There were 18 Jira Align outages since July 3, 2024 totaling 226h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://jira-align.status.atlassian.com

Critical May 14, 2026

Users experiencing issues accessing multiple Atlassian products

Detected by Pingoru
May 14, 2026, 05:24 AM UTC
Resolved
May 14, 2026, 06:48 AM UTC
Duration
1h 23m
Affected: 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
Timeline · 7 updates

Read the full incident report →

Minor January 14, 2026

Intermittent Jira Align Web Issues

Detected by Pingoru
Jan 14, 2026, 02:26 PM UTC
Resolved
Jan 14, 2026, 11:09 PM UTC
Duration
8h 42m
Affected: 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
Timeline · 9 updates

Read the full incident report →

Minor December 15, 2025

Degraded performance of Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo

Detected by Pingoru
Dec 15, 2025, 04:16 PM UTC
Resolved
Dec 15, 2025, 07:01 PM UTC
Duration
2h 45m
Affected: 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
Timeline · 5 updates
  1. identified Dec 15, 2025, 04:16 PM UTC

    We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo. We'll share updates here as more information is available.

  2. identified Dec 15, 2025, 04:26 PM UTC

    We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, and Rovo. We'll share updates here as more information is available.

  3. identified Dec 15, 2025, 04:48 PM UTC

    We have identified the cause of the issue, and our teams are diligently working on mitigations. We're currently seeing signs of improvements. We'll continue to share additional updates here in 60 minutes or as more information becomes available.

  4. identified Dec 15, 2025, 05:47 PM UTC

    Our teams are continuing to implement mitigations. Error rates have decreased across all products and we are seeing improvements. We will continue to provide updates here in 60 minutes or as more information becomes available.

  5. resolved Dec 15, 2025, 07:01 PM UTC

    On December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced performance degradations and errors on the web page and mobile apps. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Notice October 20, 2025

Atlassian Cloud Services impacted

Detected by Pingoru
Oct 20, 2025, 07:56 AM UTC
Resolved
Oct 21, 2025, 05:24 AM UTC
Duration
21h 28m
Affected: 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
Timeline · 25 updates

Read the full incident report →

Minor September 22, 2025

Degraded performance to multiple Atlassian experiences

Detected by Pingoru
Sep 22, 2025, 05:38 AM UTC
Resolved
Sep 22, 2025, 07:17 AM UTC
Duration
1h 38m
Affected: 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
Timeline · 5 updates

Read the full incident report →

Notice September 9, 2025

Degraded performance in Confluence and Jira for Microsoft Edge users

Detected by Pingoru
Sep 09, 2025, 10:23 AM UTC
Resolved
Sep 15, 2025, 06:40 AM UTC
Duration
5d 20h
Affected: 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
Timeline · 6 updates

Read the full incident report →

Notice June 17, 2025

Some Jira Align sites experiencing 500 server error

Detected by Pingoru
Jun 17, 2025, 06:44 AM UTC
Resolved
Jun 17, 2025, 07:34 AM UTC
Duration
49m
Affected: Pod 10AWS rds-us-east-2
Timeline · 3 updates
  1. investigating Jun 17, 2025, 06:44 AM UTC

    We are aware of an issue where some Jira Align customers are receiving a 500 server error when attempting to access Jira Align. Our team is aware of this issue and is investigating with urgency. We will provide an update as soon as possible.

  2. monitoring Jun 17, 2025, 07:01 AM UTC

    Jira Align sites that were impacted by this issue should now be back online. Our team is continuing to monitor the situation and will provide further updates when available.

  3. resolved Jun 17, 2025, 07:34 AM UTC

    The incident is resolved and all Jira Align sites are now fully operational.

Read the full incident report →

Notice June 4, 2025

Customers may experience delays receiving emails

Detected by Pingoru
Jun 04, 2025, 05:17 PM UTC
Resolved
Jun 04, 2025, 08:59 PM UTC
Duration
3h 41m
Affected: 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
Timeline · 2 updates
  1. investigating Jun 04, 2025, 05:17 PM UTC

    We were experiencing cases of degraded performance for outgoing emails from Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas and Compass Cloud customers. The system is recovering and mail is being processed normally as of 16:45 UTC. We will continue to monitor system performance and will provide more details within the next hour.

  2. resolved Jun 04, 2025, 05:59 PM UTC

    Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the service is operating normally.

Read the full incident report →

Critical May 22, 2025

RDS outage affecting the production database

Detected by Pingoru
May 22, 2025, 12:25 AM UTC
Resolved
May 22, 2025, 01:37 AM UTC
Duration
1h 11m
Affected: Pod 47
Timeline · 3 updates
  1. identified May 22, 2025, 12:25 AM UTC

    RDS is currently experiencing an issue that has caused an outage in the production environment. AWS is investigating. In the meantime w will perform a database restore.

  2. monitoring May 22, 2025, 01:12 AM UTC

    The database has been restored. We are monitoring the site to ensure there are no further connectivity issues. We have confirmed no data was lost during this outage.

  3. resolved May 22, 2025, 01:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 17, 2025

Intermittent Outage with Jira Align

Detected by Pingoru
Apr 17, 2025, 10:58 PM UTC
Resolved
Apr 18, 2025, 05:14 AM UTC
Duration
6h 15m
Timeline · 2 updates
  1. monitoring Apr 17, 2025, 10:58 PM UTC

    Jira Align was experiencing intermittent issues across multiple sites between 19:30 UTC and 22:12 UTC. The issue is resolved and the service is operating normally. If you continue to experience issues, please clear your browser cache and restart all open browser windows.

  2. resolved Apr 18, 2025, 05:14 AM UTC

    The issue has been resolved, service has been returned to operational status.

Read the full incident report →

Major April 17, 2025

Intermittent Outage

Detected by Pingoru
Apr 17, 2025, 09:17 PM UTC
Resolved
Apr 17, 2025, 10:24 PM UTC
Duration
1h 7m
Timeline · 5 updates
  1. investigating Apr 17, 2025, 09:17 PM UTC

    Jira Align is experiencing intermittent outages across multiple sites. The team is currently investigating.

  2. investigating Apr 17, 2025, 09:33 PM UTC

    For customers experiencing issues, incognito mode in your browser can be used as a work around.

  3. investigating Apr 17, 2025, 10:06 PM UTC

    We have been able to reproduce the issue and are investigating the root cause.

  4. investigating Apr 17, 2025, 10:24 PM UTC

    The issue has been mitigated, service has been returned to operational status. If you continue to experience issues, clear cache and restart all open browser windows.

  5. resolved Apr 17, 2025, 10:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 25, 2024

Jira Align Reports are not rendering correctly in some browsers

Detected by Pingoru
Nov 25, 2024, 09:34 PM UTC
Resolved
Nov 26, 2024, 09:31 PM UTC
Duration
23h 57m
Affected: 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-1
Timeline · 4 updates
  1. investigating Nov 25, 2024, 09:34 PM UTC

    The following reports open with a blank page due to recent Internet browser updates: ART Allocation Action Items Report Cumulative Effort Dependency Maps Feature Audit Report Feature Forecast - Average Velocity Investment by Feature Points Accepted (by Sprint) Process Flow Cycle Time Program Increment Cleanup Report Program Increment Scope Change Program Increments BurnUp Program Predictability Report Progress By Objective Resource Allocation Retrospective Risk and Impediment Status Sprint Metrics (M1) Sprint Synchronization Standup Attendance Story Audit Report Story Link Report Team Details Team Velocity Theme Rank Velocity by Team (Program Increment) WIP by State

  2. identified Nov 26, 2024, 01:38 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Nov 26, 2024, 08:38 PM UTC

    A fix has been implemented to some sites. Based upon feedback throughout today, we will finalize the deployment to the remaining sites.

  4. resolved Nov 26, 2024, 09:31 PM UTC

    This incident is resolved. Remaining sites have all been successfully updated with the fix.

Read the full incident report →

Minor November 19, 2024

RDS experiencing degraded performance

Detected by Pingoru
Nov 19, 2024, 06:09 PM UTC
Resolved
Nov 19, 2024, 06:52 PM UTC
Duration
43m
Affected: Pod 12
Timeline · 3 updates
  1. identified Nov 19, 2024, 06:09 PM UTC

    Possible performance degradation since 11/18/24 11:00:00 PM PST. Connector syncs are temporarily paused.

  2. monitoring Nov 19, 2024, 06:24 PM UTC

    Connector syncs are re-enabled and we are monitoring a return to standard performance.

  3. resolved Nov 19, 2024, 06:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 22, 2024

Intermittent 'Too many requests or error' for some Jira customers

Detected by Pingoru
Oct 22, 2024, 12:58 PM UTC
Resolved
Oct 22, 2024, 03:04 PM UTC
Duration
2h 5m
Timeline · 3 updates
  1. investigating Oct 22, 2024, 12:58 PM UTC

    We are investigating reports of intermittent 'Too many requests or errors' messages showing up for some Jira Cloud customers. Once we identify the root cause, we will provide more details.

  2. identified Oct 22, 2024, 01:57 PM UTC

    We continue to work on resolving the intermittent errors for Jira Cloud products. We have identified the root cause and expect full recovery shortly.

  3. resolved Oct 22, 2024, 03:04 PM UTC

    Between 22-Oct 09:00 AM UTC to 22-Oct 14:18 PM UTC, we experienced intermittent errors for Jira Cloud products. The issue has been resolved and the service is operating normally.

Read the full incident report →

Notice October 18, 2024

Partial unavailability in AMER region

Detected by Pingoru
Oct 18, 2024, 06:27 PM UTC
Resolved
Oct 18, 2024, 06:27 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 18, 2024, 06:27 PM UTC

    We experienced availability issues limited to a specific instance in AMER, resulting in Jira being temporarily unavailable. The issue began at 18:58 CET and was restored at 19:59 CET. All services are now fully operational

Read the full incident report →

Notice July 19, 2024

Enterprise Insights instances in US Central are impacted due to an Azure active incident

Detected by Pingoru
Jul 19, 2024, 02:52 AM UTC
Resolved
Jul 19, 2024, 04:16 AM UTC
Duration
1h 23m
Timeline · 5 updates
  1. investigating Jul 19, 2024, 01:03 AM UTC

    Enterprise Insights instances in US Central are impacted due to an Azure active incident. Teams are following the incident closely and taking the appropriate actions.

  2. identified Jul 19, 2024, 02:52 AM UTC

    Azure team has identified the problem and has been working to restore service.

  3. monitoring Jul 19, 2024, 04:06 AM UTC

    A fix has been implemented by Azure, all internal dashboards are showing promising results and we are monitoring progress.

  4. monitoring Jul 19, 2024, 04:08 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jul 19, 2024, 04:16 AM UTC

    All customer databases in US Central are fully operational. Standard monitoring activities will resume.

Read the full incident report →

Notice July 3, 2024

Some products are hard down

Detected by Pingoru
Jul 03, 2024, 08:51 PM UTC
Resolved
Jul 04, 2024, 12:34 AM UTC
Duration
3h 43m
Timeline · 3 updates
  1. investigating Jul 03, 2024, 08:51 PM UTC

    We are investigating an issue with that is impacting Atlassian, Atlassian Partners, Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira, Opsgenie, Atlassian Developer, Atlassian (deprecated), Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Atlassian Analytics, and Rovo Cloud customers. We will provide more details within the next hour.

  2. monitoring Jul 03, 2024, 09:45 PM UTC

    We have mitigated the problem and continue looking into the root cause. The outage was between 8:08pm 03/07 UTC - 08:31pm 03/07 UTC We are now monitoring closely.

  3. resolved Jul 04, 2024, 12:34 AM UTC

    Between 03-07-2024 20:08 UTC to 03-07-2024 20:31 UTC, we experienced downtime for Jira Align. The issue has been resolved and the service is operating normally.

Read the full incident report →