eazyBI had 26 outages in the last 2 years totaling 668h 14m of downtime — averaging 1.1 incidents per month.
There were 26 eazyBI outages since July 26, 2024 totaling 668h 14m of downtime. Each is summarised below — incident details, duration, and resolution information.
A few dozen eazyBI accounts are affected, and we are working on the fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
App servers are running. Monitoring and root cause analysis.
This incident has been resolved.
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.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
The problem occurred due to a change in the REST API on the Atlassian side. Was fixed by Atlassian.
There is an ongoing incident regarding the Confluence app authorization. We are in contact with Atlassian about the issue.
It is related to the Atlassian incident. https://developer.status.atlassian.com/incidents/fv07669nyqj1
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Atlassian incident impacted eazyBI app.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
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.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A third-party REST API problem
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Impact on the system from recently deployed changes.
We are currently investigating this issue.
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
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!
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Atlassian incident: [https://developer.status.atlassian.com/incidents/mc0d4jnrz122](https://developer.status.atlassian.com/incidents/mc0d4jnrz122)
We are having issues with our SSL certificate. The problem has been identified, and we are working on it.
The issue has been fixed.
SSL certificate expiration follow-up was dysfunctional.
The issue has been identified and a fix is being implemented.
The fix for displaying Gantt charts has been deployed.
Unexpected side effects of a newly deployed feature.
The error happens because the Jira REST API returns incorrect information. We are working with Atlassian on this problem.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Jira REST API returned incorrect data. Fixed by Atlassian.
We are looking for a solution with Atlassian.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Changes in the Atlassian REST API made it impossible to detect whether the site has Assets and other apps.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
An unexpected side effect of deployed changes.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Synchronization with Clickhouse DB did not work after Clickhouse upgrade.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Problem with eazyBI infrastructure that stuck the eazyBI import queue
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The PDF generation engine failed after an automatic upgrade. Version control for the engine was implemented to use a stable version
We are currently investigating the Zephyr Squad REST API behavior with the Zephyr app vendor.
A fix has been implemented and we are monitoring the results.
We are currently investigating the Zephyr Squad REST API behavior with the Zephyr app vendor.
The issue has been identified. Waiting for Zephyr Squad vendor to release the fix.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A third party REST API problem
We are currently investigating the issue with Atlassian.
The incident is related to the problem with the functioning of the JSM Assets requests. We are currently investigating the issue with Atlassian: https://jira-service-management.status.atlassian.com/
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A problem with JSM Assets REST API.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A new bug from the last deployment
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A bug in a new deployment
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The problem occurred because auto-scale options for eazyBI servers were not correctly enabled during the last deployment. This resulted in an overload of our app servers.
We are currently investigating the issue with Atlassian.
This incident has been resolved.
The problem happened because of a change in the REST API on the Atlassian side. Was fixed by Atlassian