Instaclustr 中断历史

1. 2026年10月20日 UTC 08:06investigating

   Google Cloud证实了一个影响GCP欧洲-西2区域多种服务的问题,这个问题从协调世界时约06:05开始持续. Google报道了本区域的更高错误和间歇性网络故障. 欧洲西部2-b可用区的所有节点仍然没有。 受影响的集群受到部分影响,并继续在其他供应区的节点上运行,产能下降。 以欧洲-西方2提供新的集群,此时也将失败. 根据迄今为止的试验,欧洲其他全球合作进程区域似乎没有受到影响。 我们的工程师将此事视为一个高度优先事件,并密切监测谷歌的进展。 一旦该区域恢复,我们将努力恢复受影响的节点.

2. 2026年10月20日 UTC 08:06investigating

   我们正在继续调查这一问题.

3. 2026年10月20日 UTC 08:39monitoring

   我们正在继续调查这一问题.

4. 2026年10月20日 UTC 08:57identified

   Google Cloud证实了一个影响GCP欧洲-西2区域多种服务的问题,这个问题从协调世界时约06:05开始持续. Google报道了本区域的更高错误和间歇性网络故障. 欧洲西部2-b可用区的所有节点仍然没有。 受影响的集群受到部分影响,并继续在其他供应区的节点上运行,产能下降。 以欧洲-西方2提供新的集群,此时也将失败. 根据迄今为止的试验,欧洲其他全球合作进程区域似乎没有受到影响。 我们的工程师将此事视为一个高度优先事件,并密切监测谷歌的进展。 一旦该区域恢复,我们将努力恢复受影响的节点.

5. 2026年10月20日 UTC 09:45identified

   Google Cloud现发表欧洲-西2区公共事件:https://status.cloud.google.com/incidents/Xs2XTHZAVC9YnafnPyzj Google尚未提供解决问题的变通办法或估计时间。 我们继续密切监测局势,并将在获得资料后提供进一步的最新资料.

6. 2026年10月20日 UTC 12:13monitoring

   Google Cloud表示,停电是由于欧洲-西-2-b区发生电能事件所致,现已缓解. Google正在恢复现有工作量,初步估计在协调世界时下午1:00左右全面恢复。 我们看到欧洲西部2-b的一些受影响的节点开始恢复。 其他节点仍然没有或还不稳定,随着节点重新上线,我们的小组正在核查每个受影响的集群的健康情况。 在Europe-west2中提供新的集群和节点可能会继续失败,直到Google完成恢复. 一旦恢复工作完成,我们将提供进一步的最新资料.

7. 2026年10月20日 UTC 14:35resolved

   Google Cloud解决了造成欧洲-西2-b区停电的电源事件. 所有受影响的集群都已恢复并正常运行,在GCP Europe-west2 中提供新的集群和节点的工作正在再次进行。 GCP Europe-West 2 中的集群数据中心大小调整也被重新启用. 我们对此可能造成的破坏表示歉意。 Google建议一旦完成内部调查,它将公布对事件的分析. 如果您在集群中还遇到任何问题,请联系支持@intaclustr.com.

自动翻译自官方事件更新。

1. 2026年9月23日 UTC 01:12investigating

   目前,我们正用我们的监测API来调查高延迟率和出错率。 我们的团队正在积极努力解决这一问题,我们对所造成的任何不便表示歉意。 现有的客户集群不受影响。 管理控制台和集群管理API仍在运行. 一旦收到最新资料,我们将立即提供。 如果您有紧急事项,请通过支持门户(support.instaclustr.com)或电子邮件([email protected])联系我们.

2. 2026年9月23日 UTC 01:49monitoring

   一项措施已经执行,我们正在监测结果.

3. 2026年9月23日 UTC 01:58resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年9月10日 UTC 02:56identified

   目前,我们正通过分组管理API和管理控制台处理提供组的问题。 我们的小组正在积极努力解决这一问题,我们对所造成的任何不便表示歉意。 现有的客户集群不受影响,监测API和Prometheus API已开始运作. 详细情况一旦公布,将予以提供。 如果您有紧急事项,请通过支持门户(support.instaclustr.com)或电子邮件([email protected])联系我们.

2. 2026年9月10日 UTC 03:28monitoring

   一项措施已经执行,我们正在监测结果.

3. 2026年9月10日 UTC 03:40resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月20日 UTC 17:15identified

   我们目前正在谷歌云平台地区面临服务退化和潜在干扰。 这一事件是云提供商基础设施持续出问题的结果. 您将无法提供新的集群或节点 。 我们西部1 现有的节点可能无法使用。 其他区域的集群数据中心没有受到影响,但当与西半球的节点相互作用时,正在遇到网络问题。 正在通过支持票与个别受影响客户联系。 我们正在积极监测局势,并将在掌握更多细节后提供这些细节。 GCP状态在https://status.cloud.google.com/上跟踪. 如果您有紧急事项,请通过支持门户(support.instaclustr.com)或电子邮件([email protected])联系我们.

2. 2026年8月20日 UTC 17:16identified

   我们正在继续努力解决这个问题。

3. 2026年8月20日 UTC 17:58identified

   垂直缩放在GCP us-Western1区域暂时被禁用,原因是云供应商停用. 一旦云供应商停用问题得到解决,我们将重新启用这一功能.

4. 2026年8月20日 UTC 19:06monitoring

   谷歌已完成了缓解措施并正在报告多种产品的恢复情况。 我们将继续监测这一事件,直到剩余的产品恢复。 垂直缩放在我们西区仍然被禁用.

