- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 100
What to do
Check whether your product depends on Kit. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-05-20 08:26 UTC and 2016-08-14 18:17 UTC may need a replay.Subscribe to Kit's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=convertkit works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Kit 3
- investigating
We're currently investigating an issue with intermittent downtime.
provider
- monitoring
The system's response time is returning to normal. We're still looking into some of the underlying causes.
provider
- resolved
The load on our servers has decreased. We will continue to monitor and investigate the underlying causes for the downtime.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-2f66d863fc
Is Kit still down?
No, this incident was resolved 2016-08-14 18:17 UTC. For Kit's live state, see https://down.guide/convertkit.
How long did it last?
0m, from 2026-05-20 08:26 UTC to 2016-08-14 18:17 UTC, by the times Kit posted.
What caused it?
Kit hasn't published a root cause. If it does, it shows here.
Where does this come from?
Kit's official status page, https://status.kit.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.