Boltrics incident
Customs messages are temporarily not being sent via Data Integration
Resolved after 10 hours 34 minutes, on May 20, 2026.
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.
Update timeline
- 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.
- resolved May 21, 2026, 07:29 AM UTC
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.
Your product runs on more than Boltrics
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services