Skip to content

Outage tracker / Frontegg

Is Frontegg down?

I'm having a problem

Vendor reports no incidentWhat Frontegg reports

Frontegg reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:24 UTC.

Frontegg's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 10 minutes ago

Our checks of Frontegg pass from all 10 regions we check.

As of Nov 5, 2026, 2:23 PM UTC, RealUptime's checks of Frontegg passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:23 PM UTC
US-East567 msChecks passing
US-West1140 msChecks passing
Europe321 msChecks passing
Asia-Pacific945 msChecks passing
US-Central307 msChecks passing
Canada719 msChecks passing
UK166 msChecks passing
Southeast Asia1128 msChecks passing
Australia2080 msChecks passing
South America1106 msChecks passing
their status pagetheir claim, not our reading

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

from Frontegg's own status page, checked Nov 5, 2026, 1:56 PM UTC
Frontegg's own status page shows no incident, and our checks of Frontegg pass 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
1.1sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 315ms2026-10-08 UTC: p95 293ms2026-10-09 UTC: p95 270ms2026-10-10 UTC: p95 263ms2026-10-11 UTC: p95 262ms2026-10-12 UTC: p95 303ms2026-10-13 UTC: p95 329ms2026-10-14 UTC: p95 349ms2026-10-15 UTC: p95 320ms2026-10-16 UTC: p95 457ms2026-10-17 UTC: p95 560ms2026-10-18 UTC: p95 578ms2026-10-19 UTC: p95 510ms2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 919ms2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 788ms2026-10-28 UTC: p95 631ms2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 689ms2026-10-31 UTC: p95 852ms2026-11-01 UTC: p95 929ms2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
US-West
2.4sp95 · latest
5s2.5s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 839ms2026-10-08 UTC: p95 851ms2026-10-09 UTC: p95 854ms2026-10-10 UTC: p95 816ms2026-10-11 UTC: p95 860ms2026-10-12 UTC: p95 737ms2026-10-13 UTC: p95 937ms2026-10-14 UTC: p95 823ms2026-10-15 UTC: p95 721ms2026-10-16 UTC: p95 1.0s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 903ms2026-10-21 UTC: p95 1.3s2026-10-22 UTC: p95 1.8s2026-10-23 UTC: p95 1.1s2026-10-24 UTC: p95 1.2s2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 968ms2026-10-29 UTC: p95 1.7s2026-10-30 UTC: p95 789ms2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 2.7s2026-11-03 UTC: p95 2.8s2026-11-04 UTC: p95 2.2s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
Europe
1.3sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.9s2026-10-08 UTC: p95 411ms2026-10-09 UTC: p95 200ms2026-10-10 UTC: p95 206ms2026-10-11 UTC: p95 190ms2026-10-12 UTC: p95 292ms2026-10-13 UTC: p95 344ms2026-10-14 UTC: p95 331ms2026-10-15 UTC: p95 493ms2026-10-16 UTC: p95 342ms2026-10-17 UTC: p95 634ms2026-10-18 UTC: p95 738ms2026-10-19 UTC: p95 796ms2026-10-20 UTC: p95 646ms2026-10-21 UTC: p95 541ms2026-10-22 UTC: p95 768ms2026-10-23 UTC: p95 740ms2026-10-24 UTC: p95 669ms2026-10-25 UTC: p95 673ms2026-10-26 UTC: p95 628ms2026-10-27 UTC: p95 505ms2026-10-28 UTC: p95 501ms2026-10-29 UTC: p95 517ms2026-10-30 UTC: p95 313ms2026-10-31 UTC: p95 298ms2026-11-01 UTC: p95 253ms2026-11-02 UTC: p95 1.6s2026-11-03 UTC: p95 897ms2026-11-04 UTC: p95 1.9s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Asia-Pacific
3.0sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.2s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.5s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.6s2026-10-17 UTC: p95 1.6s2026-10-18 UTC: p95 1.6s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.6s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.8s2026-10-24 UTC: p95 2.3s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.3s2026-10-27 UTC: p95 4.5s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.9s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 3.3s2026-11-05 UTC: p95 3.0s
Oct 7Oct 21Nov 5
US-Central
843msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 452ms2026-10-08 UTC: p95 407ms2026-10-09 UTC: p95 449ms2026-10-10 UTC: p95 466ms2026-10-11 UTC: p95 492ms2026-10-12 UTC: p95 432ms2026-10-13 UTC: p95 426ms2026-10-14 UTC: p95 396ms2026-10-15 UTC: p95 243ms2026-10-16 UTC: p95 784ms2026-10-17 UTC: p95 727ms2026-10-18 UTC: p95 873ms2026-10-19 UTC: p95 873ms2026-10-20 UTC: p95 572ms2026-10-21 UTC: p95 677ms2026-10-22 UTC: p95 670ms2026-10-23 UTC: p95 570ms2026-10-24 UTC: p95 459ms2026-10-25 UTC: p95 987ms2026-10-26 UTC: p95 372ms2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 695ms2026-10-29 UTC: p95 944ms2026-10-30 UTC: p95 1.0s2026-10-31 UTC: p95 1.0s2026-11-01 UTC: p95 779ms2026-11-02 UTC: p95 749ms2026-11-03 UTC: p95 851ms2026-11-04 UTC: p95 774ms2026-11-05 UTC: p95 843ms
Oct 7Oct 21Nov 5
Canada
880msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 501ms2026-10-08 UTC: p95 519ms2026-10-09 UTC: p95 465ms2026-10-10 UTC: p95 497ms2026-10-11 UTC: p95 485ms2026-10-12 UTC: p95 499ms2026-10-13 UTC: p95 528ms2026-10-14 UTC: p95 517ms2026-10-15 UTC: p95 508ms2026-10-16 UTC: p95 522ms2026-10-17 UTC: p95 562ms2026-10-18 UTC: p95 482ms2026-10-19 UTC: p95 529ms2026-10-20 UTC: p95 507ms2026-10-21 UTC: p95 544ms2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 501ms2026-10-24 UTC: p95 539ms2026-10-25 UTC: p95 528ms2026-10-26 UTC: p95 490ms2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.8s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 941ms2026-10-31 UTC: p95 757ms2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 880ms
Oct 7Oct 21Nov 5
UK
492msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 346ms2026-10-08 UTC: p95 210ms2026-10-09 UTC: p95 213ms2026-10-10 UTC: p95 257ms2026-10-11 UTC: p95 216ms2026-10-12 UTC: p95 190ms2026-10-13 UTC: p95 165ms2026-10-14 UTC: p95 193ms2026-10-15 UTC: p95 199ms2026-10-16 UTC: p95 200ms2026-10-17 UTC: p95 353ms2026-10-18 UTC: p95 323ms2026-10-19 UTC: p95 286ms2026-10-20 UTC: p95 325ms2026-10-21 UTC: p95 206ms2026-10-22 UTC: p95 324ms2026-10-23 UTC: p95 260ms2026-10-24 UTC: p95 150ms2026-10-25 UTC: p95 193ms2026-10-26 UTC: p95 384ms2026-10-27 UTC: p95 372ms2026-10-28 UTC: p95 655ms2026-10-29 UTC: p95 184ms2026-10-30 UTC: p95 172ms2026-10-31 UTC: p95 210ms2026-11-01 UTC: p95 157ms2026-11-02 UTC: p95 413ms2026-11-03 UTC: p95 726ms2026-11-04 UTC: p95 780ms2026-11-05 UTC: p95 492ms
Oct 7Oct 21Nov 5
Southeast Asia
2.0sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.2s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 1.2s2026-10-17 UTC: p95 1.2s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 2.1s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 1.4s2026-10-30 UTC: p95 2.4s2026-10-31 UTC: p95 2.7s2026-11-01 UTC: p95 1.8s2026-11-02 UTC: p95 2.0s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 1.6s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Australia
2.2sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.4s2026-10-08 UTC: p95 1.4s2026-10-09 UTC: p95 1.3s2026-10-10 UTC: p95 1.4s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.6s2026-10-13 UTC: p95 1.6s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 1.4s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.4s2026-10-18 UTC: p95 1.4s2026-10-19 UTC: p95 2.3s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.4s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 2.6s2026-10-28 UTC: p95 2.6s2026-10-29 UTC: p95 3.3s2026-10-30 UTC: p95 3.2s2026-10-31 UTC: p95 3.2s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 2.2s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
South America
1.8sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.2s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.1s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.7s2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 2.0s2026-10-23 UTC: p95 9.4s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.4s2026-10-27 UTC: p95 1.7s2026-10-28 UTC: p95 1.7s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 2.1s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.8s
Oct 7Oct 21Nov 5

Check your own site while you wait on Frontegg

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: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • AuthprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Management PortalUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Frontegg reports an incident on its status page, and again when it reports it resolved.

Get an email when Frontegg reports an incident

Email me when Frontegg reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Frontegg's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 567msstatus code: 401checked: Nov 5, 2026, 2:19 PM 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
      Checks passinglatency: 1140msstatus code: 401checked: Nov 5, 2026, 2:03 PM 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
      Checks passinglatency: 307msstatus code: 401checked: Nov 5, 2026, 1:45 PM 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
      Checks passinglatency: 719msstatus code: 401checked: Nov 5, 2026, 1:44 PM 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
    Checks passinglatency: 1106msstatus code: 401checked: Nov 5, 2026, 1:40 PM 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
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 321msstatus code: 401checked: Nov 5, 2026, 2:07 PM 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
      Checks passinglatency: 166msstatus code: 401checked: Nov 5, 2026, 1:35 PM 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
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 945msstatus code: 401checked: Nov 5, 2026, 2:23 PM 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
      Checks passinglatency: 1128msstatus code: 401checked: Nov 5, 2026, 1:59 PM 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
      Checks passinglatency: 2080msstatus code: 401checked: Nov 5, 2026, 1:50 PM 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 probe events

US degraded performance, 38mdeclared on their status page2026-10-29
Degraded Performance, 44mdeclared on their status page2026-10-11
Degraded Performance, 34mdeclared on their status page2026-10-06
Degraded Performance, 21mdeclared on their status page2026-10-04
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-05-31
Degraded performance in US region - Partial Entitlements functionalities, 1h 51mdeclared on their status page2026-03-23

check 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 check readings and Frontegg's own claim at the time, side by side.

Full check history for Frontegg: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Frontegg uptime by RealUptime's checksLive, from this page's own readings.
[![Frontegg uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Frontegg down?", https://realuptime.io/outages/frontegg. The readings change with every check, so give the date you read them.

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
secondary
https://portal.frontegg.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.frontegg.com

RealUptime is not affiliated with Frontegg; the name identifies what we checked, 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.