eazyBI Outage History

eazyBI is up right now

Pingoru has recorded 45 incidents for eazyBI: 14 in the last 12 months and 3 in the last 90 days.

Source: status.eazybi.com

45incidents recorded
14last 12 months
3last 90 days
14 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking eazyBI in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026112 of 720 (2%)
May 2026325 of 744 (3%)
June 2026317 of 720 (2%)
July 202600 of 744 (0%)
August 2026335 of 744 (5%)
September 202600 of 720 (0%)
October 202600 of 512 (0%)

Incidents, newest first

Major August 26, 2026 We are experiencing data import issues. Imports may take longer than usual. 3h 55m Web App

Started Aug 26, 2026, 08:13 AM UTC· resolved Aug 26, 2026, 12:09 PM UTC

  1. investigating Aug 26, 2026, 08:13 AM UTC

    We are currently investigating this issue.

  2. identified Aug 26, 2026, 09:38 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 26, 2026, 09:43 AM UTC

    Many imports have been restored. We are monitoring the results.

  4. resolved Aug 26, 2026, 12:09 PM UTC

    This incident has been resolved.

  5. postmortem Aug 26, 2026, 12:09 PM UTC

    Between August 25 \(~12:00 UTC\) and August 26 \(~09:00 UTC\), scheduled data imports in our EU region were delayed, in some cases by several hours. No data was lost, reports and dashboards remained fully available throughout, and all imports completed normally once processed. What happened. A small number of exceptionally large, long-running imports - combined with slow responses from some external data source APIs - gradually occupied all background import capacity on our EU import servers. As capacity filled, remaining imports slowed down as well, and a backlog of queued import jobs grew faster than it could be processed. Resolution. On the morning of August 26, we added additional import server capacity. The backlog cleared within an hour, and import processing has been running normally since. We apologize for the inconvenience the delays may have caused.

Read the full incident report →

Minor August 17, 2026 eazybi for Confluence does not include macros in PDF exports 1d 5h Web App

Started Aug 17, 2026, 06:45 AM UTC· resolved Aug 18, 2026, 12:28 PM UTC

  1. identified Aug 17, 2026, 06:45 AM UTC

    Starting on Saturday at 17:36 EEST (August 15, 2026), we have disabled the export of eazyBI macros from Confluence pages. The issue is related to the Confluence Forge version, and we are actively discussing a solution with Atlassian.

  2. monitoring Aug 18, 2026, 07:29 AM UTC

    The fix has been implemented, and the Confluence page PDF export, including eazyBI macros, is again enabled starting 10:15 EEST Augst 18, 2026. We continue to monitor.

  3. resolved Aug 18, 2026, 12:28 PM UTC

    This incident has been resolved.

  4. postmortem Aug 18, 2026, 12:28 PM UTC

    After the Confluence Forge upgrade, we received a very large number of export requests that turned out to be invalid: they were not genuine exports but Forge platform calls made during page views and other non-export contexts. To keep the application stable, on August 15 at 17:36 EEST, we stopped all macro exports; this meant eazyBI macros were temporarily not rendered in Confluence page exports. The fix was ready within hours, but we could not publish it immediately: the Forge platform still treated our app as a Connect app and would have turned a minor update into a major version change \(Atlassian acknowledged this as a platform bug\). Once the new Forge version was published successfully, it determines the export type and processes only genuine exports, rendering the macro unchanged in all other cases. On August 18 at 10:15 EEST, we re-enabled exports, and they continue to be processed successfully.

Read the full incident report →

Minor August 7, 2026 Errors when opening Jira import settings 54m Web App

Started Aug 07, 2026, 09:02 AM UTC· resolved Aug 07, 2026, 09:57 AM UTC

  1. investigating Aug 07, 2026, 09:02 AM UTC

    We are currently investigating this issue.

  2. investigating Aug 07, 2026, 09:03 AM UTC

    We are continuing to investigate this issue.

  3. resolved Aug 07, 2026, 09:57 AM UTC

    This issue has been resolved. The Jira import settings screen loads normally again. No data was lost, and imports were not interrupted.

  4. postmortem Aug 07, 2026, 10:05 AM UTC

    Opening the Jira source data import settings page returned a 500 error. A DWH table existence check, added as part of performance improvements, was performed during schema definition without a checked-out DWH connection. Cloud accounts opening Jira source data settings were affected while imports, reports, and dashboard viewing were not. No data loss or data corruption.

Read the full incident report →

Critical June 29, 2026 We’re currently experiencing an eazyBI outage. Our team is investigating and working to restore service 4h 11m Web App

Started Jun 29, 2026, 10:21 AM UTC· resolved Jun 29, 2026, 02:32 PM UTC

  1. investigating Jun 29, 2026, 10:21 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 29, 2026, 11:08 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. 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.

