Historial de interrupciones de Instaclustr

1. August 20, 2026 at 5:15 PM UTCidentified

   Actualmente estamos experimentando degradación de los servicios y posibles perturbaciones en la región de Google Cloud Platform us-west1. Este incidente es resultado de un problema continuo con la infraestructura del proveedor de la nube. No podrá suministrar nuevos racimos o nodos. Los nodos existentes en nosotros-oeste1 pueden ser indisponibles. Los centros de datos de racimo en otras regiones no son afectados, pero están experimentando problemas de redes cuando interactúan con los nodos en nosotros-oeste1. Los clientes con impacto individual están siendo contactados a través de entradas de soporte. Estamos monitoreando activamente la situación y proporcionaremos detalles adicionales cuando estén disponibles. GCP status is tracked at https://status.cloud.google.com/. Si usted tiene un asunto urgente, por favor contacte con nosotros a través del portal de soporte (support.instaclustr.com) o correo electrónico ([email protected]).

2. August 20, 2026 at 5:16 PM UTCidentified

   Seguimos trabajando para solucionar este problema.

3. August 20, 2026 at 5:58 PM UTCidentified

   El escalado vertical ha sido deshabilitado temporalmente en la región del GCP nosotros-oeste1 debido a esta pérdida de proveedores de nube. Volveremos a habilitar esta funcionalidad cuando se resuelva el outage del proveedor de la nube.

4. August 20, 2026 at 7:06 PM UTCmonitoring

   Google ha completado las mitigacións y están reportando recuperación en varios productos. Seguiremos vigilando el incidente hasta que se hayan recuperado los productos restantes. El escalado vertical permanece desactivado en nosotros-oeste1.

5. August 20, 2026 at 7:46 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 19, 2026 at 10:05 AM UTCidentified

   Actualmente estamos viendo problemas de compatibilidad entre el proveedor de Instaclustr Terraform y la API de gestión de componentes, afectando operaciones que involucran a grupos de OpenSearch. Las operaciones estándar de grupos de clientes no son afectadas. The Monitoring API and Prometheus API remain operational. Nuestro equipo está trabajando activamente para resolver el problema y nos disculpamos por cualquier inconveniente. Se proporcionarán más actualizaciones a medida que se disponga de más información. Si usted tiene un asunto urgente, póngase en contacto con nosotros a través del portal de soporte en https://support.instaclustr.com o por correo electrónico en [email protected].

2. August 19, 2026 at 12:36 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 29, 2026 at 12:11 AM UTCidentified

   Actualmente estamos experimentando problemas con la provisión de grupos de red privada PostgreSQL con 3 nodos a través de la API y la consola de gestión Cluster Management. Nuestro equipo está trabajando activamente para resolver este problema y nos disculpamos por cualquier inconveniente causado. Los clústeres de clientes existentes no son afectados, y la API de monitoreo y la API de Prometheus están operativos. Se proporcionarán detalles adicionales cuando estén disponibles. Si usted tiene un asunto urgente, por favor contacte con nosotros a través del portal de soporte (support.instaclustr.com) o correo electrónico ([email protected]).

2. July 29, 2026 at 3:38 AM UTCidentified

   Seguimos trabajando para solucionar este problema.

3. July 29, 2026 at 9:27 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 1:04 PM UTCidentified

   Actualmente estamos experimentando degradación de los servicios y posibles perturbaciones en la zona GCP us-east4-b. GCP no ha actualizado su página de estado todavía, sin embargo la investigación inicial indica un problema probable con la infraestructura del proveedor de la nube en la zona us-east4-b. Si bien estamos viendo una recuperación parcial, mientras tanto, la provisión de nuevos grupos o nodos en la zona GCP interesada se verá afectada. También los nodos existentes en la zona GCP us-east4-b pueden enfrentar problemas intermitentes y estar fuera de línea. Usted todavía debe ser capaz de acceder a sus clusters si usted está ejecutando una configuración estándar. Los clientes con impacto individual están siendo contactados a través de entradas de soporte. Estamos monitoreando activamente la situación y proporcionaremos detalles adicionales cuando estén disponibles. GCP status is tracked at https://status.cloud.google.com/. Si usted tiene un asunto urgente, por favor contacte con nosotros a través del portal de soporte (support.instaclustr.com) o correo electrónico ([email protected]).

2. July 22, 2026 at 1:34 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 21, 2026 at 4:55 AM UTCinvestigating

   Actualmente estamos experimentando problemas con el suministro de grupos de Cadence Kafka Connect en los VPC existentes a través de la API y la consola de gestión de componentes. Nuestro equipo está trabajando activamente para resolver este problema y nos disculpamos por cualquier inconveniente causado. Los clústeres de clientes existentes no son afectados, y la API de monitoreo y la API de Prometheus están operativos. Se proporcionarán detalles adicionales cuando estén disponibles. Si usted tiene un asunto urgente, por favor contacte con nosotros a través del portal de soporte (support.instaclustr.com) o correo electrónico ([email protected]).

