Is there an Frontegg outage?
Frontegg status: Systems Active
Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for Frontegg and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for Frontegg and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Frontegg.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Audit logs | Active |
| Entitlements | Active |
| Machine to machine authentication | Active |
| Management portal | Active |
| Reporting | Active |
| SSO & SAML authentication | Active |
| User authentication | Active |
| Webhooks infrastucture | Active |
View the latest incidents for Frontegg and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 6, 2023, 5:42 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 6, 2023, 5:42 p.m.
Description: ### **Executive summary:** On Wednesday May 31st, 2023, at 12:55 GMT we deployed a minor version to one of our services. Shortly after at 12:56 GMT, Frontegg’s US monitoring system started sending alerts for an authentication service which was not performing as expected, and the team immediately began investigating the issue. At 13:01 GMT we started getting alerts from Frontegg’s EU monitoring as well regarding the same service, shortly after, we started to get complaints from customers. At 13:04 GMT, 8 min after we started getting the alerts the team concluded that it was sourced by a recent change that was deployed. As part of the change, there was a database migration for one of our primary services. However, the migration job didn't run due to an edge race condition in our CD infrastructure, causing the service to remain in a schema mismatch state. At this point we immediately started a rollback process for both EU & US regions that was completed by 13:16 GMT. Once the rollback completed, we noticed that our services are working as expected again and customers also reported that they were no longer experiencing issues. **Affect:** Most requests to customers’ custom Frontegg domains resulted in 401/404 responses or inability to authenticate. For the EU region - between 12:59 to 13:16 GMT time.For the US region - between 12:56 to 13:14 GMT time ### **Mitigation and resolution:** Following the monitoring alerts the incident response team immediately identified the potential corrupted service and started rollback procedure with the previous successful deployment. ### **Preventive steps:** * We defined a gated process for deploying DB migration changes * A schema validation on service init to prevent schema mismatch cases was added * Will add deployment validation that will fail deployment if migration didn’t run * Will remove the high dependency in that specific service as a single-point-of-failure for the main system flows * Reduce service rollback time by running only relevant part of the CD pipeline
Status: Postmortem
Impact: Major | Started At: May 31, 2023, 1:08 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: May 31, 2023, 6:29 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: May 31, 2023, 6:29 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
