Historique des pannes de Instaclustr

1. 10 septembre 2026 à 02:56 UTCidentified

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

2. 10 septembre 2026 à 03:28 UTCmonitoring

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

3. 10 septembre 2026 à 03:40 UTCresolved

   This incident has been resolved.

1. 20 août 2026 à 17:15 UTCidentified

   Nous vivons actuellement une dégradation des services et des perturbations potentielles dans la région de Google Cloud Platform us-west1. Cet incident est le résultat d'un problème permanent avec l'infrastructure du fournisseur de cloud. Vous ne pourrez pas fournir de nouveaux clusters ou nœuds. Les nœuds existants dans nous-west1 peuvent ne pas être disponibles. Les centres de données en grappes dans d'autres régions ne sont pas touchés, mais connaissent des problèmes de réseautage lorsqu'ils interagissent avec des nœuds dans l'ouest de nous1. Les clients individuels touchés sont contactés via des tickets d'assistance. Nous surveillons activement la situation et fournirons des détails supplémentaires dès qu'ils seront disponibles. Le statut du GCP est suivi à https://status.cloud.google.com/. Si vous avez un problème urgent, veuillez nous contacter via le portail de support (support.instaclustr.com) ou par courriel ([email protected]).

2. 20 août 2026 à 17:16 UTCidentified

   Nous continuons de travailler sur une solution à ce problème.

3. 20 août 2026 à 17:58 UTCidentified

   L'échelle verticale a été temporairement désactivée dans la région de GCP us-west1 en raison de cette panne de fournisseur de cloud. Nous réactiverons cette fonctionnalité lorsque la panne du fournisseur de cloud sera résolue.

4. 20 août 2026 à 19:06 UTCmonitoring

   Google a terminé les mesures d'atténuation et fait état de la récupération de plusieurs produits. Nous continuerons à surveiller l'incident jusqu'à ce que les produits restants soient récupérés. L'échelle verticale reste désactivée dans nous-Ouest1.

5. 20 août 2026 à 19:46 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 19 août 2026 à 10:05 UTCidentified

   Nous voyons actuellement des problèmes de compatibilité entre le fournisseur d'Instaclustr Terraform et l'API de gestion de grappes, affectant les opérations impliquant des grappes OpenSearch. Les opérations standard des groupes de clients ne sont pas affectées. L'API de surveillance et l'API Prométhée demeurent opérationnels. Notre équipe travaille activement pour résoudre le problème et nous nous excusons pour tout désagrément. D'autres mises à jour seront fournies à mesure que de plus amples renseignements seront disponibles. Si vous avez un problème urgent, veuillez nous contacter par le biais du portail de support à https://support.instaclustr.com ou par courriel à [email protected].

2. 19 août 2026 à 12:36 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 29 juillet 2026 à 00:11 UTCidentified

   Nous rencontrons actuellement des problèmes avec la fourniture de réseaux privés PostgreSQLTM avec 3 nœuds via l'API de gestion de grappes et la console de gestion. Notre équipe travaille activement à résoudre ce problème et nous nous excusons pour tout désagrément causé. Les grappes de clients existantes ne sont pas affectées, et l'API de surveillance et l'API de Prométhée sont opérationnelles. Des renseignements supplémentaires seront fournis à mesure qu'ils seront disponibles. Si vous avez un problème urgent, veuillez nous contacter via le portail de support (support.instaclustr.com) ou par courriel ([email protected]).

2. 29 juillet 2026 à 03:38 UTCidentified

   Nous continuons de travailler sur une solution à ce problème.

3. 29 juillet 2026 à 09:27 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 22 juillet 2026 à 13:04 UTCidentified

   Nous subissons actuellement une dégradation des services et des perturbations potentielles dans la zone de GCP us-east4-b. GCP n'a pas encore mis à jour sa page d'état, cependant l'enquête initiale indique un problème probable avec l'infrastructure du fournisseur de cloud dans la zone us-east4-b. Tandis que nous assistons à une récupération partielle, dans l'intervalle, la fourniture de nouveaux groupes ou nœuds dans la zone GCP concernée sera affectée. Aussi les nœuds existants dans la zone GCP us-east4-b peuvent faire face à des problèmes intermittents et être hors ligne. Vous devriez toujours pouvoir accéder à vos clusters si vous utilisez une configuration standard. Les clients individuels touchés sont contactés via des tickets d'assistance. Nous surveillons activement la situation et fournirons des détails supplémentaires dès qu'ils seront disponibles. Le statut du GCP est suivi à https://status.cloud.google.com/. Si vous avez un problème urgent, veuillez nous contacter via le portail de support (support.instaclustr.com) ou par courriel ([email protected]).

