Skip to content
OutageDeck

Incident detail

Elevated error rates in AWS me-south-1 and me-central-1 regions

Resolved incidentMajor1 affected service

Timeline window

to

Outage alerts

Get alerted the next time Confluent Cloud breaks

Free email alerts for up to 5 providers. 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 experiencing increased error rates in some of our Confluent Cloud services in AWS me-south-1 and me-central-1 regions. This began at approximately 05:00 AM UTC today and is linked to disruptions in AWS’s availability zones in these regions (mec1-az1, mec1-az3 and mes1-az2). Team is currently working on mitigating these and will provide updates as the situation evolves.

  2. Investigating

    Confluent Cloud services in AWS me-central-1 region are experiencing a major outage. They are linked to AWS's me-central-1 regional outage

    Confluent Cloud services in AWS me-south-1 are being mitigated.

  3. Monitoring

    Confluent cloud services in AWS me-south-1 are mitigated. They are currently being monitored.

    Confluent Cloud Services in AWS me-central-1 are still disrupted owing to regional outage at AWS.

  4. Monitoring

    Confluent Cloud services in AWS me-south-1 remain stable and operating normally following mitigation. We continue to monitor for any residual issues.

    Confluent Cloud services in AWS me-central-1 continue to experience a complete outage due to the ongoing AWS regional infrastructure failure in that region.

  5. Monitoring

    AWS regional recovery is expected to be extended in both me-central-1 and me-south-1 regions. Customers requiring immediate restoration in these two regions are encouraged to review regional failover options.

  6. 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.

← Older incident

Elevated Error Rates in AWS me-central-1 region

Newer incident →

Metrics API was experiencing failures from 03:23 UTC to 03:58 UTC

All Confluent Cloud incidentsConfluent Cloud live status