Aiven status history
Current state: degraded — “Partial System Degradation” per https://status.aiven.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Aiven incidents last?
From 25 incidents with a vendor-posted start and resolve time. Longest on record: Amazon Web Services (AWS) ME-CENTRAL-1 and ME-SOUTH-1 region status — 31.5 days (2026-03-01 23:12 UTC). Excluded, never estimated: 1 still open / no resolve time. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (26)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-16 12:21 UTC | Creation of new service nodes disrupted | investigating | minor | open |
| 2026-08-08 21:28 UTC | Delayed VM Creation | resolved | minor | 9 h 00 min |
| 2026-07-29 14:29 UTC | Aiven Dynamic Disk Sizing (DDS) failures | resolved | major | 2 h 37 min |
| 2026-07-02 23:24 UTC | Delayed Service Operations Affecting All Cloud Providers (MySQL Unaffected) | resolved | major | 6 h 03 min |
| 2026-06-25 10:16 UTC | Terraform & Kubernetes operators - List Databases API Error (400) | resolved | none | 2 h 58 min |
| 2026-06-23 14:18 UTC | Kafka upgrade to 3.9 paused | resolved | none | 45 h 19 min |
| 2026-06-11 15:25 UTC | Kafka upgrades to 3.9 are paused | resolved | none | 4 d 19 h |
| 2026-06-09 15:10 UTC | Backup and restore failures affecting some Aiven for PostgreSQL services | resolved | major | 1 h 47 min |
| 2026-05-25 02:29 UTC | Service operations affected in Azure | resolved | major | 1 h 25 min |
| 2026-05-20 01:15 UTC | Issue affecting services in DigitalOcean NYC3 region | resolved | minor | 1 h 23 min |
| 2026-05-14 06:55 UTC | Multiple Aiven for Apache Kafka services experiencing disruption | resolved | none | 40 h 18 min |
| 2026-03-01 23:12 UTC | Amazon Web Services (AWS) ME-CENTRAL-1 and ME-SOUTH-1 region status | resolved | major | 31 d 12 h |
| 2025-12-12 11:33 UTC | Delays in Service Provisioning on UpCloud | resolved | none | 5 d 2 h |
| 2025-12-08 03:48 UTC | Delay for new nodes coming online | resolved | major | 16 h 52 min |
| 2025-12-05 07:19 UTC | Investigating connectivity issues in Azure Norway West region | resolved | none | 20 h 15 min |
| 2025-12-04 17:12 UTC | Metrics API Outage | resolved | none | 2 h 05 min |
| 2025-11-24 03:39 UTC | Availability affected for some PG read replica nodes. | resolved | none | 1 h 59 min |
| 2025-11-19 22:05 UTC | Issue preventing power on of PostgreSQL services | resolved | major | 2 h 02 min |
| 2025-11-18 12:08 UTC | Aiven Console and aiven.io down | resolved | none | 6 h 57 min |
| 2025-11-06 04:24 UTC | PostgreSQL nodes unable to start | resolved | major | 3 h 11 min |
| 2025-10-31 11:32 UTC | Multiple service types cannot start | resolved | major | 2 h 03 min |
| 2025-10-29 17:04 UTC | Nodes struggling to spin in BYOC environments | resolved | major | 4 h 13 min |
| 2025-10-20 09:30 UTC | New services or replacement nodes can not be created in AWS us-east-1 (United States, Virginia) due to an AWS outage. | resolved | major | 14 h 26 min |
| 2025-10-17 00:29 UTC | Issue affecting several services | resolved | major | 4 h 36 min |
| 2025-09-30 21:47 UTC | Customer using legacy MD5 password cannot connect through pgbouncer | resolved | major | 8 h 00 min |
| 2025-09-26 01:49 UTC | Delay in service user logs | resolved | minor | 4 h 15 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Aiven with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"aiven"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}