2. 22 juillet 2026 à 13:34 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 21 juillet 2026 à 04:55 UTCinvestigating

   Nous rencontrons actuellement des problèmes avec la fourniture de clusters Kafka Connect & Cadence dans les VPC existants par l'intermédiaire de l'API de gestion des grappes et de la console de gestion. Notre équipe travaille activement à résoudre ce problème et nous nous excusons pour tout désagrément causé. Les grappes de clients existantes ne sont pas affectées, et l'API de surveillance et l'API de Prométhée sont opérationnelles. Des renseignements supplémentaires seront fournis à mesure qu'ils seront disponibles. Si vous avez un problème urgent, veuillez nous contacter via le portail de support (support.instaclustr.com) ou par courriel ([email protected]).

2. 21 juillet 2026 à 05:25 UTCidentified

   Le problème a été identifié et une solution est en cours de mise en oeuvre.

3. 21 juillet 2026 à 08:12 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

4. 21 juillet 2026 à 08:56 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 16 juillet 2026 à 04:34 UTCidentified

   Nous enquêtons actuellement sur un problème qui cause une erreur de blocage des requêtes de monitoring Prometheus avec une erreur 403. D'autres requêtes de surveillance Prométheus ne sont pas concernées. Notre équipe travaille activement à résoudre le problème, et nous nous excusons de tout désagrément causé. La console de gestion, l'API de gestion des grappes et l'API de surveillance sont toujours opérationnelles. Nous fournirons des mises à jour dès qu'elles seront disponibles. Si vous avez un problème urgent, veuillez nous contacter via le portail de support (support.instaclustr.com) ou par courriel ([email protected]).

2. 16 juillet 2026 à 04:52 UTCidentified

   Le problème a été identifié et notre équipe travaille activement à la mise en oeuvre d'une solution. Les requêtes de monitoring Prometheus au niveau des grappes sont incorrectement bloquées avec une erreur 403. D'autres requêtes de surveillance Prométheus ne sont pas concernées. Les grappes de clients existantes ne sont pas affectées. La console de gestion et l'API de gestion des grappes sont toujours opérationnelles. Nous fournirons des mises à jour dès qu'elles seront disponibles. Si vous avez un problème urgent, veuillez nous contacter via le portail de support (support.instaclustr.com) ou par courriel ([email protected]).

3. 16 juillet 2026 à 08:52 UTCmonitoring

   Un correctif est en cours de déploiement et nous surveillons les résultats.

4. 16 juillet 2026 à 09:48 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 13 mai 2026 à 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 à 12:26 UTCresolved

   This incident has been resolved.

1. 8 mai 2026 à 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 à 01:55 UTCidentified

   We are continuing to monitor the issue.

3. 9 mai 2026 à 05:02 UTCresolved

   This incident has been resolved.

1. 29 avril 2026 à 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 avril 2026 à 06:35 UTCresolved

   This incident has been resolved.

1. 24 mars 2026 à 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 mars 2026 à 08:36 UTCresolved

   A fix for this issue has been deployed.

1. 10 mars 2026 à 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 mars 2026 à 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 mars 2026 à 06:04 UTCidentified

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

4. 10 mars 2026 à 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 mars 2026 à 06:53 UTCresolved

   This incident has been resolved.

1. 4 mars 2026 à 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 mars 2026 à 06:05 UTCresolved

   This incident has been resolved.

1. 12 février 2026 à 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 février 2026 à 02:46 UTCidentified

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

3. 12 février 2026 à 07:22 UTCresolved

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

1. 27 janvier 2026 à 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 janvier 2026 à 00:37 UTCmonitoring

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

3. 28 janvier 2026 à 01:03 UTCresolved

   This incident has been resolved.

1. 27 janvier 2026 à 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 janvier 2026 à 21:31 UTCidentified

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

3. 28 janvier 2026 à 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 janvier 2026 à 01:24 UTCresolved

   This incident has been resolved.

1. 23 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 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 janvier 2026 à 03:27 UTCresolved

   This incident has been resolved.

1. 9 janvier 2026 à 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 janvier 2026 à 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 décembre 2025 à 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 décembre 2025 à 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 décembre 2025 à 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 décembre 2025 à 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 décembre 2025 à 23:27 UTCresolved

   This incident has been resolved.

1. 20 octobre 2025 à 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 octobre 2025 à 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 octobre 2025 à 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 octobre 2025 à 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 octobre 2025 à 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 octobre 2025 à 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 octobre 2025 à 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 octobre 2025 à 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.