Atlassian Analytics incident

Potential data lag for Atlassian Analytics customers

Minor Resolved View vendor source →

Atlassian Analytics experienced a minor incident on May 12, 2025 affecting Atlassian Data Lake, lasting 2d 13h. The incident has been resolved; the full update timeline is below.

Started
May 12, 2025, 10:43 AM UTC
Resolved
May 15, 2025, 12:32 AM UTC
Duration
2d 13h
Detected by Pingoru
May 12, 2025, 10:43 AM UTC

Affected components

Atlassian Data Lake

Update timeline

  1. investigating May 12, 2025, 10:43 AM UTC

    We have identified an issue in our Data Lake that could potentially result in the last 6 days of data not being available in Atlassian Analytics dashboard for Identity, Atlas, Confluence entities in all regions. The root cause is identified and are working on mitigating the impacted entities. Next update will be shared in 6 hours.

  2. identified May 12, 2025, 02:08 PM UTC

    The cause of the issue has been identified and we are working on restoring missing data. Next update will be in three hours.

  3. identified May 12, 2025, 05:44 PM UTC

    Data replays are continuing and we are seeing up-to-date data appearing in some regions. We will continue to monitor progress and update again in 6 hours or at the next major change in status.

  4. identified May 13, 2025, 12:22 AM UTC

    Identity data has been completely restored across all regions. Restoration of the remaining impacted data is expected to complete in the next 30 hrs. Next update will be shared in 6 hrs.

  5. identified May 13, 2025, 06:13 AM UTC

    OpsGenie data has been completely restored across all regions. Remaining data is expected to complete in the next 24 hrs. Next update will in 24 hrs or upon completion of the next major data restoration.

  6. identified May 14, 2025, 06:42 AM UTC

    Confluence data has been completely restored across all regions. Next update when the final data restoration completes.

  7. monitoring May 14, 2025, 05:06 PM UTC

    All data has been restored. We are continuing to monitor as we conduct final validations on the data to ensure nothing was missed. Once all validations are completed, the incident will be marked as resolved.

  8. resolved May 15, 2025, 12:32 AM UTC

    All data has been restored and validated and the issue has been resolved.