New Confluent Cloud account sign-ups temporarily unavailable
New Confluent Cloud account sign-ups are temporarily unavailable. Existing organizations, clusters, and workloads are unaffected and continue to operate normally. We will post an update once sign ups are available.
The latest update from Confluent Cloud.
State
Identified
Started
Ongoing for
2 h 6 min
Worst impact
Maintenance
Timeline
1 updateIdentified
2 h 6 min 100%
Updates
Times in UTCAs posted by Confluent Cloud
New Confluent Cloud account sign-ups are temporarily unavailable. Existing organizations, clusters, and workloads are unaffected and continue to operate normally. We will post an update once sign ups are available.
Affected components
1Confluent Cloud in the last 90 days
Full historyIncidents in 90 days
17
Days with an incident
17
Median duration
3 h 41 min
This incident
Not comparable
Other Confluent Cloud incidents
All incidentsConfluent Cloud·Kafka - Increased latency and connectivity issues - Azure - brazilsouth
Kafka latency increased and connectivity failed on Confluent Cloud in the Azure brazilsouth region. Confluent Cloud reports that the incident is resolved. The incident lasted 2 hours and 9 minutes.
Confluent Cloud·Multiple Confluent Cloud services are in a degraded state - GCP EU-West2
This incident is resolved as of 18:15 UTC on October 20. Confluent Cloud in GCP EU-West2 region is operating normally.
Confluent Cloud·Delay in Kafka cluster provisioning
This incident has been resolved.
Confluent Cloud·Confluent Cloud Console (UI) degraded functionality
This incident has been resolved.
Confluent Cloud·Possible outage in AWS us-east-1
This incident has been resolved. All affected services have fully recovered.
Follow Confluent Cloud
Your coding agent knows when Confluent Cloud is down, and tells you when a failure is theirs, not yours. You can also get Confluent Cloud incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "confluent" and tell me if Confluent Cloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=confluent/feed subscribe https://outages.live/feed.xml?providers=confluentFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane