Instaclustr 장애 기록

1. 2026년 8월 20일 PM 5:15 UTCidentified

   우리는 현재 Google Cloud Platform 지역 us-west1의 서비스 등급 및 잠재적 인 붕괴를 경험하고 있습니다. 이 사건은 클라우드 공급자의 인프라로 지속적인 이슈의 결과입니다. 새 클러스터 또는 노드를 제공 할 수 없습니다. us-west1의 기존 노드는 사용할 수 없습니다. 다른 지역의 클러스터 데이터 센터는 비범죄이지만, us-west1의 노드와 상호 작용할 때 네트워킹 문제를 경험하고 있습니다. 개별 충격 고객은 지원 티켓을 통해 연락됩니다. 우리는 적극적으로 상황을 모니터링하고 가능한 한 추가 정보를 제공 할 것입니다. GCP 상태는 https://status.cloud.google.com/에서 추적됩니다. 긴급한 문제가 있는 경우 지원 포털(support.instaclustr.com) 또는 이메일([email protected])을 통해 저희에게 연락해 주십시오.

2. 2026년 8월 20일 PM 5:16 UTCidentified

   이 문제를 해결하기 위해 계속 노력하고 있습니다.

3. 2026년 8월 20일 PM 5:58 UTCidentified

   수직 스케일링은 GCP us-west1 지역에 일시적으로 비활성화되었습니다. 클라우드 공급자의 부족이 해결 될 때이 기능을 다시 활성화합니다.

4. 2026년 8월 20일 PM 7:06 UTCmonitoring

   Google은 완화를 완료하고 여러 제품을 통해 복구를보고 있습니다. 우리는 남아있는 제품이 회복될 때까지 사건을 계속 감시할 것입니다. 수직 스케일링은 us-west1에서 비활성화됩니다.

5. 2026년 8월 20일 PM 7:46 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 19일 AM 10:05 UTCidentified

   우리는 현재 Instaclustr Terraform 공급자와 Cluster Management API 사이의 호환성 문제가 있으며, OpenSearch 클러스터를 포함하는 작업에 영향을 미칩니다. 표준 고객 클러스터 가동은 unaffected. 모니터링 API 및 Prometheus API는 작동 상태를 유지합니다. 우리의 팀은 문제를 해결하기 위해 적극적으로 일하고 우리는 어떤 불편든지를 위해 사과합니다. 추가 업데이트는 더 많은 정보로 제공됩니다. 긴급한 문제가 있는 경우 https://support.instaclustr.com 또는 [email protected]에서 지원 포털을 통해 문의하시기 바랍니다.

2. 2026년 8월 19일 PM 12:36 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 29일 AM 12:11 UTCidentified

   현재 클러스터 관리 API 및 관리 콘솔을 통해 3개의 노드로 프라이빗 네트워크 PostgreSQL 클러스터를 제공함. 우리의 팀은 이 문제를 해결하기 위해 적극적으로 일하고 우리는 어떤 불편든지를 위해 사과합니다. 기존 고객 클러스터는 비범죄이며, 모니터링 API 및 Prometheus API는 조작상입니다. 추가 정보는 이용 가능합니다. 긴급한 문제가 있는 경우 지원 포털(support.instaclustr.com) 또는 이메일([email protected])을 통해 저희에게 연락해 주십시오.

2. 2026년 7월 29일 AM 3:38 UTCidentified

   이 문제를 해결하기 위해 계속 노력하고 있습니다.

3. 2026년 7월 29일 AM 9:27 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 22일 PM 1:04 UTCidentified

   현재 GCP us-east4-b 영역의 서비스 향상 및 잠재적 인 붕괴를 경험하고 있습니다. GCP는 아직 상태 페이지를 업데이트하지 않았습니다. 그러나 초기 조사는 우리에게 east4-b 영역의 클라우드 공급자의 인프라와 함께 발생하는 문제를 나타냅니다. GCP 영역의 새로운 클러스터 또는 노드를 제공하는 것은 부분 복구를 보이지만 영향을받습니다. 또한 GCP us-east4-b 영역의 기존 노드는 간헐적인 문제를 직면하고 오프라인으로 될 수 있습니다. 표준 구성을 실행하면 클러스터에 접근할 수 있어야 합니다. 개별 충격 고객은 지원 티켓을 통해 연락됩니다. 우리는 적극적으로 상황을 모니터링하고 가능한 한 추가 정보를 제공 할 것입니다. GCP 상태는 https://status.cloud.google.com/에서 추적됩니다. 긴급한 문제가 있는 경우 지원 포털(support.instaclustr.com) 또는 이메일([email protected])을 통해 저희에게 연락해 주십시오.

2. 2026년 7월 22일 PM 1:34 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 21일 AM 4:55 UTCinvestigating

   우리는 현재 클러스터 관리 API 및 관리 콘솔을 통해 기존 VPC로 Kafka Connect & Cadence 클러스터를 제공함. 우리의 팀은 이 문제를 해결하기 위해 적극적으로 일하고 우리는 어떤 불편든지를 위해 사과합니다. 기존 고객 클러스터는 비범죄이며, 모니터링 API 및 Prometheus API는 조작상입니다. 추가 정보는 이용 가능합니다. 긴급한 문제가 있는 경우 지원 포털(support.instaclustr.com) 또는 이메일([email protected])을 통해 저희에게 연락해 주십시오.

