Previous incidents

Verified customers can now manifest cons.
MachShip will continue to monitor until EOD.

We have received confirmation that clients are now able to see routes returned.

MachShip team will continue to monitor.

Update:

The team has identified and fixed the issue. Importing consignments should no longer be duplicated moving forward.

MachShip Tech Team will be looking at removing the unmanifested duplicates.

If you see any issues, please feel free to contact us.

Update:

The carrier advised that the issue has been fixed. Clients should be able to book without issues.

MachShip will continue to monitor.

Transvirtual has confirmed this is now fixed.

Customer should now be able to proceed to manifest the consignments.

MachShip will continue to monitor throughout the day.

A package upgrade on our XML handler that happend on Friday caused our platform to not be able to extract custom unique record identifiers on XML integrations. These identifiers are used to ensure no duplicate consignments are created for each inbound file.

Handling for the upgraded package changes has been implemented, and further tests have been added to our platform to proactively note such issues in the future prior to release.

Carrier has confirmed that it has fixed the issue with their pricer and rates should now be returning within MachShip for all carrier accounts setup with API Pricing.

Clients may now try to run a consignment and manifest.

MachShip will continue to monitor throughout the day.

Incident start time

2026-01-21 11:51am ADST

Incident remediation time

2026-01-21 1:21pm ADST.

Printing application was rolled back and service was restored automatically via updates pushed to the application

Incident summary

Earlier today, we have identified an issue affecting the MachShip Printer Application following a recent release causing the application to enter a state where it was unable to connect to MachShip. During this time, printers were unable to process labels a...