Is Frontegg Down?

No — Frontegg is up

Frontegg's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 749 ms

Right now

The verdict is the worse of these two. How we decide

Frontegg's status page

status.frontegg.com · read 4 minutes ago · checked every 3 minutes

Operational

“All Systems Operational”: no open incidents and no component reported in trouble.

15 locations All operational

Open their status page

FlareWarden checks

portal.frontegg.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 749 ms
Checked: 2 hours ago

By region

Chicago reachable, 352 ms
London reachable, 144 ms
Los Angeles reachable, 660 ms
San Jose reachable, 744 ms
Singapore reachable, 1134 ms
Sydney reachable, 1468 ms
Tokyo reachable, 981 ms
Toronto reachable, 509 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Chicago	33 ms	1 ms	4 ms	276 ms
London	68 ms	3 ms	4 ms	134 ms
Los Angeles	79 ms	3 ms	5 ms	519 ms
San Jose	79 ms	6 ms	8 ms	609 ms
Singapore	223 ms	1 ms	3 ms	1134 ms
Sydney	439 ms	1 ms	4 ms	1214 ms
Tokyo	151 ms	2 ms	6 ms	779 ms
Toronto	134 ms	8 ms	10 ms	442 ms

We check that portal.frontegg.com loads, not every feature behind it. Test it yourself

History

Incidents Frontegg reported

Since Oct 22, 15 days · from status.frontegg.com

Incidents: 1
Major or critical: 0
Median to resolve: 38m

US degraded performance
minor · Oct 29
lasted 38m

Frontegg website availability

Measured by FlareWarden · portal.frontegg.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 643ms

Last 30 days

21-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of portal.frontegg.com from multiple regions every 6 hours. Frontegg's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 21 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Frontegg does

Frontegg is a customer identity platform that SaaS companies build into their products for authentication, authorization and user management. It renders the login box, hosted on a Frontegg or custom domain or embedded in the application, issues the short-lived JWTs and refresh tokens that keep users signed in, and runs a self-service portal where each customer account manages its own users, SSO and roles.

What an outage looks like

The login box fails to load or spins, and users cannot sign in to applications built on Frontegg. Sessions renew through Frontegg's token refresh endpoint, so signed-in users can be sent back to the login box when their access token expires. A CDN provider fault has stopped the login box loading, and a Cloudflare outage raised error rates. Each region's Management Portal row has had incidents of its own.

What to do about it

Open status.frontegg.com and find your region: EU, US, Australia, Canada and UK each have their own Authentication APIs, Management APIs and Management Portal rows. In past CDN incidents Frontegg switched or bypassed providers on its side, and after the July 2026 CloudFront outage said customers should not need to do anything, so leave DNS and domain settings alone.

Is it down for everyone, or just you?

If this page says Frontegg is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Frontegg outage FAQ

Which Frontegg region is my application in?

The API gateway your backend calls tells you. Frontegg's docs list api.frontegg.com for EU, api.us.frontegg.com for US, api.au.frontegg.com for Australia and api.ca.frontegg.com for Canada. The status page reports each region, plus the UK, as its own group, and most recent degraded-performance incidents named a single region, so a problem in one says little about the others.

Does the check above measure my users' login page?

No. It loads portal.frontegg.com, the Frontegg dashboard where builders configure environments. Your users sign in on your own Frontegg subdomain or custom domain, which is served by the Authentication APIs that the status page reports per region. A healthy dashboard is good evidence the platform is up, but it does not prove the login path in your region is working.

Why do users get a 401 on the token refresh request?

Often it is not an outage. Frontegg's docs say a 401 from /user/token/refresh when the login box first loads is expected, because that is how it checks for an existing session. A 401 after a login attempt usually means the browser blocked third-party cookies, common in Safari, incognito and mobile browsers, and Frontegg recommends a custom domain to fix it.

Users see 'Redirect uri wasn't found' or 'You can't log in'. Is Frontegg down?

Probably not. Frontegg documents both as configuration errors. 'Redirect uri wasn't found' means the URL is missing from the hosted login redirect list in the environment's login method settings. 'You can't log in. Contact an admin for help' means an active security rule blocked the user, which the security logs under Analytics and Monitoring will name.

Is it Frontegg or Cloudflare or AWS?

Sometimes it is both. Frontegg names Cloudflare as its WAF provider, and the November 18, 2025 Cloudflare outage raised error rates until Frontegg switched to a disaster recovery setup. On July 16, 2026 an AWS CloudFront problem disrupted authentication and login, and Frontegg said customers using custom domains v2 were still impacted while it rolled a workaround out region by region.

How we measure this

We request Frontegg's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Frontegg publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Frontegg itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Frontegg goes down

We check Frontegg every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required