Kinde Outage History

Kinde is up right now

Pingoru has recorded 51 incidents for Kinde: 34 in the last 12 months and 4 in the last 90 days.

Source: status.kinde.com

51incidents recorded
34last 12 months
4last 90 days
4 hourstypical duration
Incidents per month
048AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Kinde in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202685 of 720 (1%)
May 202600 of 744 (0%)
June 202663 of 720 (0%)
July 202600 of 744 (0%)
August 202620 of 744 (0%)
September 202621 of 720 (0%)
October 202600 of 519 (0%)

Incidents, newest first

Minor September 23, 2026 504 gateway errors for some domains 1h 12m US region (Authentication), CA region (Authentication), Global (Admin area), EU region (Authentication) and 3 more

Started Sep 23, 2026, 05:53 PM UTC· resolved Sep 23, 2026, 07:05 PM UTC

  1. investigating Sep 23, 2026, 05:53 PM UTC

    We are currently investigating this incident.

  2. monitoring Sep 23, 2026, 06:20 PM UTC

    All services are returning to normal, we are monitoring.

  3. resolved Sep 23, 2026, 07:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 25, 2026 UK data region 14m

Started Aug 25, 2026, 09:32 AM UTC· resolved Aug 25, 2026, 09:46 AM UTC

  1. identified Aug 25, 2026, 09:32 AM UTC

    We are continuing to work on a fix for this incident..

  2. resolved Aug 25, 2026, 09:46 AM UTC

    This incident has been resolved..

  3. monitoring Aug 25, 2026, 02:57 PM UTC

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

Read the full incident report →

Minor June 22, 2026 Timeouts in US region 19m

Started Jun 22, 2026, 04:02 PM UTC· resolved Jun 22, 2026, 04:21 PM UTC

  1. investigating Jun 22, 2026, 04:02 PM UTC

    We are currently investigating this incident..

  2. resolved Jun 22, 2026, 04:21 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor June 16, 2026 [Third Party] x.com auth experiencing issue 1h 38m US region (Authentication), CA region (Authentication), EU region (Authentication), AU region (Authentication) and 1 more

