Skip to content

Outage tracker / Frontegg

Is Frontegg down?

I'm having a problem

Operationalchecked 29 minutes ago

We reached Frontegg from all 10 regions we check.

As of Oct 5, 2026, 7:48 PM UTC, Frontegg answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 5, 2026, 7:48 PM UTC
US-East205 msOperational
US-West283 msOperational
Europe109 msOperational
Asia-Pacific978 msOperational
US-Central203 msOperational
Canada493 msOperational
UK143 msOperational
Southeast Asia1040 msOperational
Australia1324 msOperational
South America743 msOperational
their status pagetheir claim, not our reading

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

from Frontegg's own status page, checked Oct 5, 2026, 7:52 PM 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
294msp95 · 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-06 UTC: p95 535ms2026-09-07 UTC: p95 522ms2026-09-08 UTC: p95 559ms2026-09-09 UTC: p95 525ms2026-09-10 UTC: p95 527ms2026-09-11 UTC: p95 598ms2026-09-12 UTC: p95 483ms2026-09-13 UTC: p95 469ms2026-09-14 UTC: p95 493ms2026-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 294ms
Sep 6Sep 20Oct 5
US-West
657msp95 · 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-06 UTC: p95 768ms2026-09-07 UTC: p95 796ms2026-09-08 UTC: p95 729ms2026-09-09 UTC: p95 634ms2026-09-10 UTC: p95 648ms2026-09-11 UTC: p95 703ms2026-09-12 UTC: p95 721ms2026-09-13 UTC: p95 710ms2026-09-14 UTC: p95 864ms2026-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 657ms
Sep 6Sep 20Oct 5
Europe
236msp95 · 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-09-06 UTC: p95 343ms2026-09-07 UTC: p95 359ms2026-09-08 UTC: p95 397ms2026-09-09 UTC: p95 340ms2026-09-10 UTC: p95 362ms2026-09-11 UTC: p95 393ms2026-09-12 UTC: p95 331ms2026-09-13 UTC: p95 327ms2026-09-14 UTC: p95 319ms2026-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 236ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.2sp95 · 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-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.6s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.7s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.5s2026-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.2s
Sep 6Sep 20Oct 5
US-Central
501msp95 · 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-06 UTC: p95 540ms2026-09-07 UTC: p95 474ms2026-09-08 UTC: p95 748ms2026-09-09 UTC: p95 792ms2026-09-10 UTC: p95 834ms2026-09-11 UTC: p95 809ms2026-09-12 UTC: p95 697ms2026-09-13 UTC: p95 661ms2026-09-14 UTC: p95 631ms2026-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 501ms
Sep 6Sep 20Oct 5
Canada
507msp95 · 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-06 UTC: p95 518ms2026-09-07 UTC: p95 514ms2026-09-08 UTC: p95 532ms2026-09-09 UTC: p95 512ms2026-09-10 UTC: p95 458ms2026-09-11 UTC: p95 508ms2026-09-12 UTC: p95 490ms2026-09-13 UTC: p95 500ms2026-09-14 UTC: p95 551ms2026-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 507ms
Sep 6Sep 20Oct 5
UK
178msp95 · 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-06 UTC: p95 486ms2026-09-07 UTC: p95 353ms2026-09-08 UTC: p95 619ms2026-09-09 UTC: p95 363ms2026-09-10 UTC: p95 398ms2026-09-11 UTC: p95 333ms2026-09-12 UTC: p95 287ms2026-09-13 UTC: p95 284ms2026-09-14 UTC: p95 250ms2026-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 178ms
Sep 6Sep 20Oct 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-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.1s2026-09-11 UTC: p95 1.1s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.1s2026-09-14 UTC: p95 1.1s2026-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.1s
Sep 6Sep 20Oct 5
Australia
1.3sp95 · 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-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.6s2026-09-08 UTC: p95 1.6s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.5s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.6s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.5s2026-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.3s
Sep 6Sep 20Oct 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-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.0s2026-09-08 UTC: p95 1.2s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.2s2026-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.1s
Sep 6Sep 20Oct 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

Get an email when we see Frontegg go down, and when it is back

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.

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: 205msstatus code: 401checked: Oct 5, 2026, 7:48 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
      Operationallatency: 283msstatus code: 401checked: Oct 5, 2026, 7:48 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
      Operationallatency: 203msstatus code: 401checked: Oct 5, 2026, 7:46 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
      Operationallatency: 493msstatus code: 401checked: Oct 5, 2026, 7:48 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
    Operationallatency: 743msstatus code: 401checked: Oct 5, 2026, 7:46 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 109msstatus code: 401checked: Oct 5, 2026, 7:47 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
      Operationallatency: 143msstatus code: 401checked: Oct 5, 2026, 7:48 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 978msstatus code: 401checked: Oct 5, 2026, 7:48 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
      Operationallatency: 1040msstatus code: 401checked: Oct 5, 2026, 7:45 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
      Operationallatency: 1324msstatus code: 401checked: Oct 5, 2026, 7:47 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 outages

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

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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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.