Skip to content

Outage tracker / Frontegg

Is Frontegg down?

I'm having a problem

Operationalchecked 2 minutes ago

We reached Frontegg from all 10 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Frontegg (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East280 msOperational
US-West621 msOperational
Europe157 msOperational
Asia-Pacific1035 msOperational
US-Central245 msOperational
Canada502 msOperational
UK275 msOperational
Southeast Asia1099 msOperational
Australia1987 msOperational
South America1146 msOperational
their status pagetheir claim, not our reading

Frontegg reports: All systems operational (“All Systems Operational”)

from Frontegg's own status page, checked Sep 5, 2026, 1:46 AM UTC
Our probes and Frontegg's own status page agree: both show Frontegg as reachable right now.

Frontegg's own component breakdown, as they publish it

  • Authentication APIsOperational
  • Authentication APIsOperational
  • Authentication APIsOperational
  • Authentication APIsOperational
  • Authentication APIsOperational
  • Management APIsOperational
  • Management APIsOperational
  • Management APIsOperational
  • Management APIsOperational
  • Management APIsOperational
  • Management PortalOperational
  • Management PortalOperational
  • Management PortalOperational
  • Management PortalOperational
  • Management PortalOperational

These are Frontegg's components, named and scored by Frontegg. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Frontegg's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Frontegg response time, by region

US-East
440msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 818ms2026-08-23 UTC: p95 958ms2026-08-24 UTC: p95 732ms2026-08-25 UTC: p95 637ms2026-08-26 UTC: p95 562ms2026-08-27 UTC: p95 620ms2026-08-28 UTC: p95 611ms2026-08-29 UTC: p95 620ms2026-08-30 UTC: p95 567ms2026-08-31 UTC: p95 696ms2026-09-01 UTC: p95 848ms2026-09-02 UTC: p95 645ms2026-09-03 UTC: p95 676ms2026-09-04 UTC: p95 553ms2026-09-05 UTC: p95 440ms
Aug 7Aug 21Sep 5
US-West
926msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 338ms2026-08-23 UTC: p95 862ms2026-08-24 UTC: p95 804ms2026-08-25 UTC: p95 837ms2026-08-26 UTC: p95 771ms2026-08-27 UTC: p95 706ms2026-08-28 UTC: p95 791ms2026-08-29 UTC: p95 782ms2026-08-30 UTC: p95 846ms2026-08-31 UTC: p95 887ms2026-09-01 UTC: p95 796ms2026-09-02 UTC: p95 829ms2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 926ms
Aug 7Aug 21Sep 5
Europe
276msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 305ms2026-08-23 UTC: p95 445ms2026-08-24 UTC: p95 629ms2026-08-25 UTC: p95 407ms2026-08-26 UTC: p95 381ms2026-08-27 UTC: p95 375ms2026-08-28 UTC: p95 366ms2026-08-29 UTC: p95 198ms2026-08-30 UTC: p95 180ms2026-08-31 UTC: p95 313ms2026-09-01 UTC: p95 343ms2026-09-02 UTC: p95 211ms2026-09-03 UTC: p95 522ms2026-09-04 UTC: p95 464ms2026-09-05 UTC: p95 276ms
Aug 7Aug 21Sep 5
Asia-Pacific
1.3sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.1s2026-08-23 UTC: p95 1.5s2026-08-24 UTC: p95 1.4s2026-08-25 UTC: p95 1.7s2026-08-26 UTC: p95 1.6s2026-08-27 UTC: p95 1.4s2026-08-28 UTC: p95 1.6s2026-08-29 UTC: p95 1.4s2026-08-30 UTC: p95 1.4s2026-08-31 UTC: p95 1.4s2026-09-01 UTC: p95 1.7s2026-09-02 UTC: p95 1.6s2026-09-03 UTC: p95 1.8s2026-09-04 UTC: p95 1.5s2026-09-05 UTC: p95 1.3s
Aug 7Aug 21Sep 5
US-Central
650msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 751ms2026-09-04 UTC: p95 749ms2026-09-05 UTC: p95 650ms
Aug 7Aug 21Sep 5
Canada
699msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 777ms2026-09-04 UTC: p95 737ms2026-09-05 UTC: p95 699ms
Aug 7Aug 21Sep 5
UK
264msp95 · latest
500ms250ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 500ms. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 354ms2026-09-04 UTC: p95 307ms2026-09-05 UTC: p95 264ms
Aug 7Aug 21Sep 5
Southeast Asia
1.1sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.8s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 1.1s
Aug 7Aug 21Sep 5
Australia
2.0sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.8s2026-09-04 UTC: p95 2.2s2026-09-05 UTC: p95 2.0s
Aug 7Aug 21Sep 5
South America
1.1sp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 1.1s
Aug 7Aug 21Sep 5

Is it Frontegg, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Frontegg -- it cannot diagnose Frontegg's own systems.

What we measured, function by function

Frontegg answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the auth row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • AuthprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 280msstatus code: 401checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Frontegg normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 621msstatus code: 401checked: Sep 5, 2026, 2:06 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Frontegg normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 245msstatus code: 401checked: Sep 5, 2026, 2:01 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Frontegg normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 502msstatus code: 401checked: Sep 5, 2026, 2:02 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Frontegg normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Operationallatency: 1146msstatus code: 401checked: Sep 5, 2026, 2:00 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Frontegg normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 157msstatus code: 401checked: Sep 5, 2026, 2:00 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Frontegg normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 275msstatus code: 401checked: Sep 5, 2026, 2:04 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Frontegg normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 1035msstatus code: 401checked: Sep 5, 2026, 1:54 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Frontegg normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1099msstatus code: 401checked: Sep 5, 2026, 1:58 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Frontegg normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Operationallatency: 1987msstatus code: 401checked: Sep 5, 2026, 2:03 AM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Frontegg normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Frontegg, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Frontegg yet, which is not evidence that nothing is wrong.

Recent outages

Degraded Performance - EU region, 1h 28mdeclared on their status page2026-08-20
Service Outage, 5h 36mdeclared on their status page2026-07-16
Degraded Performance in US Region – Planned Data Layer Upgrade, 1mdeclared on their status page2026-06-07
Degraded performance in US region - Partial Entitlements functionalities, 1h 51mdeclared on their status page2026-03-23
Degraded performance inEU region, 1h 29mdeclared on their status page2025-12-08
Degraded performance Authentication API EU Region, 1mdeclared on their status page2025-12-03
Elevated errors reported due to global incident with our WAF provider Cloudflare, 1h 40mdeclared on their status page2025-11-18
Degraded performance with loading login box, 34mdeclared on their status page2025-10-29

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Frontegg since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Frontegg covering any window you pick, with our measurements and Frontegg's own claim at the time, side by side.

Full availability history for Frontegg: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Frontegg, and again when they can reach it again. That is our own measurement from ten regions, not Frontegg's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Frontegg uptime measured by RealUptimeLive, from this page's own readings.
[![Frontegg uptime measured by RealUptime](https://realuptime.io/outages/frontegg/badge.svg?days=30)](https://realuptime.io/outages/frontegg)
<a href="https://realuptime.io/outages/frontegg"><img src="https://realuptime.io/outages/frontegg/badge.svg?days=30" alt="Frontegg uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Frontegg's SLA implies, from our measurement

At or above your target

We measured none of downtime for Frontegg over the 338h 8m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Frontegg's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: auth surface
https://api.frontegg.com/identity/resources/users/v3
secondary
https://frontegg.com/
secondary
https://status.frontegg.com/api/v2/status.json
RealUptime is not affiliated with Frontegg; the name identifies what we measured, and nothing here speaks for Frontegg's own team. We send a single web request to Frontegg from 10 regions on our own schedule and time the response. We do not see inside Frontegg's systems, do not use an account or real transaction, and are not the same signal Frontegg's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Frontegg is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.