outages.live
Live
AivenIncident · 2026-10-16 08:40 UTC

Issues starting new service nodes

ResolvedOfficial update

This incident has been resolved. New service nodes are able to start normally again, and running nodes were not affected at any point during the incident. We apologize for any inconvenience this may have caused.

The latest update from Aiven.

State

Resolved

Started

17 d ago

2026-10-16 08:40 UTC

Lasted

4 h 51 min

until 2026-10-16 13:31 UTC

Worst impact

Notice

Timeline

3 updates
08:4009:5211:0512:1813:31
NoticeUpdate postedTimes in UTC

Investigating

1 h 17 min 26%

Monitoring

3 h 34 min 74%

Updates

Times in UTC

As posted by Aiven

Resolved2026-10-16 13:31 UTC

This incident has been resolved. New service nodes are able to start normally again, and running nodes were not affected at any point during the incident. We apologize for any inconvenience this may have caused.

Monitoring2026-10-16 09:56 UTC

A fix has been implemented and we are currently monitoring the results. New service nodes are able to start again, and running nodes were not affected at any point. We will provide further updates once we have confirmed the issue is fully resolved.

Investigating2026-10-16 08:40 UTC

We are currently experiencing an issue with starting new service nodes for almost all service types. The running nodes are not affected. Our engineering team is actively working on a fix and we will provide another update as soon as we have more information.

Follow Aiven

Your coding agent knows when Aiven is down, and tells you when a failure is theirs, not yours. You can also get Aiven incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "aiven" and tell me if Aiven has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=aiven
Slack
/feed subscribe https://outages.cc/feed.xml?providers=aiven

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane