Histórico de interrupções do Instaclustr

1. 20 Eost 2026 da 17:15 UTCidentified

   Atualmente, estamos experimentando degradação de serviços e possíveis rupturas na região do Google Cloud Platform us-west1. Este incidente é resultado de um problema contínuo com a infraestrutura do provedor de nuvem. Você será incapaz de fornecer novos clusters ou nós. Os nós existentes em us-west1 podem não estar disponíveis. Os datacentres de cluster em outras regiões não são afetados, mas estão experimentando problemas de rede ao interagir com nós em us-west1. Clientes impactados individuais estão sendo contatados através de tickets de suporte. Estamos a acompanhar activamente a situação e iremos fornecer mais pormenores à medida que estiverem disponíveis. O status do GCP é rastreado em https://status.cloud.google.com/. Se você tem um assunto urgente, por favor, entre em contato conosco através do portal de suporte (support.instaclustr.com) ou email ([email protected]).

2. 20 Eost 2026 da 17:16 UTCidentified

   Continuamos trabalhando em uma solução para esse problema.

3. 20 Eost 2026 da 17:58 UTCidentified

   A escala vertical foi temporariamente desativada na região us-west1 do GCP devido a essa falha no provedor de nuvem. Vamos reativar esta funcionalidade quando a falha no provedor de nuvem for resolvida.

4. 20 Eost 2026 da 19:06 UTCmonitoring

   Google completaram mitigação e estão relatando recuperação em vários produtos. Continuaremos a acompanhar o incidente até que os restantes produtos tenham recuperado. A escala vertical permanece desactivada em us-west1.

5. 20 Eost 2026 da 19:46 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 19 Eost 2026 da 10:05 UTCidentified

   Estamos vendo problemas de compatibilidade entre o provedor Instaclustr Terraform e a API de gerenciamento de clusters, afetando operações envolvendo clusters OpenSearch. Operações padrão de clusters de clientes não são afetadas. A API de Monitoramento e a API Prometheus permanecem operacionais. Nossa equipe está trabalhando ativamente para resolver o problema e pedimos desculpas por qualquer inconveniente. Serão fornecidas mais actualizações à medida que mais informações estiverem disponíveis. Se você tem um assunto urgente, entre em contato conosco através do portal de suporte em https://support.instaclustr.com ou por e-mail em [email protected].

2. 19 Eost 2026 da 12:36 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 29 Gouere 2026 da 00:11 UTCidentified

   Atualmente estamos experimentando problemas com provisionamento de clusters de rede privada PostgreSQL com 3 nós através da API de gerenciamento de clusters e Console de gerenciamento. Nossa equipe está trabalhando ativamente para resolver este problema e pedimos desculpas por qualquer inconveniente causado. Os clusters de clientes existentes não são afetados, e a API de monitoramento e a API Prometheus estão operacionais. Serão fornecidos pormenores adicionais à medida que estiverem disponíveis. Se você tem um assunto urgente, por favor, entre em contato conosco através do portal de suporte (support.instaclustr.com) ou email ([email protected]).

2. 29 Gouere 2026 da 03:38 UTCidentified

   Continuamos trabalhando em uma solução para esse problema.

3. 29 Gouere 2026 da 09:27 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Gouere 2026 da 13:04 UTCidentified

   Atualmente estamos experimentando degradação de serviços e possíveis rupturas na zona us-least4-b do GCP. GCP ainda não atualizou sua página de status, no entanto, a investigação inicial indica um problema provável com a infraestrutura do provedor de nuvem na zona us-least4-b. Embora estejamos a assistir a uma recuperação parcial, entretanto o fornecimento de novos clusters ou nós na zona GCP em causa será afectado. Também os nós existentes na zona us-least4-b GCP podem enfrentar problemas intermitentes e estar offline. Você ainda deve ser capaz de acessar seus clusters se você estiver executando uma configuração padrão. Clientes impactados individuais estão sendo contatados através de tickets de suporte. Estamos a acompanhar activamente a situação e iremos fornecer mais pormenores à medida que estiverem disponíveis. O status do GCP é rastreado em https://status.cloud.google.com/. Se você tem um assunto urgente, por favor, entre em contato conosco através do portal de suporte (support.instaclustr.com) ou email ([email protected]).

