Instaclustr logo

Is Instaclustr Down?

SaaSLive status, outages, and incident history

No. Instaclustr is up right now.

Every monitored Instaclustr system is operational as of August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 46m agoLive, rechecked every 60s
How we know: the official Instaclustr status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Instaclustr Component Status

The main Instaclustr systems on this page. All 20 are operational right now.

20operational
API Documentation
Operational
AWS EC2 Regions » AWS ec2-ap-east-1
Operational
AWS EC2 Regions » AWS ec2-ap-northeast-1
Operational

17 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking AWS EC2 Regions » AWS ec2-ap-northeast-2, AWS EC2 Regions » AWS ec2-ap-northeast-3, AWS EC2 Regions » AWS ec2-ap-south-1, AWS EC2 Regions » AWS ec2-ap-southeast-1, AWS EC2 Regions » AWS ec2-ap-southeast-2, AWS EC2 Regions » AWS ec2-ca-central-1, AWS EC2 Regions » AWS ec2-eu-central-1, AWS EC2 Regions » AWS ec2-eu-north-1, AWS EC2 Regions » AWS ec2-eu-south-1, AWS EC2 Regions » AWS ec2-eu-west-1, AWS EC2 Regions » AWS ec2-eu-west-2, AWS EC2 Regions » AWS ec2-eu-west-3, and 5 more.

Create a free account

Component statuses may change independently during partial outages.

Recent Instaclustr Outages & Incidents

Incident history from the official Instaclustr status page, including resolution updates.

Uptime history4 days observed
Aug 8100.00% averageAug 11
Provisioning Failures for Private Network PostgreSQL clusters with 3 nodesResolved Jul 29, 2026 · 9h 16mResolved

This incident has been resolved. --- [2026-07-29T03:38:41.081Z] (identified) We are continuing to work on a fix for this issue. --- [2026-07-29T00:11:05.321Z] (identified) We are currently experiencing issues with provisioning private network PostgreSQL clusters with 3 nodes 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 (support@instaclustr.com).

GCP us-east4-b Operational IssuesResolved Jul 22, 2026 · 29 minResolved

This incident has been resolved. --- [2026-07-22T13:04:32.192Z] (identified) We are currently experiencing service degradation and potential disruptions in the GCP us-east4-b zone. GCP has not updated its status page yet, however initial investigation indicates an issue likely with the cloud provider's infrastructure in the us-east4-b zone. While we are seeing partial recovery, in the meantime provisioning new clusters or nodes in the concerned GCP zone will be impacted. Also existing nodes in the GCP us-east4-b zone can face intermittent issues and be offline. You should still be able to access your clusters if you are running a standard configuration. 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 (support@instaclustr.com).

Provisioning Failures for Kafka-Connect & Cadence ClustersResolved Jul 21, 2026 · 4h 1mResolved

This incident has been resolved. --- [2026-07-21T08:12:43.426Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-07-21T05:25:29.510Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-07-21T04:55:34.102Z] (investigating) We are currently experiencing issues with provisioning Kafka Connect & Cadence clusters into existing VPCs 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 (support@instaclustr.com).

Live Instaclustr Outage Reports

Problems reported by engineers using Instaclustr. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Instaclustr problems reported yet.

Something wrong with Instaclustr on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Instaclustr

Instaclustr publishes a public status page at status.instaclustr.com covering 31 components, including Management Console, AWS ec2-us-west-2 and Website. PulsAPI tracks Instaclustr outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured Instaclustr uptime at 100.00%. Response times, incident history, and SLA tracking for Instaclustr are available on the PulsAPI dashboard.

Instaclustr Status FAQ

Is Instaclustr down right now?

PulsAPI checks Instaclustr every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Instaclustr status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Instaclustr is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Instaclustr recovers.

How do I check Instaclustr uptime history?

PulsAPI tracks Instaclustr uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Instaclustr.

How fast does PulsAPI detect Instaclustr outages?

PulsAPI polls the official Instaclustr status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Instaclustr components?

Yes. PulsAPI monitors 20 individual Instaclustr components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Instaclustr goes down?

Yes. Create a PulsAPI account and subscribe to Instaclustr. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Instaclustr status changes.

How do I report an issue with Instaclustr to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Instaclustr problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Instaclustr?

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Instaclustr alongside up to 9 other services at pulsapi.com/signup.

Track Instaclustr with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Instaclustr status changes.

Start free trial