IN Brief:
- WiseTech acknowledged a CargoWise message-response problem at 10:37 on 28 October and identified Great Britain and Japan as particularly affected.
- Customers were instructed not to resend pending messages while engineers worked through the backlog, to avoid duplicated responses and rejection confusion.
- WiseTech confirmed the backlog was processed and messaging recovered at 08:33 on 29 October; individual disruption durations and the underlying cause are not established.
WiseTech Global experienced CargoWise customs messaging delays that disrupted freight forwarders handling declarations for Great Britain and Japan on 28 October 2026. The software developer acknowledged problems with message responses during the morning and confirmed the following morning that the backlog had been processed and messaging services had recovered.
Customer notices issued on 28 October establish the incident timeline. WiseTech first acknowledged a message-response problem at 10:37 and identified Great Britain and Japan as particularly affected at 11:24. Its engineering updates then tracked the backlog of customs responses that forwarders needed to continue processing consignments.
Updates at 12:04 and 14:07 described mitigation work. At 15:51 WiseTech reported slow processing of the backlog; by 20:47 most queues had been worked through, although the main issue remained under investigation. The company confirmed at 08:33 on 29 October that the backlog had been cleared and messaging services had recovered.
Almost 22 hours elapsed between the first acknowledgement and the recovery confirmation. Individual forwarders may have experienced shorter interruptions, and the notifications do not quantify the number of users or declarations affected. The incident’s root cause was not established by the available customer communications.
Electronic customs systems transmit declarations and return status messages needed to progress goods through border procedures. Where a user can prepare an entry but cannot receive a timely response, the forwarder may lack confirmation of acceptance, queries, or release. That uncertainty can hold up subsequent steps even when the physical cargo has reached its port or depot.
One UK forwarder said its staff were unable to process entries normally for much of 28 October. Customers waited while the team had little information on when routine processing would resume. The account documents an operational interruption at that business; the available reporting does not measure equivalent delays across every UK or Japanese CargoWise customer.
WiseTech instructed customers not to resubmit messages that were awaiting replies, warning that new submissions could worsen the backlog and produce confusing rejections when responses arrived. Following that instruction preserved the original transaction sequence while recovery was under way. Each forwarder still needed to reconcile its outstanding customs entries against returned acknowledgements and release statuses.
A pending message can leave staff uncertain whether the declaration has been transmitted successfully or is waiting in the response queue. Treating a delayed acknowledgement as a failed submission risks creating a second transaction, while treating an unsent entry as cleared could move cargo before the required customs step has completed. The recovery process therefore depends on matching each response to its original submission.
Unconfirmed customs status can affect the timing of haulage and warehouse movements after a ship, aircraft, or truck has arrived. Collection bookings may need to be changed until the necessary release is visible, leaving vehicles or containers waiting for the next available slot. Actual consequences vary by procedure and shipment; the incident reporting does not provide a total for delayed goods or extra storage costs.
Manufacturing shipments are affected according to the delivery timetable and the point reached in the clearance process. A component consignment due to feed production may have less scheduling flexibility than inventory already held at a distribution centre. Neither the scale of such knock-on delays nor any specific penalty costs have been quantified for the October incident.
Clearing a messaging backlog involves processing queued transactions and returning responses that operators can then match to their declarations. WiseTech’s evening updates reported progress through those queues before the next morning’s confirmation of recovery. Forwarders then needed to check remaining cases and update customers using the returned customs statuses.
WiseTech said it would continue monitoring after reporting full recovery. Separate investigation work was still required to establish the cause, which was not identified in the available incident notices. A confirmed messaging recovery establishes that the queue was cleared; it does not establish whether a particular shipment met its planned collection or delivery time.
In June, a separate CargoWise incident disrupted logins and electronic messaging in several markets and was later attributed to a faulty data update. The October event involved delayed customs message responses and has no confirmed link to that earlier cause. The comparison illustrates how different technical failures can interrupt parts of the freight workflow, without establishing a repeated fault.
By the morning of 29 October, WiseTech said the customs messaging backlog had cleared. Freight businesses could then reconcile the affected entries, check whether approvals or release messages had returned, and complete the next transport arrangements. The incident record fixes the notification and recovery times, while the duration of each customer’s shipment disruption remains a separate operational measure.
