- Level
- confirmed
- Worst impact
- Degraded
- Components
- Confluent Cloud
- Regions
- us, us-central1
- Down Index
- 40of 100
What to do
Check whether you use Confluent Cloud Confluent Cloud in us, us-central1. 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 2h 58m it lasted.
Anything that failed between 2026-07-17 22:01 UTC and 2026-07-18 00:59 UTC may need a replay.Subscribe to Confluent Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=confluent works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Confluent Cloud 4
- investigating
Flink statements are degraded in GCP us-central1 region. The impact started at 18:37 UTC on July 17. Currently, engineers are investigating the issue.
provider
- identified
Engineers have identified and implemented a fix.
provider
- monitoring
Currently, we are monitoring the results after rolling out the fix.
provider
- resolved
All the statements should be running now.
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-3607c0ed55
Is Confluent Cloud still down?
No, this incident was resolved 2026-07-18 00:59 UTC. For Confluent Cloud's live state, see https://down.guide/confluent.
How long did it last?
2h 58m, from 2026-07-17 22:01 UTC to 2026-07-18 00:59 UTC, by the times Confluent Cloud posted.
What was affected?
Confluent Cloud named Confluent Cloud in us, us-central1.
What caused it?
Confluent Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
Confluent Cloud's official status page, https://status.confluent.cloud, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.