Frigade Outage History
Frigade is up right nowPingoru has recorded 26 incidents for Frigade: 25 in the last 12 months and 8 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 3 | 0 of 720 (0%) |
| May 2026 | 2 | 0 of 744 (0%) |
| June 2026 | 6 | 0 of 720 (0%) |
| July 2026 | 3 | 0 of 744 (0%) |
| August 2026 | 8 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 566 (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.
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.
Minor August 5, 2026 Frigade Dashboard API recovered –
Started Aug 05, 2026, 06:38 PM UTC· resolved Aug 05, 2026, 06:38 PM UTC
No vendor updates were posted for this incident.
Minor February 17, 2026 Latency issues with the Frigade Engage API 16m section-149143 (Frigade Users API), section-149143 (Frigade Flows API), section-149143 (Frigade Users API), section-149143 (Frigade Flows API)
Started Feb 17, 2026, 04:27 PM UTC· resolved Feb 17, 2026, 04:43 PM UTC
- 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.
- resolved Feb 17, 2026, 04:43 PM UTC
The fix has been deployed and all systems are operational again
Major December 31, 2024 SSL error 9m section-149143 (Frigade Users API), section-149143 (Frigade Flows API)
Started Dec 31, 2024, 12:03 AM UTC· resolved Dec 31, 2024, 12:12 AM UTC
- investigating Dec 31, 2024, 12:03 AM UTC
We've detected that api.frigade.com returns invalid SSL certificate errors.
- 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.