Time: April 3, 2024, 8:25 a.m.

Status: Resolved

Update: We have identified the list of tenants affected by this change and will be reaching out to the customers to share details about the issue and the required changes. In the meantime, if you have any queries, kindly reach out to support through https://support.atlassian.com/.

Time: April 3, 2024, 7:25 a.m.

Status: Identified

Update: We have detected an issue with the incoming email not working due to a cipher mismatch that is impacting our Jira Service Management customers. We've implemented changes to our cipher support across Jira Software, Jira Work Management, and Jira Service Management. Unsupported ciphers, not explicitly listed on our "Supported Security Protocols for Atlassian Cloud Products" page (https://support.atlassian.com/security-and-access-policies/docs/supported-security-protocols-for-atlassian-cloud-products/), have been removed. This means that inbound email processing on these platforms using unsupported ciphers will no longer be supported. We strongly encourage our customers to switch to a supported cipher from the list provided on our "Supported Security Protocols for Atlassian Cloud Products" page.

Time: March 29, 2024, 8:40 a.m.

Status: Resolved

Update: Between 00:00 UTC to 06:30 UTC, we experienced issues with the admin screens used to schedule data residency migrations for Confluence, Jira Work Management, Jira Service Management, and Jira Software. The issue has been resolved and the service is operating normally.

Time: March 29, 2024, 7:35 a.m.

Status: Investigating

Update: We are investigating reports of errors when attempting to schedule a data residency migrations for Confluence, Jira Work Management, Jira Service Management, and Jira Software Cloud customers. We will provide more details once we identify the root cause.

Time: March 29, 2024, 8:40 a.m.

Status: Resolved

Update: Between 00:00 UTC to 06:30 UTC, we experienced issues with the admin screens used to schedule data residency migrations for Confluence, Jira Work Management, Jira Service Management, and Jira Software. The issue has been resolved and the service is operating normally.

Time: March 29, 2024, 7:35 a.m.

Status: Investigating

Update: We are investigating reports of errors when attempting to schedule a data residency migrations for Confluence, Jira Work Management, Jira Service Management, and Jira Software Cloud customers. We will provide more details once we identify the root cause.

Time: March 26, 2024, 3:17 a.m.

Status: Resolved

Update: We have identified and resolved a problem with Forge hosted storage, where some paginated queries kept repeating the last page. The incident was detected by our internal monitoring and was resolved quickly after detection by reverting the deployment. Activating changes recently made to the query cursors for paginated queries introduced a bug that impacted some apps. A small number of requests were impacted over a 16-minute window, while the incident lasted. Timeline: - 25/Mar/24 10:08 p.m. UTC - Impact started, when the changes were deployed to production - 25/Mar/24 10:09 p.m. UTC - Incident was detected - 25/Mar/24 10:24 p.m. UTC - Incident was resolved and impact ended The impact of this incident has been completely mitigated and our monitoring tools confirm that query operations are back to the pre-incident behaviour. We have also resolved the underlying bug and deployed the fix to production, completely eliminating the cause of this incident. We apologise for any inconvenience this may have caused to our customers and our developer community.

Time: March 26, 2024, 3:17 a.m.

Status: Resolved

Update: We have identified and resolved a problem with Forge hosted storage, where some paginated queries kept repeating the last page. The incident was detected by our internal monitoring and was resolved quickly after detection by reverting the deployment. Activating changes recently made to the query cursors for paginated queries introduced a bug that impacted some apps. A small number of requests were impacted over a 16-minute window, while the incident lasted. Timeline: - 25/Mar/24 10:08 p.m. UTC - Impact started, when the changes were deployed to production - 25/Mar/24 10:09 p.m. UTC - Incident was detected - 25/Mar/24 10:24 p.m. UTC - Incident was resolved and impact ended The impact of this incident has been completely mitigated and our monitoring tools confirm that query operations are back to the pre-incident behaviour. We have also resolved the underlying bug and deployed the fix to production, completely eliminating the cause of this incident. We apologise for any inconvenience this may have caused to our customers and our developer community.

Time: March 20, 2024, 10:41 p.m.

Status: Resolved

Update: Between 18:16 UTC and 22:XX UTC, March 20, 2024, we experienced creating issues and transitions for Jira Service Management, Jira Work Management, and Jira Software. The issue has been resolved and the service is operating normally.

Time: March 20, 2024, 10:05 p.m.

Status: Identified

Update: We are have identified an issue with creating issues and transitions that is impacting some Cloud customers. A fix is being rolled out now. Another update will be published in the next hour.