Kinde - Notice history

All systems operational

Notice history

2026 Jun

[Third Party] x.com auth experiencing issue
  • Resolved
    Resolved

    x.com OAuth2 is now resolving and working.

  • Identified
    Identified

    x.com OAuth2 is currently experiencing issues resulting in a too many redirect errors.

    If you rely or use x.com login on your application, please reach to support and we will assist with your options.

Degraded performance
  • Resolved
    Resolved

    This incident has been resolved and our identified the issue.

  • Investigating
    Investigating
    We are currently investigating this incident.

2026 May

No notices reported this month

2026 Apr

High latency for AU region
  • Resolved
    Resolved

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

  • Monitoring
    Monitoring

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

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

  • Resolved
    Resolved

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

  • Update
    Update

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

  • Monitoring
    Monitoring

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

  • Investigating
    Investigating
    We are currently investigating this incident.
500 errors on auth flow
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified
    We are continuing to work on a fix for this incident.
  • Resolved
    Resolved
    This incident has been resolved.
High latency for AU region
  • Resolved
    Resolved

    This incident has been resolved. We will continue to monitor latency internally.

  • Monitoring
    Monitoring

    Latency has returned to normal. We are currently monitoring the result.

  • Investigating
    Investigating
    We are currently investigating this incident.
Increased errors
  • Resolved
    Resolved

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

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

2026 Apr to 2026 Jun

Next