Skip to content
UpButler
ProductAgentsStatus pagesDocsPricing
Sign inStart free

Is Confluent Cloud down?

Confluent Cloud has a partial outage

Right now

Partly. Experiencing high error rate in AZURE in West Europe region.

Last checked (2026-10-10 07:16 UTC) from status.confluent.cloud · every 180s

For agents

fallback

Use a fallback, next attempt in 300s.

GET upbutler.com/status/confluent/status.agent.json

MCP: upstream_status {"service":"confluent"}

Managed Kafka, Flink and connectors.

What Confluent Cloud says

Partial outage· 1 open incident

Taken as is from Confluent Cloud's own status page API. Incident titles and component names below are theirs.

Open status.confluent.cloud

What UpButler measured

There is no keyless endpoint of Confluent Cloud that says anything useful, so UpButler does not probe it. To check your own Confluent Cloud account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Confluent Cloud

Text written by Confluent Cloud, shown unchanged.

Which part of Confluent Cloud?

Confluent Cloud components

1 of 1 not operational

  • Confluent CloudPartial outage

Confluent Cloud incidents, last 90 days

  1. 2026-07-13: no record
  2. 2026-07-14: no record
  3. 2026-07-15: no record
  4. 2026-07-16: no record
  5. 2026-07-17: no record
  6. 2026-07-18: no record
  7. 2026-07-19: no record
  8. 2026-07-20: no record
  9. 2026-07-21: no record
  10. 2026-07-22: no record
  11. 2026-07-23: no record
  12. 2026-07-24: no record
  13. 2026-07-25: no record
  14. 2026-07-26: no record
  15. 2026-07-27: no record
  16. 2026-07-28: no record
  17. 2026-07-29: no record
  18. 2026-07-30: no record
  19. 2026-07-31: no record
  20. 2026-08-01: no record
  21. 2026-08-02: no record
  22. 2026-08-03: no record
  23. 2026-08-04: no record
  24. 2026-08-05: no record
  25. 2026-08-06: no record
  26. 2026-08-07: no record
  27. 2026-08-08: no record
  28. 2026-08-09: no record
  29. 2026-08-10: no record
  30. 2026-08-11: no record
  31. 2026-08-12: no record
  32. 2026-08-13: no record
  33. 2026-08-14: no record
  34. 2026-08-15: no record
  35. 2026-08-16: no record
  36. 2026-08-17: no record
  37. 2026-08-18: no record
  38. 2026-08-19: no record
  39. 2026-08-20: no record
  40. 2026-08-21: no record
  41. 2026-08-22: no record
  42. 2026-08-23: no record
  43. 2026-08-24: no record
  44. 2026-08-25: no record
  45. 2026-08-26: no record
  46. 2026-08-27: no record
  47. 2026-08-28: no record
  48. 2026-08-29: no record
  49. 2026-08-30: no record
  50. 2026-08-31: no record
  51. 2026-09-01: no record
  52. 2026-09-02: no record
  53. 2026-09-03: no record
  54. 2026-09-04: no record
  55. 2026-09-05: no record
  56. 2026-09-06: no record
  57. 2026-09-07: no record
  58. 2026-09-08: no record
  59. 2026-09-09: no record
  60. 2026-09-10: no record
  61. 2026-09-11: no record
  62. 2026-09-12: no record
  63. 2026-09-13: no record
  64. 2026-09-14: no record
  65. 2026-09-15: no record
  66. 2026-09-16: no record
  67. 2026-09-17: no record
  68. 2026-09-18: no record
  69. 2026-09-19: no record
  70. 2026-09-20: no record
  71. 2026-09-21: no record
  72. 2026-09-22: no record
  73. 2026-09-23: no record
  74. 2026-09-24: no record
  75. 2026-09-25: no record
  76. 2026-09-26: minor incident
  77. 2026-09-27: major incident
  78. 2026-09-28: no incident reported
  79. 2026-09-29: no incident reported
  80. 2026-09-30: no incident reported
  81. 2026-10-01: no incident reported
  82. 2026-10-02: no incident reported
  83. 2026-10-03: no incident reported
  84. 2026-10-04: no incident reported
  85. 2026-10-05: no incident reported
  86. 2026-10-06: no incident reported
  87. 2026-10-07: no incident reported
  88. 2026-10-08: major incident
  89. 2026-10-09: major incident
  90. 2026-10-10: major incident
2026-07-135 of 15 days with an incidenttoday

Each bar is a day, coloured by the worst incident Confluent Cloud reported. It is their incident record, not a measurement of uptime.

Incidents
4
3 major or critical
Typical time to resolve
56 min
median
Nine in ten within
—
major ones: 56 min
Longest
13 h 4 min
record since 2026-09-26
Started (UTC)IncidentImpactLasted
Possible outage in AWS us-east-1major56 min
Experiencing high error rate in AZURE in Germany West Central regionmajor56 min
Missing Metrics on Confluent Cloudmajorunder a minute
Elevated error rates in Azure East USminor13 h 4 min

Get alerted when Confluent Cloud goes down

No account. One email when Confluent Cloud reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add Confluent Cloud as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Confluent Cloud's current status in a README or an internal wiki. It updates by itself.

Confluent Cloud status badge

[![Confluent Cloud status](https://upbutler.com/status/confluent/badge.svg)](https://upbutler.com/status/confluent)

Tell your outage from Confluent Cloud's

Declare that your project depends on Confluent Cloud. When one of your monitors fails while Confluent Cloud has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start freeHow it works
upbutler.yaml
# upbutler.yaml
dependencies:
  - confluent
Ask before you retry
curl -s https://upbutler.com/status/confluent/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "confluent",
  "verdict": "fallback",
  "status": "partial_outage",
  "reason": "Experiencing high error rate in AZURE in West Europe region",
  "retryAfterSec": 300,
  "incident": {
    "title": "Experiencing high error rate in AZURE in West Europe region",
    "url": "https://status.confluent.cloud/incidents/07y1w8m52p0q"
  },
  "probe": null
}

Questions

Is Confluent Cloud down right now?
Partly. As of 2026-10-10 07:16 UTC, Confluent Cloud has a partial outage, with an open incident: "Experiencing high error rate in AZURE in West Europe region". This page reads the status again every 3 minutes.
How long do Confluent Cloud outages usually last?
Of the 4 incidents Confluent Cloud reported in the last 90 days, half were resolved within 56 min; the longest took 13 h 4 min. Incidents rated major or critical typically took 56 min. These are the provider's own start and end times.
Where does this status come from?
From Confluent Cloud's own status page API at https://status.confluent.cloud. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Confluent Cloud's words.
Can I get an alert when Confluent Cloud goes down?
Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Confluent Cloud reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/confluent/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Confluent Cloud status?
Fetch https://upbutler.com/status/confluent/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"confluent"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Confluent Cloud's?
Add "confluent" to the dependencies of your UpButler workspace. When one of your monitors fails while Confluent Cloud has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Confluent Cloud. Status and incident text belong to Confluent Cloud and are read from their public status source; the probe result is UpButler's own measurement.