Frigade incident

Latency issues with the Fri...

Minor Resolved View vendor source →

Frigade experienced a minor incident on February 17, 2026 affecting Current status by service (Frigade Engage) (Frigade Users API) and Current status by service (Frigade Engage) (Frigade Flows API), lasting 16m. The incident has been resolved; the full update timeline is below.

Started
Feb 17, 2026, 04:27 PM UTC
Resolved
Feb 17, 2026, 04:43 PM UTC
Duration
16m
Detected by Pingoru
Feb 17, 2026, 04:27 PM UTC

Affected components

Current status by service (Frigade Engage) (Frigade Users API)Current status by service (Frigade Engage) (Frigade Flows API)

Update timeline

  1. investigating Feb 17, 2026, 04:27 PM UTC

    Frigade Engage is experiencing increased latency on select API endpoints. Affected requests are taking longer than expected to complete, potentially impacting user-facing onboarding flows and in-app engagement features.

  2. resolved Feb 17, 2026, 04:43 PM UTC

    The fix has been deployed and all systems are operational again