Skip to content

Incident detail

Performance degradation for resources in GCP us-central1-a

Resolved incidentCritical1 affected service

Timeline window

to

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.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    This manifests itself as networking errors on affected clusters. We are currently investigating and attempting to mitigate or provide a work-around.

  2. Investigating

    Affected resources are limited to a single zone in GCP, us-central1-a. We are continuing to investigate.

  3. Investigating

    GCP has confirmed that starting, August 6th 12:46 PM UTC, us-central1 is experiencing packet loss causing elevated latency and errors. GCP have communicated that they will provide an update shortly

  4. Investigating

    Resources in multiple zones in GCP us-central1 are affected. We are continuing to investigate

  5. Monitoring

    Many clusters in the affected region are recovering. We are continuing to monitor.

  6. Monitoring

    We are seeing mitigation for all impacted Kafka clusters in GCP us-central1 and are continuing to monitor.

  7. Resolved

    This incident has been resolved.

Keep exploring

More from Confluent Cloud

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