Instaclustr Outage History

22 incidents recorded over the last 365 days, 21 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Instaclustr status100.00% uptime history

Every Recorded Instaclustr Incident

Instaclustr incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 20, 2026GCP outage affecting clusters in europe-west2Google Cloud has resolved the power event that caused the outage in the europe-west2-b zone. All affected clusters have been restored and are operating normally, and provisioning of new clusters and nodes in GCP…6h 28mResolved
Sep 23, 2026Monitoring API Latency and Error IssuesThis incident has been resolved.46 minResolved
Sep 10, 2026Degraded Cluster ProvisioningThis incident has been resolved.43 minResolved
Aug 20, 2026GCP us-west1 Operational IssuesThis incident has been resolved.2h 30mResolved
Aug 19, 2026Compatability issues for Instaclustr OpenSearch issues and Instaclustr Terraform providerThis incident has been resolved.2h 31mResolved
Jul 29, 2026Provisioning Failures for Private Network PostgreSQL clusters with 3 nodesThis incident has been resolved.9h 16mResolved
Jul 22, 2026GCP us-east4-b Operational IssuesThis incident has been resolved.29 minResolved
Jul 21, 2026Provisioning Failures for Kafka-Connect & Cadence ClustersThis incident has been resolved.4h 1mResolved
Jul 21, 2026Metrics Processing Pipeline MaintenanceThe scheduled maintenance has been completed.6h 0mScheduled
Jul 16, 2026403 Forbidden errors when accessing Cluster-Level Prometheus Monitoring QueriesThis incident has been resolved.5h 13mResolved
May 13, 2026Monitoring API Latency and Error IssuesThis incident has been resolved.5h 38mResolved
May 8, 2026AWS US-EAST-1 Operational Issues in a single Availability Zone use1-az4This incident has been resolved.27h 28mResolved
Apr 29, 2026Monitoring API Latency and Error IssuesThis incident has been resolved.1h 6mResolved
Mar 24, 2026Provisioning Failures for Cadence and Kafka Connect into a Private NetworkA fix for this issue has been deployed.7h 26mResolved
Mar 10, 2026Provisioning failures and high latencies for cluster management operations and monitoringThis incident has been resolved.3h 30mResolved
Mar 4, 2026Provisioning Failures for Cadence and Kafka Connect into existing AWS VPCThis incident has been resolved.5h 46mResolved
Feb 12, 2026Provisioning Failures for OpenSearchA fix has been deployed and the ability to provision OpenSearch clusters has been restored.5h 34mResolved
Jan 27, 2026Elevated Cluster Management API LatencyThis incident has been resolved.1h 56mResolved
Jan 27, 2026Delays in making changes to Clickhouse Configurations, Clickhouse Kafka integrations and Kafka UsersThis incident has been resolved.39h 47mResolved
Jan 23, 2026Delays in cluster Provisioning and Kafka integration API callsThis incident has been resolved.3h 7mResolved
Jan 9, 2026Microsoft Social SSO Login Unavailable for Management ConsoleMicrosoft Social SSO login for Management Console has been fixed and customers can use the Sign in with Microsoft option again.4h 8mResolved
Dec 23, 2025Delayed aggregated metrics on Monitoring APIThis incident has been resolved.25h 46mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Instaclustr incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Instaclustr Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Instaclustr acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Instaclustr outage in this window ran 1d 15h, against a mean recovery of 7h 41m. If you depend on Instaclustr in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.