Is Aiven down?

Last checked 18m ago
Current status
Aiven is having a partial outage

Active incident: Kafka upgrades to 3.9 are paused

Official status page: https://status.aiven.io · Polled every 5 minutes · 2 components tracked

Aiven is reporting a partial outage right now (last checked 18m ago). Some components are affected; others remain operational.

Real-time Aiven status, recent outages, and incident history — pulled directly from Aiven's official status page at https://status.aiven.io every 5 minutes. Pingoru tracks 2 Aiven services and has captured 6 incidents in the last 90 days (95.56% uptime). Get email, Slack, Discord, or webhook alerts the moment Aiven reports a new incident — free for 5 monitors, no credit card.

Users who monitor Aiven also follow these Database services: Snowflake Supabase Stitch Data ClickHouse Iron.io SolarWinds Observability Neo4j Aura Upstash Pinecone PlanetScale View all 6,000+ providers
Aiven uptime 95.56% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Active incident 1

  1. Ongoing ● 2d 12h
    Started Jun 11, 2026, 03:25 PM UTC
    Timeline · 1 update
    • investigating · Jun 11, 2026, 03:25 PM UTC

      Status: Investigating We have identified an issue affecting KRaft migrations during Kafka upgrades to version 3.9, and have temporarily paused those upgrades while we investigate. If you try to upgrade now, your request will be rejected with an error asking you to contact support. We will re-enable upgrades once the issue is resolved. Impact: Running Kafka services are not affected and continue to operate normally. Customers who attempt to upgrade a Kafka service to version 3.9 or later will receive an HTTP 403 error and the upgrade will not proceed. No data or service availability is impacted.

    Latest: Status: Investigating We have identified an issue affecting KRaft migrations during Kafka upgrades to version 3.9, and have temporarily paused those upgrades while we investigate. …

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jun 09, 2026, 04:57 PM UTC · Resolved Jun 09, 2026, 04:57 PM UTC
    Aiven
    Timeline · 5 updates
    • investigating · Jun 09, 2026, 03:10 PM UTC

      Status: Investigating Aiven engineers are currently investigating a bug on Aiven for PostgreSQL that causes affected cluster fail to take backups and restore from backup. Known affected clouds are AWS and DigitalOcean. Thank you for your patience as we continue our work on this incident. Affected components Aiven (Partial outage)

    • identified · Jun 09, 2026, 03:57 PM UTC

      Status: Identified Our team has identified a potential root cause and is working to fix the issue on the affected services. Affected components Aiven (Partial outage)

    • monitoring · Jun 09, 2026, 04:18 PM UTC

      Status: Monitoring The fix has been applied to the affected services, and Aiven will continue to monitor to confirm that no further action is needed. Thank you for your patience. Affected components Aiven (Partial outage)

    • monitoring · Jun 09, 2026, 04:36 PM UTC

      Status: Monitoring Correction: Aiven for Apache Kafka services as well as Aiven for PostgreSQL services were affected. All services identified to have the issue have been fixed as per the previous status message. Affected components Aiven (Partial outage)

    • resolved · Jun 09, 2026, 04:57 PM UTC

      Status: Resolved The monitoring period has passed without further evidence of the issue occurring. Incident has been declared resolved. Affected components Aiven (Operational)

    Latest: Status: Resolved The monitoring period has passed without further evidence of the issue occurring. Incident has been declared resolved. Affected components Aiven (Operational)

  2. Resolved
    Started May 25, 2026, 03:54 AM UTC · Resolved May 25, 2026, 03:54 AM UTC
    Aiven
    Timeline · 3 updates
    • investigating · May 25, 2026, 02:29 AM UTC

      Status: Investigating We are experiencing an issue affecting service operations across Azure regions. While existing services remain up and running, operations such as service creation, plan changes, and scheduled maintenance are currently failing. We are actively working on a fix to restore full functionality as quickly as possible. We will continue to update here on the progress of this issue. Affected components Aiven (Partial outage)

    • identified · May 25, 2026, 03:48 AM UTC

      Status: Identified We have identified the root cause and are currently deploying a fix to resolve the issues affecting service operations across Azure regions. While existing services remain up and running, operations such as service creation, plan changes, and maintenance updates are currently failing. We are monitoring the deployment closely to ensure full functionality is restored as quickly as possible. We will continue to update here on the progress of this issue. Affected components Aiven (Partial outage)

    • resolved · May 25, 2026, 03:54 AM UTC

      Status: Resolved We have resolved the underlying cause of the issue affection service operations in our Azure regions. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one. Affected components Aiven (Operational)

    Latest: Status: Resolved We have resolved the underlying cause of the issue affection service operations in our Azure regions. Should any further issues be encountered, please reach out to…

  3. Resolved
    Started May 20, 2026, 02:38 AM UTC · Resolved May 20, 2026, 02:38 AM UTC
    Aiven
    Timeline · 2 updates
    • investigating · May 20, 2026, 01:15 AM UTC

      Status: Investigating We are experiencing performance degradation and node unresponsiveness affecting some Aiven services hosted in the DigitalOcean NYC3 region. This is tied to an underlying infrastructure issue currently being tracked by our cloud provider. You can monitor their infrastructure health directly on the DigitalOcean Status Page: https://status.digitalocean.com/incidents/spgd2scvttth Our engineering team is actively investigating the extent of the impact on our services and working to mitigate issues where possible. Affected components Aiven (Degraded performance)

    • resolved · May 20, 2026, 02:38 AM UTC

      Status: Resolved This issue is now resolved. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this issue. Affected components Aiven (Operational)

    Latest: Status: Resolved This issue is now resolved. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused …

  4. Resolved
    Started May 15, 2026, 11:13 PM UTC · Resolved May 15, 2026, 11:13 PM UTC
    Timeline · 5 updates
    • investigating · May 14, 2026, 06:55 AM UTC

      Status: Investigating We are currently aware of an issue affecting Aiven for Kafka services. Our teams are currently investigating the root cause as a priority. We will continue to provide status updates as they become available.

    • identified · May 14, 2026, 07:36 AM UTC

      Status: Identified We have identified the root cause of the issue affecting multiple Aiven for Apache Kafka services and are currently working to restore the affected services. Our teams are actively applying fixes and will continue to provide updates as progress is made.

    • monitoring · May 14, 2026, 10:49 AM UTC

      Status: Monitoring We have applied a fix to the affected services and are seeing recovery progress. Our team is closely monitoring the platform and will continue to mitigate any remaining impact if needed.

    • monitoring · May 14, 2026, 03:13 PM UTC

      Status: Monitoring Our team has seen the impacted services recover, and we are now closely monitoring for any remaining impact.

    • resolved · May 15, 2026, 11:13 PM UTC

      Status: Resolved We have resolved the underlying cause of the kafka service disruption. Should any further issues be encountered, please reach out to support via the Aiven console. We apologise for the inconvenience caused by this issue, and commit to analysing and improving our platform to avoid future incidents similar to this one.

    Latest: Status: Resolved We have resolved the underlying cause of the kafka service disruption. Should any further issues be encountered, please reach out to support via the Aiven console.…

  5. Resolved
    Started Apr 02, 2026, 11:23 AM UTC · Resolved Apr 02, 2026, 11:23 AM UTC
    Aiven
    Timeline · 5 updates
    • monitoring · Mar 01, 2026, 11:12 PM UTC

      Status: 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

    • monitoring · Mar 02, 2026, 08:16 AM UTC

      Status: 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

    • monitoring · Mar 02, 2026, 03:38 PM UTC

      Status: 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

    • monitoring · Mar 03, 2026, 03:01 AM UTC

      Status: 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 Affected components Aiven (Partial outage)

    • resolved · Apr 02, 2026, 11:23 AM UTC

      Status: 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 Affected components Aiven (Operational)

    Latest: Status: 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 disable…

See the full Aiven outage history

1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Aiven outage history →

Or sign up free to get alerts when Aiven breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 6 incidents View full outage history →