Returnflows incident

DAO Elevated Error Rate

Minor Resolved View vendor source →

Returnflows experienced a minor incident on August 31, 2026 affecting DAO, lasting —. The incident has been resolved; the full update timeline is below.

Started
Aug 31, 2026, 08:00 PM UTC
Resolved
Aug 31, 2026, 08:00 PM UTC
Duration
Detected by Pingoru
Aug 31, 2026, 08:00 PM UTC

Affected components

DAO

Update timeline

  1. investigating Aug 31, 2026, 01:54 PM UTC

    Status: Investigating We are currently experiencing issues with DAO's services. This may cause delays or errors when creating shipments, generating labels, and updating tracking information in Returnflows. We are in contact with DAO and are working to clarify the extent of the problems. We are continuously monitoring the situation and will share further updates as soon as we have more information. We apologize for any inconvenience this may cause and thank you for your patience. Affected components DAO (Degraded performance)

  2. monitoring Aug 31, 2026, 02:42 PM UTC

    Status: Monitoring Labels are being generated successfully again. We're continuing to monitor closely, and will regenerate any labels that failed during the disruption. Thanks for your patience, more updates to follow if needed. Affected components DAO (Degraded performance)

  3. identified Aug 31, 2026, 03:16 PM UTC

    Status: Identified We are continuing to see high error rates, only some labels were successfully generated in the short timeframe. All labels will regenerate and resend all customer labels once the service is fully operational again. Affected components DAO (Degraded performance)

  4. monitoring Aug 31, 2026, 07:53 PM UTC

    Status: Monitoring Labels are being generated successfully again. We're continuing to monitor closely, and will regenerate any labels that failed during the disruption. Thanks for your patience, more updates to follow if needed. Affected components DAO (Operational)

  5. resolved Aug 31, 2026, 08:00 PM UTC

    Status: Resolved We're seeing label generation working with error rates as usually. The queue of failed generations during downtime have been reprocessed without any issues as well. This incident is hereby closed! Affected components DAO (Operational)