Skip to main content
Aiven logo

Is Aiven Down?

No — Aiven is up

Reachable from all 8 checked regions

Average response time: 427ms

Last checked · checks run every 6 hours

Official status page: https://status.aiven.io

Aiven uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
423ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 15 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

15-day clean streak
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: no data
Aug 20: no data
Aug 21: no data
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: 100.00% uptime, 16 checks
Aug 28: 100.00% uptime, 31 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 30 checks
Sep 2: 100.00% uptime, 30 checks
Sep 3: 100.00% uptime, 31 checks
Sep 4: 100.00% uptime, 31 checks
Sep 5: 100.00% uptime, 31 checks
Sep 6: 100.00% uptime, 28 checks
Sep 7: 100.00% uptime, 29 checks
Sep 8: 100.00% uptime, 56 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 8 checks
Aug 12 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra
155ms
DNS 0ms TCP 1ms TLS 10ms TTFB 151ms
gru
537ms
DNS 0ms TCP 2ms TLS 12ms TTFB 534ms
iad
348ms
DNS 1ms TCP 1ms TLS 10ms TTFB 342ms
jnb
579ms
DNS 0ms TCP 0ms TLS 7ms TTFB 576ms
lax
518ms
DNS 0ms TCP 1ms TLS 11ms TTFB 515ms
lhr
94ms
DNS 0ms TCP 2ms TLS 8ms TTFB 91ms
nrt
818ms
DNS 0ms TCP 1ms TLS 9ms TTFB 816ms
ord
372ms
DNS 0ms TCP 2ms TLS 7ms TTFB 369ms

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 18 cities across three regions to find out where it breaks.

Test it yourself

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.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Aiven goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required