Duffel incident

Unusual high amount of 422 responses from Stays fetch rates endpoint

Minor Resolved View vendor source →
Started
Apr 10, 2026, 04:32 PM UTC
Resolved
Apr 10, 2026, 04:32 PM UTC
Duration
—
Detected by Pingoru
Apr 10, 2026, 04:32 PM UTC

Update timeline

  1. monitoring Apr 10, 2026, 04:25 PM UTC

    Status: Monitoring We’ve had a short period of our fetch rates endpoint responding with 422s (signal to retry) as a result of being unable to reach our suppliers due to an issue. This occurred around 15:50 to 16:10 UTC and has since settled down. We’re monitoring it and expecting it to be stable throughout.

  2. resolved Apr 10, 2026, 04:32 PM UTC

    Status: Resolved The endpoint has been confirmed to be within SLA and is proceeding as normal.

Looking to track Duffel downtime and outages?

Pingoru polls Duffel's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Duffel reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Duffel alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Duffel for free

5 free monitors · No credit card required