2. July 21, 2026 at 5:25 AM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. July 21, 2026 at 8:12 AM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. July 21, 2026 at 8:56 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 16, 2026 at 4:34 AM UTCidentified

   Actualmente estamos investigando un problema que causa el nivel de grupo Prometheus solicitudes de monitoreo de consultas para ser bloqueadas incorrectamente con un error 403. Otras consultas de monitoreo Prometheus no son afectadas. Nuestro equipo está trabajando activamente para resolver el problema, y nos disculpamos por cualquier inconveniente causado. La Consola de Gestión, la API de Gestión de Grupos y la API de Monitoreo siguen funcionando. Proporcionaremos actualizaciones tan pronto como estén disponibles. Si usted tiene un asunto urgente, por favor contacte con nosotros a través del portal de soporte (support.instaclustr.com) o correo electrónico ([email protected]).

2. July 16, 2026 at 4:52 AM UTCidentified

   La cuestión ha sido identificada, y nuestro equipo está trabajando activamente en la aplicación de una solución. Las solicitudes de seguimiento de Prometheus a nivel de grupo están siendo bloqueadas incorrectamente con un error de 403. Otras consultas de monitoreo Prometheus no son afectadas. Los grupos de clientes existentes no son afectados. La Consola de Gestión y la API de Gestión de Grupos aún están en funcionamiento. Proporcionaremos actualizaciones tan pronto como estén disponibles. Si usted tiene un asunto urgente, por favor contacte con nosotros a través del portal de soporte (support.instaclustr.com) o correo electrónico ([email protected]).

3. July 16, 2026 at 8:52 AM UTCmonitoring

   Se está poniendo en marcha una solución y estamos monitoreando los resultados.

4. July 16, 2026 at 9:48 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. May 13, 2026 at 6:47 AM 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. May 13, 2026 at 12:26 PM UTCresolved

   This incident has been resolved.

1. May 8, 2026 at 1:33 AM 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. May 8, 2026 at 1:55 AM UTCidentified

   We are continuing to monitor the issue.

3. May 9, 2026 at 5:02 AM UTCresolved

   This incident has been resolved.

1. April 29, 2026 at 5:28 AM 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. April 29, 2026 at 6:35 AM UTCresolved

   This incident has been resolved.

1. March 24, 2026 at 1:10 AM 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. March 24, 2026 at 8:36 AM UTCresolved

   A fix for this issue has been deployed.

1. March 10, 2026 at 3:22 AM 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. March 10, 2026 at 4:54 AM 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. March 10, 2026 at 6:04 AM UTCidentified

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

4. March 10, 2026 at 6:28 AM 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. March 10, 2026 at 6:53 AM UTCresolved

   This incident has been resolved.

1. March 4, 2026 at 12:18 AM 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. March 4, 2026 at 6:05 AM UTCresolved

   This incident has been resolved.

1. February 12, 2026 at 1:47 AM 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. February 12, 2026 at 2:46 AM UTCidentified

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

3. February 12, 2026 at 7:22 AM UTCresolved

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

1. January 27, 2026 at 11:06 PM 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. January 28, 2026 at 12:37 AM UTCmonitoring

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

3. January 28, 2026 at 1:03 AM UTCresolved

   This incident has been resolved.

1. January 27, 2026 at 9:37 AM 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. January 27, 2026 at 9:31 PM UTCidentified

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

3. January 28, 2026 at 8:56 AM 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. January 29, 2026 at 1:24 AM UTCresolved

   This incident has been resolved.

1. January 23, 2026 at 12:19 AM 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. January 23, 2026 at 1:18 AM 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. January 23, 2026 at 2:17 AM 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. January 23, 2026 at 3:27 AM UTCresolved

   This incident has been resolved.

1. January 9, 2026 at 12:48 AM 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. January 9, 2026 at 4:56 AM UTCresolved

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

1. December 23, 2025 at 9:40 PM 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. December 23, 2025 at 11:01 PM 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. December 24, 2025 at 4:04 AM 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. December 24, 2025 at 10:35 AM 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. December 24, 2025 at 11:27 PM UTCresolved

   This incident has been resolved.

1. October 20, 2025 at 9:33 AM 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. October 20, 2025 at 10:52 AM 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. October 20, 2025 at 12:30 PM 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. October 20, 2025 at 1:58 PM 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. October 20, 2025 at 5:06 PM 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. October 20, 2025 at 8:33 PM 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. October 21, 2025 at 12:22 AM 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. October 21, 2025 at 12:26 AM 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. October 8, 2025 at 5:27 PM 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. October 8, 2025 at 5:55 PM UTCidentified

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

3. October 8, 2025 at 7:25 PM UTCinvestigating

   We are continuing to investigate this issue.

4. October 8, 2025 at 7:26 PM UTCmonitoring

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

5. October 8, 2025 at 7:48 PM UTCresolved

   This incident has been resolved.