Skip to main content
Frontegg

Degradation in Tenant API Token authentication

Degraded Lasted 0m · started · Frontegg's page

Level
confirmed
Worst impact
Degraded
Down Index
8of 100

What to do

  • Check whether your product depends on Frontegg. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2023-06-01 08:21 UTC and 2023-05-16 10:00 UTC may need a replay.
  • Subscribe to Frontegg's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=frontegg works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Frontegg 1

  1. resolved

    Users with Tenant API tokens that were with client credentials had an issue with authenticating the api token. The authenticate API token route was returning a 400 response. Access token API Tokens were fully opperational

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-9cb8263ffd

Is Frontegg still down?

No, this incident was resolved 2023-05-16 10:00 UTC. For Frontegg's live state, see https://down.guide/frontegg.

How long did it last?

0m, from 2023-06-01 08:21 UTC to 2023-05-16 10:00 UTC, by the times Frontegg posted.

What caused it?

Frontegg hasn't published a root cause. If it does, it shows here.

Where does this come from?

Frontegg's official status page, https://status.frontegg.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.