Confluence incident

Notifications are delayed

Major Resolved View vendor source →

Confluence experienced a major incident on August 25, 2026 affecting View Content and iOS App and 1 more component, lasting 5h 51m. The incident has been resolved; the full update timeline is below.

Started
Aug 25, 2026, 08:42 AM UTC
Resolved
Aug 25, 2026, 02:33 PM UTC
Duration
5h 51m
Detected by Pingoru
Aug 25, 2026, 08:42 AM UTC

Affected components

View ContentiOS AppCreate and EditAndroid AppCommentsAuthentication and User ManagementSearchAdministrationNotificationsMarketplace Apps

Update timeline

  1. investigating Aug 25, 2026, 08:42 AM UTC

    We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and slack notifications for Jira, JSM and Confluence. Our teams are investigating the issue and more information will be shared within the next 1 hour.

  2. investigating Aug 25, 2026, 09:44 AM UTC

    Our teams have identified the impacted regions and are actively working to mitigate the issue. We will provide further updates within an hour, or sooner if we have significant progress to share.

  3. investigating Aug 25, 2026, 10:49 AM UTC

    Our teams have taken few corrective measures to mitigate the issue in one of the impacted regions and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.

  4. monitoring Aug 25, 2026, 01:01 PM UTC

    Our teams continue to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.

  5. resolved Aug 25, 2026, 02:33 PM UTC

    On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers.