Is Instaclustr Down?
- Instaclustr's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 235 ms
Right now
The verdict is the worse of these two. How we decide
Instaclustr's status page
status.instaclustr.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Management Console | Operational |
| Website | Operational |
| Monitoring API | Operational |
| Cluster Management API | Operational |
| Terraform Provider | Operational |
| Support Portal | Operational |
| Prometheus API | Operational |
| API Documentation (Powered by Redocly) | Operational |
| Google Cloud Platform Google Cloud Storage | Operational |
| Google Cloud Platform Google Compute Engine | Operational |
FlareWarden checks
instaclustr.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 235 ms
- Checked
By region
- Amsterdam reachable, 147 ms
- Dallas reachable, 77 ms
- Paris reachable, 93 ms
- San Jose reachable, 174 ms
- Singapore reachable, 449 ms
- Stockholm reachable, 217 ms
- Sydney reachable, 623 ms
- Toronto reachable, 106 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 62 ms | 3 ms | 22 ms | 136 ms |
| Dallas | 28 ms | 2 ms | 11 ms | 70 ms |
| Paris | 42 ms | 2 ms | 14 ms | 87 ms |
| San Jose | 80 ms | 4 ms | 15 ms | 162 ms |
| Singapore | 177 ms | 1 ms | 11 ms | 444 ms |
| Stockholm | 66 ms | 16 ms | 26 ms | 172 ms |
| Sydney | 363 ms | 1 ms | 10 ms | 619 ms |
| Toronto | 31 ms | 1 ms | 11 ms | 100 ms |
History
Incidents Instaclustr reported
Since Nov 4, 2 days · from status.instaclustr.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Instaclustr website availability
Measured by FlareWarden · instaclustr.com
- Last 7 days
- —
- Last 30 days
- —
- Last 90 days
- —
- Avg response, 30 days
- —
Last 30 days
Measured by FlareWarden's own checks of instaclustr.com from multiple regions every 6 hours. Instaclustr's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Instaclustr does
NetApp Instaclustr runs managed open source data infrastructure: Apache Kafka, Apache Cassandra, OpenSearch, PostgreSQL, Cadence, Apache Spark and Valkey clusters hosted in AWS and Google Cloud regions. Teams use it for the databases and streaming platforms behind their own applications. Its status page lists the Management Console, the Cluster Management, Monitoring and Prometheus APIs, the Terraform provider, the support portal and one row per AWS region.
What an outage looks like
Most incidents stop provisioning or slow monitoring while existing clusters keep running. On September 10, 2026 new clusters could not be provisioned through the console or the Cluster Management API for about 40 minutes. Cloud faults reach the clusters themselves: on October 20 every node in Google Cloud's europe-west2-b zone was unavailable for about 6.5 hours, and affected clusters ran with reduced capacity on their nodes in the other zones.
What to do about it
Check status.instaclustr.com and read which row the incident names: the console, each API, the Terraform provider and each AWS region are listed separately. A Monitoring API or Prometheus API incident means metrics are slow or missing, not that a cluster is down. During the October 20 Google Cloud incident, provisioning in the region failed and data centre resizes there were disabled until Google recovered. For urgent problems it points to support.instaclustr.com and support@instaclustr.com.
Is it down for everyone, or just you?
If this page says Instaclustr is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Instaclustr outage FAQ
Are my Instaclustr clusters down when the console or API has an incident?
Does a Google Cloud or AWS outage affect Instaclustr?
Why are my Instaclustr metrics missing or returning 403?
Can I use Terraform with Instaclustr during an incident?
How we measure this
- We request Instaclustr's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Instaclustr publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Instaclustr itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Instaclustr goes down
We check Instaclustr every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring