Frigade Outage History

Frigade is up right now

Pingoru has recorded 22 incidents for Frigade: 21 in the last 12 months and 0 in the last 90 days.

Source: status.frigade.com

22incidents recorded
21last 12 months
0last 90 days
19 minutestypical duration
Incidents per month
036AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Frigade in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 202620 of 744 (0%)
June 202660 of 720 (0%)
July 202630 of 744 (0%)
August 202660 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 107 (0%)

Incidents, newest first

Minor August 5, 2026 Frigade Users API recovered –

Started Aug 05, 2026, 08:00 PM UTC· resolved Aug 05, 2026, 08:00 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor August 5, 2026 Frigade Flows API recovered –

Started Aug 05, 2026, 07:59 PM UTC· resolved Aug 05, 2026, 07:59 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor August 5, 2026 Frigade Users API recovered 20m

Started Aug 05, 2026, 06:34 PM UTC· resolved Aug 05, 2026, 06:55 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor August 5, 2026 Frigade Dashboard API recovered 8m

Started Aug 05, 2026, 06:30 PM UTC· resolved Aug 05, 2026, 06:38 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor August 5, 2026 Frigade Users API recovered –

Started Aug 05, 2026, 05:55 PM UTC· resolved Aug 05, 2026, 05:55 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor August 5, 2026 Frigade Flows API recovered –

Started Aug 05, 2026, 05:52 PM UTC· resolved Aug 05, 2026, 05:52 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor July 24, 2026 Frigade Flows API recovered –

Started Jul 24, 2026, 11:12 AM UTC· resolved Jul 24, 2026, 11:12 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor July 24, 2026 Frigade Users API recovered –

Started Jul 24, 2026, 11:12 AM UTC· resolved Jul 24, 2026, 11:12 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor July 24, 2026 Frigade Dashboard API recovered –

Started Jul 24, 2026, 11:12 AM UTC· resolved Jul 24, 2026, 11:12 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 29, 2026 Frigade Flows API recovered –

Started Jun 29, 2026, 05:39 PM UTC· resolved Jun 29, 2026, 05:39 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 28, 2026 Frigade Flows API recovered –

Started Jun 28, 2026, 09:51 PM UTC· resolved Jun 28, 2026, 09:51 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 16, 2026 Frigade Dashboard API recovered –

Started Jun 16, 2026, 10:28 PM UTC· resolved Jun 16, 2026, 10:28 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 16, 2026 Frigade Dashboard API recovered –

Started Jun 16, 2026, 09:53 PM UTC· resolved Jun 16, 2026, 09:53 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 16, 2026 Frigade Dashboard API recovered –

Started Jun 16, 2026, 08:25 PM UTC· resolved Jun 16, 2026, 08:25 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor June 11, 2026 Frigade Dashboard API recovered –

Started Jun 11, 2026, 04:40 AM UTC· resolved Jun 11, 2026, 04:40 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 10, 2026 Frigade Dashboard API recovered –

Started May 10, 2026, 05:40 AM UTC· resolved May 10, 2026, 05:40 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 10, 2026 Frigade Dashboard API recovered –

Started May 10, 2026, 02:44 AM UTC· resolved May 10, 2026, 02:44 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 15, 2026 Frigade Flows API recovered 29m

Started Apr 15, 2026, 05:42 PM UTC· resolved Apr 15, 2026, 06:12 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor February 17, 2026 Frigade Flows API recovered –

Started Feb 17, 2026, 05:17 PM UTC· resolved Feb 17, 2026, 05:17 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor February 17, 2026 Latency issues with the Frigade Engage API 16m Current status by service (Frigade Engage) (Frigade Users API), Current status by service (Frigade Engage) (Frigade Flows API)

Started Feb 17, 2026, 04:27 PM UTC· resolved Feb 17, 2026, 04:43 PM UTC

  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. investigating Feb 17, 2026, 04:36 PM UTC

    We've identified the root cause and are rolling out a fix

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

    The fix has been deployed and all systems are operational again

Read the full incident report →

Minor February 17, 2026 Frigade Flows API recovered –

Started Feb 17, 2026, 04:09 PM UTC· resolved Feb 17, 2026, 04:09 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major December 31, 2024 SSL error 9m Current status by service (Frigade Engage) (Frigade Users API), Current status by service (Frigade Engage) (Frigade Flows API)

Started Dec 31, 2024, 12:03 AM UTC· resolved Dec 31, 2024, 12:12 AM UTC

  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.

Read the full incident report →