- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- me-central-1, me-south-1
- Down Index
- 41of 100
What to do
Check whether you use Aiven in me-central-1, me-south-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 31d 12h it lasted.
Anything that failed between 2026-03-01 23:12 UTC and 2026-04-02 11:23 UTC may need a replay.Subscribe to Aiven's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=aiven works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Aiven 5
- monitoring
Amazon Web Services (AWS) currently has an outage that is impacting deployments of services in the ME-CENTRAL-1 Region (mec1-az2) specifically. Aiven provides the capability to let users move their workloads off this region, and we would recommend that users do so. For more information please see the AWS status page: https://health.aws.amazon.com/health/status
provider
- monitoring
Amazon Web Services (AWS) currently has an outage that is impacting deployments of services in the ME-CENTRAL-1 Region. Aiven provides the capability to let users move their workloads off this region, and we would recommend that users do so. For more information please see the AWS status page: https://health.aws.amazon.com/health/status
provider
- monitoring
Amazon Web Services (AWS) currently has an outage that is impacting deployments of services in the ME-CENTRAL-1 Region. We have disabled the creation of new nodes and services in this region. AWS has advised that users run their Disaster Recovery Plans for AWS products and services in that region and we are recommending the same. For more information please see the AWS status page: [https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status "https://health.aws.amazon.com/health/status")
provider
- monitoring
Amazon Web Services (AWS) currently has an outage that is impacting deployments of services in the ME-CENTRAL-1 and ME-SOUTH-1 regions. We have disabled the creation of new nodes and services in both of these regions. AWS has advised that users run their Disaster Recovery Plans for AWS products and services in both of these regions and we are recommending the same. For more information please see the AWS status page: https://health.aws.amazon.com/health/status
provider
- resolved
The underlying issues with Amazon Web Services (AWS) in the **ME-CENTRAL-1** and **ME-SOUTH-1** regions are ongoing, and AWS continues to work on recovery. We have disabled the creation of new services and nodes in the affected regions to prevent further impact. We recommend our customers to migrate their services to a stable region as part of their disaster recovery plan. As there are no further actions we can take at this time, we are moving this incident to a resolved state on our status page. The recovery of these regions is fully dependent on AWS. We will make **ME-CENTRAL-1** and **ME-SOUTH-1** regions available again for Aiven services once AWS confirms they are fully restored and stable. We recommend customers continue to monitor the official AWS Health Status Page for updates. https://health.aws.amazon.com/health/status
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-948ae732ef
Is Aiven still down?
No, this incident was resolved 2026-04-02 11:23 UTC. For Aiven's live state, see https://down.guide/aiven.
How long did it last?
31d 12h, from 2026-03-01 23:12 UTC to 2026-04-02 11:23 UTC, by the times Aiven posted.
What was affected?
Aiven named in me-central-1, me-south-1.
What caused it?
Aiven hasn't published a root cause. If it does, it shows here.
Where does this come from?
Aiven's official status page, https://status.aiven.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.