Atlassian Outage History

Atlassian is up right now

Atlassian had 694 outages in the last 2 years totaling 563h 10m of downtime — averaging 29 incidents per month.

There were 694 Atlassian outages since July 3, 2024 totaling 563h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

Minor June 26, 2026 via Atlassian Developer

Remote Forge Apps facing rate-limiting issues

Detected by Pingoru
Jun 26, 2026, 02:32 PM UTC
Resolved
Jun 26, 2026, 09:39 PM UTC
Duration
7h 6m
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 · 5 updates
  1. identified Jun 26, 2026, 02:32 PM UTC

    We have identified the source of service performance issues, affecting your forge remote-apps services. Our team has initiated a remediation and is actively monitoring recovery. We will provide the next update within the next one hour.

  2. identified Jun 26, 2026, 03:28 PM UTC

    Our team has applied the mitigation, and we are seeing recovery. We will continue to share additional updates here as more information becomes available.

  3. identified Jun 26, 2026, 07:43 PM UTC

    Our team continues to monitor the recovery in progress, and we will share additional updates here as more information becomes available.

  4. monitoring Jun 26, 2026, 09:24 PM UTC

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

  5. resolved Jun 26, 2026, 09:39 PM UTC

    On June 26, 2026, some customers may have experienced performance degradation with remote Forge apps facing rate-limiting issues. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Major June 19, 2026 via Jira Service Desk

Jira : Incoming emails partial outage

Detected by Pingoru
Jun 19, 2026, 10:46 PM UTC
Resolved
Jun 26, 2026, 05:13 AM UTC
Duration
6d 6h
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssistAssets
Timeline · 2 updates
  1. monitoring Jun 19, 2026, 10:46 PM UTC

    Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.

  2. resolved Jun 26, 2026, 05:13 AM UTC

    Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.

Read the full incident report →

Major June 19, 2026 via Jira Service Management

Jira : Incoming emails partial outage

Detected by Pingoru
Jun 19, 2026, 10:46 PM UTC
Resolved
Jun 26, 2026, 05:13 AM UTC
Duration
6d 6h
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssistAssets
Timeline · 2 updates
  1. monitoring Jun 19, 2026, 10:46 PM UTC

    Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.

  2. resolved Jun 26, 2026, 05:13 AM UTC

    Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.

Read the full incident report →

Major June 19, 2026 via Jira Software

Jira : Incoming emails partial outage

Detected by Pingoru
Jun 19, 2026, 10:46 PM UTC
Resolved
Jun 26, 2026, 05:13 AM UTC
Duration
6d 6h
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 2 updates
  1. monitoring Jun 19, 2026, 10:46 PM UTC

    Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.

  2. resolved Jun 26, 2026, 05:13 AM UTC

    Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.

Read the full incident report →

Minor June 16, 2026 via Confluence

Confluence Cloud experiencing degraded viewing experience

Detected by Pingoru
Jun 16, 2026, 01:46 PM UTC
Resolved
Jun 16, 2026, 03:56 PM UTC
Duration
2h 9m
Affected: View ContentiOS AppCreate and EditAndroid AppCommentsAuthentication and User ManagementSearchAdministrationNotificationsMarketplace AppsPurchasing & LicensingSignupConfluence AutomationsCloud to Cloud Migrations - Copy Product DataServer to Cloud Migrations - Copy Product Data
Timeline · 5 updates

Read the full incident report →

Minor June 12, 2026 via Jira Product Discovery

Data viewing issues on Jira Product Discovery

Detected by Pingoru
Jun 12, 2026, 01:50 PM UTC
Resolved
Jun 12, 2026, 02:29 PM UTC
Duration
38m
Affected: Open projectsCreate and delete fieldsAdd/view data points ("Capture")
Timeline · 2 updates
  1. monitoring Jun 12, 2026, 01:50 PM UTC

    We are investigating reports of incomplete or missing field data in Jira Product Discovery views, including list, timeline, and single idea views. A limited number of customers are affected. Your data is safe, this is a display issue only. We have identified the root cause and a fix is being deployed. We will provide an update once recovery is confirmed.

  2. resolved Jun 12, 2026, 02:29 PM UTC

    On June 12th 2026, between 07:30 UTC to 13:48 UTC, some users experienced viewing disruptions with our product discovery service. The issue has now been resolved and the service is operating normally for all the customers.

Read the full incident report →

Minor June 11, 2026 via Bitbucket

Degraded performance of Bitbucket

