Paazl Outage History
Paazl partial outage View live status →Pingoru has recorded 50 incidents for Paazl: 1 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 515 (0%) |
Incidents, newest first
Major January 13, 2026 Temporary Outage: 400 Bad Request from GET & Order overview, searching by reference, barcode or address details is temporarily unavailable 2h 15m Paazl Live Web Application, Paazl Staging Web Application
Started Jan 13, 2026, 11:57 AM UTC· resolved Jan 13, 2026, 02:12 PM UTC
- investigating Jan 13, 2026, 11:57 AM UTC
Some customers are currently receiving an "400 Bad Request from GET" within their response and/or seeing within the Paazl web app the message "Order overview, searching by reference, barcode or address details is temporarily unavailable". We are currently investigating the root cause and will provide an update as soon as possible.
- identified Jan 13, 2026, 01:07 PM UTC
The issue has been identified and we are working on a solution.
- resolved Jan 13, 2026, 02:12 PM UTC
This incident has been resolved.
Minor October 3, 2025 Web app: HTTP Status 500 – Internal Server Error 3d 2h Paazl Live Web Application
Started Oct 03, 2025, 07:58 AM UTC· resolved Oct 06, 2025, 10:28 AM UTC
- identified Oct 03, 2025, 07:58 AM UTC
For some carriers, it is currently not possible to create a new shipment or edit an existing shipment within the Paazl web app. This results in a page showing a HTTP Status 500 – Internal Server Error. We are aware of this situation and are actively working on a it. As a temporary workaround, we recommend using the API calls, which are not affected by this.
- resolved Oct 06, 2025, 10:28 AM UTC
The issue has been resolved. We thank you for your patience.
Notice June 24, 2025 DPD BE downtime 3h 25m DPD Parcelshops, DPD Shipping Labels
Started Jun 24, 2025, 08:02 AM UTC· resolved Jun 24, 2025, 11:27 AM UTC
- identified Jun 24, 2025, 08:02 AM UTC
DPD Belgium is currently experiencing downtime. We are awaiting their resolve.
- resolved Jun 24, 2025, 11:27 AM UTC
DPD BE has fixed the issue.
Minor May 15, 2025 DHL Parcel PUDO keyword identifiers 1d 4h DHL Parcel (E-Commerce)
Started May 15, 2025, 03:39 PM UTC· resolved May 16, 2025, 08:32 PM UTC
- identified May 15, 2025, 03:39 PM UTC
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.
- monitoring May 16, 2025, 02:16 PM UTC
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.
- resolved May 16, 2025, 08:32 PM UTC
This incident has been resolved.
- postmortem May 19, 2025, 10:54 AM UTC
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.
Major February 21, 2025 UPS: service not responding 25m UPS
Started Feb 21, 2025, 09:30 AM UTC· resolved Feb 21, 2025, 09:56 AM UTC
- investigating Feb 21, 2025, 09:30 AM UTC
We are noticing that the UPS web service is not responding properly. This may affect the printing of UPS labels. Example of an error code: "[server_error]" UPS is aware of the situation and is working on a solution.
- resolved Feb 21, 2025, 09:56 AM UTC
UPS confirmed that everything should be fully operational again.
Notice December 12, 2024 Degraded performance in checkouts 16h 51m Paazl Checkout Widget, Paazl Live Webservice
Started Dec 12, 2024, 03:41 PM UTC· resolved Dec 13, 2024, 08:33 AM UTC
- investigating Dec 12, 2024, 03:41 PM UTC
We are seeing higher error-rates in our monitoring which is affecting our response times. We are currently investigating this issue.
- identified Dec 12, 2024, 05:32 PM UTC
The issue has been identified and repairs are ongoing.
- monitoring Dec 12, 2024, 06:43 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 13, 2024, 08:33 AM UTC
This incident has been resolved.
Notice November 28, 2024 Paazl Web Application 6h 25m Paazl Checkout Widget, Paazl Live Webservice, Paazl Live Web Application
Started Nov 28, 2024, 11:30 AM UTC· resolved Nov 28, 2024, 05:56 PM UTC
- monitoring Nov 28, 2024, 11:30 AM UTC
We have noticed that the response of our Web Application, Checkout Widget, and API had degraded performance. We have immediately identified and rolled out a fix. Our performance is back to normal at this moment. We are investigation the issue further and will come back with more information as soon as possible
- resolved Nov 28, 2024, 05:56 PM UTC
This incident has been resolved.
Minor November 25, 2024 Paazl Web Application: slow response 19h 1m Paazl Live Webservice, Paazl Live Web Application
Started Nov 25, 2024, 06:35 PM UTC· resolved Nov 26, 2024, 01:37 PM UTC
- identified Nov 25, 2024, 06:35 PM UTC
We are noticing issues with our Web Application. We have identified the issue and are performing corrections.
- monitoring Nov 25, 2024, 06:53 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Nov 25, 2024, 07:42 PM UTC
We have noticed a potential issue with labels that were requested during the time period of this issue. The barcode may not have been pre-registered at the carrier. Please verify in your carrier portal whether the barcodes are known to them. If they are not, then please consider relabeling the packages.
- resolved Nov 26, 2024, 01:37 PM UTC
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