Temporary Outage: 400 Bad Request from GET & Order overview, searching by reference, barcode or address details is temporarily unavailable
This incident has been resolved.
Home
/
Status
/
Service
Shipping software for seamless e-commerce delivery.
Source
auto
Category
Development
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Degraded
Checked 29m ago
39
Components
0
Active incidents
0
Maintenance
0%
90d uptime
Temporary Outage: 400 Bad Request from GET & Order overview, searching by reference, barcode or address details is temporarily unavailable
Jan 13, 11:57 AM
Normalized official status-page data for incidents, maintenance, components, and history.
0%
Known uptime
12 known history days
39
Components tracked
4 outage, 0 degraded
50
Incidents indexed
0 active right now
51
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
B2C Europe
Partial Outage
GLS
Partial Outage
TNT Express
Partial Outage
bpost
Partial Outage
Fedex
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
0
operational days
0
degraded days
4
outage days
8
maintenance days
78
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
The issue has been resolved. We thank you for your patience.
DPD BE has fixed the issue.
Last week, we deployed an endpoint migration at around 11:30 on Tuesday 13 May. On Thursday, we discovered that the migration had caused an unexpected response. As a result, PUDO shipments for DHL Express Ecommerce \(DHL For You and DHL Parcel Connect\) received an incorrect keyword identifier. The impact was that 3PLs received incorrect keyword identifiers and were unable to generate labels. Of the labels that could be generated, DHL was unable to recognise the identifier, resulting in shipments being re-routed to the recipient's home address, which caused potential delays. To resolve the situation, Paazl implemented a fix on Friday 16 May at around 15:30, additionally we updated committed orders that had not yet been shipped in the Paazl portal by overwriting the incorrect keyword identifier with the correct version.
UPS confirmed that everything should be fully operational again.
This incident has been resolved.
This incident has been resolved.
The fix of yesterday has resolved the issues. Please see the further timeline and impact below. - Timeline 18:57 Paazl monitoring picks up issue with cache cleaning mechanism resulting in partial outages 19:00 Customers begin reporting issues with labels and webapp login 19:20 IT Teams finds the issue 19:31 IT team implements fix 19:39 First customers notice improvements 19:51 IT team confirms that fix has worked for all customers 19:52 Statuspage updated to reflect fix - Technical impact The cache cleaning mechanism that we rely on throughout our platform is set to evict old cache entries whenever it’s full. In this instance it did not do so. We have identified the issue in this mechanism and fixed it. The load testing that we performed in preparation for Black Friday were volume tests, performed over a specific period of time. This kind of stress test does not replicate the cache filling of a full day of volumes. The most significant impact of this issue, related to the generation of shipping labels, and the logging into our webapp. During the affected period, we noticed a potential issue with labels that were requested. The barcodes created may not have been pre-registered at the carrier. We advise you to verify in your carrier portal whether the created barcodes are known to them. If they are not, then please consider re-labeling those packages. We remain confident in our preparation for this peak season and the steps we have taken to make it a success
This incident has been resolved.
This incident has been resolved.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Paazl status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.paazl.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 25 of 39 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Paazl | Operational | Group | 6/18/2026 |
Australia Post | Operational | Group | Not recorded |
Budbee | Operational | Group | Not recorded |
Cycloon | Operational | Group | Not recorded |
DHL | Operational | Group | Not recorded |
DPD | Operational | Group | Not recorded |
Australia Post Shipping Labels | Operational | Component | Not recorded |
Budbee Shipping Labels | Operational | Component | Not recorded |
Cycloon Shipping Labels | Operational | Component | Not recorded |
DHL Parcel Benelux | Operational | Component | Not recorded |
DPD Parcelshops | Operational | Component | Not recorded |
Paazl Checkout Widget | Operational | Component | Not recorded |
DHL Deutschland | Operational | Component | Not recorded |
DPD Shipping Labels | Operational | Component | Not recorded |
Paazl Live Webservice https://ost.paazl.com/parcelshipperservice/orderRequest.wsdl | Operational | Component | Not recorded |
B2C Europe | Partial Outage | Component | 6/22/2026 |
DHL Parcel (E-Commerce) | Operational | Component | Not recorded |
Paazl Live Web Application https://ship.paazl.com | Operational | Component | Not recorded |
DHL Express | Operational | Component | Not recorded |
Paazl Staging Webservice https://staging.paazl.com/parcelshipperservice/orderRequest.wsdl | Operational | Component | 6/18/2026 |
bpost | Partial Outage | Component | 6/15/2026 |
BRT Bartolini | Operational | Component | Not recorded |
Paazl Staging Web Application | Operational | Component | 6/18/2026 |
Paazl Push API API that pushes track & trace status updates to client servers. | Operational | Component | Not recorded |
Colissimo | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Paazl is currently marked as Degraded in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.