- Level
- confirmed
- Worst impact
- Degraded
- Components
- MyKinsta analytics servers
- Down Index
- 23of 100
What to do
Check whether you use Kinsta MyKinsta analytics servers. 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 20h 28m it lasted.
Anything that failed between 2026-04-04 03:55 UTC and 2026-04-05 00:23 UTC may need a replay.Subscribe to Kinsta's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=kinsta works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Kinsta 4
- investigating
We are investigating issues with Analytics data which might not be logged at the moment: Visits, Bandwidth, CDN Bandwidth. We'll provide updates as we make progress.
provider
- identified
We have identified the cause of the issue and a solution has been implemented. It will take some time for all data to become present in the analytics system.
provider
- identified
We are continuing to investigate this issue.
provider
- resolved
This incident has been resolved.
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-b53789ed95
Is Kinsta still down?
No, this incident was resolved 2026-04-05 00:23 UTC. For Kinsta's live state, see https://down.guide/kinsta.
How long did it last?
20h 28m, from 2026-04-04 03:55 UTC to 2026-04-05 00:23 UTC, by the times Kinsta posted.
What was affected?
Kinsta named MyKinsta analytics servers.
What caused it?
Kinsta hasn't published a root cause. If it does, it shows here.
Where does this come from?
Kinsta's official status page, https://status.kinsta.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.