Cronologia delle interruzioni di Instaclustr

1. 20 agosto 2026 alle ore 17:15 UTCidentified

   Attualmente stiamo sperimentando il degrado dei servizi e potenziali interruzioni nella regione di Google Cloud Platform us-west1. Questo incidente è il risultato di un problema in corso con l'infrastruttura del provider cloud. Non sarai in grado di fornire nuovi cluster o nodi. I nodi esistenti in noi-ovest1 potrebbero non essere disponibili. I Cluster datacentres in altre regioni non sono influenzati, ma stanno sperimentando problemi di rete quando interagiscono con i nodi in us-west1. I clienti con impatto individuale vengono contattati tramite biglietti di supporto. Stiamo monitorando attivamente la situazione e fornire ulteriori dettagli come diventano disponibili. Lo stato del GCP è seguito all'indirizzo https://status.cloud.google.com/. Se avete una questione urgente, contattateci tramite il portale di supporto (support.instaclustr.com) o e-mail ([email protected]).

2. 20 agosto 2026 alle ore 17:16 UTCidentified

   Stiamo continuando a lavorare per risolvere questo problema.

3. 20 agosto 2026 alle ore 17:58 UTCidentified

   Lo scaling verticale è stato temporaneamente disabilitato nella regione GCP us-west1 a causa di questo outage del provider cloud. Riaccenderemo questa funzionalità quando il cloud provider outage viene risolto.

4. 20 agosto 2026 alle ore 19:06 UTCmonitoring

   Google ha completato le mitigazioni e stanno segnalando il recupero attraverso più prodotti. Continueremo a monitorare l'incidente fino al recupero dei prodotti rimanenti. Ridimensionamento verticale rimane disabilitato in noi-west1.

5. 20 agosto 2026 alle ore 19:46 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 19 agosto 2026 alle ore 10:05 UTCidentified

   Attualmente stiamo vedendo problemi di compatibilità tra il provider Instaclustr Terraform e l'API Cluster Management, che interessano operazioni che coinvolgono cluster OpenSearch. Le operazioni di cluster di clienti standard non sono influenzate. L'API di monitoraggio e l'API Prometheus rimangono operativi. Il nostro team sta lavorando attivamente per risolvere il problema e ci scusiamo per qualsiasi disagio. Ulteriori aggiornamenti saranno forniti come ulteriori informazioni diventano disponibili. Se avete una questione urgente, vi preghiamo di contattarci tramite il portale di supporto all'indirizzo https://support.instaclustr.com o via e-mail all'indirizzo [email protected].

2. 19 agosto 2026 alle ore 12:36 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 29 luglio 2026 alle ore 00:11 UTCidentified

   Stiamo attualmente sperimentando problemi con la fornitura di cluster di rete privata PostgreSQL con 3 nodi attraverso l'API di gestione cluster e la console di gestione. Il nostro team sta attivamente lavorando per risolvere questo problema e ci scusiamo per qualsiasi inconveniente causato. I cluster dei clienti esistenti non sono influenzati e le API di monitoraggio e Prometheus sono operative. Ulteriori dettagli saranno forniti come diventano disponibili. Se avete una questione urgente, contattateci tramite il portale di supporto (support.instaclustr.com) o e-mail ([email protected]).

2. 29 luglio 2026 alle ore 03:38 UTCidentified

   Stiamo continuando a lavorare per risolvere questo problema.

3. 29 luglio 2026 alle ore 09:27 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 22 luglio 2026 alle ore 13:04 UTCidentified

   Attualmente stiamo sperimentando il degrado dei servizi e potenziali interruzioni nella zona GCP us-east4-b. GCP non ha ancora aggiornato la sua pagina di stato, tuttavia l'indagine iniziale indica un problema probabile con l'infrastruttura del provider cloud nella zona us-east4-b. Mentre stiamo vedendo il recupero parziale, nel frattempo la fornitura di nuovi cluster o nodi nella zona GCP interessata sarà influenzata. Anche i nodi esistenti nella zona GCP us-east4-b possono affrontare problemi intermittenti ed essere offline. Si dovrebbe ancora essere in grado di accedere ai cluster se si esegue una configurazione standard. I clienti con impatto individuale vengono contattati tramite biglietti di supporto. Stiamo monitorando attivamente la situazione e fornire ulteriori dettagli come diventano disponibili. Lo stato del GCP è seguito all'indirizzo https://status.cloud.google.com/. Se avete una questione urgente, contattateci tramite il portale di supporto (support.instaclustr.com) o e-mail ([email protected]).

