Atlassian Loom incident

Confluence, Jira Mobile and Forge users may experience authentication issues

Minor Resolved View vendor source →
Started
Feb 03, 2026, 10:19 AM UTC
Resolved
Feb 03, 2026, 10:50 AM UTC
Duration
30m
Detected by Pingoru
Feb 03, 2026, 10:19 AM UTC

Affected components

RecordingViewingAuthenticationLoom AI

Update timeline

  1. investigating Feb 03, 2026, 10:19 AM UTC

    Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

  2. investigating Feb 03, 2026, 10:24 AM UTC

    Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or sooner.

  3. resolved Feb 03, 2026, 10:50 AM UTC

    Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Looking to track Atlassian Loom downtime and outages?

Pingoru polls Atlassian Loom's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Atlassian Loom reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Atlassian Loom alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Atlassian Loom for free

5 free monitors · No credit card required