2. 22 Gouere 2026 da 13:34 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 21 Gouere 2026 da 04:55 UTCinvestigating

   Atualmente estamos experimentando problemas com o provisionamento de clusters Kafka Connect & Cadence em VPCs existentes através da API de gerenciamento de clusters e Console de gerenciamento. Nossa equipe está trabalhando ativamente para resolver este problema e pedimos desculpas por qualquer inconveniente causado. Os clusters de clientes existentes não são afetados, e a API de monitoramento e a API Prometheus estão operacionais. Serão fornecidos pormenores adicionais à medida que estiverem disponíveis. Se você tem um assunto urgente, por favor, entre em contato conosco através do portal de suporte (support.instaclustr.com) ou email ([email protected]).

2. 21 Gouere 2026 da 05:25 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 21 Gouere 2026 da 08:12 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 21 Gouere 2026 da 08:56 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Gouere 2026 da 04:34 UTCidentified

   Atualmente estamos investigando um problema que faz com que pedidos de consulta de monitoramento de nível de cluster Prometheus sejam incorretamente bloqueados com um erro 403. Outras consultas de monitoramento Prometheus não são afetadas. Nossa equipe está trabalhando ativamente para resolver o problema, e pedimos desculpas por qualquer inconveniente causado. O Console de gerenciamento, API de gerenciamento de clusters e API de monitoramento ainda estão operacionais. Forneceremos atualizações assim que estiverem disponíveis. Se você tem um assunto urgente, por favor, entre em contato conosco através do portal de suporte (support.instaclustr.com) ou email ([email protected]).

2. 16 Gouere 2026 da 04:52 UTCidentified

   A questão foi identificada, e nossa equipe está trabalhando ativamente na implementação de uma correção. As solicitações de consulta de monitoramento Prometheus de nível de cluster estão sendo incorretamente bloqueadas com um erro 403. Outras consultas de monitoramento Prometheus não são afetadas. Os clusters de clientes existentes não são afetados. A API de gerenciamento e gerenciamento de clusters ainda estão operacionais. Forneceremos atualizações assim que estiverem disponíveis. Se você tem um assunto urgente, por favor, entre em contato conosco através do portal de suporte (support.instaclustr.com) ou email ([email protected]).

3. 16 Gouere 2026 da 08:52 UTCmonitoring

   Está a ser feita uma correcção e estamos a monitorizar os resultados.

4. 16 Gouere 2026 da 09:48 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

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

   This incident has been resolved.

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

   We are continuing to monitor the issue.

3. 9 Mae 2026 da 05:02 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

   A fix for this issue has been deployed.

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

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

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

   This incident has been resolved.

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

   This incident has been resolved.

1. 12 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 02:46 UTCidentified

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

3. 12 Cʼhwevrer 2026 da 07:22 UTCresolved

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

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

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

3. 28 Genver 2026 da 01:03 UTCresolved

   This incident has been resolved.

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

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

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

   This incident has been resolved.

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

   This incident has been resolved.

1. 9 Genver 2026 da 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 Genver 2026 da 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 Kerzu 2025 da 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 Kerzu 2025 da 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 Kerzu 2025 da 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 Kerzu 2025 da 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 Kerzu 2025 da 23:27 UTCresolved

   This incident has been resolved.

1. 20 Here 2025 da 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 Here 2025 da 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 Here 2025 da 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 Here 2025 da 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 Here 2025 da 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 Here 2025 da 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 Here 2025 da 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 Here 2025 da 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 Here 2025 da 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 Here 2025 da 17:55 UTCidentified

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

3. 8 Here 2025 da 19:25 UTCinvestigating

   We are continuing to investigate this issue.

4. 8 Here 2025 da 19:26 UTCmonitoring

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

5. 8 Here 2025 da 19:48 UTCresolved

   This incident has been resolved.