What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Paazl now? Check the current statusAffected services
Updates (4)
- 19-05-2025 12:54DHL Parcel PUDO keyword identifiers
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.
Paazl ↗ - 16-05-2025 22:32DHL Parcel PUDO keyword identifiers
This incident has been resolved.
Paazl ↗ - 16-05-2025 16:16DHL Parcel PUDO keyword identifiers
We have created a fix for this. All orders that were already entered in Paazl but did not yet have a generated label now have a corrected keyword identifier, and all new orders will be processed as usual.
Paazl ↗ - 15-05-2025 17:39DHL Parcel PUDO keyword identifiers
At this moment the DHL Parcel keyword identifiers for a PUDO delivery are not being processed correctly. This may affect the label generation via third-party logistics (3PL) providers. In cases where the label has already been created, affected parcels may be redirected to the recipient’s home address instead of the intended service point. Our team is actively working on a solution and will provide updates as soon as more information becomes available.
Paazl ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Paazl's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.
View all comments