← Live dashboard

Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Apr 24, 2026, 05:18 PM · Resolved Apr 25, 2026, 12:14 AM

This incident has been resolved.

Confluent Cloud live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Confluent Cloud now? Check the current status

Affected services

Confluent Cloud

Updates (5)

  1. Apr 25, 2026, 12:14 AM
    Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements

    This incident has been resolved.

    Confluent Cloud ↗
  2. Apr 24, 2026, 11:06 PM
    Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements

    A fix has been implemented and we are monitoring for next hour.

    Confluent Cloud ↗
  3. Apr 24, 2026, 10:27 PM
    Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements

    Roll out of fix is progressing, expecting all clusters to complete in approximately 30 minutes.

    Confluent Cloud ↗
  4. Apr 24, 2026, 08:14 PM
    Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements

    The issue has been identified and fix is being rolled out. ETA for rollout complete across impacted regions 2 hours.

    Confluent Cloud ↗
  5. Apr 24, 2026, 05:18 PM
    Some customers using Confluent Cloud Flink on Azure with PrivateLink connectivity are experiencing issues submitting new Flink statements

    We are currently investigating this issue.

    Confluent Cloud ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Confluent Cloud's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.