Is Boltrics down?

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.

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.

We are aware of an issue affecting customs related message flows through Boltrics Data Integration. Due to a DNS issue in the underlying Azure infrastructure, customs messages (including Transit Arrival / T1 flows) were temporarily not transmitted to Customs systems. The issue occurred between 20-05-2026 22:41 CET and 21-05-2026 08:03 CET. During this period, messages may have remained pending and were not delivered successfully.

A DNS-related infrastructure issue in Azure temporarily impacted customs message flows through Boltrics Data Integration between 20-05-2026 22:41 CET and 21-05-2026 08:03 CET. As a result, customs messages may not have been delivered successfully during this timeframe. The issue has been resolved and message processing is functioning normally again. Customers can resend affected messages from Business Central.

We are aware of an issue affecting customs related message flows through Boltrics Data Integration. Due to a DNS issue in the underlying Azure infrastructure, customs messages (including Transit Arrival / T1 flows) were temporarily not transmitted to Customs systems. The issue occurred between 20-05-2026 22:41 CET and 21-05-2026 08:03 CET. During this period, messages may have remained pending and were not delivered successfully.

A DNS-related infrastructure issue in Azure temporarily impacted customs message flows through Boltrics Data Integration between 20-05-2026 22:41 CET and 21-05-2026 08:03 CET. As a result, customs messages may not have been delivered successfully during this timeframe. The issue has been resolved and message processing is functioning normally again. Customers can resend affected messages from Business Central if required.