← Live dashboard

Issues with 403 user authentication errors across Atlassian products

ResolvedminorOfficial source confirmedFirst recorded update Mar 4, 2025, 07:31 AM · Resolved Mar 4, 2025, 07:31 AM

We are aware of an issue that was impacting user authentication to Atlassian services between 6:10AM Tuesday 4th March UTC and 6:35AM Tuesday 4th March UTC. Users that were already logged in would not have been impacted by this issue. A deployment suspected of causing this issue was rolled back and the problem was subsequently resolved.

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Atlassian (Jira & Confluence) now? Check the current status

Updates (1)

  1. Mar 4, 2025, 07:31 AM
    Issues with 403 user authentication errors across Atlassian products

    We are aware of an issue that was impacting user authentication to Atlassian services between 6:10AM Tuesday 4th March UTC and 6:35AM Tuesday 4th March UTC. Users that were already logged in would not have been impacted by this issue. A deployment suspected of causing this issue was rolled back and the problem was subsequently resolved.

    Atlassian (Jira & Confluence) ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Atlassian (Jira & Confluence)'s status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.