Provider
KindeIncident detail
UK data region
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 a
Resolved incidentMajor3 affected services
Timeline window
to
Get alerted the next time Kinde breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Identified
UK data region
Identified
We are continuing to work on a fix for this incident.
Resolved
This incident has been resolved.
Resolved
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.
Keep exploring
More from Kinde
Neighboring incidents on Kinde's timeline and the rest of their record on OutageDeck.