What to check if Confluent Cloud is unreachable

Resolution

1. Check the Status Page for current issues, any updates will be posted there

https://status.confluent.cloud/

You can also subscribe to any updates to ensure you get the latest status, directly into your Inbox.

2. Check your Clients are configured as recommended, to handle upgrades and maintenance tasks

https://docs.confluent.io/cloud/current/client-apps/config-client.html#configuring-clients-for-cluster-rolls

During a cluster roll, Clients may encounter the following retryable exceptions, which will generate warnings on incorrectly configured Clients, more details can be found within the above link.

UNKNOWN_TOPIC_OR_PARTITION: "This server does not host this topic-partition."
LEADER_NOT_AVAILABLE: "There is no leader for this topic-partition as we are in the middle of a leadership election."
NOT_LEADER_FOR_PARTITION: "This server is not the leader for that topic-partition."
NOT_ENOUGH_REPLICAS: "Messages are rejected since there are fewer in-sync replicas than required."
NOT_ENOUGH_REPLICAS_AFTER_APPEND: "Messages are written to the log, but to fewer in-sync replicas than required."

3. Test connectivity to Confluent Cloud

https://docs.confluent.io/cloud/current/networking/testing.html#test-connectivity-to-ccloud

Please include the result of the above tests into the Confluent Support Case, if you end up needing to create one.

4. Test connectivity to Confluent Cloud with Private Link

https://docs.confluent.io/cloud/current/networking/private-links/aws-privatelink.html#validate-connectivity-to-ccloud

https://docs.confluent.io/cloud/current/networking/private-links/azure-privatelink.html#validate-connectivity-to-ccloud

Please include the result of the above tests into the Confluent Support Case, if you end up needing to create one.

5. Open up a Case with Confluent Support

If you been through the above and still feel you need to create a Case with Confluent Support, please attach as much of the following as possible, to help us troubleshoot the issue effectively:

• Client configurations
• Client DEBUG logfiles
• Client used library
• Client version
• Timeframe when you had connectivity Issues
• Confluent Cloud Cluster ID (lkc-* / pkc-*)
• Connectivity test results

Note: If you don‘t have a valid support subscription you will still be able to create a support ticket as a „Cloud Outage Report“. This type of Support Case does not include expert technical support guidance but Confluent will check internally for issues with your Confluent Cloud hosted Cluster and loop back with you once validated.