Read the full incident report →

Critical June 26, 2026 Jira user authorization problems in eazyBI app 9h 4m Web App

Started Jun 26, 2026, 08:30 AM UTC· resolved Jun 26, 2026, 05:34 PM UTC

  1. investigating Jun 26, 2026, 08:30 AM UTC

    We are currently investigating this issue.

  2. 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.

  3. 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.

  4. resolved Jun 26, 2026, 05:34 PM UTC

    This incident has been resolved.

  5. 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.

Read the full incident report →

Minor June 9, 2026 Data import gives an error on several eazyBI sites when importing project roles dimensions 3h 25m Web App

Started Jun 09, 2026, 10:33 AM UTC· resolved Jun 09, 2026, 01:59 PM UTC

  1. identified Jun 09, 2026, 10:33 AM UTC

    A few dozen eazyBI accounts are affected, and we are working on the fix.

  2. monitoring Jun 09, 2026, 01:18 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 09, 2026, 01:59 PM UTC

    This incident has been resolved.

  4. 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.

Read the full incident report →

Major May 22, 2026 Slowness of data imports in eazyBI app 18h 7m Web App

Started May 22, 2026, 11:59 AM UTC· resolved May 23, 2026, 06:07 AM UTC

  1. 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

  2. resolved May 23, 2026, 06:07 AM UTC

    This incident has been resolved.

  3. 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.

Read the full incident report →

Major May 14, 2026 eazyBI app unavailable 2h 54m Web App

Started May 14, 2026, 11:48 AM UTC· resolved May 14, 2026, 02:43 PM UTC

  1. identified May 14, 2026, 11:48 AM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring May 14, 2026, 12:48 PM UTC

    App servers are running. Monitoring and root cause analysis.

  3. resolved May 14, 2026, 02:43 PM UTC

    This incident has been resolved.

  4. 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.

Read the full incident report →

Minor May 14, 2026 We are experiencing data import issues for Jira Cloud sites with temporary license extension. 3h 58m Web App

Started May 14, 2026, 06:24 AM UTC· resolved May 14, 2026, 10:23 AM UTC

  1. investigating May 14, 2026, 06:24 AM UTC

    We are currently investigating this issue.

  2. identified May 14, 2026, 06:34 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 14, 2026, 07:18 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 14, 2026, 10:23 AM UTC

    This incident has been resolved.

  5. postmortem May 14, 2026, 10:24 AM UTC

    eazyBI sites without an Atlassian subscription that use a development license extension had lost their license status, resulting in import errors across several eazyBI accounts. We have restored the license status validation for development extensions and verified successful import completion across affected sites.

Read the full incident report →

Major April 23, 2026 On some sites the Assets object schema and the Assets custom fields import returns an error. 11h 31m Web App

Started Apr 23, 2026, 08:25 PM UTC· resolved Apr 24, 2026, 07:56 AM UTC

  1. investigating Apr 23, 2026, 08:25 PM UTC

    We are currently investigating this issue.

  2. identified Apr 24, 2026, 05:41 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 24, 2026, 06:55 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Apr 24, 2026, 07:02 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Apr 24, 2026, 07:56 AM UTC

    This incident has been resolved.

  6. postmortem Apr 24, 2026, 07:57 AM UTC

    The problem occurred due to a change in the REST API on the Atlassian side. Was fixed by Atlassian.

Read the full incident report →

Major March 24, 2026 There are problems with eazyBI for Confluence app authorization 53m Web App

Started Mar 24, 2026, 08:01 AM UTC· resolved Mar 24, 2026, 08:55 AM UTC

  1. identified Mar 24, 2026, 08:01 AM UTC

    There is an ongoing incident regarding the Confluence app authorization. We are in contact with Atlassian about the issue.

  2. identified Mar 24, 2026, 08:33 AM UTC

    It is related to the Atlassian incident. https://developer.status.atlassian.com/incidents/fv07669nyqj1

  3. monitoring Mar 24, 2026, 08:46 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Mar 24, 2026, 08:55 AM UTC

    This incident has been resolved.

  5. postmortem Mar 24, 2026, 08:55 AM UTC

    Atlassian incident impacted eazyBI app.

Read the full incident report →

Critical March 16, 2026 eazyBI was unavailable due to database connection problems. 5h 41m Web App, Docs

Started Mar 16, 2026, 06:17 AM UTC· resolved Mar 16, 2026, 11:59 AM UTC

  1. monitoring Mar 16, 2026, 06:17 AM UTC

    A fix has been implemented and we are monitoring the results.

  2. monitoring Mar 16, 2026, 08:37 AM UTC

    We are continuing to monitor for any further issues.

  3. resolved Mar 16, 2026, 11:59 AM UTC

    This incident has been resolved.

  4. postmortem Mar 19, 2026, 09:31 AM UTC

    Service was unavailable due to a large number of unterminated SQL transactions, which exhausted available database connections. The issue was detected by monitoring systems; however, as it occurred outside working hours, response and remediation were delayed. To prevent recurrence, we are updating timeout configurations to reduce the risk of lingering transactions. Monitoring has been improved with severity-based alerting to ensure timely notification and response.

Read the full incident report →

Minor February 6, 2026 We are experiencing data import issues from Time to SLA app. 2d 22h Web App

Started Feb 06, 2026, 09:43 AM UTC· resolved Feb 09, 2026, 07:58 AM UTC

  1. investigating Feb 06, 2026, 09:43 AM UTC

    We are currently investigating this issue.

  2. monitoring Feb 09, 2026, 07:54 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 09, 2026, 07:58 AM UTC

    This incident has been resolved.

  4. postmortem Feb 09, 2026, 08:44 AM UTC

    A third-party REST API problem

Read the full incident report →

Minor January 21, 2026 Data imports into eazyBI accounts with the Xray app are failing 1d 12h Web App

Started Jan 21, 2026, 06:54 AM UTC· resolved Jan 22, 2026, 07:07 PM UTC

  1. identified Jan 21, 2026, 06:54 AM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Jan 22, 2026, 02:00 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 22, 2026, 07:07 PM UTC

    This incident has been resolved.

  4. postmortem Apr 14, 2026, 02:17 PM UTC

    The incident was caused by an incomplete solution for Xray data import changes. Import via the Xray GraphQL API was added alongside backup processing, but unlike backups, the GraphQL API enforces project-level permissions — so instance admins who could access the full Xray backup were denied data for projects where they lacked explicit access.

Read the full incident report →

Minor October 15, 2025 eazyBI dashboards may give an error when opening 1h 42m Web App

Started Oct 15, 2025, 10:58 AM UTC· resolved Oct 15, 2025, 12:40 PM UTC

  1. investigating Oct 15, 2025, 10:58 AM UTC

    We are currently investigating this issue.

  2. monitoring Oct 15, 2025, 11:55 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 15, 2025, 12:40 PM UTC

    This incident has been resolved.

  4. postmortem Jan 21, 2026, 06:59 AM UTC

    Impact on the system from recently deployed changes.

Read the full incident report →

Major September 15, 2025 On some sites, the Assets object schema and the Assets custom fields import give an error. 3d 23h Web App