5. 2026年8月20日 UTC 19:46resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年8月19日 UTC 10:05identified

   目前我们看到Instacluser Terraform供应商与集群管理API之间的相容性问题,影响了OpenSearch集群的业务. 标准客户集群业务不受影响. 监测API和Prometheus API仍在运作。 我们的团队正在积极努力解决这一问题,我们对任何不便表示歉意。 一旦获得更多信息,将提供进一步的最新资料。 如有紧急事项,请通过https://support.intaclustr.com的支助门户或[email protected]的电子邮件与我们联系.

2. 2026年8月19日 UTC 12:36resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月29日 UTC 00:11identified

   目前我们正面临通过集群管理API和管理控制台提供3个节点的私人网络PostgreSQL集群的问题。 我们的小组正在积极努力解决这一问题,我们对所造成的任何不便表示歉意。 现有的客户集群不受影响,监测API和Prometheus API已开始运作. 详细情况一旦公布,将予以提供。 如果您有紧急事项,请通过支持门户(support.instaclustr.com)或电子邮件([email protected])联系我们.

2. 2026年7月29日 UTC 03:38identified

   我们正在继续努力解决这个问题。

3. 2026年7月29日 UTC 09:27resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月22日 UTC 13:04identified

   目前在GCP东4-b区,我们正面临服务退化和潜在中断。 GCP尚未更新其状态页面,然而初步调查显示,云提供商在我们东4-b区的基础设施可能存在问题。 虽然我们看到部分恢复,但与此同时,在有关全球氯化石蜡区提供新的集群或节点将受到影响。 GCP-east4-b区现有的节点也可面临断断续续的问题并脱线. 如果您正在运行一个标准配置, 您仍应该能够访问您的集群 。 正在通过支持票与个别受影响客户联系。 我们正在积极监测局势,并将在掌握更多细节后提供这些细节。 GCP状态在https://status.cloud.google.com/上跟踪. 如果您有紧急事项,请通过支持门户(support.instaclustr.com)或电子邮件([email protected])联系我们.

2. 2026年7月22日 UTC 13:34resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月21日 UTC 04:55investigating

   目前我们正面临通过集群管理API和管理控制台向现有VPC提供Kafka Connection & Cadence集群的问题。 我们的小组正在积极努力解决这一问题,我们对所造成的任何不便表示歉意。 现有的客户集群不受影响,监测API和Prometheus API已开始运作. 详细情况一旦公布,将予以提供。 如果您有紧急事项,请通过支持门户(support.instaclustr.com)或电子邮件([email protected])联系我们.

2. 2026年7月21日 UTC 05:25identified

   这一问题已经确定,一个解决办法正在实施之中.

3. 2026年7月21日 UTC 08:12monitoring

   一项措施已经执行,我们正在监测结果.

4. 2026年7月21日 UTC 08:56resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月16日 UTC 04:34identified

   我们正在调查一个导致集群级Prometheus监测查询请求被错误地以403个错误被阻断的问题. 其他普罗米修斯监测查询不受影响. 我们的团队正在积极努力解决这一问题,我们对所造成的任何不便表示歉意。 管理控制台、集群管理API和监测API仍在运行。 一旦收到最新资料,我们将立即提供。 如果您有紧急事项,请通过支持门户(support.instaclustr.com)或电子邮件([email protected])联系我们.

2. 2026年7月16日 UTC 04:52identified

   这一问题已经确定,我们的团队正在积极努力执行一个解决办法。 集群级的Prometheus监测查询请求被错误地以403个错误被阻. 其他普罗米修斯监测查询不受影响. 现有的客户集群不受影响。 管理控制台和集群管理API仍在运行. 一旦收到最新资料,我们将立即提供。 如果您有紧急事项,请通过支持门户(support.instaclustr.com)或电子邮件([email protected])联系我们.

3. 2026年7月16日 UTC 08:52monitoring

   目前正在推出一个解决方案,我们正在监测结果.

4. 2026年7月16日 UTC 09:48resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年5月13日 UTC 06:47investigating

   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日 UTC 12:26resolved

   This incident has been resolved.

1. 2026年5月8日 UTC 01:33identified

   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日 UTC 01:55identified

   We are continuing to monitor the issue.

3. 2026年5月9日 UTC 05:02resolved

   This incident has been resolved.

1. 2026年4月29日 UTC 05:28investigating

   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日 UTC 06:35resolved

   This incident has been resolved.

1. 2026年3月24日 UTC 01:10identified

   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日 UTC 08:36resolved

   A fix for this issue has been deployed.

1. 2026年3月10日 UTC 03:22investigating

   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日 UTC 04:54investigating

   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日 UTC 06:04identified

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

4. 2026年3月10日 UTC 06:28monitoring

   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日 UTC 06:53resolved

   This incident has been resolved.

1. 2026年3月4日 UTC 00:18identified

   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日 UTC 06:05resolved

   This incident has been resolved.

1. 2026年2月12日 UTC 01:47investigating

   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日 UTC 02:46identified

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

3. 2026年2月12日 UTC 07:22resolved

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

1. 2026年1月27日 UTC 23:06investigating

   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日 UTC 00:37monitoring

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

3. 2026年1月28日 UTC 01:03resolved

   This incident has been resolved.

1. 2026年1月27日 UTC 09:37investigating

   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日 UTC 21:31identified

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

3. 2026年1月28日 UTC 08:56monitoring

   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日 UTC 01:24resolved

   This incident has been resolved.

1. 2026年1月23日 UTC 00:19investigating

   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日 UTC 01:18identified

   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日 UTC 02:17monitoring

   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日 UTC 03:27resolved

   This incident has been resolved.

1. 2026年1月9日 UTC 00:48identified

   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日 UTC 04:56resolved

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