Operational Aiven status
aiven.io · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Aiven looks fine itself, but Amazon Web Services, a provider it may run on (inferred), reports major outage. Watch for knock-on effects.
confidence: low Vendor: operational · users: normal · routing: no data · upstream providers: major.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Amazon Web Services: Major outage
- CISA KEV (context) no recent entries for this vendor
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 65 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Creation of new service nodes disrupted”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- Amazon Web Services reports an issue. Aiven may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside Aiven's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data · upstream providers: major. Vendor status and outside signals roughly agree.
Who depends on whom
Aiven may run on Amazon Web Services, Google Cloud, Microsoft Azure (inferred). We don't map other services that depend on Aiven. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Aiven or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Aiven. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Creation of new service nodes disrupted
minor resolved · started · resolved
4 updates
- investigating
We are investigating issues with creating new nodes for services on the Aiven platform currently. The effect is slower creation time for new nodes. Any any event where a new node is created are impacted such as failovers, switchovers, upgrades and maintenance updates. Our engineers are currently investigating the root cause and working on a fix for the issue. We apologise for the inconvenience caused by this issue. We will provide a further update as our team continues on the solution for this situation.
- monitoring
We are monitoring our mitigating actions to issues with creating new nodes for services on the Aiven platform. Our engineers have done mitigating steps and we see improvements in the node creation, but we'll continue investigating and monitoring of the issue. We apologise for the inconvenience caused by this issue. We will provide a further update as our team continues monitoring and triaging this situation.
- monitoring
We have completed our mitigating actions and the creation of new nodes for services on the Aiven platform has returned to normal. Customers can now proceed with any operations that were delayed during this issue, including service creation, scaling, upgrades, maintenance updates and configuration changes. Operations that were left pending should continue automatically. Our engineers continue to monitor the platform to confirm the issue is fully resolved. We apologise for the inconvenience caused by this issue. We will provide a further update as our team completes monitoring of this situation.
- resolved
We have resolved the underlying cause of the new node creation and new nodes are able to be created without issues. 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.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.