Company Logo

Is there an Frontegg outage?

Frontegg status: Systems Active

Last checked: a minute ago

Get notified about any outages, downtime or incidents for Frontegg and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Frontegg outages and incidents

Outage and incident data over the last 30 days for Frontegg.

There have been 0 outages or incidents for Frontegg in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

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 Now

Components and Services Monitored for Frontegg

Outlogger tracks the status of these components for Xero:

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
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

Latest Frontegg outages and incidents.

View the latest incidents for Frontegg and check for official updates:

Updates:

  • Time: Aug. 6, 2024, 6:16 p.m.
    Status: Resolved
    Update: The incident is resolved. Email should be sent now.
  • Time: Aug. 6, 2024, 5:50 p.m.
    Status: Investigating
    Update: We are working with our email provider on a solution at the moment
  • Time: Aug. 6, 2024, 4:43 p.m.
    Status: Investigating
    Update: Some emails are not getting sent. For example Magic code and Magic link emails. We are investigating with our email provider

Updates:

  • Time: July 30, 2024, 9:16 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: July 30, 2024, 2:26 p.m.
    Status: Monitoring
    Update: We are monitoring the issue and in contact with Azure
  • Time: July 30, 2024, 1:38 p.m.
    Status: Investigating
    Update: We are receiving reports on sporadic issues to loading the hosted login page for some users - it does not appear to be widely affecting usage, the team is currently investigating. The issue appears to be due to an Azure incident affecting our CDN service.

Updates:

  • Time: July 24, 2024, 10:57 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: July 24, 2024, 10:37 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: July 24, 2024, 9:40 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: July 24, 2024, 9:20 a.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: July 24, 2024, 9:14 a.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: July 24, 2024, 10:57 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: July 24, 2024, 10:37 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: July 24, 2024, 9:40 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: July 24, 2024, 9:20 a.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: July 24, 2024, 9:14 a.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Updates:

  • Time: July 26, 2024, 2 p.m.
    Status: Postmortem
    Update: # **Root Cause Analysis \(RCA\) Report** **Date and Time**: July 24, 2024**Duration**: 22 minutes **Affected Services**: Authentication and core services**Impact**: Customers in the EU region were hanging and returned as 504 timeouts**Reported By**: Internal monitoring systems and customers \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ **Executive summary:** On Wednesday, July 24th, at 08:43 GMT, Frontegg's internal monitoring systems indicated that the API Gateway encountered an issue following the deployment of a new OpenTelemetry propagator \(OTEL instrumentation\), causing service disruptions in the EU. As a result, some of our customers were experiencing timeout errors \(HTTP status 504\) returned by Frontegg. During the upgrade of our API Gateway, Frontegg also updated the OpenTelemetry library. This update inadvertently caused the system to send data one piece at a time instead of using efficient batches due to a misconfiguration in the data handling settings. OTEL transmitted millions of traces individually rather than in aggregated batches. Although our system was rigorously tested under various conditions, the high load in the EU environment caused our auto-scaling mechanism to lag behind the incoming traffic. This led to the API gateway being overwhelmed by the volume of client requests. ‌ **Cause Analysis:** The primary cause of the incident was the deployment of a new OTEL instrumentation in the API Gateway, which led to a significant increase in trace data volume. Contributing factors included: * The API Gateway's OTEL was configured with the BasicPropagator instead of a BatchPropogator, sending each trace as part of the flow. * The fast rise of HTTP requests to the OTEL collector overloaded the API gateway to handle incoming requests. Although it was autoscaled, it lacked in response to the number of requests. * With the increase of traces being sent, the OTEL Collector failed to handle millions of traces at such a rate, increasing the request handling time, which caused another increase in API-gateway HTTP requests ‌ **Customer Impact** During the incident, customers in the European region experienced significant service degradation. Specific issues included failures in hosted login monitors and general service instability. ‌ **Mitigation and resolution:** Upon receiving the initial alerts, the Frontegg team began investigating the issue promptly. After identifying the problem with the OTEL propagator and collector, we increased the allocated resources and reverted to the latest working version. Following the implementation of this change, the systems returned to normal operations. **Mitigation**: * Increased the CPU allocation for the OTEL Gateway to handle the increased workload. * Revert to the latest Api-gateway version. **Resolution**: * Restarted the API Gateway to clear hanging requests and stabilize the OTEL Gateway. * Deployed a new version of the API gateway with the correct configuration ‌ **Prevention and Future steps:** Enhance OTEL Propagator: Implement batch processing, asynchronous handling, and strict timeouts. * **Upgrade OTEL Gateway**: Allocate additional resources to the OTEL Gateway and implement autoscaling to handle increased workloads effectively. * **Implement Aggressive Timeouts**: Implement stringent timeout policies for all HTTP requests that are not customer-related. This measure will proactively prevent delays and mitigate the risk of unresponsive requests. * Stress tests: change the deployment pipeline to include stress testing instead of the nightly testing suite. ‌ **Communication:** **Enhance Status Page Communication**: Ensure the status page provides clear and timely updates during incidents. Develop and maintain standardized templates for incident communication to facilitate prompt and consistent information, even if the root cause is not immediately identified.
  • Time: July 24, 2024, 10:58 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: July 24, 2024, 10:37 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: July 24, 2024, 9:47 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: July 24, 2024, 9:47 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: July 24, 2024, 9:13 a.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: July 24, 2024, 9:13 a.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: July 24, 2024, 9:06 a.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: July 24, 2024, 9:06 a.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: July 24, 2024, 8:51 a.m.
    Status: Investigating
    Update: We are currently investigating this issue.
  • Time: July 24, 2024, 8:51 a.m.
    Status: Investigating
    Update: We are currently investigating this issue.

Check the status of similar companies and alternatives to Frontegg

NetSuite
NetSuite

Systems Active

ZoomInfo
ZoomInfo

Systems Active

SPS Commerce
SPS Commerce

Systems Active

Miro
Miro

Systems Active

Field Nation
Field Nation

Systems Active

Outreach
Outreach

Systems Active

Own Company

Systems Active

Mindbody
Mindbody

Systems Active

TaskRabbit
TaskRabbit

Systems Active

Nextiva
Nextiva

Systems Active

6Sense

Systems Active

BigCommerce
BigCommerce

Systems Active

Frequently Asked Questions - Frontegg

Is there a Frontegg outage?
The current status of Frontegg is: Systems Active
Where can I find the official status page of Frontegg?
The official status page for Frontegg is here
How can I get notified if Frontegg is down or experiencing an outage?
To get notified of any status changes to Frontegg, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Frontegg every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Frontegg do?
Frontegg is a user management platform for B2B SaaS, supporting PLG to enterprise strategies. It offers easy migration and no credit card requirement.