Boltrics Outage History

PTV has resolved the issue and PTV Developer should be working again. Routing should now function as normal. If you applied the workaround, please restore your original settings in Transport Setup: 1. Set Default Activity Calculation Type back to its previous value. 2. Re-enter the values you noted down in the xServer xMap URL, xServer xLocate URL, xServer xRoute URL and xServer Profile fields. Trips created during the outage may be missing driving kilometres and times, and ETAs may not have been calculated. These trips can be recalculated once the settings are restored. If you still experience problems after restoring your settings, please contact Boltrics Support. We apologize for any 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.

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.

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.

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.

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.

We've now resolved the incident. Thanks for your patience.

The issue has been mitigated, and you should no longer receive any related emails. We will delete the newly created test environments. They will be recreated 7 days prior to your scheduled production update, in line with the normal process.

All new incoming customs messages are being received and processed correctly. Messages that were received earlier (including DMS and EMCS messages) have been successfully restarted and processed. If you believe any messages are still missing, please contact Support for assistance. **Root cause:** The issue was caused by an authentication problem between Datahub and Business Central following a recent change by Microsoft. **Resolution & mitigation:** Authentication has been restored and the affected flows have been restarted. To prevent similar issues in the future, monitoring and alerts have been implemented to detect and address this situation at an early stage.

All previously affected Dutch Customs (Douane) services are fully operational again as of 11:19 CET. The emergency and fallback procedures are no longer applicable.

The earlier issue causing DMS messages to be stuck in a loop has been resolved. Message processing is now functioning as expected. However, it is possible that some messages were not processed. If you are missing a message, please contact Customs to request a resend. We apologize for the inconvenience and appreciate your patience while we worked to resolve the issue.

Dear Customer, We would like to inform you that the earlier reported system-wide outage at Cargonaut has been resolved. Thank you for your patience.

Microsoft has resolved the connectivity issue affecting Business Central environments. All users should now be able to log in and access their environments as expected. If you continue to experience issues, please contact support for further assistance.

Final PIR - Azure Front Door - Connectivity issues across multiple regions: Incident ID: YKYN-BWZ Full Report available: https://app.azure.com/h/QNBQ-5W8/e7ac71

Issues with Front Door haven been resolved.

The performance issues affecting NL environments on major version 25 have now been resolved. Systems are operating normally again, and no further disruptions have been reported. We want to thank you for your patience and understanding during this incident. The Root Cause Analysis (RCA) will be shared as soon as we receive it from Microsoft. We will publish it on this page to keep you fully informed. If you continue to experience any unexpected behavior, please reach out to our support team.

Microsoft has identified and resolved an issue impacting performance for multiple tenants on the same cluster. The root cause was related to resource starvation on the shared application service. As of March 26, 2025, we have been monitoring the telemetry and we can confirm that the issue has been mitigated, and performance has returned to normal.

After a full week of monitoring, we can confirm that performance has remained stable across all environments. We continue to work closely with Microsoft to explore long-term solutions and will provide further updates as new information becomes available. Thank you for your patience and trust.

Earlier today, we received reports of performance issues affecting multiple tenants running on the same cluster. Microsoft has investigated and identified that the cluster was running low on memory. To mitigate the issue, all service nodes were restarted, and performance should now be back to normal. We have been actively monitoring the telemetry for the affected tenants throughout the afternoon and have observed significant improvement. Since the situation appears to be stable, we will be closing all support requests related to the recent performance issues. If you are still experiencing problems, you can reopen the same support request, and we will follow up accordingly. We sincerely apologize for the inconvenience this has caused and appreciate your patience and cooperation. Boltrics Support Team