The issue has been resolved. Should you continue to experience this issue, please send us a new ticket containing any specifically affected shipment references in plain text where possible, so we can investigate further.
Posted Nov 11, 2025 - 14:49 CET
Monitoring
A fix for the issue has been deployed and we are currently monitoring it.
If you want to keep yourself updated about this incident, please subscribe to this post.
Posted Nov 11, 2025 - 14:18 CET
Investigating
Since 2025-11-11, at 13:00 the connection with DPA is down. These are the errors you can see when trying to book/manifest shipments:
"Shipment submit failure: Shipment booking failed. Internal service call failed. Bad Request: An internal server error occurred, - Service Unavailable [503]Shipment submit failure: Shipment booking failed. Internal service call failed. Bad Request: An internal server error occurred, - Service Unavailable [503]"
"Shipment submit failure: Shipment booking failed. Internal service call failed. Bad Request: An internal server error occurred, - I/O error: Read timed out; nested exception is java.net.SocketTimeoutException: Read timed outShipment submit failure: Shipment booking failed. Internal service call failed. Bad Request: An internal server error occurred, - I/O error: Read timed out; nested exception is java.net.SocketTimeoutException: Read timed out"
We are in contact with the carrier to solve this as soon as possible and will comment here when the issue is solved.
If you want to keep yourself updated about this incident, please subscribe to this post.
Posted Nov 11, 2025 - 13:54 CET
This incident affected: Carrier connections (DPD).