Vendor Status Watch

← all vendors

Instaclustr status history

Current state: operational — “All Systems Operational” per https://status.instaclustr.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

3incidents, last 30 days
7incidents, last 90 days
24incidents on record
Incidents per week, last 12 weeks:

How long do Instaclustr incidents last?

4.1 hmedian incident duration24 measured
27.5 h90th percentile1 in 10 ran longer
5.2 hmedian, major/critical only7 incidents

From 24 incidents with a vendor-posted start and resolve time. Longest on record: Postgres application logs not displayed in Console — 5.1 days (2025-08-20 03:37 UTC). Excluded, never estimated: nothing. 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 (24)

StartedIncidentStatusImpactDuration
2026-09-10 02:56 UTCDegraded Cluster Provisioningresolvedminor43 min
2026-08-20 17:15 UTCGCP us-west1 Operational Issuesresolvedmajor2 h 30 min
2026-08-19 10:05 UTCCompatability issues for Instaclustr OpenSearch issues and Instaclustr Terraform providerresolvedminor2 h 31 min
2026-07-29 00:11 UTCProvisioning Failures for Private Network PostgreSQL clusters with 3 nodesresolvednone9 h 16 min
2026-07-22 13:04 UTCGCP us-east4-b Operational Issuesresolvedminor29 min
2026-07-21 04:55 UTCProvisioning Failures for Kafka-Connect & Cadence Clustersresolvednone4 h 01 min
2026-07-16 04:34 UTC403 Forbidden errors when accessing Cluster-Level Prometheus Monitoring Queriesresolvedcritical5 h 13 min
2026-05-13 06:47 UTCMonitoring API Latency and Error Issuesresolvednone5 h 38 min
2026-05-08 01:33 UTCAWS US-EAST-1 Operational Issues in a single Availability Zone use1-az4resolvedminor27 h 28 min
2026-04-29 05:28 UTCMonitoring API Latency and Error Issuesresolvedminor1 h 06 min
2026-03-24 01:10 UTCProvisioning Failures for Cadence and Kafka Connect into a Private Networkresolvedmajor7 h 26 min
2026-03-10 03:22 UTCProvisioning failures and high latencies for cluster management operations and monitoringresolvedminor3 h 30 min
2026-03-04 00:18 UTCProvisioning Failures for Cadence and Kafka Connect into existing AWS VPCresolvedmajor5 h 46 min
2026-02-12 01:47 UTCProvisioning Failures for OpenSearchresolvedmajor5 h 34 min
2026-01-27 23:06 UTCElevated Cluster Management API Latencyresolvedminor1 h 56 min
2026-01-27 09:37 UTCDelays in making changes to Clickhouse Configurations, Clickhouse Kafka integrations and Kafka Usersresolvedminor39 h 47 min
2026-01-23 00:19 UTCDelays in cluster Provisioning and Kafka integration API callsresolvedminor3 h 07 min
2026-01-09 00:48 UTCMicrosoft Social SSO Login Unavailable for Management Consoleresolvedminor4 h 08 min
2025-12-23 21:40 UTCDelayed aggregated metrics on Monitoring APIresolvedminor25 h 46 min
2025-10-20 09:33 UTCMultiple systems affected by outage in AWS us-east-1resolvednone14 h 52 min
2025-10-08 17:27 UTCKafka Cluster Certificate Download Disruptionresolvednone2 h 20 min
2025-09-15 19:50 UTCIssues with the Instaclustr Terraform providerresolvedmajor4 h 00 min
2025-09-15 08:41 UTCService Disruptions for Management Console and APIsresolvedmajor1 h 04 min
2025-08-20 03:37 UTCPostgres application logs not displayed in Consoleresolvedminor5 d 1 h

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 Instaclustr with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "instaclustr"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}