Aiven incident

Service operations affected in Azure

Minor Resolved View vendor source →

Aiven experienced a minor incident on May 25, 2026 affecting Aiven, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 25, 2026, 03:54 AM UTC
Resolved
May 25, 2026, 03:54 AM UTC
Duration
Detected by Pingoru
May 25, 2026, 03:54 AM UTC

Affected components

Aiven

Update timeline

  1. 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)

  2. 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)

  3. 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)