Resolved after 58 minutes, affecting Glean service, on March 25, 2026.
The issue of authentication errors for Jira and Confluence is now resolved. The root cause was an IP block from Atlassian which was triggered by a spike in the number of user token requests. We have worked with Atlassian to get the IP block removed. We have also made fixes to fail gracefully when Atlassian starts returning errors for auth requests.
Affected components
Update timeline
- resolved Mar 25, 2026, 07:39 AM UTC
The issue of authentication errors for Jira and Confluence is now resolved. The root cause was an IP block from Atlassian which was triggered by a spike in the number of user token requests. We have worked with Atlassian to get the IP block removed. We have also made fixes to fail gracefully when Atlassian starts returning errors for auth requests.
- resolved Jul 14, 2026, 07:33 PM UTC
The issue of authentication errors for Jira and Confluence is now resolved. The root cause was an IP block from Atlassian which was triggered by a spike in the number of user token requests. We have worked with Atlassian to get the IP block removed. We have also made fixes to fail gracefully when Atlassian starts returning errors for auth requests.
Your product runs on more than Glean
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services