Kinde

OPERATIONAL

Since Jun 2025 · 25 incidents · status.kinde.com · checked just now

Compare Add to stack Status page

GradeA+Last 90 days

A+PRODA+SHIP

Overview

30d 90d 1y

Admitted uptime

Time not covered by a widespread Sev 1 the provider posted itself. A best case.

100.000%Grade A+

Incidents

Everything posted on the status page except scheduled maintenance.

20 Sev 1

Sev 1 downtime

Total minutes of Sev 1 incidents, as posted.

Median fix

Median time to resolve. Half of incidents were fixed faster.

1h 12m

Longest

Longest Sev 1–2 incident, start to resolved.

1h 12m

Since last

Time since the last counted incident was resolved.

29d 22h

By area

A+Production

2INCIDENTS

1h 26mAFFECTED

Your users are hit: apps, APIs, databases, inference

Worst, 90d

SEV 2Sep 23, 2026 · 1h 12m · some customers504 gateway errors for some domains

SEV 2Aug 25, 2026 · 14m · regionalUK data region

Most hit

Authentication2

Discord community1

Admin area1

Email delivery1

Better. 5 in the last 6 months, 12 in the 6 before.

A+Shipping

2INCIDENTS

1h 26mAFFECTED

You can't deploy, build or manage: CI, CLI, dashboard, auth, billing

Worst, 90d

SEV 3Sep 23, 2026 · 1h 12m · some customers504 gateway errors for some domains

SEV 3Aug 25, 2026 · 14m · regionalUK data region

Most hit

Authentication2

Discord community1

Admin area1

Email delivery1

4 in the last 6 months, 4 in the 6 before.

CleanSev 3–4Sev 1–2No data

Trend, last 12 months

Better. 5 in the last 6 months, 12 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0

Sev 2 · BleedingProd degraded or partly down2

Sev 3 · Can't shipCan't deploy, build or manage it0

Sev 4 · PapercutDocs, status page, slow dashboard0

When it breaks

Start times, last 12 months, UTC.

Mon

Tue

Wed

Thu

Fri

Sat

Sun

0006121823

What breaks

Authentication13 incidents

SMS delivery7 incidents

Management API7 incidents

Custom domains6 incidents

User export and import6 incidents

New user registration6 incidents

Communication

Updates each

Status page updates per incident, on average.

3.3Last 12 months

Update gap

Median time between status page updates during an incident.

30mLast 12 months

Postmortems

Sev 1–2 incidents with a published write-up.

2 of 17Sev 1–2

Incident history

Sep 23, 20261h 12mSEV 2

504 gateway errors for some domainsAuthentication returned 504 gateway errors for some customer domains for about 72 minutes; the text does not give failure rates.AI-graded · some customers · Authentication +2

Why this grade

RULES · SEV 2
Sev 2 because Authentication had degraded performance
CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
Authentication returned 504 gateway errors for some customer domains for about 72 minutes; the text does not give failure rates.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

3 updates

17:53 UTC · investigating
We are currently investigating this incident.
18:20 UTC · monitoring
All services are returning to normal, we are monitoring.
19:05 UTC · resolved
This incident has been resolved.

Source

Aug 25, 202614mSEV 2

UK data regionTraffic to the UK data region failed for about 14 minutes, hitting sign-in, email, SMS, webhooks and the management API; other regions were not reported affected.AI-graded · regional · Authentication +7

Why this grade

RULES · SEV 2
Sev 2 because Authentication had degraded performance
CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
Traffic to the UK data region failed for about 14 minutes, hitting sign-in, email, SMS, webhooks and the management API; other regions were not reported affected.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

3 updates

09:32 UTC · identified
We are continuing to work on a fix for this incident.
09:46 UTC · resolved
This incident has been resolved.
14:57 UTC · postmortem
The outage was caused by our internal reverse proxy failing to scale cleanly, resulting in incoming traffic not routing though our infrastructure correctly. A manual redeployment rectified the issue and service was restored. We have identified the cause for the failed scale and are putting changes in place to prevent re-occurrence.

Postmortem Source

Jun 22, 202619mSEV 2

