User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
confluent.cloud · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Tests confluent.cloud from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 1014 ms · 9 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:00 | 0 | 0.0 | 1103 ms | 0 |
| 03:15 | 0 | 0.0 | 396 ms | 0 |
| 03:30 | 0 | 0.0 | 1246 ms | 0 |
| 03:45 | 0 | 0.0 | 698 ms | 0 |
| 04:00 | 0 | 0.0 | 899 ms | 0 |
| 04:15 | 0 | 0.0 | 840 ms | 0 |
| 04:30 | 0 | 0.0 | 580 ms | 0 |
| 04:45 | 0 | 0.0 | 981 ms | 0 |
| 05:00 | 0 | 0.0 | 1170 ms | 0 |
| 05:15 | 0 | 0.0 | 853 ms | 0 |
| 05:30 | 0 | 0.0 | 824 ms | 0 |
| 05:45 | 0 | 0.0 | 407 ms | 0 |
| 06:00 | 0 | 0.0 | 1029 ms | 0 |
| 06:15 | 0 | 0.0 | 554 ms | 0 |
| 06:30 | 0 | 0.0 | 462 ms | 0 |
| 06:45 | 0 | 0.0 | 605 ms | 0 |
| 07:00 | 0 | 0.0 | 1066 ms | 0 |
| 07:15 | 0 | 0.0 | 905 ms | 0 |
| 07:30 | 0 | 0.0 | 792 ms | 0 |
| 07:45 | 0 | 0.0 | 576 ms | 0 |
| 08:00 | 0 | 0.0 | 1012 ms | 0 |
| 08:15 | 0 | 0.0 | 1025 ms | 0 |
| 08:30 | 0 | 0.0 | 685 ms | 0 |
| 08:45 | 0 | 0.0 | 949 ms | 0 |
| 09:00 | 0 | 0.0 | 626 ms | 0 |
| 09:15 | 0 | 0.0 | 341 ms | 0 |
| 09:30 | 0 | 0.0 | 283 ms | 0 |
| 09:45 | 0 | 0.0 | 996 ms | 0 |
| 10:00 | 0 | 0.0 | 544 ms | 0 |
| 10:15 | 0 | 0.0 | 908 ms | 0 |
| 10:30 | 0 | 0.0 | 857 ms | 0 |
| 10:45 | 0 | 0.0 | 450 ms | 0 |
| 11:00 | 0 | 0.0 | 767 ms | 0 |
| 11:15 | 0 | 0.0 | 642 ms | 0 |
| 11:30 | 0 | 0.0 | 632 ms | 0 |
| 11:45 | 0 | 0.0 | 508 ms | 0 |
| 12:00 | 0 | 0.0 | 657 ms | 0 |
| 12:15 | 0 | 0.0 | 931 ms | 0 |
| 12:30 | 0 | 0.0 | 952 ms | 0 |
| 12:45 | 0 | 0.0 | 418 ms | 0 |
| 13:00 | 0 | 0.0 | 588 ms | 0 |
| 13:15 | 0 | 0.0 | 1014 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Confluent yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Confluent goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Confluent alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Confluent is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Confluent's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.