Previous incidents
TNT Manifest Issue
Resolved Jul 23, 2025 at 4:07am UTC
Update:
TNT advised that the issue is now fixed on their end and is back up and running.
Clients may now be able to book/manifest their cons with TNT.
MachShip will continue to monitor for the rest of the day.
2 previous updates
Centurion - Unable to Manifest Consignments
Resolved Jul 15, 2025 at 1:58am UTC
Update:
Centurion has advised that the issue is now fixed on their end and is back up and running.
Clients may now be able to book/manifest their cons with Centurion.
MachShip will continue to monitor for the rest of the day.
1 previous update
MachShip System issues - 15/7/2025
Resolved Jul 14, 2025 at 10:22pm UTC
System stability and functionality will now have been returned
If further issues are found please contact support@machship.com
2 previous updates
Australia Post International Booking Issues
Resolved Jul 11, 2025 at 5:41am UTC
Resolved:
This is now fixed, and customers should be able to create international shipments.
The carrier is experiencing technical issues with international shipment creation.
They advised that they are working to resolve this problem and MachShip will continue to monitor and advise any updates once available.
Freight Specialist Manifesting errors
Resolved Jul 3, 2025 at 4:00am UTC
The carrier has corrected things on their side and this is back up and running
1 previous update
Northline Manifest Issue
Resolved Jul 1, 2025 at 4:33am UTC
Northline is now back up and running.
Clients should be able to proceed with manifesting cons with the carrier.
2 previous updates
TNT Manifest Issue
Resolved May 22, 2025 at 2:18am UTC
Update:
TNT have advised that the issue is now fixed on their end and is now back up and running.
Clients may now be able to book/manifest their cons with TNT.
MachShip will continue to monitor for the rest of the day.
7 previous updates
TNT Manifest Issue
Resolved May 8, 2025 at 12:36am UTC
This incident has been resolved.
4 previous updates
TNT Manifest Issue
Resolved May 8, 2025 at 12:36am UTC
This incident has been resolved.
4 previous updates