Is Boltrics down?

An issue is affecting the processing of incoming customs messages in Boltrics Data Integration. Our team is investigating and will provide an update as soon as more information becomes available.

Incoming customs messages are being processed again. If you are still missing a message, please resend it. We will continue to monitor the situation. We apologize for the inconvenience.

The issue affecting the processing of incoming customs messages has been resolved. After monitoring the service, we can confirm that incoming messages are being processed normally again. The issue was related to a temporary connection disruption, which has since been restored. We apologize for the inconvenience and thank you for your patience.

An issue is affecting incomming customs message flows through Boltrics Data Integration. Our team is investigating the issue. We will provide an update as soon as more information becomes available.

The issue has been resolved, and all communication with Customs has been fully restored. We will update this ticket with the root cause as soon as the analysis has been completed.

We have not yet been able to resolve the incident permanently. As a result, incoming messages are currently not being processed. We are actively investigating the issue. We will provide another update as soon as more information becomes available.

The issue has been resolved, and all communication with Customs has been fully restored. We will update this ticket with the root cause as soon as the analysis has been completed. Thanks for your patience.

Our Data Integration Team has resolved the issue, and services are operating normally again. **Required action** If any DataHub flows failed during the incident, restart the affected flow runs. This should allow the processing to complete successfully. If you continue to experience issues after restarting the affected runs, please contact Boltrics Support.

**Root Cause Analysis:** The issue was caused by a defect introduced in a recent DataHub update that included improvements to the efficiency of SFTP flow processing. Due to this defect, unused SFTP connections were not correctly released. Over time, these accumulated and exhausted the available connection pool, preventing new SFTP flows from being processed. The defect was identified and corrected immediately. The fix ensures that unused connections are properly cleared, restoring normal and efficient processing of SFTP flows. No further customer action is required beyond restarting any flows that failed during the incident.

We are currently investigating an issue affecting the **DataHub 1 platform**. As a result, some incoming and outgoing messages may not be processed as expected. Our team has identified the cause of the issue and is actively working to restore normal message processing as quickly as possible. We will provide another update as soon as more information becomes available.

The issue affecting the processing of incoming and outgoing messages has been resolved. All messages are now being received and processed correctly. Messages that were not processed during the incident have been successfully restarted and completed. If you believe any messages are still missing or have not been processed, please contact our Support team for assistance. **Root Cause** The incident was caused by an issue in the processing of XSLT 3.0 transformations. **Resolution & Mitigation** The underlying issue has been resolved, and all affected message flows have been restarted to ensure normal message processing has resumed.

We are currently investigating an issue affecting Data Integration flows. Some customers may experience failures when integrations attempt to connect to Microsoft Entra ID (Azure AD). As a result, affected integrations may not process data as expected and could return authentication-related errors. Our team has identified that the issue is related to expired authentication credentials used by the integration service and is working on restoring normal operation as quickly as possible.

The authentication issue affecting Data Integration flows has been resolved: The required authentication credentials have been renewed and new integration messages are being processed successfully. Our Data Integration team is currently restarting and processing messages that were impacted during the outage. We continue to monitor the service and will provide a further update once all backlog processing has been completed.

The issue affecting Data Integration flows has been resolved. The root cause was an expired authentication credential used for Microsoft Entra ID access. This occurred due to a manual error during the credential renewal process, resulting in authentication failures for affected integration flows. The authentication credential has been renewed and Data Integration services are operating normally. New messages are being processed successfully. To prevent similar incidents in the future, we are implementing a new version that uses Microsoft-managed keyless authentication, eliminating the need for manual credential renewals. We apologize for the inconvenience and thank you for your patience.