eazyBI incident
Jira user authorization problems in eazyBI app
eazyBI experienced a critical incident on June 26, 2026 affecting Web App, lasting 9h 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 26, 2026, 08:30 AM UTC
We are currently investigating this issue.
- identified Jun 26, 2026, 01:35 PM UTC
Atlassian user authorization is failing as UserAuthTokens are not being issued. Atlassian has acknowledged the incident and is currently investigating.
- monitoring Jun 26, 2026, 03:11 PM UTC
We have implemented a solution for user token caching, and the imports in failing sites are restarted.
- resolved Jun 26, 2026, 05:34 PM UTC
This incident has been resolved.
- postmortem Jul 03, 2026, 02:12 PM UTC
On June 26, 2026, eazyBI accounts that import data from Atlassian Cloud experienced authorization failures. Atlassian's authentication service temporarily returned the user tokens that eazyBI uses to access Jira on each user's behalf with a zero validity period, and eazyBI could no longer reuse them. Investigation of the incident began at 11:30 EEST, and the cause was identified at 16:35 EEST. As a workaround, we added a fallback that reads each token's actual expiry, so valid tokens can be reused. This reduces our exposure to similar Atlassian disruptions in the future. We deployed the change, restarted the affected imports at 18:11 EEST, and confirmed normal operation by 20:34 EEST. Restarting the imports restored the imported data. During follow-up, we found that calculated members on custom field dimensions had been removed and not automatically restored, so affected reports may show incomplete results until these members are restored from the audit log.