Instaclustr incident

Provisioning Failures for Cadence and Kafka Connect into existing AWS VPC

Major Resolved View vendor source →
Started
Mar 04, 2026, 12:18 AM UTC
Resolved
Mar 04, 2026, 06:05 AM UTC
Duration
5h 46m
Detected by Pingoru
Mar 04, 2026, 12:18 AM UTC

Affected components

Management ConsoleCluster Management API

Update timeline

  1. identified Mar 04, 2026, 12:18 AM UTC

    We are currently experiencing issues with provisioning Cadence and Kafka Connect clusters on AWS when provisioning into an existing VPC through the Cluster Management API and Management Console. Provisioning a Cadence cluster into the same VPC as its linked Cassandra cluster or a Kafka Connect cluster into the same VPC as its linked Kafka cluster will fail. 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]).

  2. resolved Mar 04, 2026, 06:05 AM UTC

    This incident has been resolved.

Looking to track Instaclustr downtime and outages?

Pingoru polls Instaclustr's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Instaclustr reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Instaclustr alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Instaclustr for free

5 free monitors · No credit card required