Is eazyBI Down?

On November 2, 2026, between 00:35 and 02:45 EET, a Jira Cloud incident caused Jira to leave some existing fields out of its responses, including custom fields and Jira Software and Service Management fields such as Sprint, Epic Link, Team, and the SLA fields. eazyBI imports that ran during this time treated these fields as deleted in Jira and removed their dimensions, custom hierarchies, renamed All members, and calculated members across about 900 accounts. The next imports recreated the dimensions but without the data for issues that had not changed since the previous import. We re-imported the data of the affected accounts, and on November 3 we restored the custom hierarchies, renamed All members, and calculated members from the audit log. The largest accounts, including some with Xray data, took longer, and the last of these accounts finished on November 10. To prevent this in the future, we are changing the import so it stops with an error instead of removing a field that Jira or an app manages when Jira temporarily does not return it. We will also monitor unusual mass removals across accounts. --- [2026-11-03T17:31:58.897+02:00] (resolved) The data of most affected accounts has been re-imported, and custom hierarchies have been restored. All members rename and calculated members that were removed during the incident have been restored. A few accounts with large data volumes are still finishing their re-import; we will restore them as soon as it completes. If a report still shows missing data or a missing calculated member, please contact eazyBI support. --- [2026-11-02T20:01:46.232+02:00] (monitoring) We are re-importing the data of the affected accounts. About two-thirds of the accounts have finished the data re-import; the larger accounts take longer. The custom hierarchies, renamed All members and calculated members, that were removed during the incident have not yet been restored. We will post an update about restoring them. Until the recovery is complete, reports that use the affected dimensions may show incomplete data or errors. No action is needed from you. --- [2026-11-02T11:32:28.497+02:00] (monitoring) Our investigation shows that between 22:35 and 00:45 UTC, eazyBI imports removed some Jira dimensions that were not returned to eazyBI because of the Jira Cloud incident, including custom fields, Sprint, Epic Link, Parent Link, Team, Story Points, and Service Management SLA fields. The next import recreated the dimensions, but their historical data is incomplete, and custom hierarchies and calculated members defined on them need to be restored. We are running full re-imports for the affected accounts and will restore the custom hierarchies and calculated members once each account's re-import completes. No action is needed from you. Reports that use these dimensions may show incomplete data until then. We will post an update when the recovery is complete. --- [2026-11-02T09:36:23.670+02:00] (monitoring) Following an earlier Jira Cloud incident about missing fields on work items, we have identified that some custom field values were not imported into eazyBI for some accounts. More details about the Jira incident here: https://jira-software.status.atlassian.com/incidents/1blzrf38268l

From October 26, 13:02 UTC to October 28, 11:44 UTC, imports of Time to SLA data failed with an HTTP 403 error for 22 accounts that use Jira Cloud sites with data residency. The Time to SLA vendor started to require that these sites use their regional API host. eazyBI kept sending the requests to the global host, which now rejects them. On October 28 we deployed a fix: eazyBI now sends the requests to the regional host. All affected accounts imported successfully by 12:49 UTC, and no user action was needed. --- [2026-10-28T16:06:16.948+02:00] (resolved) This incident has been resolved. --- [2026-10-28T13:48:55.449+02:00] (monitoring) We have deployed a fix for the HTTP 403 errors in Time to SLA data imports on Jira Cloud sites with data residency. Imports for the affected accounts have been restarted and will be picked up by the queue. You don't need to change your API token. We are monitoring the results. --- [2026-10-27T23:58:09.339+02:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-10-27T23:58:00.356+02:00] (investigating) Since October 26, 13:00 UTC, some imports of Time to SLA data from Jira Cloud have been failing with an HTTP 403 (not authorized) error. We are investigating the cause.

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. --- [2026-08-26T15:09:06.045+03:00] (resolved) This incident has been resolved. --- [2026-08-26T12:43:18.231+03:00] (monitoring) Many imports have been restored. We are monitoring the results. --- [2026-08-26T12:38:27.116+03:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-08-26T11:13:40.327+03:00] (investigating) We are currently investigating this issue.

We will be undergoing scheduled maintenance during this time. --- [2026-11-13T15:43:22.149+02:00] (scheduled) We are upgrading the eazyBI database. During the maintenance, eazyBI is in read-only mode. You can log in and view your reports and dashboards, but you cannot save changes, and data imports are paused.