All Systems Operational

Updated a few seconds ago

Quoting




Operational

Labelling




Operational

Booking




Operational

Tracking




Operational

Reporting




Operational

Webhook




Operational

Shippit Connect (Plugins & Extensions)




Operational

Shippit Web Application




Operational

Shippit Public Website




Operational

3rd Party Services




Operational

Insights




Operational

1

Upcoming Maintenances

2

Incidents Last 30 Days

3

Maintenances Last 30 Days

Scheduled Maintenance

Schedule

June 9, 2026 8:30PM - 9:00PM AEST

Components

3rd Party Services

Locations

Primary Data Center

Description

Our carrier partner Aramex will be performing a scheduled system release on Tuesday 9 June 2026. During this window (up to 30 minutes), the Aramex API will be unavailable. The outage window is: Start: 8:30pm (AEST) / 10:30pm (NZST) End: 9:00pm (AEST) / 11:00pm (NZST) Duration: Up to 30 minutes Impact to services: During this release, we do anticipate a service impact of approximately 15-20 minutes where the aramexConnect user interface and API endpoints will be unavailable. We recommend avoiding Aramex shipments during this window where possible. All other carriers will remain unaffected.

History (Last 7 days)

Incident Status

Partial Service Disruption


Components

3rd Party Services


Locations

Primary Data Center




June 4, 2026 10:07AM AEST
INVESTIGATING

We wanted to give you a heads-up that our carrier partner SEKO is currently experiencing an issue affecting label generation for UK-bound consignments. Some users may encounter errors when attempting to generate labels at this time. SEKO is actively working with their UK carrier to resolve this as quickly as possible. We'll keep you updated as soon as we have a resolution. In the meantime, if you have any urgent shipments affected, please contact your Seko account manager Or our Support team and we'll do our best to assist.

June 4, 2026 12:58PM AEST
RESOLVED

We are pleased to confirm that SEKO services have been restored. Thank you for your patience while we worked to resolve this issue.