Started Jun 16, 2026, 01:54 PM UTC· resolved Jun 16, 2026, 03:33 PM UTC

  1. identified Jun 16, 2026, 01:54 PM UTC

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

  2. resolved Jun 16, 2026, 03:33 PM UTC

    [x.com](http://x.com) OAuth2 is now resolving and working.

Read the full incident report →

Minor June 12, 2026 Degraded performance 30m

Started Jun 12, 2026, 06:15 AM UTC· resolved Jun 12, 2026, 06:45 AM UTC

  1. investigating Jun 12, 2026, 06:15 AM UTC

    We are currently investigating this incident..

  2. resolved Jun 12, 2026, 06:45 AM UTC

    This incident has been resolved and our identified the issue..

Read the full incident report →

Minor April 17, 2026 High latency for AU region 2h 47m

Started Apr 17, 2026, 03:27 AM UTC· resolved Apr 17, 2026, 06:14 AM UTC

  1. investigating Apr 17, 2026, 03:27 AM UTC

    We are currently investigating this incident..

  2. monitoring Apr 17, 2026, 03:42 AM UTC

    We are currently monitoring the result. Latency is returning to normal..

  3. monitoring Apr 17, 2026, 03:58 AM UTC

    We are continuing to monitor. Latency is returning to normal levels, and the team is actively working to return to baseline..

  4. resolved Apr 17, 2026, 04:06 AM UTC

    This incident has been resolved. The team will continue to monitor..

  5. monitoring Apr 17, 2026, 05:28 AM UTC

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

  6. monitoring Apr 17, 2026, 05:52 AM UTC

    Our team is working on a fix and is actively monitoring to ensure latency returns to baseline levels..

  7. resolved Apr 17, 2026, 06:14 AM UTC

    This incident has been resolved, and a solution has been rolled out. Latency has resolved to baseline levels..

Read the full incident report →

Minor April 16, 2026 500 errors on auth flow 45m

Started Apr 16, 2026, 07:25 PM UTC· resolved Apr 16, 2026, 08:10 PM UTC

  1. resolved Apr 16, 2026, 07:25 PM UTC

    This incident has been resolved..

  2. identified Apr 16, 2026, 07:55 PM UTC

    We are continuing to work on a fix for this incident..

  3. resolved Apr 16, 2026, 08:10 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor April 11, 2026 Increased errors 47m

Started Apr 11, 2026, 10:11 AM UTC· resolved Apr 11, 2026, 10:58 AM UTC

  1. monitoring Apr 11, 2026, 10:11 AM UTC

    We implemented a fix and are currently monitoring the result..

  2. resolved Apr 11, 2026, 10:58 AM UTC

    This incident has been resolved and the team is monitoring and will investigate the cause..

Read the full incident report →

Minor March 17, 2026 Intermittent 5xx timeouts for auth flows in AU region 31m

Started Mar 17, 2026, 02:38 AM UTC· resolved Mar 17, 2026, 03:10 AM UTC

  1. investigating Mar 17, 2026, 02:38 AM UTC

    We are currently investigating this incident..

  2. monitoring Mar 17, 2026, 02:46 AM UTC

    We are currently monitoring..

  3. resolved Mar 17, 2026, 03:10 AM UTC

    This incident has been resolved. Please reach out to the team if you need any assistance..

Read the full incident report →

Minor February 3, 2026 Delay with webhooks in London region 1h 48m

Started Feb 03, 2026, 12:33 PM UTC· resolved Feb 03, 2026, 02:21 PM UTC

  1. investigating Feb 03, 2026, 12:33 PM UTC

    We are currently investigating a delay with webhooks in the London region.

  2. resolved Feb 03, 2026, 02:21 PM UTC

    We have resolved the webhook delay..

Read the full incident report →

Minor January 7, 2026 One Time Password (OTP) Email errors 15m

Started Jan 07, 2026, 01:58 PM UTC· resolved Jan 07, 2026, 02:14 PM UTC

  1. identified Jan 07, 2026, 01:58 PM UTC

    The issue has been identified and a fix is currently being deployed..

  2. resolved Jan 07, 2026, 02:14 PM UTC

    This incident has been resolved..

Read the full incident report →

Minor December 8, 2025 SMS delivery problems to Vodafone Australia numbers 20h 54m

Started Dec 08, 2025, 07:27 AM UTC· resolved Dec 09, 2025, 04:21 AM UTC

  1. identified Dec 08, 2025, 07:27 AM UTC

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

  2. monitoring Dec 09, 2025, 03:51 AM UTC

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

  3. resolved Dec 09, 2025, 04:21 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor December 5, 2025 Connections from the UK to Kinde's AU region are timing out 3d 10h

Started Dec 05, 2025, 06:41 PM UTC· resolved Dec 09, 2025, 05:18 AM UTC

  1. investigating Dec 05, 2025, 06:41 PM UTC

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

  2. identified Dec 05, 2025, 08:44 PM UTC

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

  3. identified Dec 05, 2025, 11:07 PM UTC

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

  4. resolved Dec 09, 2025, 03:53 AM UTC

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

  5. resolved Dec 09, 2025, 05:18 AM UTC

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

Read the full incident report →

Minor December 4, 2025 AU region SMS delivery experiencing issues with the SMS provider. Not affecting Twilio setups 4h 4m

Started Dec 04, 2025, 06:20 AM UTC· resolved Dec 04, 2025, 10:24 AM UTC

  1. identified Dec 04, 2025, 06:20 AM UTC

    We are continuing to work on a fix for this incident..

  2. resolved Dec 04, 2025, 10:24 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor November 20, 2025 Increase in SMS sending errors 2h 43m

Started Nov 20, 2025, 05:48 AM UTC· resolved Nov 20, 2025, 08:31 AM UTC

  1. identified Nov 20, 2025, 05:48 AM UTC

    Impacting custom SMS providers, not the default Kinde SMS sending. We are continuing to work on a fix for this incident..

  2. monitoring Nov 20, 2025, 08:12 AM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Nov 20, 2025, 08:31 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor November 3, 2025 US custom domain timeouts 53m

Started Nov 03, 2025, 01:22 AM UTC· resolved Nov 03, 2025, 02:16 AM UTC

  1. investigating Nov 03, 2025, 01:22 AM UTC

    We are currently investigating this incident. This is impacting Kinde businesses in the US region running on a custom domain..

  2. monitoring Nov 03, 2025, 01:24 AM UTC

    Custom domains are back online and we're currently monitoring.

  3. resolved Nov 03, 2025, 02:16 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor October 20, 2025 AU region API experiencing degraded performance 37m

Started Oct 20, 2025, 05:41 AM UTC· resolved Oct 20, 2025, 06:18 AM UTC

  1. investigating Oct 20, 2025, 05:41 AM UTC

    We are currently investigating this incident..

  2. monitoring Oct 20, 2025, 06:01 AM UTC

    Error have decreased and our team are currently monitoring..

  3. resolved Oct 20, 2025, 06:18 AM UTC

    This incident has been resolved and team is investigation the cause..

Read the full incident report →

Minor October 16, 2025 Some customers experience high latency in EU region 49m

Started Oct 16, 2025, 09:39 AM UTC· resolved Oct 16, 2025, 10:28 AM UTC

  1. investigating Oct 16, 2025, 09:39 AM UTC

    We are currently investigating this incident..

  2. monitoring Oct 16, 2025, 10:13 AM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Oct 16, 2025, 10:28 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor September 3, 2025 Known authentication errors 23h 13m

Started Sep 03, 2025, 01:07 AM UTC· resolved Sep 04, 2025, 12:20 AM UTC

  1. investigating Sep 03, 2025, 01:07 AM UTC

    We are currently investigating this incident..

  2. identified Sep 03, 2025, 01:37 AM UTC

    We have identified a critical authentication error affecting Social SSO, email and SMS. Enterprise Connections/SSO are not affected..

  3. monitoring Sep 03, 2025, 01:41 AM UTC

    We implemented a fix that resolves the issue and are currently monitoring the result. This is being treated as a serious incident and our team is working urgently..

  4. monitoring Sep 03, 2025, 02:08 AM UTC

    We are currently working on invalidating all sessions that took place during the incident..

  5. identified Sep 03, 2025, 02:19 AM UTC

    There is high latency for the Sydney region currently..

  6. monitoring Sep 03, 2025, 02:22 AM UTC

    Sydney region is operational and user sessions are in the process of being invalidated..

  7. monitoring Sep 03, 2025, 04:00 AM UTC

    \\-- -- Apologies for the broken formatting on this longer update. We will provide a nicer view of this report in the coming days as part of a post mortem -- -- To all the Kinde customers impacted by the authentication incident that occurred today (3 September 2025) at 10:40am Sydney time, we are so sorry for the impact this has had on your businesses. It was entirely our fault. We fu\\\*#ed up. We accidentally introduced an authentication bug during a routine feature deployment. The bug has been fixed and we are swarming to respond and remediate. More updates will be posted to our status page, where you can subscribe to the incident and receive updates. If you have one, please use your dedicated channel in Kinde Slack. \\-- -- Summary -- -- This was not a malicious attack and there was no Kinde data breach. We caused it. Social auth connections were impacted (not enterprise connections). End-users who authenticated during the incident were signed in to a profile that was not theirs. We are working to invalidate all sessions that were signed into during the incident period. This will invalidate auth tokens and force the affected users to sign in again. The deployment was rolled back 68 minutes after the bug appeared, fixing the issue. Users who sign in to your app now, will be unaffected. This is being treated as a security incident due to the impact to users when using our customer’s products, however Kinde has not been breached. \\-- -- What we know -- -- A recent code change was deployed introducing a bug that redirected authenticated users to the wrong profile. They signed in as usual via social authentication, but the bug assigned the incorrect user ID to them when returning to the app. This effectively showed them the profile of another user after the login. Users logging into the Kinde admin were also impacted when using the Google or Github authentication options, and were directed to the incorrect organisation selector. To the best of our knowledge, enterprise connections (such as SAML and MS Entra OAuth2) were not impacted by this bug. \\-- -- Current actions -- -- The bug is fixed. Here’s what we are doing right now: Determining how many users were affected. i.e. the scope of the incident Working out the best remedy (i.e. invalidate invalid sessions) to impact the least users Running diffs with a restored copy of the data prior to the incident for validation Performing a code analysis of the change We will reach out to customers directly with more information, as we have it. \\-- -- Incident timeline - 3 September 2025 -- -- Change deployed at 10:40 am Sydney time First notification of incorrect logins is 11:07 am Sydney time Change reverted at 11:41 am Sydney time Total duration where a user could log into the wrong profile: 61 minutes.

  8. monitoring Sep 03, 2025, 06:02 AM UTC

    The team are continuing to investigate the total breadth of the incident, specifically with the invalidation of logins during the incident. We will continue to update this status page with high level information and directly to customers for information specific to their business..

  9. resolved Sep 03, 2025, 08:04 AM UTC

    We will be closing this incident on the status page, however updates will still be provided here publicly and directly to customers where required. Only users who logged in during the hour long incident window were impacted. The initial bug from this morning was resolved. All impacted sessions and tokens for the Kinde admin have been invalidated. Additionally all customer sessions during the incident window have been invalidated on the Kinde side. We are compiling a list of users impacted and will be reaching out directly to customers to verify if there are any cached access or refresh tokens that need to be invalidated..

  10. resolved Sep 04, 2025, 12:20 AM UTC

    A brief update to the summary from yesterday. Incident window on September 3 between 10:40am to 11:41am Sydney time (12:40am to 01:41am UTC). This was not a malicious attack and there was no Kinde data breach from an external attacker. We caused it. The deployment was rolled back 61 minutes after the bug appeared, fixing the issue. Users who logged in outside of the incident window are not affected. Only OAuth and OIDC type connections were impacted, such as all social authentication connections and the Entra OAuth enterprise connection. Email, username, SMS, and SAML connections were not impacted. There was no cross-business profile exposure. For each of your OAuth2 or OIDC connections, the first user to authenticate during the incident window became the profile for subsequent users on that OAuth2 or OIDC connection. For example, say user 1 authenticated at the beginning of the incident. When any subsequent user authenticated (e.g. user 2, 3, and 4) they were shown the profile for user 1. Less than 100 user profiles globally were exposed by this incident. Sessions and tokens during the incident window were identified and invalidated by the evening of Sep 3 Sydney time. The Kinde team are actively reaching out directly to impacted Kinde businesses who have had authentication sessions during the incident window to provide further information and assistance..

  11. monitoring Sep 08, 2025, 11:47 AM UTC

    **Post-incident report now available.** Following the incident of 3 September 2025, we've now prepared a post-incident report, containing detailed information about the root cause, remedies, future actions, etc. [View post-incident report](https://kinde.com/blog/post-mortem/2025-09-03-authenticated-to-wrong-user-profile). If you have any questions, or need any additional information, please reach out to us by [email](mailto:[email protected]), or in our [Slack](https://join.slack.com/t/thekindecommunity/shared%5Finvite/zt-25gshkj52-AAn0R3V86WWsWkd8IH~~0g) and [Discord](https://discord.gg/wHX6j7wG5d) communities. We're here to support you however we can. Again, we are deeply apologetic for the inconvenience caused to you and your customers. We are making it impossible to happen again..

Read the full incident report →

Minor September 2, 2025 SMS delivery for Sydney region failing 44m

Started Sep 02, 2025, 07:50 AM UTC· resolved Sep 02, 2025, 08:34 AM UTC

  1. investigating Sep 02, 2025, 07:50 AM UTC

    We are currently investigating this incident..

  2. monitoring Sep 02, 2025, 08:10 AM UTC

    We implemented a fix and are currently monitoring the result..

  3. resolved Sep 02, 2025, 08:34 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor August 22, 2025 Access to Kinde admin errors 17m

Started Aug 22, 2025, 07:03 AM UTC· resolved Aug 22, 2025, 07:20 AM UTC

  1. investigating Aug 22, 2025, 07:03 AM UTC

    We are currently investigating this incident..

  2. resolved Aug 22, 2025, 07:20 AM UTC

    Fix has been applied and Kinde admin errors are now resolved.

Read the full incident report →

Minor August 22, 2025 Performance issues with auth 47m

Started Aug 22, 2025, 04:31 AM UTC· resolved Aug 22, 2025, 05:18 AM UTC

  1. investigating Aug 22, 2025, 04:31 AM UTC

    We are currently investigating this incident..

  2. monitoring Aug 22, 2025, 04:39 AM UTC

    We implemented a fix and are currently monitoring..

  3. resolved Aug 22, 2025, 05:18 AM UTC

    This incident has been resolved..

Read the full incident report →

Minor June 4, 2025 SMS 2FA delivery 5h 30m

Started Jun 04, 2025, 10:29 AM UTC· resolved Jun 04, 2025, 03:59 PM UTC

  1. identified Jun 04, 2025, 10:29 AM UTC

    SMS for 2FA are currently not delivering, we have identified an issue with our provider and are working to resolve this..

  2. identified Jun 04, 2025, 01:31 PM UTC

    We're currently working with our upstream SMS provider to resolve the delivery problems.

  3. monitoring Jun 04, 2025, 03:44 PM UTC

    We have resolved the issue with our provider and are currently monitoring the result..

  4. resolved Jun 04, 2025, 03:59 PM UTC

    This incident has been resolved..

Read the full incident report →