2. 22 luglio 2026 alle ore 13:34 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 21 luglio 2026 alle ore 04:55 UTCinvestigating

   Attualmente stiamo vivendo problemi con la fornitura di cluster Kafka Connect & Cadence in VPC esistenti attraverso l'API di Gestione cluster e la console di gestione. Il nostro team sta attivamente lavorando per risolvere questo problema e ci scusiamo per qualsiasi inconveniente causato. I cluster dei clienti esistenti non sono influenzati e le API di monitoraggio e Prometheus sono operative. Ulteriori dettagli saranno forniti come diventano disponibili. Se avete una questione urgente, contattateci tramite il portale di supporto (support.instaclustr.com) o e-mail ([email protected]).

2. 21 luglio 2026 alle ore 05:25 UTCidentified

   Il problema è stato identificato e si sta attuando una correzione.

3. 21 luglio 2026 alle ore 08:12 UTCmonitoring

   Una soluzione è stata implementata e stiamo monitorando i risultati.

4. 21 luglio 2026 alle ore 08:56 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 16 luglio 2026 alle ore 04:34 UTCidentified

   Stiamo attualmente indagando su un problema che causa il livello di cluster Le richieste di monitoraggio Prometheus per essere bloccate in modo errato con un errore di 403. Altre domande di monitoraggio Prometheus non sono influenzate. Il nostro team sta lavorando attivamente per risolvere il problema, e ci scusiamo per qualsiasi disagio causato. Le API Gestione Console, Gestione cluster e Monitoraggio sono ancora operative. Forniremo aggiornamenti non appena saranno disponibili. Se avete una questione urgente, contattateci tramite il portale di supporto (support.instaclustr.com) o e-mail ([email protected]).

2. 16 luglio 2026 alle ore 04:52 UTCidentified

   Il problema è stato identificato, e il nostro team sta attivamente lavorando per implementare una correzione. Le richieste di monitoraggio Prometheus di livello Cluster vengono bloccate in modo errato con un errore di 403. Altre domande di monitoraggio Prometheus non sono influenzate. I cluster dei clienti esistenti non sono influenzati. Le API Gestione Console e Gestione cluster sono ancora operative. Forniremo aggiornamenti non appena saranno disponibili. Se avete una questione urgente, contattateci tramite il portale di supporto (support.instaclustr.com) o e-mail ([email protected]).

3. 16 luglio 2026 alle ore 08:52 UTCmonitoring

   Una soluzione è in fase di roll out e stiamo monitorando i risultati.

4. 16 luglio 2026 alle ore 09:48 UTCresolved

   Questo incidente è stato risolto.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 13 maggio 2026 alle ore 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 maggio 2026 alle ore 12:26 UTCresolved

   This incident has been resolved.

1. 8 maggio 2026 alle ore 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 maggio 2026 alle ore 01:55 UTCidentified

   We are continuing to monitor the issue.

3. 9 maggio 2026 alle ore 05:02 UTCresolved

   This incident has been resolved.

1. 29 aprile 2026 alle ore 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 aprile 2026 alle ore 06:35 UTCresolved

   This incident has been resolved.

1. 24 marzo 2026 alle ore 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 marzo 2026 alle ore 08:36 UTCresolved

   A fix for this issue has been deployed.

1. 10 marzo 2026 alle ore 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 marzo 2026 alle ore 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 marzo 2026 alle ore 06:04 UTCidentified

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

4. 10 marzo 2026 alle ore 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 marzo 2026 alle ore 06:53 UTCresolved

   This incident has been resolved.

1. 4 marzo 2026 alle ore 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 marzo 2026 alle ore 06:05 UTCresolved

   This incident has been resolved.

1. 12 febbraio 2026 alle ore 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 febbraio 2026 alle ore 02:46 UTCidentified

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

3. 12 febbraio 2026 alle ore 07:22 UTCresolved

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

1. 27 gennaio 2026 alle ore 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 gennaio 2026 alle ore 00:37 UTCmonitoring

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

3. 28 gennaio 2026 alle ore 01:03 UTCresolved

   This incident has been resolved.

1. 27 gennaio 2026 alle ore 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 gennaio 2026 alle ore 21:31 UTCidentified

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

3. 28 gennaio 2026 alle ore 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 gennaio 2026 alle ore 01:24 UTCresolved

   This incident has been resolved.

1. 23 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 03:27 UTCresolved

   This incident has been resolved.

1. 9 gennaio 2026 alle ore 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 gennaio 2026 alle ore 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 dicembre 2025 alle ore 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 dicembre 2025 alle ore 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 dicembre 2025 alle ore 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 dicembre 2025 alle ore 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 dicembre 2025 alle ore 23:27 UTCresolved

   This incident has been resolved.

1. 20 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 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 ottobre 2025 alle ore 17:55 UTCidentified

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

3. 8 ottobre 2025 alle ore 19:25 UTCinvestigating

   We are continuing to investigate this issue.

4. 8 ottobre 2025 alle ore 19:26 UTCmonitoring

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

5. 8 ottobre 2025 alle ore 19:48 UTCresolved

   This incident has been resolved.