Kinsta: Bot Management - Increased False Positives

What to do

Check whether you use Kinsta Cloudflare Integration. 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 3h 53m it lasted.
Anything that failed between 2026-06-03 03:22 UTC and 2026-06-03 07:15 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.

monitoringJun 3, 2026, 3:22 AM UTC
Our service partner, Cloudflare, is currently experiencing an issue in which certain legitimate requests are being incorrectly assigned a low bot score. As a result, some requests may be blocked by our Bot Protection feature if it is enabled on the site. A fix has been released, and we are closely monitoring its results. You may also follow the link to Cloudflare's status page: https://www.cloudflarestatus.com/incidents/3xzf6gwrv137.
provider
monitoringJun 3, 2026, 7:13 AM UTC
We are continuing to monitor the situation. Thank you for your patience.
provider
resolvedJun 3, 2026, 7:15 AM UTC
This incident has been resolved.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Kinsta still down?

No, this incident was resolved 2026-06-03 07:15 UTC. For Kinsta's live state, see https://down.guide/kinsta.

How long did it last?

3h 53m, from 2026-06-03 03:22 UTC to 2026-06-03 07:15 UTC, by the times Kinsta posted.

What was affected?

Kinsta named Cloudflare Integration.

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.