Detected by Pingoru
Jun 11, 2026, 10:48 PM UTC
Resolved
Jun 12, 2026, 12:14 AM UTC
Duration
1h 26m
Affected: WebsiteAPIGit via SSHAuthentication and user managementGit via HTTPSWebhooksSource downloadsPipelinesGit LFSEmail deliveryPurchasing & LicensingSignupPackages
Timeline · 4 updates
  1. investigating Jun 11, 2026, 10:48 PM UTC

    We are actively investigating reports of performance degradation affecting Bitbucket OAuth login. We will share updates here as more information is available.

  2. identified Jun 11, 2026, 11:21 PM UTC

    We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience OAuth login issues in Bitbucket. We will continue to share additional updates here as more information is available.

  3. monitoring Jun 11, 2026, 11:58 PM UTC

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

  4. resolved Jun 12, 2026, 12:14 AM UTC

    On June 11, 2026, Bitbucket users may have experienced performance degradation affecting Bitbucket OAuth login. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Minor June 10, 2026 via Jira Service Desk

Unable to load Assets page

Detected by Pingoru
Jun 10, 2026, 09:42 AM UTC
Resolved
Jun 10, 2026, 10:00 AM UTC
Duration
17m
Affected: Jira Service Management Web
Timeline · 2 updates
  1. investigating Jun 10, 2026, 09:42 AM UTC

    Users are facing degraded performance while accessing Assets page which is impacting Assets object creation, updation and deletion activities. Our teams are investigating actively and will be sharing more details in next 1 hour.

  2. resolved Jun 10, 2026, 10:00 AM UTC

    On June 10 2026, between 08:10 and 09:08 UTC, users experienced degraded performance and inability to load the Assets page, which is impacting the ability to create, update, and delete assets. We have implemented a fix and services have been restored to normal operation for all affected customers.

Read the full incident report →

Minor June 10, 2026 via Jira Service Management

Unable to load Assets page

Detected by Pingoru
Jun 10, 2026, 09:42 AM UTC
Resolved
Jun 10, 2026, 10:00 AM UTC
Duration
17m
Affected: Jira Service Management Web
Timeline · 2 updates
  1. investigating Jun 10, 2026, 09:42 AM UTC

    Users are facing degraded performance while accessing Assets page which is impacting Assets object creation, updation and deletion activities. Our teams are investigating actively and will be sharing more details in next 1 hour.

  2. resolved Jun 10, 2026, 10:00 AM UTC

    On June 10 2026, between 08:10 and 09:08 UTC, users experienced degraded performance and inability to load the Assets page, which is impacting the ability to create, update, and delete assets. We have implemented a fix and services have been restored to normal operation for all affected customers.

Read the full incident report →

Minor June 10, 2026 via Jira Product Discovery

Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps

Detected by Pingoru
Jun 10, 2026, 06:14 AM UTC
Resolved
Jun 10, 2026, 06:31 AM UTC
Duration
17m
Affected: Open projectsCreate and delete fieldsAdd/view data points ("Capture")
Timeline · 4 updates
  1. investigating Jun 10, 2026, 06:14 AM UTC

    We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

  2. identified Jun 10, 2026, 06:14 AM UTC

    Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

  3. monitoring Jun 10, 2026, 06:14 AM UTC

    Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

  4. resolved Jun 10, 2026, 06:31 AM UTC

    We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Minor June 10, 2026 via Atlassian Customer Service Management

Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps

Detected by Pingoru
Jun 10, 2026, 06:14 AM UTC
Resolved
Jun 10, 2026, 06:31 AM UTC
Duration
17m
Affected: Customer experienceCustomer Service Management AI agentSupport websiteEmail requestCustomer Service Management spacesCustomer profilesAutomation for Jira
Timeline · 4 updates
  1. investigating Jun 10, 2026, 06:14 AM UTC

    We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

  2. identified Jun 10, 2026, 06:14 AM UTC

    Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

  3. monitoring Jun 10, 2026, 06:14 AM UTC

    Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

  4. resolved Jun 10, 2026, 06:31 AM UTC

    We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Minor June 10, 2026 via Confluence

Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps

Detected by Pingoru
Jun 10, 2026, 06:14 AM UTC
Resolved
Jun 10, 2026, 06:31 AM UTC
Duration
17m
Affected: View ContentiOS AppCreate and EditAndroid AppCommentsAuthentication and User ManagementSearchAdministrationNotificationsMarketplace AppsPurchasing & LicensingSignupConfluence AutomationsCloud to Cloud Migrations - Copy Product DataServer to Cloud Migrations - Copy Product Data
Timeline · 4 updates
  1. investigating Jun 10, 2026, 06:14 AM UTC

    We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

  2. identified Jun 10, 2026, 06:14 AM UTC

    Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

  3. monitoring Jun 10, 2026, 06:14 AM UTC

    Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

  4. resolved Jun 10, 2026, 06:31 AM UTC

    We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Minor June 10, 2026 via Jira Service Desk

Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps

