← Live dashboard

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

ResolvedmajorOfficial source confirmedSpecific component onlySource start 13-01-2026 12:57 · Resolved 13-01-2026 15:12

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.

Paazl live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

View all comments
    Having problems with Paazl now? Check the current status

    Affected services

    Paazl Staging Web ApplicationPaazl Live Web Application

    Updates (3)

    1. 13-01-2026 15:12
      Temporary Outage: 400 Bad Request from GET & Order overview, searching by reference, barcode or address details is temporarily unavailable

      This incident has been resolved.

      Paazl ↗
    2. 13-01-2026 14:07
      Temporary Outage: 400 Bad Request from GET & Order overview, searching by reference, barcode or address details is temporarily unavailable

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

      Paazl ↗
    3. 13-01-2026 12:57
      Temporary Outage: 400 Bad Request from GET & Order overview, searching by reference, barcode or address details is temporarily unavailable

      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.

      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.