Historia awarii Instaclustr

1. 20 sierpnia 2026 17:15 UTCidentified

   Obecnie mamy do czynienia z degradacją usług i potencjalnymi zakłóceniami w regionie Google Cloud Platform na zachód od Europy1. Ten incydent jest wynikiem trwającego problemu z infrastrukturą operatora chmury. Nie będziesz w stanie zapewnić nowych klastrów lub węzłów. Istniejące węzły w us- west1 mogą być niedostępne. Klaster danych w innych regionach są nienaruszone, ale doświadczają problemów sieciowych podczas interakcji z węzłami w us- west1. Indywidualni wpływający klienci są kontaktowani za pośrednictwem biletów wsparcia. Aktywnie monitorujemy sytuację i zapewnimy dodatkowe szczegóły w miarę ich dostępności. Status GCP jest śledzony pod adresem https: / / status.cloudd.google.com /. Jeśli masz pilną sprawę, skontaktuj się z nami poprzez portal wsparcia (support.instaclustr.com) lub e-mail (support @ instaclustr.com).

2. 20 sierpnia 2026 17:16 UTCidentified

   Kontynuujemy prace nad rozwiązaniem tego problemu.

3. 20 sierpnia 2026 17:58 UTCidentified

   Skala pionowa została tymczasowo wyłączona w regionie GCP us- west1 ze względu na brak zasilania w chmurze. Uaktywnimy tę funkcjonalność po rozwiązaniu awarii operatora chmury.

4. 20 sierpnia 2026 19:06 UTCmonitoring

   Google zakończyło działania łagodzące i informuje o odzyskaniu wielu produktów. Będziemy monitorować ten incydent do czasu odzyskania pozostałych produktów. Pionowe skalowanie pozostaje wyłączone w naszym westrze1.

5. 20 sierpnia 2026 19:46 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 19 sierpnia 2026 10:05 UTCidentified

   Obecnie obserwujemy problemy kompatybilności pomiędzy dostawcą Instaclustr Terraform a API zarządzania klastrami, wpływające na operacje obejmujące klastry OpenSearch. Operacje standardowych klastrów klientów nie ulegają zmianie. API Monitorowania i API Prometeusza nadal działają. Nasz zespół aktywnie pracuje nad rozwiązaniem problemu i przepraszamy za wszelkie niedogodności. Dalsze aktualizacje będą dostarczane w miarę dostępności większej ilości informacji. Jeśli masz pilną sprawę, skontaktuj się z nami za pośrednictwem portalu wsparcia pod adresem https: / / support.instaclustr.com lub pocztą elektroniczną na adres support @ instaclustr.com.

2. 19 sierpnia 2026 12:36 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 29 lipca 2026 00:11 UTCidentified

   Obecnie doświadczamy problemów z zaopatrzeniem prywatnych sieci PostgreSQL klastry z 3 węzły poprzez API zarządzania klastrem i konsoli zarządzania. Nasz zespół aktywnie pracuje nad rozwiązaniem tego problemu i przepraszamy za wszelkie niedogodności. Istniejące klastry klientów nie ulegają zmianie, a API Monitorowania i API Prometeusza działają. Dodatkowe informacje zostaną podane w miarę ich dostępności. Jeśli masz pilną sprawę, skontaktuj się z nami poprzez portal wsparcia (support.instaclustr.com) lub e-mail (support @ instaclustr.com).

2. 29 lipca 2026 03:38 UTCidentified

   Kontynuujemy prace nad rozwiązaniem tego problemu.

3. 29 lipca 2026 09:27 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 22 lipca 2026 13:04 UTCidentified

   Obecnie mamy do czynienia z degradacją usług i potencjalnymi zakłóceniami w strefie GCP - east4- b. GCP nie zaktualizował jeszcze swojej strony statusu, jednak wstępne dochodzenie wskazuje na problem prawdopodobny z infrastrukturą dostawcy chmur w strefie us- east4- b. Podczas gdy obserwujemy częściową regenerację, w międzyczasie wpływ będzie miało tworzenie nowych klastrów lub węzłów w danej strefie GCP. Również istniejące węzły w strefie GCP us- east4- b mogą mieć problemy przerywane i być wyłączone. Nadal powinieneś mieć dostęp do swoich klastrów, jeśli prowadzisz standardową konfigurację. Indywidualni wpływający klienci są kontaktowani za pośrednictwem biletów wsparcia. Aktywnie monitorujemy sytuację i zapewnimy dodatkowe szczegóły w miarę ich dostępności. Status GCP jest śledzony pod adresem https: / / status.cloudd.google.com /. Jeśli masz pilną sprawę, skontaktuj się z nami poprzez portal wsparcia (support.instaclustr.com) lub e-mail (support @ instaclustr.com).

