Frigade incident

SSL error

Major Resolved View vendor source →

Frigade experienced a major incident on December 31, 2024 affecting Current status by service (Frigade Engage) (Frigade Users API) and Current status by service (Frigade Engage) (Frigade Flows API), lasting 9m. The incident has been resolved; the full update timeline is below.

Started
Dec 31, 2024, 12:03 AM UTC
Resolved
Dec 31, 2024, 12:12 AM UTC
Duration
9m
Detected by Pingoru
Dec 31, 2024, 12:03 AM 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 Dec 31, 2024, 12:03 AM UTC

    We've detected that api.frigade.com returns invalid SSL certificate errors.

  2. resolved Dec 31, 2024, 12:12 AM UTC

    The incident is now resolved. The root cause was due to a change in the SSL-version by a third party provider. We've since pinned the SSL version such that this cannot occur in the future.