Timeouts in US regionAuthentication and Management API requests timed out in the US region for about 19 minutes; the text gives no further detail on other regions.AI-graded · regional · Authentication +1

Why this grade

RULES · SEV 2
Sev 2 because Authentication had degraded performance
CLAUDE · SEV 2 · REGIONAL · LOW CONFIDENCE
Authentication and Management API requests timed out in the US region for about 19 minutes; the text gives no further detail on other regions.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

2 updates

16:02 UTC · investigating
We are currently investigating this incident.
16:21 UTC · resolved
This incident has been resolved.

Source

Jun 16, 20261h 39mSEV 2

[Third Party] x.com auth experiencing issueSev 2 because Authentication had degraded performanceAuthentication

2 updates

13:54 UTC · identified
[x.com](http://x.com) OAuth2 is currently experiencing issues resulting in a too many redirect errors. If you rely or use [x.com](http://x.com) login on your application, please reach to support and we will assist with your options.
15:33 UTC · resolved
[x.com](http://x.com) OAuth2 is now resolving and working.

Source

Jun 12, 202630mSEV 2

Degraded performanceSev 2 because Authentication had degraded performanceManagement API +3

2 updates

06:15 UTC · investigating
We are currently investigating this incident.
06:45 UTC · resolved
This incident has been resolved and our identified the issue.

Source

Apr 17, 202639mSEV 2

High latency for AU regionSev 2 because Custom domains had degraded performanceCustom domains +8

7 updates

03:27 UTC · investigating
We are currently investigating this incident.
03:42 UTC · monitoring
We are currently monitoring the result. Latency is returning to normal.
03:58 UTC · monitoring
We are continuing to monitor. Latency is returning to normal levels, and the team is actively working to return to baseline.
04:06 UTC · resolved
This incident has been resolved. The team will continue to monitor.
05:28 UTC · postmortem
We experienced high latency in our caching layer, which caused problems for a majority of our customers in the AU region. We have applied mitigations and will be prioritizing more performance enhancements soon.
05:52 UTC · monitoring
Our team is working on a fix and is actively monitoring to ensure latency returns to baseline levels.
06:14 UTC · resolved
This incident has been resolved, and a solution has been rolled out. Latency has resolved to baseline levels.

Postmortem Source

Apr 16, 20260mSEV 2

500 errors on auth flowSev 2 because User export and import had degraded performanceUser export and import +3

3 updates

19:25 UTC · resolved
This incident has been resolved.
19:55 UTC · identified
We are continuing to work on a fix for this incident.
20:10 UTC · resolved
This incident has been resolved.

Source

Apr 16, 202622mSEV 2

High latency for AU regionSev 2 because Custom domains had degraded performanceCustom domains +7

3 updates

08:12 UTC · investigating
We are currently investigating this incident.
08:21 UTC · monitoring
Latency has returned to normal. We are currently monitoring the result.
08:34 UTC · resolved
This incident has been resolved. We will continue to monitor latency internally.

Source

Apr 11, 202647mSEV 2

Increased errorsSev 2 because SMS delivery had degraded performanceSMS delivery +8

2 updates

10:11 UTC · monitoring
We implemented a fix and are currently monitoring the result.
10:58 UTC · resolved
This incident has been resolved and the team is monitoring and will investigate the cause.

Source

Mar 17, 202632mSEV 2

Intermittent 5xx timeouts for auth flows in AU regionSev 2 because Authentication had degraded performanceAuthentication +1

3 updates

02:38 UTC · investigating
We are currently investigating this incident.
02:46 UTC · monitoring
We are currently monitoring.
03:10 UTC · resolved
This incident has been resolved. Please reach out to the team if you need any assistance.

Source

Feb 3, 20261h 48mSEV 2

Delay with webhooks in London regionSev 2 because Webhooks had degraded performanceWebhooks

2 updates

12:33 UTC · investigating
We are currently investigating a delay with webhooks in the London region
14:21 UTC · resolved
We have resolved the webhook delay.

Source

Jan 7, 202616mSEV 2

One Time Password (OTP) Email errorsSev 2 because Authentication had degraded performanceAuthentication

2 updates

13:58 UTC · identified
The issue has been identified and a fix is currently being deployed.
14:14 UTC · resolved
This incident has been resolved.

Source

Dec 8, 202520h 55mSEV 2

SMS delivery problems to Vodafone Australia numbersSev 2 because SMS delivery had degraded performanceSMS delivery

3 updates

07:27 UTC · identified
We are working with out SMS provider to unblock these. At the moment, any messages from Kinde businesses based in the Sydney AU data region being sent to numbers with Vodafone Australia will not be delivered.
03:51 UTC · monitoring
An update has been applied to unblock delivery to Vodafone Australia. The team will continue monitoring until there's a sufficient volume of successful messages.
04:21 UTC · resolved
This incident has been resolved.

Source

Dec 5, 20253d 9hSEV 2

Connections from the UK to Kinde's AU region are timing outSev 2 because Custom domains had degraded performanceCustom domains +1

5 updates

18:41 UTC · investigating
We are currently investigating this incident. Connections from the UK to Kinde's AU region are timing out. Currently only the ISP "Sky" has been identified. This will impact users who are connecting from the UK and trying to accessing Kinde businesses that run in the AU data region.
20:44 UTC · identified
Based on regional testing, it looks like users using Sky as their ISP in the UK are not able to connect to Kinde businesses in the AU data region. We're in contact with our cloud provider and continuing to troubleshoot this issue.
23:07 UTC · identified
Our cloud provider has acknowledged the issue is affecting all of their customers and not just Kinde. And are continuing their investigation to provide a resolution.
03:53 UTC · resolved
This is a network routing issue between Sky’s infrastructure and AWS Sydney, and is also affecting other services hosted in this region. Sky customers have reported similar issues in Sky’s support forums. There is currently no ETA for resolution from Sky. We do have a workaround available, if you’re affected by this issue, please reach out to our support team. For now, we're going to mark this as closed and will update this status post as more information becomes available.
05:18 UTC · resolved
This is a network routing issue between Sky’s infrastructure and AWS Sydney, and is also affecting other services hosted in this region. Sky customers have reported similar issues in Sky’s support forums. There is currently no ETA for resolution from Sky. We do have a workaround available, if you’re affected by this issue, please reach out to our support team. We’ll update this status as more information becomes available.

Source

Dec 4, 20254h 04mSEV 2

AU region SMS delivery experiencing issues with the SMS provider. Not affecting Twilio setupsSev 2 because SMS delivery had degraded performanceSMS delivery

2 updates

06:20 UTC · identified
We are continuing to work on a fix for this incident.
10:24 UTC · resolved
This incident has been resolved.

Source

Nov 20, 20252h 44mSEV 2

Increase in SMS sending errorsSev 2 because SMS delivery had degraded performanceSMS delivery

3 updates

05:48 UTC · identified
Impacting custom SMS providers, not the default Kinde SMS sending. We are continuing to work on a fix for this incident.
08:12 UTC · monitoring
We implemented a fix and are currently monitoring the result.
08:31 UTC · resolved
This incident has been resolved.

Source

Nov 3, 202554mSEV 2

US custom domain timeoutsSev 2 because Authentication had degraded performanceAuthentication +1

3 updates

01:22 UTC · investigating
We are currently investigating this incident. This is impacting Kinde businesses in the US region running on a custom domain.
01:24 UTC · monitoring
Custom domains are back online and we're currently monitoring
02:16 UTC · resolved
This incident has been resolved.

Source

Oct 20, 202538mSEV 3

AU region API experiencing degraded performanceSev 3 because Management API had degraded performanceManagement API

3 updates

05:41 UTC · investigating
We are currently investigating this incident.
06:01 UTC · monitoring
Error have decreased and our team are currently monitoring.
06:18 UTC · resolved
This incident has been resolved and team is investigation the cause.

Source

Oct 16, 202549mSEV 2

Some customers experience high latency in EU regionSev 2 because Authentication had degraded performancesome customers · Authentication +6

3 updates

09:39 UTC · investigating
We are currently investigating this incident.
10:13 UTC · monitoring
We implemented a fix and are currently monitoring the result.
10:28 UTC · resolved
This incident has been resolved.

Source