Dutchie incident

Degraded Performance of Reporting and Public API

Minor Resolved View vendor source →

Dutchie experienced a minor incident on March 3, 2026 affecting Reporting and Dutchie POS API, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 03, 2026, 01:18 AM UTC
Resolved
Mar 03, 2026, 01:18 AM UTC
Duration
Detected by Pingoru
Mar 03, 2026, 01:18 AM UTC

Affected components

ReportingDutchie POS API

Update timeline

  1. investigating Mar 03, 2026, 12:35 AM UTC

    Status: Investigating We are currently investigating an issue affecting reporting features within the POS Backoffice. Customers may experience errors or timeouts when attempting to run reports or access analytics. Our team is engaged and working with our upstream infrastructure provider toward a resolution. Affected components Dutchie POS API (Degraded performance) Reporting (Degraded performance)

  2. identified Mar 03, 2026, 12:51 AM UTC

    Status: Identified Reporting and Public API services have returned to normal operation. We are continuing to work with our infrastructure provider to resolve the remaining impact on BI Tools (Looker/Analytics). Customers may still experience errors or timeouts specifically when attempting to access these advanced reporting features. Affected components Dutchie POS API (Operational) Reporting (Degraded performance)

  3. resolved Mar 03, 2026, 01:18 AM UTC

    Status: Resolved Reporting, BI Tools (Looker/Analytics) and Public API services have returned to normal operation. Affected components Dutchie POS API (Operational) Reporting (Operational)