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 | 60 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 “Aiven Console and API are down”. 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
Aiven Console and API are down
major resolved · started · resolved
5 updates
- investigating
We are aware of an issue affecting the Aiven API. The Aiven Console, the Aiven CLI, the Terraform provider and any custom scripts or integrations all run through this same API, so customers may see errors across any of them. You may experience being unable to load or sign in to the Console, and failures when creating, modifying or querying services. Our engineering team is investigating and work to restore service is underway. We will provide a further update within 30 minutes, or sooner if there is news to share. We apologise for the disruption.
- identified
We have identified the cause of this issue and a fix is now being rolled out across our API nodes in stages. The Aiven Console and API are already working again for some customers. Until the rollout completes you may still see intermittent sign-in failures, or errors when creating, modifying or querying services via the Console, CLI, Terraform provider or direct API calls. Retrying will often succeed. We will confirm here once the rollout is complete. Thank you for your patience.
- identified
The rollout of the fix is still progressing across our API nodes. Most customers should now find the Aiven Console, API, CLI and Terraform provider working normally, and we expect any remaining errors to clear as the rollout completes. We will confirm here once it is complete. Thank you for your patience.
- monitoring
This incident is now resolved. Between approximately 00:10 and 02:05 UTC on 22 September, an issue affecting our public API endpoints caused sign-in failures and errors for customers using the Aiven Console, the Aiven API, the CLI, the Terraform provider and other API-based integrations. The issue was corrected and we have seen no further errors during our monitoring period. We are following up with additional changes to prevent this from recurring. We apologise for the disruption. If you are still seeing problems, please contact Aiven support.
- resolved
This incident is now resolved. Earlier today a certificate problem affecting our public API endpoints caused sign-in failures and errors for customers using the Aiven Console, the Aiven API, the CLI, the Terraform provider and other API-based integrations. A corrected certificate has been in place across all API nodes since 02:05 UTC, and we have seen no further errors during our monitoring period. We are following up with a permanent fix to prevent this from recurring. We apologize for the disruption. If you are still seeing problems, please contact Aiven support at [support@aiven.io](mailto:support@aiven.io)
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.