Unrated
identified
since
API requests failing/timing out
The issue has been mitigated, and our Engineering team is working on a permanent fix.
Latest update 10 hours ago
Is Aiven Down?
Partially — Aiven is degraded
- Aiven's status page
- Open incident · unrated incident (“API requests failing/timing out”)
- FlareWarden checks
- Website reachable · 8 of 8 regions · 450 ms
Right now
The verdict is the worse of these two. How we decide
Aiven's status page
status.aiven.io · read · checked every 3 minutes
| Component | Status |
|---|---|
| Aiven the service itself | Operational |
| Support Ticketing System | Operational |
FlareWarden checks
console.aiven.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 450 ms
- Checked
By region
- Amsterdam reachable, 309 ms
- Ashburn reachable, 411 ms
- Dallas reachable, 591 ms
- Frankfurt reachable, 257 ms
- Newark reachable, 506 ms
- Paris reachable, 288 ms
- Stockholm reachable, 282 ms
- São Paulo reachable, 959 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 155 ms | 3 ms | 11 ms | 309 ms |
| Ashburn | 59 ms | 0 ms | 12 ms | 411 ms |
| Dallas | 99 ms | 2 ms | 13 ms | 591 ms |
| Frankfurt | 63 ms | 2 ms | 12 ms | 237 ms |
| Newark | 192 ms | 2 ms | 8 ms | 506 ms |
| Paris | 133 ms | 2 ms | 10 ms | 268 ms |
| Stockholm | 88 ms | 1 ms | 8 ms | 281 ms |
| São Paulo | 363 ms | 26 ms | 23 ms | 959 ms |
We check that console.aiven.io loads, not every feature behind it.
Test it yourself
History
Incidents Aiven reported
Since Oct 22, 15 days · from status.aiven.io
- Incidents
- 1
- Major or critical
- 0
- Median to resolve
- —
- Ongoing
API requests failing/timing out
Unrated ·
Aiven website availability
Measured by FlareWarden · console.aiven.io
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 594ms
Last 30 days
71-day clean streakOct 7
Today
No downtime
Partial
Downtime
Not measurable
No data
Measured by FlareWarden's own checks of console.aiven.io from multiple regions every 6 hours. Aiven's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 71 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Aiven does
Aiven runs managed open source data infrastructure, including PostgreSQL, Apache Kafka, ClickHouse, OpenSearch and Valkey, across AWS, Google Cloud, Azure and other clouds. Customers use its console and API to provision, scale and back up services, while their applications connect straight to the database endpoints. Those two paths fail separately, and the difference decides how bad an incident is.
What an outage looks like
Usually the console and API rather than your data. console.aiven.io fails to load or loops on sign-in, Terraform runs against the Aiven provider error out, and operations that create, resize or replace nodes stall. Applications connected to existing services normally keep reading and writing throughout, so the symptom is that you cannot change anything, not that nothing works.
What to do about it
Check status.aiven.io. Aiven's published incident notices state that running services are not impacted by issues affecting its console and control plane, so confirm your application is actually failing before treating this as a database outage. Postpone provisioning, resizing and maintenance work, which is what slows first. Aiven reports a single broad component, so its page will not tell you which service or region is affected.
Is it down for everyone, or just you?
If this page says Aiven is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Aiven outage FAQ
Are my databases down when Aiven is down?
Usually not. Aiven's own incident notices during console and control plane outages state that running services are not impacted, and applications connected to existing endpoints keep working normally. The control plane is how you manage services, not how your application reaches them. Run a query from your application before assuming your data is unreachable.
What actually stops working?
Management operations. Creating, resizing, upgrading or replacing services goes through the control plane, and Aiven has published incidents where existing services ran normally while operations requiring new or replaced nodes saw significant delays. Terraform runs and CI pipelines that provision Aiven resources fail during those windows even though production is healthy.
Aiven's status page shows one component. How do I tell what is affected?
Largely you cannot from that page. Aiven reports a single Aiven component plus a Support Ticketing System, so a PostgreSQL problem in one region and a Kafka problem in another look identical on it. That coarseness is why measuring the endpoints yourself, from more than one region, tells you more than the vendor banner does.
Does an Aiven incident always mean Aiven broke?
No. Aiven has published console outages caused by an upstream Cloudflare Global Network incident and resolved when Cloudflare fixed it. A hosted data platform sits on cloud providers, CDNs and DNS, so an incident on its status page can be a symptom of one of those rather than a fault inside Aiven itself.
How we measure this
- We request Aiven's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Aiven publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Aiven itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Aiven goes down
We check Aiven every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free MonitoringFree plan available
No credit card required