История сбоев Paazl

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.

The issue has been identified and we are working on a solution.

This incident has been resolved.

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.

The issue has been resolved. We thank you for your patience.

DPD Belgium is currently experiencing downtime. We are awaiting their resolve.

DPD BE has fixed the issue.

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.

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.

This incident has been resolved.

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.

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.

UPS confirmed that everything should be fully operational again.

We are seeing higher error-rates in our monitoring which is affecting our response times. We are currently investigating this issue.

The issue has been identified and repairs are ongoing.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

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

This incident has been resolved.

We are noticing issues with our Web Application. We have identified the issue and are performing corrections.

A fix has been implemented and we are monitoring the results.

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.

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

All connections to GLS are currently not operational. We are awaiting an update from GLS.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

DPD is currently experiencing an issue which makes their services unavailable. The issue is on their side so we are awaiting updates.

DPD has resolved the issue

We are currently not getting results when trying to fetch DPD Parcelshops locations. We are investigating the issue and will update the statuspage accordingly.

We have found the cause of this issue and are implementing a fix.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Paazl is currently experiencing an issue with generating labels. We're looking into it and will post updates as soon as we have more information.

We have identified the issue and rolled a fix.

The issue has not been completely resolved in every instance. We're currently looking into it again.

The problem has been identified and we're currently initiating a rollback.

We performed a rollback and are currently monitoring the performance.

This incident has been resolved.

Yesterday we experienced degraded performance due to two different issues. First, A server upgrade ended up in us losing a previously configured time zone, which was essential for some of our platform functionality. This caused issues with printing labels. This was solved within the hour. This fixed the label issues for most customers. Setting our status page to monitoring. During the monitoring phase, a second issue was reported by a few customers around 13:15. The SOAP generateLabel response was changed to have a namespace prefix ns2:. The introduction of this non-blank namespace prefix in our SOAP responses caused issues with some integrations using XML parsers not equipped to deal with namespace prefixes. This was fixed with a rollback around 15:30.‌ Unfortunately, this is an issue undetectable by heavy testing, as this is coming from OMS/WMS specific settings. We are currently working on a fix to suppress the namespace and intent to roll out this release today during the afternoon. However, to avoid similar issues we also heavily advise our customers to update their parsing mechanism for scalability.

We have noticed an issue with retrieving available servicepoints, and we are following up with the carrier for further support. In case there is more information known, we will update this notice.

The issue has been resolved, the Colissimo locator is operational again.

We have noticed that an issue with the connection between some of our servers. We have contacted our provider and are looking into the issue. This impacts the performance of our email notification, order overview and some of our pre-registration towards carriers.

The issue has been resolved around 15:35. There was a temporary impact on the order overview which caused orders not to be shown properly. The orders were known to our software and pre-registrations were send properly. We will be monitoring this situation.

This incident has been resolved.

We are currently experiencing issues with PostNL's SFTP server, and have reached out to the carrier for further support. At the moment, no preregistration files or status data are processed for our self-built shipping options. We will update this alert if more information is available on this matter.

This incident has been resolved.

Due to an outage at DPD, DPD META API is currently unavailable. We are reaching out to DPD for further support. As soon as the DPD web service is operational again, we will update this alert.

This incident has been resolved.

We have noticed that services from Mondial Relay are currently unavailable. We are following up with the carrier in order to solve this issue as soon as possible.

This incident has been resolved.

We have noticed that services from Budbee are delayed and time outs are experienced. We are following up with the carrier in order to solve this issue as soon as possible.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We have noticed that services from TNT Express are unreachable at the moment. We are following up with the carrier in order to solve this issue as soon as possible.

This incident has been resolved.