Skip to main content
Kinde logo

Is Kinde Down?

No — Kinde is up

Reachable from all 8 checked regions

Average response time: 574ms

Last checked · checks run every 6 hours

Official status page: https://status.kinde.com

Kinde uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
504ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 13 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

13-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: no data
Sep 3: no data
Sep 4: no data
Sep 5: no data
Sep 6: no data
Sep 7: no data
Sep 8: 100.00% uptime, 16 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 16 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

jnb
916ms
DNS 348ms TCP 0ms TLS 4ms TTFB 899ms
lax
419ms
DNS 99ms TCP 2ms TLS 3ms TTFB 388ms
lhr
460ms
DNS 87ms TCP 3ms TLS 6ms TTFB 442ms
nrt
782ms
DNS 201ms TCP 2ms TLS 6ms TTFB 766ms
ord
538ms
DNS 124ms TCP 1ms TLS 7ms TTFB 525ms
sin
829ms
DNS 351ms TCP 1ms TLS 3ms TTFB 817ms
sjc
554ms
DNS 81ms TCP 1ms TLS 5ms TTFB 521ms
syd
101ms
DNS 30ms TCP 0ms TLS 5ms TTFB 80ms

What Kinde does

Kinde is an authentication and user management platform that applications use for sign-up, sign-in, social and enterprise connections, organisations and permissions. Each customer's environment is hosted in a chosen geographic region rather than a single global deployment. Applications integrate it through SDKs and hosted sign-in pages, making it the dependency every session passes through.

What an outage looks like

Sign-in and sign-up fail while users with existing sessions continue unaffected, so the proportion of people affected grows as sessions expire rather than appearing all at once. Redirects to the hosted sign-in page hang or return errors, token exchange and refresh calls fail, and applications that gate everything behind authentication look entirely down to new arrivals.

What to do about it

Read status.kinde.com and find your region: it reports AU, CA, EU, UK and US as separate groups, with Global and Support groups alongside them. A region-specific incident leaves every other region working, so a colleague signing in normally proves nothing unless they are on the same one. Avoid invalidating sessions during an incident, since users holding them are the ones still able to work, and hold off on connection or configuration changes you cannot verify.

Is it down for everyone, or just you?

If this page says Kinde 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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Auth0 (Okta)
Auth0 (Okta)
Clerk
Clerk
FusionAuth
FusionAuth
Okta
Okta

Kinde outage FAQ

Kinde says all systems operational but my users cannot sign in. Why?
Check the region rather than the headline. Kinde reports AU, CA, EU, UK and US as separate component groups, so an incident confined to one region sits beneath an otherwise healthy summary, and your environment lives in exactly one of them. Expand the group matching your region on status.kinde.com. If that is clear too, look at your callback URLs and client credentials next.
Only some of my users are affected. Is that consistent with a Kinde outage?
Yes, and it is the normal shape. Users who signed in before the incident hold valid tokens and carry on, while anyone signing in fresh or refreshing an expired token fails. The affected group grows steadily rather than appearing at once, which makes an authentication incident look like a problem with particular accounts when it is not.
Does a Kinde outage in one region affect the others?
Not usually. Kinde publishes AU, CA, EU, UK and US as their own groups precisely because they are operated separately, and it maintains a Global group for anything spanning them. A US incident and an EU one are different events. Confirm which region your Kinde environment is in before drawing conclusions from someone else's experience.
Will users be signed out during a Kinde outage?
Existing sessions generally survive, because the application holds a token that stays valid until it expires. What fails is issuing new tokens and refreshing old ones, so users are lost gradually as their tokens age rather than immediately. Avoid triggering a forced sign-out or a session purge during an incident, since that converts users who are working into users who cannot sign back in.
Is Kinde down or is my application's configuration wrong?
Compare scope and timing. A configuration fault follows a change on your side and typically affects one environment, one callback URL or one connection, while a Kinde incident affects every sign-in in that region at once. status.kinde.com publishes incident detail pages and a notice history, so an active entry naming your region confirms the platform side.

How we measure this

  • We request Kinde's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • 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. We only change the 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 Kinde publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Kinde goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required