Paazl Outage History

Paazl partial outage View live status →

Paazl had 14 outages in the last 2 years totaling 392h 53m of downtime — averaging 0.6 incidents per month.

There were 14 Paazl outages since May 28, 2024 totaling 392h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.paazl.com

Major January 13, 2026

Temporary Outage: 400 Bad Request from GET & Order overview, searching by reference, barcode or address details is temporarily unavailable

Detected by Pingoru
Jan 13, 2026, 11:57 AM UTC
Resolved
Jan 13, 2026, 02:12 PM UTC
Duration
2h 15m
Affected: Paazl Live Web ApplicationPaazl Staging Web Application
Timeline · 3 updates
  1. 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.

  2. identified Jan 13, 2026, 01:07 PM UTC

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

  3. resolved Jan 13, 2026, 02:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 3, 2025

Web app: HTTP Status 500 – Internal Server Error

Detected by Pingoru
Oct 03, 2025, 07:58 AM UTC
Resolved
Oct 06, 2025, 10:28 AM UTC
Duration
3d 2h
Affected: Paazl Live Web Application
Timeline · 2 updates
  1. 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.

  2. resolved Oct 06, 2025, 10:28 AM UTC

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

Read the full incident report →

Notice June 24, 2025

DPD BE downtime

Detected by Pingoru
Jun 24, 2025, 08:02 AM UTC
Resolved
Jun 24, 2025, 11:27 AM UTC
Duration
3h 25m
Affected: DPD ParcelshopsDPD Shipping Labels
Timeline · 2 updates
  1. identified Jun 24, 2025, 08:02 AM UTC

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

  2. resolved Jun 24, 2025, 11:27 AM UTC

    DPD BE has fixed the issue.

Read the full incident report →

Minor May 15, 2025

DHL Parcel PUDO keyword identifiers

Detected by Pingoru
May 15, 2025, 03:39 PM UTC
Resolved
May 16, 2025, 08:32 PM UTC
Duration
1d 4h
Affected: DHL Parcel (E-Commerce)
Timeline · 4 updates
  1. 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.

  2. 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.

  3. resolved May 16, 2025, 08:32 PM UTC

    This incident has been resolved.

  4. 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.

Read the full incident report →

Major February 21, 2025

UPS: service not responding

Detected by Pingoru
Feb 21, 2025, 09:30 AM UTC
Resolved
Feb 21, 2025, 09:56 AM UTC
Duration
25m
Affected: UPS
Timeline · 2 updates
  1. 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.

  2. resolved Feb 21, 2025, 09:56 AM UTC

    UPS confirmed that everything should be fully operational again.

Read the full incident report →

Notice December 12, 2024

Degraded performance in checkouts

Detected by Pingoru
Dec 12, 2024, 05:32 PM UTC
Resolved
Dec 13, 2024, 08:33 AM UTC
Duration
15h
Affected: Paazl Checkout WidgetPaazl Live Webservice
Timeline · 4 updates
  1. 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.

  2. identified Dec 12, 2024, 05:32 PM UTC

    The issue has been identified and repairs are ongoing.

  3. monitoring Dec 12, 2024, 06:43 PM UTC

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

  4. resolved Dec 13, 2024, 08:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 28, 2024

Paazl Web Application

Detected by Pingoru
Nov 28, 2024, 11:30 AM UTC
Resolved
Nov 28, 2024, 05:56 PM UTC
Duration
6h 25m
Affected: Paazl Checkout WidgetPaazl Live WebservicePaazl Live Web Application
Timeline · 2 updates
  1. 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

  2. resolved Nov 28, 2024, 05:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 4, 2024

GLS API is unresponsive

Detected by Pingoru
Oct 04, 2024, 11:40 AM UTC
Resolved
Oct 04, 2024, 02:00 PM UTC
Duration
2h 20m
Affected: GLS
Timeline · 2 updates
  1. investigating Oct 04, 2024, 11:40 AM UTC

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

  2. resolved Oct 04, 2024, 02:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 25, 2024

DPD webservice timeout

Detected by Pingoru
Jul 25, 2024, 09:14 AM UTC
Resolved
Jul 26, 2024, 06:48 AM UTC
Duration
21h 34m
Affected: DPD ParcelshopsDPD Shipping Labels
Timeline · 2 updates
  1. identified Jul 25, 2024, 09:14 AM UTC

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

  2. resolved Jul 26, 2024, 06:48 AM UTC

    DPD has resolved the issue

Read the full incident report →

Major July 22, 2024

DPD Parcelshops not being retrieved.

Detected by Pingoru
Jul 22, 2024, 12:46 PM UTC
Resolved
Jul 23, 2024, 09:22 AM UTC
Duration
20h 35m
Affected: DPD Parcelshops
Timeline · 4 updates
  1. investigating Jul 22, 2024, 12:46 PM UTC

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

  2. identified Jul 22, 2024, 02:06 PM UTC

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

  3. monitoring Jul 22, 2024, 02:38 PM UTC

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

  4. resolved Jul 23, 2024, 09:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 28, 2024

Colissimo Servicepoints unavailable

Detected by Pingoru
May 28, 2024, 07:25 AM UTC
Resolved
May 31, 2024, 03:08 PM UTC
Duration
3d 7h
Affected: Colissimo
Timeline · 2 updates
  1. identified May 28, 2024, 07:25 AM UTC

    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.

  2. resolved May 31, 2024, 03:08 PM UTC

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

Read the full incident report →