Skip to content
OutageDeck

Incident detail

Service Disruption affecting Authentication, Schema Registry, ksqlDB, and Flink in AWS us-east-1

Active incidentMinor1 affected service

Timeline window

Started

Get alerted the next time Confluent Cloud breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Confluent Cloud alerts work

Timeline

Incident updates

Every update Confluent Cloud posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

    We are investigating a service disruption affecting multiple services in AWS us-east-1 region. Affected customers may experience authentication failures, errors accessing Schema Registry, or issues with KSQL and Flink workloads. We are actively investigating the root cause and working toward mitigation.

  2. Identified

    The issue has been identified and a fix is being implemented.

  3. Investigating

    We are currently investigating this issue.

  4. Identified

    The issue has been identified and a fix is being implemented.

  5. Identified

    We continue to work on remediating the service disruption in AWS us-east-1.

    Confirmed impact:

    • Authentication — a subset of requests may fail
    • Schema Registry — authorization errors on a subset of requests
    • ksqlDB — a subset of queries/requests may be affected
    • Flink — statement management operations (create/update/delete) are degraded, and some running Flink jobs may fail or restart
    • Kafka operations (create, delete etc)

    Not impacted: Kafka cluster data-plane operations are not affected by this incident. This issue is isolated to the AWS us-east-1 region; other regions are unaffected

  6. Identified

    We continue to work on remediating the service disruption in AWS us-east-1. Not confirmed ETA at this time.

  7. Identified

    Confluent is continuing to work on remediating the service disruption in AWS us-east-1.

Keep exploring

More from Confluent Cloud

Neighboring incidents on Confluent Cloud's timeline and the rest of their record on OutageDeck.

← Older incident

Investigating Elevated Errors in GCP us-central1

Newer incident →

Connectivity degradation - AWS us-east-1

All Confluent Cloud incidentsConfluent Cloud live status