eazyBI Outage History
eazyBI is up right nowPingoru has recorded 45 incidents for eazyBI: 14 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 12 of 720 (2%) |
| May 2026 | 3 | 25 of 744 (3%) |
| June 2026 | 3 | 17 of 720 (2%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 3 | 35 of 744 (5%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 592 (0%) |
Incidents, newest first
Minor February 20, 2025 JSM Assets data import into eazyBI is not working 9h 9m Web App
Started Feb 20, 2025, 06:45 AM UTC· resolved Feb 20, 2025, 03:54 PM UTC
- investigating Feb 20, 2025, 06:45 AM UTC
We are currently investigating the issue with Atlassian.
- identified Feb 20, 2025, 08:51 AM UTC
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/
- monitoring Feb 20, 2025, 02:09 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 20, 2025, 03:54 PM UTC
This incident has been resolved.
- postmortem Apr 17, 2025, 08:06 AM UTC
A problem with JSM Assets REST API.
Notice February 14, 2025 New Jira data sources cannot be created in some eazyBI accounts 6h 8m Web App
Started Feb 14, 2025, 07:24 AM UTC· resolved Feb 14, 2025, 01:32 PM UTC
- investigating Feb 14, 2025, 07:24 AM UTC
We are currently investigating this issue.
- monitoring Feb 14, 2025, 10:36 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 14, 2025, 01:32 PM UTC
This incident has been resolved.
- postmortem Apr 17, 2025, 08:03 AM UTC
A new bug from the last deployment
Notice January 6, 2025 In some instances eazyBI accounts are not available in the home view of eazyBI app 43m Web App
Started Jan 06, 2025, 12:00 PM UTC· resolved Jan 06, 2025, 12:43 PM UTC
- investigating Jan 06, 2025, 12:00 PM UTC
We are currently investigating this issue.
- monitoring Jan 06, 2025, 12:40 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 06, 2025, 12:43 PM UTC
This incident has been resolved.
- postmortem Apr 17, 2025, 08:01 AM UTC
A bug in a new deployment