Störungsverlauf von Instaclustr

1. 20. August 2026 um 17:15 UTCidentified

   Wir erleben derzeit Service-Degradation und potenzielle Störungen in der Google Cloud Platform Region us-west1. Dieser Vorfall ist das Ergebnis eines anhaltenden Problems mit der Infrastruktur des Cloud-Anbieters. Sie können keine neuen Cluster oder Knoten bereitstellen. Bestehende Knoten in us-west1 sind möglicherweise nicht verfügbar. Cluster-Rechenzentren in anderen Regionen sind nicht betroffen, haben aber Netzwerkprobleme bei der Interaktion mit Knoten in us-west1. Einzelne betroffene Kunden werden über Support-Tickets kontaktiert. Wir beobachten die Situation aktiv und werden zusätzliche Details zur Verfügung stellen, sobald sie verfügbar sind. Der GCP-Status wird unter https://status.cloud.google.com/ verfolgt. Wenn Sie eine dringende Angelegenheit haben, kontaktieren Sie uns bitte über das Support-Portal (support.instaclustr.com) oder per E-Mail ([email protected]).

2. 20. August 2026 um 17:16 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

3. 20. August 2026 um 17:58 UTCidentified

   Die vertikale Skalierung wurde in der GCP-Region us-west1 aufgrund dieses Cloud-Anbieterausfalls vorübergehend deaktiviert. Wir werden diese Funktionalität wieder aktivieren, wenn der Ausfall des Cloud-Anbieters behoben ist.

4. 20. August 2026 um 19:06 UTCmonitoring

   Google hat Abhilfemaßnahmen abgeschlossen und meldet die Wiederherstellung für mehrere Produkte. Wir werden den Vorfall weiter überwachen, bis sich die verbleibenden Produkte erholt haben. Die vertikale Skalierung bleibt in us-west1 deaktiviert.

5. 20. August 2026 um 19:46 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 19. August 2026 um 10:05 UTCidentified

   Wir sehen derzeit Kompatibilitätsprobleme zwischen dem Instaclustr Terraform-Anbieter und der Cluster-Management-API, die sich auf Vorgänge mit OpenSearch-Clustern auswirken. Standard Customer Cluster Operationen sind nicht betroffen. Die Monitoring API und die Prometheus API bleiben funktionsfähig. Unser Team arbeitet aktiv daran, das Problem zu lösen, und wir entschuldigen uns für alle Unannehmlichkeiten. Weitere Updates werden bereitgestellt, sobald mehr Informationen verfügbar werden. Wenn Sie eine dringende Angelegenheit haben, kontaktieren Sie uns bitte über das Support-Portal unter https://support.instaclustr.com oder per E-Mail unter [email protected].

2. 19. August 2026 um 12:36 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 29. Juli 2026 um 00:11 UTCidentified

   Wir haben derzeit Probleme mit der Bereitstellung privater Netzwerk-PostgreSQL-Cluster mit 3 Knoten über die Cluster Management API und die Management Console. Unser Team arbeitet aktiv an der Lösung dieses Problems und wir entschuldigen uns für jegliche Unannehmlichkeiten. Bestehende Kundencluster sind nicht betroffen, und die Monitoring-API und die Prometheus-API sind funktionsfähig. Zusätzliche Details werden zur Verfügung gestellt, sobald sie verfügbar sind. Wenn Sie eine dringende Angelegenheit haben, kontaktieren Sie uns bitte über das Support-Portal (support.instaclustr.com) oder per E-Mail ([email protected]).

2. 29. Juli 2026 um 03:38 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

3. 29. Juli 2026 um 09:27 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Juli 2026 um 13:04 UTCidentified

   Wir erleben derzeit Service-Degradation und mögliche Störungen in der GCP-US-Ost4-B-Zone. GCP hat seine Statusseite noch nicht aktualisiert, jedoch deuten erste Untersuchungen auf ein Problem mit der Infrastruktur des Cloud-Anbieters in der US-East4-B-Zone hin. Während wir eine teilweise Erholung sehen, wird in der Zwischenzeit die Bereitstellung neuer Cluster oder Knoten in der betroffenen GCP-Zone betroffen sein. Auch bestehende Knoten in der GCP-Zone us-east4-b können intermittierende Probleme haben und offline sein. Sie sollten weiterhin auf Ihre Cluster zugreifen können, wenn Sie eine Standardkonfiguration ausführen. Einzelne betroffene Kunden werden über Support-Tickets kontaktiert. Wir beobachten die Situation aktiv und werden zusätzliche Details zur Verfügung stellen, sobald sie verfügbar sind. Der GCP-Status wird unter https://status.cloud.google.com/ verfolgt. Wenn Sie eine dringende Angelegenheit haben, kontaktieren Sie uns bitte über das Support-Portal (support.instaclustr.com) oder per E-Mail ([email protected]).

