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-10-14 13:59 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 15 minutes ago

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

As of Oct 14, 2026, 1:52 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 Oct 14, 2026, 1:52 PM UTC
US-East268 msChecks passing
US-West237 msChecks passing
Europe150 msChecks passing
Asia-Pacific1083 msChecks passing
US-Central258 msChecks passing
Canada335 msChecks passing
UK158 msChecks passing
Southeast Asia895 msChecks passing
Australia454 msChecks passing
South America902 msChecks passing
their status pagetheir claim, not our reading

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

from Frontegg's own status page, checked Oct 14, 2026, 1:42 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
339msp95 · 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-09-15 UTC: p95 467ms2026-09-16 UTC: p95 771ms2026-09-17 UTC: p95 855ms2026-09-18 UTC: p95 778ms2026-09-19 UTC: p95 700ms2026-09-20 UTC: p95 714ms2026-09-21 UTC: p95 683ms2026-09-22 UTC: p95 676ms2026-09-23 UTC: p95 656ms2026-09-24 UTC: p95 706ms2026-09-25 UTC: p95 654ms2026-09-26 UTC: p95 678ms2026-09-27 UTC: p95 721ms2026-09-28 UTC: p95 640ms2026-09-29 UTC: p95 696ms2026-09-30 UTC: p95 521ms2026-10-01 UTC: p95 570ms2026-10-02 UTC: p95 785ms2026-10-03 UTC: p95 667ms2026-10-04 UTC: p95 559ms2026-10-05 UTC: p95 299ms2026-10-06 UTC: p95 302ms2026-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 339ms
Sep 15Sep 29Oct 14
US-West
766msp95 · 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-09-15 UTC: p95 735ms2026-09-16 UTC: p95 741ms2026-09-17 UTC: p95 746ms2026-09-18 UTC: p95 751ms2026-09-19 UTC: p95 742ms2026-09-20 UTC: p95 773ms2026-09-21 UTC: p95 831ms2026-09-22 UTC: p95 924ms2026-09-23 UTC: p95 791ms2026-09-24 UTC: p95 761ms2026-09-25 UTC: p95 780ms2026-09-26 UTC: p95 813ms2026-09-27 UTC: p95 705ms2026-09-28 UTC: p95 829ms2026-09-29 UTC: p95 780ms2026-09-30 UTC: p95 755ms2026-10-01 UTC: p95 755ms2026-10-02 UTC: p95 720ms2026-10-03 UTC: p95 1.2s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 709ms2026-10-06 UTC: p95 773ms2026-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 766ms
Sep 15Sep 29Oct 14
Europe
331msp95 · 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-09-15 UTC: p95 336ms2026-09-16 UTC: p95 549ms2026-09-17 UTC: p95 545ms2026-09-18 UTC: p95 578ms2026-09-19 UTC: p95 538ms2026-09-20 UTC: p95 561ms2026-09-21 UTC: p95 366ms2026-09-22 UTC: p95 376ms2026-09-23 UTC: p95 513ms2026-09-24 UTC: p95 440ms2026-09-25 UTC: p95 572ms2026-09-26 UTC: p95 456ms2026-09-27 UTC: p95 495ms2026-09-28 UTC: p95 505ms2026-09-29 UTC: p95 427ms2026-09-30 UTC: p95 343ms2026-10-01 UTC: p95 369ms2026-10-02 UTC: p95 335ms2026-10-03 UTC: p95 367ms2026-10-04 UTC: p95 303ms2026-10-05 UTC: p95 242ms2026-10-06 UTC: p95 236ms2026-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 331ms
Sep 15Sep 29Oct 14
Asia-Pacific
1.4sp95 · 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-09-15 UTC: p95 1.5s2026-09-16 UTC: p95 1.4s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.7s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.6s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.7s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.6s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.7s2026-09-28 UTC: p95 1.7s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.6s2026-10-02 UTC: p95 1.6s2026-10-03 UTC: p95 1.7s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.2s2026-10-06 UTC: p95 1.1s2026-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.4s
Sep 15Sep 29Oct 14
US-Central
293msp95 · 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-15 UTC: p95 726ms2026-09-16 UTC: p95 629ms2026-09-17 UTC: p95 700ms2026-09-18 UTC: p95 700ms2026-09-19 UTC: p95 680ms2026-09-20 UTC: p95 660ms2026-09-21 UTC: p95 810ms2026-09-22 UTC: p95 840ms2026-09-23 UTC: p95 864ms2026-09-24 UTC: p95 858ms2026-09-25 UTC: p95 733ms2026-09-26 UTC: p95 986ms2026-09-27 UTC: p95 683ms2026-09-28 UTC: p95 667ms2026-09-29 UTC: p95 633ms2026-09-30 UTC: p95 883ms2026-10-01 UTC: p95 760ms2026-10-02 UTC: p95 693ms2026-10-03 UTC: p95 649ms2026-10-04 UTC: p95 529ms2026-10-05 UTC: p95 499ms2026-10-06 UTC: p95 479ms2026-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 293ms
Sep 15Sep 29Oct 14
Canada
457msp95 · 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-15 UTC: p95 472ms2026-09-16 UTC: p95 497ms2026-09-17 UTC: p95 525ms2026-09-18 UTC: p95 484ms2026-09-19 UTC: p95 495ms2026-09-20 UTC: p95 533ms2026-09-21 UTC: p95 479ms2026-09-22 UTC: p95 591ms2026-09-23 UTC: p95 567ms2026-09-24 UTC: p95 501ms2026-09-25 UTC: p95 549ms2026-09-26 UTC: p95 515ms2026-09-27 UTC: p95 534ms2026-09-28 UTC: p95 486ms2026-09-29 UTC: p95 480ms2026-09-30 UTC: p95 518ms2026-10-01 UTC: p95 494ms2026-10-02 UTC: p95 479ms2026-10-03 UTC: p95 735ms2026-10-04 UTC: p95 645ms2026-10-05 UTC: p95 503ms2026-10-06 UTC: p95 532ms2026-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 457ms
Sep 15Sep 29Oct 14
UK
195msp95 · 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-09-15 UTC: p95 241ms2026-09-16 UTC: p95 288ms2026-09-17 UTC: p95 309ms2026-09-18 UTC: p95 299ms2026-09-19 UTC: p95 297ms2026-09-20 UTC: p95 303ms2026-09-21 UTC: p95 322ms2026-09-22 UTC: p95 531ms2026-09-23 UTC: p95 400ms2026-09-24 UTC: p95 357ms2026-09-25 UTC: p95 408ms2026-09-26 UTC: p95 386ms2026-09-27 UTC: p95 371ms2026-09-28 UTC: p95 323ms2026-09-29 UTC: p95 335ms2026-09-30 UTC: p95 314ms2026-10-01 UTC: p95 555ms2026-10-02 UTC: p95 590ms2026-10-03 UTC: p95 894ms2026-10-04 UTC: p95 442ms2026-10-05 UTC: p95 177ms2026-10-06 UTC: p95 201ms2026-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 195ms
Sep 15Sep 29Oct 14
Southeast Asia
1.2sp95 · 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-15 UTC: p95 1.1s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.3s2026-09-19 UTC: p95 1.1s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.2s2026-09-22 UTC: p95 1.5s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.3s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.1s2026-09-30 UTC: p95 1.1s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.1s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.1s2026-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.2s
Sep 15Sep 29Oct 14
Australia
1.4sp95 · 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-15 UTC: p95 1.7s2026-09-16 UTC: p95 1.6s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 1.6s2026-09-19 UTC: p95 1.7s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 1.6s2026-09-22 UTC: p95 1.6s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.6s2026-09-25 UTC: p95 2.0s2026-09-26 UTC: p95 2.1s2026-09-27 UTC: p95 1.4s2026-09-28 UTC: p95 1.5s2026-09-29 UTC: p95 1.5s2026-09-30 UTC: p95 1.4s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.6s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.3s2026-10-06 UTC: p95 1.3s2026-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.4s
Sep 15Sep 29Oct 14
South America
1.2sp95 · 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-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.2s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.2s2026-09-20 UTC: p95 1.2s2026-09-21 UTC: p95 1.1s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.3s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.4s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.5s2026-10-02 UTC: p95 1.2s2026-10-03 UTC: p95 1.3s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.1s2026-10-06 UTC: p95 1.1s2026-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.2s
Sep 15Sep 29Oct 14

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

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: 268msstatus code: 401checked: Oct 14, 2026, 1:40 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: 237msstatus code: 401checked: Oct 14, 2026, 1:41 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: 258msstatus code: 401checked: Oct 14, 2026, 1:39 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: 335msstatus code: 401checked: Oct 14, 2026, 1:38 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: 902msstatus code: 401checked: Oct 14, 2026, 1:42 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: 150msstatus code: 401checked: Oct 14, 2026, 1:52 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: 158msstatus code: 401checked: Oct 14, 2026, 1:41 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: 1083msstatus code: 401checked: Oct 14, 2026, 1:39 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: 895msstatus code: 401checked: Oct 14, 2026, 1:41 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: 454msstatus code: 401checked: Oct 14, 2026, 1:39 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

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
Degraded performance inEU region, 1h 29mdeclared on their status page2025-12-08

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

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"></a>

The badge shows the share of our checks that passed 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 and shows no color. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

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.

Checking a site of your own? The free website down checker sends it one request and reports the answer, and the SLA calculator shows how much downtime an uptime figure allows.

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

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.