Is Kinde Down?

No — Kinde is up

Kinde's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 605 ms

Right now

The verdict is the worse of these two. How we decide

Kinde's status page

status.kinde.com · read 3 minutes ago · checked every 3 minutes

Operational

Kinde's components, as its status page reports them
Component	Status
Admin area	Operational
Documentation	Operational
Website	Operational
AU region	Operational
CA region	Operational
EU region	Operational
US region	Operational
UK region	Operational
Global	Operational
Support	Operational
Live chat	Operational
Support email	Operational

2 more, all operational · show all 14

All of Kinde's components
Component	Status
Global
Admin area	Operational
Documentation	Operational
Website	Operational
AU region	Operational
CA region	Operational
EU region	Operational
US region	Operational
UK region	Operational
Global	Operational
Support	Operational
Support
Live chat	Operational
Support email	Operational
Slack community	Operational
Discord community	Operational

40 locations All operational

Open their status page

FlareWarden checks

kinde.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 605 ms
Checked: 1 hour ago

By region

Chicago reachable, 386 ms
Johannesburg reachable, 854 ms
London reachable, 470 ms
Los Angeles reachable, 448 ms
San Jose reachable, 1286 ms
Singapore reachable, 681 ms
Sydney reachable, 159 ms
Tokyo reachable, 557 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Chicago	126 ms	2 ms	5 ms	374 ms
Johannesburg	156 ms	1 ms	4 ms	832 ms
London	66 ms	3 ms	5 ms	444 ms
Los Angeles	148 ms	2 ms	6 ms	421 ms
San Jose	78 ms	92 ms	86 ms	847 ms
Singapore	285 ms	2 ms	5 ms	665 ms
Sydney	88 ms	2 ms	5 ms	138 ms
Tokyo	196 ms	2 ms	6 ms	541 ms

We check that kinde.com loads, not every feature behind it. Test it yourself

History

Incidents Kinde reported

Since Oct 27, 10 days · from status.kinde.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Kinde website availability

Measured by FlareWarden · kinde.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 553ms

Last 30 days

59-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of kinde.com from multiple regions every 6 hours. Kinde's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 59 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Kinde itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Kinde goes down

We check Kinde every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required