Is eazyBI down?
Last checked 1m agoNo incidents right now.
eazyBI is operational right now. Last checked 1m ago; the most recent incident resolved 32d ago.
Real-time eazyBI status, recent outages, and incident history — pulled directly from eazyBI's official status page at https://status.eazybi.com every 5 minutes. Pingoru tracks 2 eazyBI services and has captured 9 incidents in the last 90 days (94.72% uptime). Get email, Slack, Discord, or webhook alerts the moment eazyBI reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Web App
Timeline · 3 updates
- investigating · Jun 29, 2026, 10:21 AM UTC
We are currently investigating this issue.
- monitoring · Jun 29, 2026, 11:08 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jun 29, 2026, 02:32 PM UTC
During a routine infrastructure maintenance operation, a transient inconsistency occurred in the cloud load balancer's health state tracking. Although the application servers were running and healthy, the load balancer temporarily failed to route traffic to them.
Latest: During a routine infrastructure maintenance operation, a transient inconsistency occurred in the cloud load balancer's health state tracking. Although the application servers were …
-
- Web App
Timeline · 5 updates
- 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.
Latest: On June 26, 2026, eazyBI accounts that import data from Atlassian Cloud experienced authorization failures. Atlassian's authentication service temporarily returned the user tokens …
-
- Web App
Timeline · 4 updates
- identified · Jun 09, 2026, 10:33 AM UTC
A few dozen eazyBI accounts are affected, and we are working on the fix.
- monitoring · Jun 09, 2026, 01:18 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jun 09, 2026, 01:59 PM UTC
This incident has been resolved.
- postmortem · Jun 09, 2026, 02:00 PM UTC
A change in the import structure introduced an unexpected error affecting project role dimension imports. The issue was identified quickly, and a fix has been deployed to prevent recurrence.
Latest: A change in the import structure introduced an unexpected error affecting project role dimension imports. The issue was identified quickly, and a fix has been deployed to prevent r…
-
- Web App
Timeline · 3 updates
- monitoring · May 22, 2026, 11:59 AM UTC
Due to recent database changes, the first import is running longer, resulting in longer import queues than usual. Our team is aware of the issue and is monitoring performance
- resolved · May 23, 2026, 06:07 AM UTC
This incident has been resolved.
- postmortem · May 25, 2026, 06:29 AM UTC
Changes in the structure of imported data caused unplanned DB performance issues. As a result, imports took longer than expected and larger queues accumulated. We are planning to optimize DB resources and performance.
Latest: Changes in the structure of imported data caused unplanned DB performance issues. As a result, imports took longer than expected and larger queues accumulated. We are planning to o…
-
- Web App
Timeline · 4 updates
- identified · May 14, 2026, 11:48 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring · May 14, 2026, 12:48 PM UTC
App servers are running. Monitoring and root cause analysis.
- resolved · May 14, 2026, 02:43 PM UTC
This incident has been resolved.
- postmortem · Jun 10, 2026, 07:09 AM UTC
We experienced a short outage caused by a hardware failure in Google Cloud infrastructure beyond our control. The incident has been resolved quickly, and we have implemented architectural changes.
Latest: We experienced a short outage caused by a hardware failure in Google Cloud infrastructure beyond our control. The incident has been resolved quickly, and we have implemented archit…
-
See the full eazyBI outage history
1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse eazyBI outage history →Or sign up free to get alerts when eazyBI breaks · 10 free monitors · No credit card
- Started Jun 29, 2026, 10:21 AM UTC · Resolved Jun 29, 2026, 02:32 PM UTC · 4h 11m
- Started Jun 26, 2026, 08:30 AM UTC · Resolved Jun 26, 2026, 05:34 PM UTC · 9h 4m
- Started Jun 09, 2026, 10:33 AM UTC · Resolved Jun 09, 2026, 01:59 PM UTC · 3h 25m
- Started May 22, 2026, 11:59 AM UTC · Resolved May 23, 2026, 06:07 AM UTC · 18h 7m
- eazyBI app unavailable ResolvedStarted May 14, 2026, 11:48 AM UTC · Resolved May 14, 2026, 02:43 PM UTC · 2h 54m
- We are experiencing data import issues for Jira Cloud sites with temporary license extension. ResolvedStarted May 14, 2026, 06:24 AM UTC · Resolved May 14, 2026, 10:23 AM UTC · 3h 58m