Detected by Pingoru
Jun 10, 2026, 04:55 AM UTC
Resolved
Jun 10, 2026, 06:31 AM UTC
Duration
1h 35m
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 · 4 updates
  1. investigating Jun 10, 2026, 04:55 AM UTC

    We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

  2. identified Jun 10, 2026, 05:39 AM UTC

    Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

  3. monitoring Jun 10, 2026, 06:14 AM UTC

    Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

  4. resolved Jun 10, 2026, 06:31 AM UTC

    We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Minor June 10, 2026 via Jira Service Management

Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps

Detected by Pingoru
Jun 10, 2026, 04:55 AM UTC
Resolved
Jun 10, 2026, 06:31 AM UTC
Duration
1h 35m
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 · 4 updates
  1. investigating Jun 10, 2026, 04:55 AM UTC

    We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

  2. identified Jun 10, 2026, 05:39 AM UTC

    Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

  3. monitoring Jun 10, 2026, 06:14 AM UTC

    Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

  4. resolved Jun 10, 2026, 06:31 AM UTC

    We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Minor June 10, 2026 via Atlassian Developer

Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps

Detected by Pingoru
Jun 10, 2026, 04:55 AM UTC
Resolved
Jun 10, 2026, 06:31 AM UTC
Duration
1h 35m
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 · 4 updates
  1. investigating Jun 10, 2026, 04:55 AM UTC

    We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

  2. identified Jun 10, 2026, 05:39 AM UTC

    Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

  3. monitoring Jun 10, 2026, 06:14 AM UTC

    Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

  4. resolved Jun 10, 2026, 06:31 AM UTC

    We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Minor June 10, 2026 via Jira Software

Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps

Detected by Pingoru
Jun 10, 2026, 04:55 AM UTC
Resolved
Jun 10, 2026, 06:31 AM UTC
Duration
1h 35m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
  1. investigating Jun 10, 2026, 04:55 AM UTC

    We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

  2. identified Jun 10, 2026, 05:39 AM UTC

    Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

  3. monitoring Jun 10, 2026, 06:14 AM UTC

    Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

  4. resolved Jun 10, 2026, 06:31 AM UTC

    We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Minor June 8, 2026 via Jira Software

Users experiencing issues loading work items in Jira and JSM

Detected by Pingoru
Jun 08, 2026, 01:53 AM UTC
Resolved
Jun 08, 2026, 02:56 AM UTC
Duration
1h 2m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministration
Timeline · 3 updates
  1. investigating Jun 08, 2026, 01:53 AM UTC

    We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.

  2. identified Jun 08, 2026, 02:36 AM UTC

    We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

  3. resolved Jun 08, 2026, 02:56 AM UTC

    On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.

Read the full incident report →

Minor June 8, 2026 via Jira Service Desk

Users experiencing issues loading work items in Jira and JSM

Detected by Pingoru
Jun 08, 2026, 01:53 AM UTC
Resolved
Jun 08, 2026, 02:56 AM UTC
Duration
1h 2m
Affected: Jira Service Management WebAuthentication and User Management
Timeline · 3 updates
  1. investigating Jun 08, 2026, 01:53 AM UTC

    We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.

  2. identified Jun 08, 2026, 02:36 AM UTC

    We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

  3. resolved Jun 08, 2026, 02:56 AM UTC

    On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.

Read the full incident report →

Minor June 8, 2026 via Jira Service Management

Users experiencing issues loading work items in Jira and JSM

Detected by Pingoru
Jun 08, 2026, 01:53 AM UTC
Resolved
Jun 08, 2026, 02:56 AM UTC
Duration
1h 2m
Affected: Jira Service Management WebAuthentication and User Management
Timeline · 3 updates
  1. investigating Jun 08, 2026, 01:53 AM UTC

    We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.

  2. identified Jun 08, 2026, 02:36 AM UTC

    We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

  3. resolved Jun 08, 2026, 02:56 AM UTC

    On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.

Read the full incident report →

Major June 6, 2026 via Jira Software

Users experiencing issues loading work items in Atlassian products

Detected by Pingoru
Jun 06, 2026, 11:21 PM UTC
Resolved
Jun 07, 2026, 12:13 AM UTC
Duration
51m
Affected: Viewing contentCreate and edit
Timeline · 3 updates
  1. investigating Jun 06, 2026, 11:21 PM UTC

    We are aware of users currently experiencing loading work items across Atlassian products in some regions. We are investigating with urgency and will provide update within one hour.

  2. monitoring Jun 07, 2026, 12:07 AM UTC

    A fix has been implemented for the issues some customers have been experiencing with creating and viewing work items in Jira. We are now monitoring for this recovery and will update shortly with further confirmation.

  3. resolved Jun 07, 2026, 12:13 AM UTC

    The issues relating to viewing and creating work items in Jira should now be fully resolved.

Read the full incident report →