2. 2026년 7월 21일 AM 5:25 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 7월 21일 AM 8:12 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

4. 2026년 7월 21일 AM 8:56 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 16일 AM 4:34 UTCidentified

   우리는 현재 클러스터 레벨 Prometheus 모니터링 쿼리 요청이 잘못 403 오류로 차단되는 문제를 조사하고 있습니다. 다른 Prometheus 모니터링 쿼리는 비공식적입니다. 우리의 팀은 문제를 해결하기 위해 적극적으로 일하고, 우리는 어떤 불편든지를 위해 사과합니다. 관리 콘솔, 클러스터 관리 API 및 모니터링 API는 여전히 작동. 우리는 그들이 가능한 한 빨리 업데이트 제공 할 것입니다. 긴급한 문제가 있는 경우 지원 포털(support.instaclustr.com) 또는 이메일([email protected])을 통해 저희에게 연락해 주십시오.

2. 2026년 7월 16일 AM 4:52 UTCidentified

   문제는 확인되었으며, 우리 팀은 해결을 구현하는 데 적극적으로 노력하고 있습니다. Cluster-level Prometheus Monitoring 쿼리 요청은 403 오류로 잘못 차단됩니다. 다른 Prometheus 모니터링 쿼리는 비공식적입니다. 기존 고객 클러스터는 비범죄입니다. 관리 콘솔 및 클러스터 관리 API는 여전히 운영됩니다. 우리는 그들이 가능한 한 빨리 업데이트 제공 할 것입니다. 긴급한 문제가 있는 경우 지원 포털(support.instaclustr.com) 또는 이메일([email protected])을 통해 저희에게 연락해 주십시오.

3. 2026년 7월 16일 AM 8:52 UTCmonitoring

   수정은 밖으로 구출되고 우리는 결과를 감시하고 있습니다.

4. 2026년 7월 16일 AM 9:48 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 5월 13일 AM 6: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. 2026년 5월 13일 PM 12:26 UTCresolved

   This incident has been resolved.

1. 2026년 5월 8일 AM 1: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. 2026년 5월 8일 AM 1:55 UTCidentified

   We are continuing to monitor the issue.

3. 2026년 5월 9일 AM 5:02 UTCresolved

   This incident has been resolved.

1. 2026년 4월 29일 AM 5: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. 2026년 4월 29일 AM 6:35 UTCresolved

   This incident has been resolved.

1. 2026년 3월 24일 AM 1: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. 2026년 3월 24일 AM 8:36 UTCresolved

   A fix for this issue has been deployed.

1. 2026년 3월 10일 AM 3: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. 2026년 3월 10일 AM 4: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. 2026년 3월 10일 AM 6:04 UTCidentified

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

4. 2026년 3월 10일 AM 6: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. 2026년 3월 10일 AM 6:53 UTCresolved

   This incident has been resolved.

1. 2026년 3월 4일 AM 12: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. 2026년 3월 4일 AM 6:05 UTCresolved

   This incident has been resolved.

1. 2026년 2월 12일 AM 1: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. 2026년 2월 12일 AM 2:46 UTCidentified

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

3. 2026년 2월 12일 AM 7:22 UTCresolved

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

1. 2026년 1월 27일 PM 11: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. 2026년 1월 28일 AM 12:37 UTCmonitoring

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

3. 2026년 1월 28일 AM 1:03 UTCresolved

   This incident has been resolved.

1. 2026년 1월 27일 AM 9: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. 2026년 1월 27일 PM 9:31 UTCidentified

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

3. 2026년 1월 28일 AM 8: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. 2026년 1월 29일 AM 1:24 UTCresolved

   This incident has been resolved.

1. 2026년 1월 23일 AM 12: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. 2026년 1월 23일 AM 1: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. 2026년 1월 23일 AM 2: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. 2026년 1월 23일 AM 3:27 UTCresolved

   This incident has been resolved.

1. 2026년 1월 9일 AM 12: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. 2026년 1월 9일 AM 4:56 UTCresolved

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

1. 2025년 12월 23일 PM 9: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. 2025년 12월 23일 PM 11: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. 2025년 12월 24일 AM 4: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. 2025년 12월 24일 AM 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. 2025년 12월 24일 PM 11:27 UTCresolved

   This incident has been resolved.

1. 2025년 10월 20일 AM 9: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. 2025년 10월 20일 AM 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. 2025년 10월 20일 PM 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. 2025년 10월 20일 PM 1: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. 2025년 10월 20일 PM 5: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. 2025년 10월 20일 PM 8: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. 2025년 10월 21일 AM 12: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. 2025년 10월 21일 AM 12: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. 2025년 10월 8일 PM 5: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. 2025년 10월 8일 PM 5:55 UTCidentified

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

3. 2025년 10월 8일 PM 7:25 UTCinvestigating

   We are continuing to investigate this issue.

4. 2025년 10월 8일 PM 7:26 UTCmonitoring

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

5. 2025년 10월 8일 PM 7:48 UTCresolved

   This incident has been resolved.