2. 22. Juli 2026 um 13:34 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. Juli 2026 um 04:55 UTCinvestigating

   Wir haben derzeit Probleme mit der Bereitstellung von Kafka Connect & Cadence-Clustern in bestehenden VPCs über die Cluster Management API und die Management Console. Unser Team arbeitet aktiv an der Lösung dieses Problems und wir entschuldigen uns für jegliche Unannehmlichkeiten. Bestehende Kundencluster sind nicht betroffen, und die Monitoring-API und die Prometheus-API sind funktionsfähig. Zusätzliche Details werden zur Verfügung gestellt, sobald sie verfügbar sind. Wenn Sie eine dringende Angelegenheit haben, kontaktieren Sie uns bitte über das Support-Portal (support.instaclustr.com) oder per E-Mail ([email protected]).

2. 21. Juli 2026 um 05:25 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 21. Juli 2026 um 08:12 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 21. Juli 2026 um 08:56 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juli 2026 um 04:34 UTCidentified

   Wir untersuchen derzeit ein Problem, das dazu führt, dass Prometheus-Überwachungsanfragen auf Clusterebene mit einem 403-Fehler falsch blockiert werden. Andere Prometheus Überwachungsanfragen sind nicht betroffen. Unser Team arbeitet aktiv daran, das Problem zu lösen, und wir entschuldigen uns für etwaige Unannehmlichkeiten. Die Management Console, die Cluster Management API und die Monitoring API sind noch in Betrieb. Wir werden Updates bereitstellen, sobald sie verfügbar sind. Wenn Sie eine dringende Angelegenheit haben, kontaktieren Sie uns bitte über das Support-Portal (support.instaclustr.com) oder per E-Mail ([email protected]).

2. 16. Juli 2026 um 04:52 UTCidentified

   Das Problem wurde identifiziert und unser Team arbeitet aktiv an der Implementierung eines Fixes. Prometheus-Überwachungsabfragen auf Clusterebene werden fälschlicherweise mit einem 403-Fehler blockiert. Andere Prometheus Überwachungsanfragen sind nicht betroffen. Bestehende Kundencluster sind nicht betroffen. Die Management Console und die Cluster Management API sind weiterhin in Betrieb. Wir werden Updates bereitstellen, sobald sie verfügbar sind. Wenn Sie eine dringende Angelegenheit haben, kontaktieren Sie uns bitte über das Support-Portal (support.instaclustr.com) oder per E-Mail ([email protected]).

3. 16. Juli 2026 um 08:52 UTCmonitoring

   Ein Fix wird eingeführt und wir überwachen die Ergebnisse.

4. 16. Juli 2026 um 09:48 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 13. Mai 2026 um 06:47 UTCinvestigating

   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]).

2. 13. Mai 2026 um 12:26 UTCresolved

   This incident has been resolved.

1. 8. Mai 2026 um 01:33 UTCidentified

   We are currently experiencing service degradation and potential disruptions in the AWS region US-EAST-1. This incident is a result of an ongoing issue with the cloud provider's infrastructure. Customers using the AWS availability zone "use1-az4" are impacted, with nodes in this availability zone observed to become unavailable. Clusters are expected to be available overall, and not significantly impacted. We are actively monitoring the situation and will provide additional details as they become available. AWS status is tracked at https://health.aws.amazon.com/health/status. If you have an urgent matter, please reach out to us via the support portal (support.instaclustr.com) or email ([email protected]).

2. 8. Mai 2026 um 01:55 UTCidentified

   We are continuing to monitor the issue.

3. 9. Mai 2026 um 05:02 UTCresolved

   This incident has been resolved.

1. 29. April 2026 um 05:28 UTCinvestigating

   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]).

2. 29. April 2026 um 06:35 UTCresolved

   This incident has been resolved.

1. 24. März 2026 um 01:10 UTCidentified

   We are currently experiencing issues with provisioning Cadence and Kafka Connect clusters on AWS when provisioning into a Private Network 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]).

2. 24. März 2026 um 08:36 UTCresolved

   A fix for this issue has been deployed.

1. 10. März 2026 um 03:22 UTCinvestigating

   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. In addition, operations on existing clusters such as replacing nodes and restores aren't functional, and we are investigating elevated latencies with the Monitoring API. 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. 10. März 2026 um 04:54 UTCinvestigating

   We are further seeing elevated latencies and error rates with our Monitoring API and Cluster Management API and additionally seeing issues logging into our Management Console. 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 partially degraded at this time. 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]).

3. 10. März 2026 um 06:04 UTCidentified

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

