Atlassian Outage History

Atlassian degraded · 1 active incident View live status →

Atlassian had 481 outages in the last 2 years totaling 41h 13m of downtime — averaging 20 incidents per month.

There were 481 Atlassian outages since May 22, 2025 totaling 41h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.atlassian.com · Aggregated across Atlassian products

Minor May 20, 2026 via Atlassian Developer

Forge custom fields are not getting created

Detected by Pingoru
May 20, 2026, 12:06 PM UTC
Resolved
May 20, 2026, 02:14 PM UTC
Duration
2h 8m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 2 updates
  1. identified May 20, 2026, 12:06 PM UTC

    Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 3 hours, or sooner if we have any meaningful developments to report. The impact is limited to new deployments with Forge custom fields on Jira work items, however existing deployments with custom fields are running without any issues.

  2. resolved May 20, 2026, 02:14 PM UTC

    The root cause has been identified and a fix has been applied. Full service restoration has been completed.

Read the full incident report →

Notice May 20, 2026 via Atlassian Developer

Incorrect Banner appeared on MarketPlace Apps

Detected by Pingoru
May 20, 2026, 10:16 AM UTC
Resolved
May 20, 2026, 10:16 AM UTC
Duration
—
Affected: Forge App Alerts
Timeline · 1 update
  1. resolved May 20, 2026, 10:16 AM UTC

    Due to an incorrect deployment, a banner stating 'This app may stop working soon' was briefly displayed on the Marketplace Apps. This banner was not intended to appear on these apps. The feature has since been corrected and the banner is no longer appearing. No action is required, the banner was displayed in error and there is no impact to app functionality or availability. We apologise for any confusion this may have caused.

Read the full incident report →

Minor May 20, 2026 via Jira Software

Forge custom fields are not getting created

Detected by Pingoru
May 20, 2026, 09:17 AM UTC
Resolved
May 20, 2026, 02:14 PM UTC
Duration
4h 57m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
  1. investigating May 20, 2026, 09:17 AM UTC

    Users are reporting an issue with Forge custom fields not getting created on Jira work items page, after deploying an application. Our teams are investigating the issue and more updates will be shared within next 2 hour or sooner.

  2. investigating May 20, 2026, 11:20 AM UTC

    Our teams are actively working on the identifying the root cause and we will provide an update within 3 hours, or sooner if there is any significant progress. Thank you for your patience.

  3. identified May 20, 2026, 12:06 PM UTC

    Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 3 hours, or sooner if we have any meaningful developments to report. The impact is limited to new deployments with Forge custom fields on Jira work items, however existing deployments with custom fields are running without any issues.

  4. resolved May 20, 2026, 02:14 PM UTC

    The root cause has been identified and a fix has been applied. Full service restoration has been completed.

Read the full incident report →

Minor May 15, 2026 via Trello

Trello - degraded performance (resolved)

Detected by Pingoru
May 15, 2026, 03:14 PM UTC
Resolved
May 15, 2026, 06:04 PM UTC
Duration
2h 50m
Affected: Trello.comAPIAtlassian Support - Support PortalAtlassian Support TicketingAtlassian Support Knowledge Base
Timeline · 5 updates
  1. investigating May 15, 2026, 03:14 PM UTC

    We are investigating degraded performance of some Trello features. We will provide more details within the next hour.

  2. investigating May 15, 2026, 03:31 PM UTC

    Trello engineers are actively working on resolving issues that our users may be seeing around commenting on cards, deleting comments, and adding new attachments. Users may also find that recent changes to cards are not reflected in search results. We are continuing to work on it and will provide more updates within the hour.

  3. identified May 15, 2026, 04:40 PM UTC

    The Trello team has identified and mitigated most of the issues with cards and comments. Users may still see delays in search indexing for short time while it catches up to realtime.

  4. monitoring May 15, 2026, 05:36 PM UTC

    The team has resolved the previous issues and is now monitoring the system to ensure a full return to baseline. Search indexing is still approximately 1h delayed, but will be up to date shortly. Thank you for your patience

  5. resolved May 15, 2026, 06:04 PM UTC

    Search is now fully up to date for all users, and all issues with previous degraded functionality have been resolved.

Read the full incident report →

Critical May 14, 2026 via Atlassian Developer

Disrupted Service Desk availability

Detected by Pingoru
May 14, 2026, 09:04 PM UTC
Resolved
May 14, 2026, 09:35 PM UTC
Duration
31m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 3 updates
  1. identified May 14, 2026, 09:04 PM UTC

    We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inaccessibility for Developer and Marketplace service desks. We will continue to share additional updates here as more information is available.

  2. monitoring May 14, 2026, 09:20 PM UTC

    The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

  3. resolved May 14, 2026, 09:35 PM UTC

    On May 14, 2026, Developer and Marketplace service desks were inaccessible for affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Critical May 14, 2026 via Jira Align

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 →

Critical May 14, 2026 via Atlassian Compass

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: GraphQLBitbucketWebhooksComponent TemplatesScorecardsGitHub API RequestsOn-call flowsRESTComponentsAuthentication and User ManagementGitlabEmailMetricsGitHub WebhooksAlert flowsSearchCircleCICheckOpsCircleCI CircleCI WebhooksJSMActivity TimelineJSWPurchasing & LicensingNewRelicOpsgenieSignupPagerDutySlackSwaggerUIStatuspageGithub
Timeline · 7 updates

Read the full incident report →

Critical May 14, 2026 via Atlassian Developer

Users experiencing issues accessing multiple Atlassian products

Detected by Pingoru
May 14, 2026, 05:11 AM UTC
Resolved
May 14, 2026, 06:49 AM UTC
Duration
1h 38m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 7 updates
  1. identified May 14, 2026, 05:11 AM UTC

    Further confirmations of impacted products have now been added to the incident. Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

  2. 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.

  3. 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.

  4. 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.

  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. monitoring May 14, 2026, 06:41 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.

  7. resolved May 14, 2026, 06:49 AM UTC

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

Read the full incident report →

Critical May 14, 2026 via Atlassian Migrations

Users experiencing issues accessing multiple Atlassian products

Detected by Pingoru
May 14, 2026, 05:11 AM UTC
Resolved
May 14, 2026, 06:48 AM UTC
Duration
1h 37m
Affected: Jira: Cloud to Cloud Migrations - Copy Product DataJira: Server / Data Center to Cloud MigrationsJira: Backup, Restore, Import & ExportJira: SandboxConfluence: Cloud to Cloud Migrations - Copy Product DataConfluence: Server / Data Center to Cloud MigrationsConfluence: Backup, Restore, Import & ExportConfluence: SandboxApps: Server / Data Center to Cloud MigrationsBitbucket: Server / Data Center to Cloud MigrationsMigration API
Timeline · 8 updates

Read the full incident report →

Critical May 14, 2026 via Jira Service Desk

Users experiencing issues accessing multiple Atlassian products

Detected by Pingoru
May 14, 2026, 05:03 AM UTC
Resolved
May 14, 2026, 06:48 AM UTC
Duration
1h 44m
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssist
Timeline · 9 updates

Read the full incident report →

Critical May 14, 2026 via Jira Service Management

Users experiencing issues accessing multiple Atlassian products

Detected by Pingoru
May 14, 2026, 05:03 AM UTC
Resolved
May 14, 2026, 06:48 AM UTC
Duration
1h 44m
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssist
Timeline · 9 updates

Read the full incident report →