Boltrics Outage History

Boltrics is up right now

Boltrics had 14 outages in the last 2 years totaling 764h 47m of downtime — averaging 0.6 incidents per month.

There were 14 Boltrics outages since June 19, 2025 totaling 764h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.boltrics.com

Major May 20, 2026

Customs messages are temporarily not being sent via Data Integration

Detected by Pingoru
May 20, 2026, 08:41 PM UTC
Resolved
Jun 14, 2026, 01:57 AM UTC
Duration
24d 5h
Timeline · 1 update
  1. investigating May 21, 2026, 07:08 AM UTC

    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.

Read the full incident report →

Major April 22, 2026

Investigating issues with Boltrics DataHub

Detected by Pingoru
Apr 22, 2026, 08:35 AM UTC
Resolved
Apr 22, 2026, 01:05 PM UTC
Duration
4h 29m
Timeline · 2 updates
  1. investigating Apr 22, 2026, 08:35 AM UTC

    At the moment, there are issues with one or more DataHub platforms (datahub flow). Therefore, you might experience difficulties using Boltrics’ DataHub Platform. Our team is actively investigating the incident and will provide updates here soon. Note: It only impacts transaction processing, your logistics processes in Business Central will continue.

  2. resolved Apr 22, 2026, 01:05 PM UTC

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

Read the full incident report →

Major March 31, 2026

Unintended roll out of test environments

Detected by Pingoru
Mar 31, 2026, 11:29 AM UTC
Resolved
Mar 31, 2026, 11:43 AM UTC
Duration
13m
Timeline · 1 update
  1. resolved Mar 31, 2026, 11:43 AM UTC

    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.

Read the full incident report →

Major February 10, 2026

Incoming customs messages not being processed

Detected by Pingoru
Feb 10, 2026, 07:51 AM UTC
Resolved
Feb 10, 2026, 11:37 AM UTC
Duration
3h 45m
Timeline · 1 update
  1. resolved Feb 10, 2026, 11:37 AM UTC

    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.

Read the full incident report →

Major January 27, 2026

Dutch Customs Systems Unavailable

Detected by Pingoru
Jan 27, 2026, 10:00 PM UTC
Resolved
Jan 28, 2026, 10:40 AM UTC
Duration
12h 40m
Timeline · 1 update
  1. resolved Jan 28, 2026, 10:40 AM UTC

    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.

Read the full incident report →

Major January 12, 2026

Issue with Incoming Customs Messages

Detected by Pingoru
Jan 12, 2026, 11:15 AM UTC
Resolved
Jan 13, 2026, 08:17 AM UTC
Duration
21h 2m
Timeline · 1 update
  1. resolved Jan 13, 2026, 08:17 AM UTC

    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.

Read the full incident report →

Major November 17, 2025

Cargonaut Outage.

Detected by Pingoru
Nov 17, 2025, 08:00 AM UTC
Resolved
Nov 17, 2025, 09:51 AM UTC
Duration
1h 51m
Timeline · 1 update
  1. resolved Nov 17, 2025, 09:51 AM UTC

    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.

Read the full incident report →

Major October 30, 2025

Business Central environment unreachable – ERR_HTTP2_PROTOCOL_ERROR

Detected by Pingoru
Oct 30, 2025, 08:52 AM UTC
Resolved
Oct 30, 2025, 10:17 AM UTC
Duration
1h 24m
Timeline · 1 update
  1. resolved Oct 30, 2025, 10:17 AM UTC

    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.

Read the full incident report →

Major June 19, 2025

Performance Degradation in Business Central – NL Environments on Major Version 25 Affected

Detected by Pingoru
Jun 19, 2025, 05:16 AM UTC
Resolved
Jun 19, 2025, 11:26 AM UTC
Duration
6h 10m
Timeline · 1 update
  1. resolved Jun 19, 2025, 11:26 AM UTC

    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.

Read the full incident report →