4. 10. März 2026 um 06:28 UTCmonitoring

   A fix has been implemented and operations such as provisioning clusters, replacing nodes and restores are now functional as-well. The Management Console and Cluster Management API are now fully operational. We are still seeing some elevated latencies with the Monitoring API and have implemented a fix for this. We will provide more 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]).

5. 10. März 2026 um 06:53 UTCresolved

   This incident has been resolved.

1. 4. März 2026 um 00:18 UTCidentified

   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. 4. März 2026 um 06:05 UTCresolved

   This incident has been resolved.

1. 12. Februar 2026 um 01:47 UTCinvestigating

   We are currently experiencing issues with provisioning OpenSearch clusters on all providers 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]).

2. 12. Februar 2026 um 02:46 UTCidentified

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

3. 12. Februar 2026 um 07:22 UTCresolved

   A fix has been deployed and the ability to provision OpenSearch clusters has been restored.

1. 27. Januar 2026 um 23:06 UTCinvestigating

   We are currently investigating increased latencies and error rates affecting our Cluster Management API. Our team is actively working to resolve the issue, and we apologize for any inconvenience this may cause. During this time, you may experience slower load times on the Management Console and delayed API responses. Existing cluster operations are unaffected. 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]).

2. 28. Januar 2026 um 00:37 UTCmonitoring

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

3. 28. Januar 2026 um 01:03 UTCresolved

   This incident has been resolved.

1. 27. Januar 2026 um 09:37 UTCinvestigating

   We are currently experiencing delays with applying configuration and Kafka Integration changes to Clickhouse clusters via Terraform, the Cluster Management API and Management Console. During this time, making configuration changes to Clickhouse clusters may take longer than usual. 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. 27. Januar 2026 um 21:31 UTCidentified

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

3. 28. Januar 2026 um 08:56 UTCmonitoring

   We have additionally identified that making changes to Kafka User via Terraform, the Cluster Management API, and the Management Console is also experiencing delays. We have implemented a fix that has significantly reduced the delays experienced when applying configuration and Kafka integration changes to Clickhouse clusters and also reduced the delays when making changes to Kafka Users on Kafka Clusters via Terraform, the Cluster Management API, and the Management Console. We will continue to monitor the results of the fix and provide additional updates 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]).

4. 29. Januar 2026 um 01:24 UTCresolved

   This incident has been resolved.

1. 23. Januar 2026 um 00:19 UTCinvestigating

   We are currently experiencing delays with provisioning clusters through the Cluster Management API and Management Console. During this time, cluster provisioning (and other related operations such as adding and removing nodes) may take longer than usual. 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. 23. Januar 2026 um 01:18 UTCidentified

   We are still experiencing delays with provisioning clusters through the Cluster Management API and Management Console and we have also identified API causing delays when adding/deleting Kafka Integrations. As a result these API's may take longer than usual. Due to this Customer-initiated resize via the console and API have been temporarily disabled. If you require a resize of your cluster, please contact our support team. We have identified the cause and our team is working on resolving this problem. 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]).

3. 23. Januar 2026 um 02:17 UTCmonitoring

   A fix has been implemented and we are monitoring the results. If you have an urgent matter, please reach out to us via the support portal (support.instaclustr.com) or email ([email protected]).

4. 23. Januar 2026 um 03:27 UTCresolved

   This incident has been resolved.

1. 9. Januar 2026 um 00:48 UTCidentified

   We are currently fixing the unavailability of Microsoft Social SSO login for our Management Console. Our team is actively working to resolve the issue and we apologise for any inconvenience caused. Other login methods for Management Console are still working. The Cluster Management API, Monitoring API, Prometheus API and Support Portal 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]).

2. 9. Januar 2026 um 04:56 UTCresolved

   Microsoft Social SSO login for Management Console has been fixed and customers can use the Sign in with Microsoft option again.

1. 23. Dezember 2025 um 21:40 UTCinvestigating

   We are currently investigating some delayed aggregated metrics on our Monitoring API. Our team is actively working to resolve the issue and we apologise for any inconvenience caused. This issue means that the "last 3 hours" and "last 6 hours" view for metrics on the console (and the monitoring API) are not working. Realtime metrics, and viewing metrics over a longer duration still works. 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]).

2. 23. Dezember 2025 um 23:01 UTCmonitoring

   We've identified the issue and have implemented a fix. We have monitored a decrease in the delay for these aggregated metrics. We will continue to monitor the issue while the backlog of metrics are processed.

3. 24. Dezember 2025 um 04:04 UTCmonitoring

   We have monitored a further decrease in the delay for these aggregated metrics. We will continue to monitor the issue while more of the backlog of metrics are processed. As a result the "last 3 hours" and "last 6 hours" view for metrics on the console (and the monitoring API) are now showing a limited set of metrics. Realtime metrics, and viewing metrics over a longer duration still works. We will provide more 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]).

