Vendor Status Watch

← all vendors

Aiven status history

Current state: degraded — “Partial System Degradation” per https://status.aiven.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
6incidents, last 90 days
26incidents on record
Incidents per week, last 12 weeks:

How long do Aiven incidents last?

4.6 hmedian incident duration25 measured
4.8 days90th percentile1 in 10 ran longer
4.2 hmedian, major/critical only13 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-16 12:21 UTCCreation of new service nodes disruptedinvestigatingminoropen
2026-08-08 21:28 UTCDelayed VM Creationresolvedminor9 h 00 min
2026-07-29 14:29 UTCAiven Dynamic Disk Sizing (DDS) failuresresolvedmajor2 h 37 min
2026-07-02 23:24 UTCDelayed Service Operations Affecting All Cloud Providers (MySQL Unaffected)resolvedmajor6 h 03 min
2026-06-25 10:16 UTCTerraform & Kubernetes operators - List Databases API Error (400)resolvednone2 h 58 min
2026-06-23 14:18 UTCKafka upgrade to 3.9 pausedresolvednone45 h 19 min
2026-06-11 15:25 UTCKafka upgrades to 3.9 are pausedresolvednone4 d 19 h
2026-06-09 15:10 UTCBackup and restore failures affecting some Aiven for PostgreSQL servicesresolvedmajor1 h 47 min
2026-05-25 02:29 UTCService operations affected in Azureresolvedmajor1 h 25 min
2026-05-20 01:15 UTCIssue affecting services in DigitalOcean NYC3 regionresolvedminor1 h 23 min
2026-05-14 06:55 UTCMultiple Aiven for Apache Kafka services experiencing disruptionresolvednone40 h 18 min
2026-03-01 23:12 UTCAmazon Web Services (AWS) ME-CENTRAL-1 and ME-SOUTH-1 region statusresolvedmajor31 d 12 h
2025-12-12 11:33 UTCDelays in Service Provisioning on UpCloudresolvednone5 d 2 h
2025-12-08 03:48 UTCDelay for new nodes coming onlineresolvedmajor16 h 52 min
2025-12-05 07:19 UTCInvestigating connectivity issues in Azure Norway West regionresolvednone20 h 15 min
2025-12-04 17:12 UTCMetrics API Outageresolvednone2 h 05 min
2025-11-24 03:39 UTCAvailability affected for some PG read replica nodes.resolvednone1 h 59 min
2025-11-19 22:05 UTCIssue preventing power on of PostgreSQL servicesresolvedmajor2 h 02 min
2025-11-18 12:08 UTCAiven Console and aiven.io downresolvednone6 h 57 min
2025-11-06 04:24 UTCPostgreSQL nodes unable to startresolvedmajor3 h 11 min
2025-10-31 11:32 UTCMultiple service types cannot startresolvedmajor2 h 03 min
2025-10-29 17:04 UTCNodes struggling to spin in BYOC environmentsresolvedmajor4 h 13 min
2025-10-20 09:30 UTCNew services or replacement nodes can not be created in AWS us-east-1 (United States, Virginia) due to an AWS outage.resolvedmajor14 h 26 min
2025-10-17 00:29 UTCIssue affecting several servicesresolvedmajor4 h 36 min
2025-09-30 21:47 UTCCustomer using legacy MD5 password cannot connect through pgbouncerresolvedmajor8 h 00 min
2025-09-26 01:49 UTCDelay in service user logsresolvedminor4 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
}