2. 22 lipca 2026 13:34 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 21 lipca 2026 04:55 UTCinvestigating

   Obecnie mamy do czynienia z problemami z zaopatrzeniem klastrów Kafka Connect & Cadence w istniejące VPC za pośrednictwem API zarządzania klastrem i konsoli zarządzania. Nasz zespół aktywnie pracuje nad rozwiązaniem tego problemu i przepraszamy za wszelkie niedogodności. Istniejące klastry klientów nie ulegają zmianie, a API Monitorowania i API Prometeusza działają. Dodatkowe informacje zostaną podane w miarę ich dostępności. Jeśli masz pilną sprawę, skontaktuj się z nami poprzez portal wsparcia (support.instaclustr.com) lub e-mail (support @ instaclustr.com).

2. 21 lipca 2026 05:25 UTCidentified

   Problem został zidentyfikowany i jest w trakcie wdrażania.

3. 21 lipca 2026 08:12 UTCmonitoring

   Wprowadzono rozwiązanie i monitorujemy wyniki.

4. 21 lipca 2026 08:56 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 16 lipca 2026 04:34 UTCidentified

   Obecnie badamy problem, który powoduje, że poziom klastra Prometeusz monitorowania żądania zapytania są nieprawidłowo zablokowane z 403 błąd. Inne pytania dotyczące monitorowania Prometeusza pozostają bez zmian. Nasz zespół aktywnie pracuje nad rozwiązaniem problemu i przepraszamy za wszelkie niedogodności. Konsola zarządzania, API zarządzania klastrem i API monitorowania nadal działają. Dostarczymy aktualizacje jak tylko staną się dostępne. Jeśli masz pilną sprawę, skontaktuj się z nami poprzez portal wsparcia (support.instaclustr.com) lub e-mail (support @ instaclustr.com).

2. 16 lipca 2026 04:52 UTCidentified

   Problem został zidentyfikowany, a nasz zespół aktywnie pracuje nad wdrożeniem rozwiązania. Prometeusz na poziomie klastrowymżądania monitorowania zapytań są nieprawidłowo blokowane przy pomocy błędu 403. Inne pytania dotyczące monitorowania Prometeusza pozostają bez zmian. Istniejące klastry klientów nie ulegają zmianie. API zarządzania konsolą zarządzania i klastrem nadal działa. Dostarczymy aktualizacje jak tylko staną się dostępne. Jeśli masz pilną sprawę, skontaktuj się z nami poprzez portal wsparcia (support.instaclustr.com) lub e-mail (support @ instaclustr.com).

3. 16 lipca 2026 08:52 UTCmonitoring

   Rozwiązujemy problem i monitorujemy wyniki.

4. 16 lipca 2026 09:48 UTCresolved

   Ten incydent został rozwiązany.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

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

   This incident has been resolved.

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

   We are continuing to monitor the issue.

3. 9 maja 2026 05:02 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

   A fix for this issue has been deployed.

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

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

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

   This incident has been resolved.

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

   This incident has been resolved.

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

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

3. 12 lutego 2026 07:22 UTCresolved

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

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

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

3. 28 stycznia 2026 01:03 UTCresolved

   This incident has been resolved.

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

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

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

   This incident has been resolved.

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

   This incident has been resolved.

1. 9 stycznia 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 stycznia 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 grudnia 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 grudnia 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 grudnia 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 grudnia 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 grudnia 2025 23:27 UTCresolved

   This incident has been resolved.

1. 20 października 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 października 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 października 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 października 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 października 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 października 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 października 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 października 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.

1. 8 października 2025 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 października 2025 17:55 UTCidentified

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

3. 8 października 2025 19:25 UTCinvestigating

   We are continuing to investigate this issue.

4. 8 października 2025 19:26 UTCmonitoring

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

5. 8 października 2025 19:48 UTCresolved

   This incident has been resolved.