4. 24. Dezember 2025 um 10:35 UTCmonitoring

   We have monitored an even further decrease in the delay for these aggregated metrics. Most of the backlog of metrics have been processed. As a result the "last 3 hours" view for metrics on the console (and the monitoring API) may not show some metrics. Realtime metrics, and viewing metrics over a longer duration still works. We will provide more 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]).

5. 24. Dezember 2025 um 23:27 UTCresolved

   This incident has been resolved.

1. 20. Oktober 2025 um 09:33 UTCmonitoring

   Multiple Instaclustr systems have been affected by an incident which is affecting multiple AWS services in us-east-1 During this incident, cluster provisioning operations will not work. Existing clusters and our monitoring systems are unaffected. We have disabled some platform functionality including customer-initated resizes to limit the impact of this issue. We are continuing to monitor the incident and will restore disabled functionality when the issue is resolved. For more information, refer to https://status.instaclustr.com or contact [email protected]

2. 20. Oktober 2025 um 10:52 UTCmonitoring

   Multiple Instaclustr systems have been affected by an incident which is affecting AWS DynamoDB and related services in us-east-1. Many systems are showing signs of recovery, however we are continuing to see some issues affecting provisioning operations. We are continuing to investigate these issues Cluster resizes and node replaces remain disabled. For more information, refer to https://status.instaclustr.com or contact [email protected]

3. 20. Oktober 2025 um 12:30 UTCmonitoring

   We are continuing to see issues with provisioning operations in AWS us-east-1. Operations in other regions appear to be restored, but resizes and replaces will remain disabled until the issues in us-east-1 are confirmed to be resolved. We are continuing to monitor these issues. For more information, refer to https://status.instaclustr.com or contact [email protected]

4. 20. Oktober 2025 um 13:58 UTCmonitoring

   We are continuing to see issues with provisioning operations in AWS us-east-1. Operations in other regions appear to be restored, but resizes and replaces will remain disabled until the issues in us-east-1 are confirmed to be resolved. We are continuing to monitor these issues and will re-evaluate when operations in the region become more reliable. For more information, refer to https://status.instaclustr.com or contact [email protected]

5. 20. Oktober 2025 um 17:06 UTCmonitoring

   We are continuing to see issues with provisioning operations in AWS us-east-1. Operations in other regions appear to be restored, but resizes and replaces will remain disabled until the issues in us-east-1 are confirmed to be resolved. At this time AWS is still reporting a large number of impacted services, and EC2 operations are being rate-limited. We are continuing to monitor these issues and will re-evaluate when operations in the region become more reliable. For more information, refer to https://status.instaclustr.com or contact [email protected]

6. 20. Oktober 2025 um 20:33 UTCmonitoring

   Update - We are seeing recovery for provisioning operations in AWS us-east-1. Operations in other regions appear to be restored, but resizes and replaces will remain disabled until the issues in us-east-1 are confirmed to be resolved. At this time AWS is still reporting some throttling of EC2 instance launches, though it has been reduced. We are continuing to monitor these issues and will re-evaluate when operations in the region become more reliable. For more information, refer to https://status.instaclustr.com or contact [email protected]

7. 21. Oktober 2025 um 00:22 UTCmonitoring

   Update - We have observed stable provisioning operations in AWS us-east-1, and AWS has reported all AWS services have returned to normal operations. Resize and replace operations have been restored on the Instaclustr Managed Platform, and no additional impact is remaining from this incident.

8. 21. Oktober 2025 um 00:26 UTCresolved

   Update - We have observed stable provisioning operations in AWS us-east-1, and AWS has reported all AWS services have returned to normal operations. Resize and replace operations have been restored on the Instaclustr Managed Platform, and no additional impact is remaining from this incident.

1. 8. Oktober 2025 um 17:27 UTCinvestigating

   We are experiencing issues with downloading certificates for Kafka clusters via the Instaclustr Console and API. This affects both new and existing Kafka-only clusters downloads. Other application clusters remain unaffected by this issue Our team is actively investigating the problem and working on a resolution. We will provide updates as soon as more information becomes available.If you have an urgent matter, please reach out to us via the support portal (support.instaclustr.com) or email ([email protected]).

2. 8. Oktober 2025 um 17:55 UTCidentified

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

3. 8. Oktober 2025 um 19:25 UTCinvestigating

   We are continuing to investigate this issue.

4. 8. Oktober 2025 um 19:26 UTCmonitoring

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

5. 8. Oktober 2025 um 19:48 UTCresolved

   This incident has been resolved.