Is Instaclustr down?

Last checked 22m ago
Current status
Instaclustr is up

No incidents right now.

Instaclustr is operational right now. Last checked 22m ago; the most recent incident resolved 8d ago.

Real-time Instaclustr status, recent outages, and incident history: pulled directly from Instaclustr's official status page at status.instaclustr.com every 5 minutes. Pingoru tracks 30 Instaclustr services and has captured 5 incidents in the last 90 days (99.44% uptime). Get email, Slack, Discord, or webhook alerts the moment Instaclustr reports a new incident, free for 3 monitors, no credit card.

Users who monitor Instaclustr also follow these Database services: Snowflake Supabase Stitch Data ClickHouse Iron.io Aiven SolarWinds Observability Neo4j Aura Upstash Pinecone View all 8,000+ providers
Instaclustr uptime 99.44% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 6h 28m
    Started Oct 20, 2026, 08:06 AM UTC · Resolved Oct 20, 2026, 02:35 PM UTC
    Management ConsoleCluster Management APITerraform ProviderGoogle Cloud Platform Google Compute Engine
    Timeline · 8 updates
    • investigating · Oct 20, 2026, 08:06 AM UTC

      We are currently investigating an infrastructure issue affecting the GCP europe-west2 region. All nodes in the europe-west2-b availability zone have become unavailable, resulting in reduced capacity for affected clusters. Provisioning new clusters in the europe-west2 region may also fail at this time. Based on our investigation and testing to date, other GCP regions in Europe do not appear to be affected. Our engineers are treating this as a high-priority incident and are working with urgency to restore full service.

    • investigating · Oct 20, 2026, 08:06 AM UTC

      We are continuing to investigate this issue.

    • monitoring · Oct 20, 2026, 08:39 AM UTC

      A fix has been implemented and we are monitoring the results.

    • identified · Oct 20, 2026, 08:48 AM UTC

      The issue has been identified and a fix is being implemented.

    • identified · Oct 20, 2026, 08:57 AM UTC

      We are continuing to work on a fix for this issue.

    • identified · Oct 20, 2026, 09:45 AM UTC

      Google Cloud has now published a public incident for the europe-west2 region: https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj Google has not yet provided a workaround or an estimated time to resolution. We continue to monitor the situation closely and will provide further updates as information becomes available.

    • monitoring · Oct 20, 2026, 12:13 PM UTC

      Google Cloud has advised that the outage was caused by a power event in the europe-west2-b zone, which has now been mitigated. Google is recovering existing workloads and has tentatively estimated full recovery by approximately 13:00 UTC. We are seeing some affected nodes in europe-west2-b begin to recover. Other nodes are still unavailable or not yet stable, and our team is verifying the health of each affected cluster as nodes come back online. Provisioning new clusters and nodes in europe-west2 may continue to fail until Google completes recovery. We will provide a further update once recovery is complete.

    • resolved · Oct 20, 2026, 02:35 PM UTC

      Google 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 europe-west2 is working again. Cluster data centre resizes in GCP europe-west2 have also been re-enabled. We apologise for any disruption this may have caused. Google has advised it will publish an analysis of the incident once its internal investigation is complete. If you are still experiencing any issues with your clusters, please contact [email protected].

    Latest: Google 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 o…

  2. Resolved 46m
    Started Sep 23, 2026, 01:12 AM UTC · Resolved Sep 23, 2026, 01:58 AM UTC
    Monitoring API
    Timeline · 3 updates
    • investigating · Sep 23, 2026, 01:12 AM UTC

      We are currently investigating elevated latencies and error rates with our Monitoring API. Our team is actively working to resolve the issue and we apologise for any inconvenience caused. Existing customer clusters are unaffected. The Management Console and Cluster Management API are still operational. We will provide updates as soon as they become available. If you have an urgent matter, please reach out to us via the support portal (support.instaclustr.com) or email ([email protected]).

    • monitoring · Sep 23, 2026, 01:49 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Sep 23, 2026, 01:58 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 43m
    Started Sep 10, 2026, 02:56 AM UTC · Resolved Sep 10, 2026, 03:40 AM UTC
    Management ConsoleCluster Management API
    Timeline · 3 updates
    • identified · Sep 10, 2026, 02:56 AM UTC

      We are currently experiencing issues with provisioning clusters through the Cluster Management API and Management Console. Our team is actively working on resolving this problem and we apologise for any inconvenience caused. Existing customer clusters are unaffected, and the Monitoring API and Prometheus API are operational. Additional details will be provided as they become available. If you have an urgent matter, please reach out to us via the support portal (support.instaclustr.com) or email ([email protected]).

    • monitoring · Sep 10, 2026, 03:28 AM UTC

      A fix has been implemented and we are monitoring the results.

    • resolved · Sep 10, 2026, 03:40 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 2h 30m
    Started Aug 20, 2026, 05:15 PM UTC · Resolved Aug 20, 2026, 07:46 PM UTC
    Cluster Management APITerraform ProviderGoogle Cloud Platform Google Cloud StorageGoogle Cloud Platform Google Compute Engine
    Timeline · 5 updates
    • identified · Aug 20, 2026, 05:15 PM UTC

      We are currently experiencing service degradation and potential disruptions in the Google Cloud Platform region us-west1. This incident is a result of an ongoing issue with the cloud provider's infrastructure. You will be unable to provision new clusters or nodes. Existing nodes in us-west1 may be unavailable. Cluster datacentres in other regions are unaffected, but are experiencing networking issues when interacting with nodes in us-west1. Individual impacted customers are being contacted via support tickets. We are actively monitoring the situation and will provide additional details as they become available. GCP status is tracked at https://status.cloud.google.com/. If you have an urgent matter, please reach out to us via the support portal (support.instaclustr.com) or email ([email protected]).

    • identified · Aug 20, 2026, 05:16 PM UTC

      We are continuing to work on a fix for this issue.

    • identified · Aug 20, 2026, 05:58 PM UTC

      Vertical scaling has been temporarily disabled in the GCP us-west1 region due to this cloud provider outage. We will re-enable this functionality when the cloud provider outage is resolved.

    • monitoring · Aug 20, 2026, 07:06 PM UTC

      Google have completed mitigations and are reporting recovery across multiple products. We will continue monitoring the incident until the remaining products have recovered. Vertical scaling remains disabled in us-west1.

    • resolved · Aug 20, 2026, 07:46 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 2h 31m
    Started Aug 19, 2026, 10:05 AM UTC · Resolved Aug 19, 2026, 12:36 PM UTC
    Cluster Management APITerraform Provider
    Timeline · 2 updates
    • identified · Aug 19, 2026, 10:05 AM UTC

      We are currently seeing compatibility issues between the Instaclustr Terraform provider and the Cluster Management API, affecting operations involving OpenSearch clusters. Standard customer clusters operations are unaffected. The Monitoring API and Prometheus API remain operational. Our team is actively working to resolve the issue and we apologise for any inconvenience. Further updates will be provided as more information becomes available. If you have an urgent matter, please contact us through the support portal at https://support.instaclustr.com or by email at [email protected].

    • resolved · Aug 19, 2026, 12:36 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Incident record

Since April 2026 · Statuspage by Atlassian · 30 components checked every 5 minutes
53incidents recorded
21last 12 months
5last 90 days
8 hourstypical duration, 12 months

The longest incident in the last year, Delays in making changes to Clickhouse Configurations, Clickhouse Kafka integrations and Kafka Users on January 27, 2026, ran for 40 hours. 1 maintenance window announced in the same period.

Most affected components, last 12 months

  • Cluster Management API13
  • Management Console11
  • Monitoring API6
  • Terraform Provider6
  • Google Cloud Platform Google Compute Engine2

Latest incidents

  • GCP outage affecting clusters in europe-west2 October 20, 2026 · 6 hours · degraded service

    We are currently investigating an infrastructure issue affecting the GCP europe-west2 region. All nodes in the europe-west2-b availability zone have become…

  • Monitoring API Latency and Error Issues September 23, 2026 · 46 minutes · degraded service

    We are currently investigating elevated latencies and error rates with our Monitoring API. Our team is actively working to resolve the issue and we apologise…

  • Degraded Cluster Provisioning September 10, 2026 · 43 minutes · degraded service

    We are currently experiencing issues with provisioning clusters through the Cluster Management API and Management Console. Our team is actively working on…

Outage history

Past 90 days · 5 incidents View full outage history →