- Detected by Pingoru
- Sep 14, 2026, 11:51 AM UTC
- Resolved
- Sep 14, 2026, 01:33 PM UTC
- Duration
- 1h 42m
Affected: Performance
Timeline · 3 updates
-
investigating Sep 14, 2026, 11:51 AM UTC
Earlier this morning, an issue at our data center caused temporary downtime across our environments. The data center provider has successfully resolved the problem, and all systems are now fully restored and operating normally. We apologize for any inconvenience this disruption may have caused and appreciate your patience.
-
monitoring Sep 14, 2026, 12:42 PM UTC
Following our previous communication, our platforms experienced a brief recurrence of downtime related to the data center issue. Services are currently back online and operating normally. We are closely monitoring the environment alongside the data center provider to ensure ongoing stability. We apologize for the repeated disruption and appreciate your continued patience.
-
resolved Sep 14, 2026, 01:33 PM UTC
We have received official confirmation from the data center provider that the root cause of today's service interruptions has been fully resolved. All platforms are currently stable and operating normally. We appreciate your patience and understanding throughout these disruptions.
Read the full incident report →
- Detected by Pingoru
- Sep 11, 2026, 07:43 AM UTC
- Resolved
- Sep 11, 2026, 11:03 AM UTC
- Duration
- 3h 19m
Affected: On-Premise Data Gateway
Timeline · 3 updates
-
investigating Sep 11, 2026, 07:43 AM UTC
We are currently investigating an issue causing data load failures for platforms utilising an on-premise connection. Initial findings indicate that the problem stems from the zipping and transmission of data from the server to the BrightSync client. Our team is actively working to identify the root cause and resolve the issue. We will provide another update as soon as more information becomes available.
-
identified Sep 11, 2026, 09:45 AM UTC
The root cause of the data load failures affecting platforms with on-premise connections has been identified. Our development team is actively developing and testing a fix for the data transmission issue. We will provide another update as soon as the solution is deployed or if there are any changes to the timeline.
-
resolved Sep 11, 2026, 11:03 AM UTC
The data transmission issue causing load failures for on-premise connections has been fully resolved, and normal operations have resumed. Please note that we will not be performing a restart of the failed loads to prevent excessive strain on the system processes. If you require your data to be updated immediately, please initiate a manual load from your environment. Thank you for your patience while we resolved this issue.
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2026, 07:40 AM UTC
- Resolved
- Aug 26, 2026, 09:41 AM UTC
- Duration
- 2h 1m
Affected: General Dataloads
Timeline · 2 updates
-
investigating Aug 26, 2026, 07:40 AM UTC
We are currently investigating an issue that caused all overnight data loads for the connector Odoo to fail. Our development team is actively working on a hotfix to restore normal functionality as quickly as possible. We will provide a new update as soon as the fix is deployed or more information becomes available.
-
resolved Aug 26, 2026, 09:41 AM UTC
The issue affecting the Odoo overnight data loads has been successfully resolved. We have implemented a fix and all affected data loads have been automatically restarted. Processing is now returning to normal. Thank you for your patience and understanding while we worked to resolve this issue.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 07:45 AM UTC
- Resolved
- Jun 18, 2026, 09:28 AM UTC
- Duration
- 1h 43m
Affected: General Dataloads
Timeline · 3 updates
-
investigating Jun 18, 2026, 07:45 AM UTC
We are currently investigating an issue affecting some of our scheduled overnight data loads. Please note that this issue is isolated to some platforms, and not all platforms are impacted. For the affected platforms, manual restarts of the data loads are temporarily unavailable. Our development team is actively working to resolve the root cause and restore full functionality as quickly as possible. We apologise for the inconvenience and will provide further updates here.
-
identified Jun 18, 2026, 09:04 AM UTC
The root cause of the current issue has been identified and linked to yesterday's system update. Our development team is already working to resolve this as quickly as possible. We apologize for the inconvenience and will provide further updates as they become available.
-
resolved Jun 18, 2026, 09:28 AM UTC
We have successfully resolved the issue. Systems are now operating normally. If you require up-to-date data, you can now safely trigger the dataload manually in your environment. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 11:10 AM UTC
- Resolved
- Jun 10, 2026, 11:10 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Jun 10, 2026, 11:10 AM UTC
The earlier issue that prevented tasks from resuming automatically after the update has been fully resolved. The backlog and delays in processing loads have been cleared, and all operations have returned to normal. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 08:09 AM UTC
- Resolved
- Jun 10, 2026, 08:09 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Jun 10, 2026, 08:09 AM UTC
We experienced an issue with our BrightSync system that prevented some tasks from resuming automatically after an update. This has now been resolved, and tasks can start processing again. Please note that a queue has formed, causing delays in processing loads. It may take some time for the system to fully catch up and for all delays to be resolved. We appreciate your patience as we work through the queue.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 07:55 AM UTC
- Resolved
- Jun 08, 2026, 07:55 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Jun 08, 2026, 07:55 AM UTC
The underlying server issue has been successfully resolved and our systems are fully operational again. To prevent excessive load on the servers, we will not be automatically restarting the failed data loads. If you require up-to-date data immediately, please trigger the data load manually within your BrightAnalytics environment. Thank you for your cooperation and patience.
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 07:46 AM UTC
- Resolved
- Jun 08, 2026, 07:46 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Jun 08, 2026, 07:46 AM UTC
We are currently experiencing an issue with our nightly data loads due to server unavailability. As a result, today's data has not been updated. At this moment, the data loads cannot be restarted yet while we actively work to restore server connectivity. Thank you for your patience; further updates will follow here.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 02:32 PM UTC
- Resolved
- Jun 01, 2026, 02:32 PM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Jun 01, 2026, 02:32 PM UTC
The database issues from last night have been successfully resolved, and the queue of backlog tasks and pipelines has been completely processed. All systems are operating normally and performance has stabilized. Thank you for your patience and understanding while we worked on this.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 09:19 AM UTC
- Resolved
- Jun 01, 2026, 09:19 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Jun 01, 2026, 09:19 AM UTC
Last night, a database outage caused issues with processing tasks and pipelines. The database is now back online and being monitored closely. While data loads have resumed, a large queue has formed, causing ongoing delays for tasks and pipelines. Clearing this queue will likely take several hours. We are currently investigating performance patches to optimize the database. Thank you for your patience and understanding as we work to resolve this.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 07:55 AM UTC
- Resolved
- May 19, 2026, 07:55 AM UTC
- Duration
- –
Affected: Performance
Timeline · 1 update
-
resolved May 19, 2026, 07:55 AM UTC
All systems are fully up and running, and performance has completely normalized. The previous delays have now been completely resolved. We are currently finalizing our post-incident analysis to prevent future issues. Thank you for your patience! If you have any questions, feel free to reach out at [email protected].
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 05:46 PM UTC
- Resolved
- May 18, 2026, 05:46 PM UTC
- Duration
- –
Affected: Performance
Timeline · 1 update
-
resolved May 18, 2026, 05:46 PM UTC
Update: Resolved The issue has been successfully resolved and services are now recovering. While systems are already getting back up to speed, we anticipate full, normal performance levels by tomorrow morning. A full post-incident analysis is underway to ensure future stability. Thank you for your patience, and please contact [email protected] if you need immediate assistance.
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 04:58 PM UTC
- Resolved
- May 18, 2026, 04:58 PM UTC
- Duration
- –
Affected: Performance
Timeline · 1 update
-
resolved May 18, 2026, 04:58 PM UTC
We are pleased to inform you that the cause of the issue has been found. However, you may still experience delays over the next period as everything fully catches up. We apologize for any inconvenience this may have caused and appreciate your understanding. Our team will conduct a thorough post-incident analysis to prevent similar issues in the future. If you have further questions, don't hesitate to contact us via [email protected].
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 03:29 PM UTC
- Resolved
- May 18, 2026, 03:29 PM UTC
- Duration
- –
Affected: Performance
Timeline · 1 update
-
resolved May 18, 2026, 03:29 PM UTC
We are currently experiencing some performance issues with our applications, which may affect several platforms and projects. We are aware of the situation and are actively working to resolve it. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 08:39 AM UTC
- Resolved
- Apr 22, 2026, 08:39 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Apr 22, 2026, 08:39 AM UTC
We are pleased to inform you that the issue has been resolved. Our team has solved the issue so you can trigger your data load again. Our team will conduct a thorough post-incident analysis to prevent similar issues in the future. If you have further questions, don't hesitate to contact us via [email protected].
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 08:06 AM UTC
- Resolved
- Apr 22, 2026, 08:06 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Apr 22, 2026, 08:06 AM UTC
Our team has identified the root cause of the issue and is implementing a fix. We expect services to be restored shortly. We appreciate your continued patience and understanding. We will provide another update once the issue has been fully resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 07:50 AM UTC
- Resolved
- Apr 22, 2026, 07:50 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Apr 22, 2026, 07:50 AM UTC
We are currently experiencing an issue with the nightly data loads. Our team is actively investigating and working to resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience. We will provide an update on the situation as soon as we know more.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 09:01 AM UTC
- Resolved
- Feb 11, 2026, 09:01 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Feb 11, 2026, 09:01 AM UTC
We have resolved the issue affecting the data loads. The root cause was identified as an error in the query logic, which caused several scheduled loads to fail. Our team has corrected the query and restarted all affected loads. Data should be appearing as expected shortly. We apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Feb 11, 2026, 07:42 AM UTC
- Resolved
- Feb 11, 2026, 07:42 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Feb 11, 2026, 07:42 AM UTC
We are currently experiencing an issue with the data loads. Our team is actively investigating and working to resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience. We will provide an update on the situation as soon as we know more.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 09:17 AM UTC
- Resolved
- Feb 09, 2026, 09:17 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Feb 09, 2026, 09:17 AM UTC
We are pleased to inform you that the underlying issue affecting the Exact Online connection has been resolved. To resume your data loads, a manual re-authorization of the connection is required. You can quickly restore the link by following these steps in your BrightAnalytics platform: Step 1: Click the heart icon in the upper right corner of your BrightAnalytics platform. Step 2: Go to Cloud integrations. Step 3: Find the connection marked as Disconnected and click Connect. Step 4: Log in to Exact Online via the prompt to re-establish the link. Once the status returns to Connected, your data loads will be able to run as usual. Thank you for your patience while we worked on this fix.
Read the full incident report →
- Detected by Pingoru
- Feb 09, 2026, 07:49 AM UTC
- Resolved
- Feb 09, 2026, 07:49 AM UTC
- Duration
- –
Timeline · 1 update
-
resolved Feb 09, 2026, 07:49 AM UTC
We are currently experiencing an issue with the data loads out of Exact Online. Our team is actively investigating and working to resolve the issue as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience. We will provide an update on the situation as soon as we know more.
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 09:29 AM UTC
- Resolved
- Jan 16, 2026, 09:29 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Jan 16, 2026, 09:29 AM UTC
Our team has solved the issue so you can trigger your dataload again. We apologize for any inconvenience this may cause and appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 09:11 AM UTC
- Resolved
- Jan 16, 2026, 09:11 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Jan 16, 2026, 09:11 AM UTC
Our team has identified the root cause of the issue and is implementing a fix. We expect services to be restored shortly. We appreciate your continued patience and understanding. We will provide another update once the issue has been fully resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 16, 2026, 08:34 AM UTC
- Resolved
- Jan 16, 2026, 08:34 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Jan 16, 2026, 08:34 AM UTC
Our team is aware of the reported issue concerning the failed data loads and is actively investigating. We apologize for any inconvenience this may cause and appreciate your patience. Rest assured, we are working to resolve the issue as quickly as possible. We will provide updates as soon as more information becomes available.
Read the full incident report →
- Detected by Pingoru
- Nov 25, 2025, 11:00 AM UTC
- Resolved
- Nov 25, 2025, 11:00 AM UTC
- Duration
- –
Affected: General Dataloads
Timeline · 1 update
-
resolved Nov 25, 2025, 11:00 AM UTC
We’re pleased to inform you that the issue has been resolved. The systems are fully operational again, and you can now rerun the data loads manually. Thank you for your understanding and patience.
Read the full incident report →