Started Sep 15, 2025, 06:03 AM UTC· resolved Sep 19, 2025, 05:48 AM UTC

  1. investigating Sep 15, 2025, 06:03 AM UTC

    We are currently investigating this issue.

  2. identified Sep 15, 2025, 02:10 PM UTC

    UPD. Sep-16. The problem is escalated to Atlassian. There is an internal incident open and Atlassian teams are working on the fix. They were able to reproduce the issue and are working on the resolution. We will keep you updated on this. Atlassian incident: https://developer.status.atlassian.com/incidents/mc0d4jnrz122

  3. identified Sep 17, 2025, 08:18 AM UTC

    UPD from Atlassian. Apologies for the delay! Our Engineering team is still investigating this and will let you know as soon as we get an update!

  4. monitoring Sep 17, 2025, 10:28 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Sep 19, 2025, 05:48 AM UTC

    This incident has been resolved.

  6. postmortem Oct 06, 2025, 02:36 PM UTC

    Atlassian incident: [https://developer.status.atlassian.com/incidents/mc0d4jnrz122](https://developer.status.atlassian.com/incidents/mc0d4jnrz122)

Read the full incident report →

Notice September 15, 2025 SSL certificate issue 19m Web App, Docs

Started Sep 15, 2025, 04:57 AM UTC· resolved Sep 15, 2025, 05:16 AM UTC

  1. identified Sep 15, 2025, 04:57 AM UTC

    We are having issues with our SSL certificate. The problem has been identified, and we are working on it.

  2. resolved Sep 15, 2025, 05:16 AM UTC

    The issue has been fixed.

  3. postmortem Oct 06, 2025, 02:31 PM UTC

    SSL certificate expiration follow-up was dysfunctional.

Read the full incident report →

Minor September 1, 2025 We are currently experiencing difficulties displaying Gantt charts 1h 34m Web App

Started Sep 01, 2025, 10:37 AM UTC· resolved Sep 01, 2025, 12:11 PM UTC

  1. identified Sep 01, 2025, 10:37 AM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved Sep 01, 2025, 12:11 PM UTC

    The fix for displaying Gantt charts has been deployed.

  3. postmortem Oct 06, 2025, 02:30 PM UTC

    Unexpected side effects of a newly deployed feature.

Read the full incident report →

Minor August 7, 2025 Data import gives error on some sites 18h 30m Web App

Started Aug 07, 2025, 12:16 PM UTC· resolved Aug 08, 2025, 06:47 AM UTC

  1. identified Aug 07, 2025, 12:16 PM UTC

    The error happens because the Jira REST API returns incorrect information. We are working with Atlassian on this problem.

  2. monitoring Aug 07, 2025, 02:58 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 08, 2025, 06:47 AM UTC

    This incident has been resolved.

  4. postmortem Oct 06, 2025, 02:29 PM UTC

    Jira REST API returned incorrect data. Fixed by Atlassian.

Read the full incident report →

Minor August 4, 2025 On some sites, the Assets object schema and the Assets custom fields import give an error. The data import from other apps might also be affected. 22h 49m Web App

Started Aug 04, 2025, 07:42 AM UTC· resolved Aug 05, 2025, 06:32 AM UTC

  1. investigating Aug 04, 2025, 07:42 AM UTC

    We are looking for a solution with Atlassian.

  2. identified Aug 04, 2025, 02:03 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 04, 2025, 02:06 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 05, 2025, 06:32 AM UTC

    This incident has been resolved.

  5. postmortem Oct 06, 2025, 02:25 PM UTC

    Changes in the Atlassian REST API made it impossible to detect whether the site has Assets and other apps.

Read the full incident report →

Minor July 8, 2025 Some reports may fail with an error message "Failed to execute query. Error message:" 7h 13m Web App

Started Jul 08, 2025, 12:16 PM UTC· resolved Jul 08, 2025, 07:30 PM UTC

  1. investigating Jul 08, 2025, 12:16 PM UTC

    We are currently investigating this issue.

  2. monitoring Jul 08, 2025, 05:45 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 08, 2025, 07:30 PM UTC

    This incident has been resolved.

  4. postmortem Oct 06, 2025, 02:19 PM UTC

    An unexpected side effect of deployed changes.

Read the full incident report →

Notice May 14, 2025 We are experiencing the slowness of eazyBI app 33m Web App

Started May 14, 2025, 01:50 PM UTC· resolved May 14, 2025, 02:23 PM UTC

  1. investigating May 14, 2025, 01:50 PM UTC

    We are currently investigating this issue.

  2. monitoring May 14, 2025, 02:21 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 14, 2025, 02:23 PM UTC

    This incident has been resolved.

  4. postmortem Jul 07, 2025, 02:39 PM UTC

    Synchronization with Clickhouse DB did not work after Clickhouse upgrade.

Read the full incident report →

Major March 24, 2025 Regular import jobs are stuck in import queue and data might not be refreshed. 2h 45m Web App

Started Mar 24, 2025, 07:10 AM UTC· resolved Mar 24, 2025, 09:56 AM UTC

  1. investigating Mar 24, 2025, 07:10 AM UTC

    We are currently investigating this issue.

  2. monitoring Mar 24, 2025, 07:42 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 24, 2025, 09:56 AM UTC

    This incident has been resolved.

  4. postmortem Apr 17, 2025, 08:10 AM UTC

    Problem with eazyBI infrastructure that stuck the eazyBI import queue

Read the full incident report →

Minor March 19, 2025 PDF export and dashboard subscription is not working 3h 50m Web App

Started Mar 19, 2025, 08:40 AM UTC· resolved Mar 19, 2025, 12:31 PM UTC

  1. investigating Mar 19, 2025, 08:40 AM UTC

    We are currently investigating this issue.

  2. monitoring Mar 19, 2025, 10:11 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 19, 2025, 12:31 PM UTC

    This incident has been resolved.

  4. postmortem Apr 17, 2025, 08:13 AM UTC

    The PDF generation engine failed after an automatic upgrade. Version control for the engine was implemented to use a stable version

Read the full incident report →

Minor March 10, 2025 Import error while importing Zephyr Squad data into eazyBI 13d 22h Web App

Started Mar 10, 2025, 08:45 AM UTC· resolved Mar 24, 2025, 07:12 AM UTC

  1. investigating Mar 10, 2025, 08:45 AM UTC

    We are currently investigating the Zephyr Squad REST API behavior with the Zephyr app vendor.

  2. monitoring Mar 11, 2025, 03:45 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. investigating Mar 12, 2025, 07:44 AM UTC

    We are currently investigating the Zephyr Squad REST API behavior with the Zephyr app vendor.

  4. identified Mar 13, 2025, 10:13 AM UTC

    The issue has been identified. Waiting for Zephyr Squad vendor to release the fix.

  5. monitoring Mar 19, 2025, 02:53 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Mar 24, 2025, 07:12 AM UTC

    This incident has been resolved.

  7. postmortem Apr 17, 2025, 08:16 AM UTC

    A third party REST API problem

Read the full incident report →