История сбоев Instaclustr

1. 10 сентября 2026 г. в 02:56 UTCidentified

   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. 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. 10 сентября 2026 г. в 03:28 UTCmonitoring

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

3. 10 сентября 2026 г. в 03:40 UTCresolved

   This incident has been resolved.

1. 20 августа 2026 г. в 17:15 UTCidentified

   В настоящее время мы испытываем деградацию услуг и потенциальные сбои в области облачной платформы Google us-west1. Этот инцидент является результатом продолжающейся проблемы с инфраструктурой облачного провайдера. Вы не сможете предоставить новые кластеры или узлы. Существующие узлы в us-west1 могут быть недоступны. Кластерные центры обработки данных в других регионах не затронуты, но испытывают проблемы с сетью при взаимодействии с узлами в us-west1. С отдельными пострадавшими клиентами связываются через билеты поддержки. Мы активно следим за ситуацией и предоставим дополнительные детали по мере их поступления. Статус GCP отслеживается по https://status.cloud.google.com/. Если у вас есть срочное дело, пожалуйста, свяжитесь с нами через портал поддержки (support.instaclustr.com) или по электронной почте ([email protected]).

2. 20 августа 2026 г. в 17:16 UTCidentified

   Мы продолжаем работать над решением этой проблемы.

3. 20 августа 2026 г. в 17:58 UTCidentified

   Вертикальное масштабирование было временно отключено в регионе GCP us-west1 из-за отключения облачного провайдера. Мы повторно включим эту функцию, когда отключение облачного провайдера будет устранено.

4. 20 августа 2026 г. в 19:06 UTCmonitoring

   Google завершил смягчение последствий и сообщает о восстановлении нескольких продуктов. Мы будем продолжать следить за инцидентом до тех пор, пока оставшаяся продукция не восстановится. Вертикальное масштабирование остается отключенным в США-Запад1.

5. 20 августа 2026 г. в 19:46 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 19 августа 2026 г. в 10:05 UTCidentified

   В настоящее время мы наблюдаем проблемы совместимости между провайдером Instaclustr Terraform и API управления кластерами, влияющие на операции с участием кластеров OpenSearch. Стандартные операции клиентских кластеров не затрагиваются. API мониторинга и API Prometheus остаются в рабочем состоянии. Наша команда активно работает над решением проблемы, и мы приносим свои извинения за любые неудобства. Дальнейшие обновления будут предоставляться по мере поступления дополнительной информации. Если у вас есть срочное дело, пожалуйста, свяжитесь с нами через портал поддержки по адресу https://support.instaclustr.com или по электронной почте [email protected].

2. 19 августа 2026 г. в 12:36 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 29 июля 2026 г. в 00:11 UTCidentified

   В настоящее время мы испытываем проблемы с предоставлением кластеров PostgreSQL с 3 узлами через API управления кластерами и консоль управления. Наша команда активно работает над решением этой проблемы и приносим свои извинения за причиненные неудобства. Существующие кластеры клиентов не затронуты, а API мониторинга и API Prometheus работают. Дополнительные детали будут предоставлены по мере их поступления. Если у вас есть срочное дело, пожалуйста, свяжитесь с нами через портал поддержки (support.instaclustr.com) или по электронной почте ([email protected]).

2. 29 июля 2026 г. в 03:38 UTCidentified

   Мы продолжаем работать над решением этой проблемы.

3. 29 июля 2026 г. в 09:27 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 22 июля 2026 г. в 13:04 UTCidentified

   В настоящее время мы испытываем деградацию услуг и потенциальные сбои в зоне US-east4-b. GCP еще не обновила свою страницу статуса, однако первоначальное расследование указывает на проблему, вероятно, с инфраструктурой облачного провайдера в зоне US-east4-b. Хотя мы наблюдаем частичное восстановление, тем временем будут затронуты новые кластеры или узлы в соответствующей зоне GCP. Также существующие узлы в зоне GCP us-east4-b могут сталкиваться с периодическими проблемами и быть автономными. Вы все равно должны иметь доступ к своим кластерам, если вы используете стандартную конфигурацию. С отдельными пострадавшими клиентами связываются через билеты поддержки. Мы активно следим за ситуацией и предоставим дополнительные детали по мере их поступления. Статус GCP отслеживается по https://status.cloud.google.com/. Если у вас есть срочное дело, пожалуйста, свяжитесь с нами через портал поддержки (support.instaclustr.com) или по электронной почте ([email protected]).

2. 22 июля 2026 г. в 13:34 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 21 июля 2026 г. в 04:55 UTCinvestigating

   В настоящее время мы испытываем проблемы с предоставлением кластеров Kafka Connect & Cadence в существующие VPC через API управления кластерами и консоль управления. Наша команда активно работает над решением этой проблемы и приносим свои извинения за причиненные неудобства. Существующие кластеры клиентов не затронуты, а API мониторинга и API Prometheus работают. Дополнительные детали будут предоставлены по мере их поступления. Если у вас есть срочное дело, пожалуйста, свяжитесь с нами через портал поддержки (support.instaclustr.com) или по электронной почте ([email protected]).

2. 21 июля 2026 г. в 05:25 UTCidentified

   Этот вопрос был определен, и в настоящее время осуществляется исправление.

3. 21 июля 2026 г. в 08:12 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

4. 21 июля 2026 г. в 08:56 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 16 июля 2026 г. в 04:34 UTCidentified

   В настоящее время мы расследуем проблему, в результате которой запросы на мониторинг запросов на уровне кластера Prometheus были неправильно заблокированы с ошибкой 403. Другие запросы мониторинга Prometheus не затронуты. Наша команда активно работает над решением проблемы, и мы приносим свои извинения за причиненные неудобства. Консоль управления, API управления кластерами и API мониторинга все еще работают. Мы предоставим обновления, как только они станут доступны. Если у вас есть срочное дело, пожалуйста, свяжитесь с нами через портал поддержки (support.instaclustr.com) или по электронной почте ([email protected]).

2. 16 июля 2026 г. в 04:52 UTCidentified

   Вопрос выявлен, и наша команда активно работает над реализацией исправления. Запросы запросов мониторинга на уровне кластера Prometheus неправильно блокируются с ошибкой 403. Другие запросы мониторинга Prometheus не затронуты. Существующие группы клиентов не затронуты. Консоль управления и API управления кластерами все еще работают. Мы предоставим обновления, как только они станут доступны. Если у вас есть срочное дело, пожалуйста, свяжитесь с нами через портал поддержки (support.instaclustr.com) или по электронной почте ([email protected]).

3. 16 июля 2026 г. в 08:52 UTCmonitoring

   В настоящее время вводится исправление, и мы отслеживаем результаты.

4. 16 июля 2026 г. в 09:48 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 13 мая 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 мая 2026 г. в 12:26 UTCresolved

   This incident has been resolved.

1. 8 мая 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 мая 2026 г. в 01:55 UTCidentified

   We are continuing to monitor the issue.

3. 9 мая 2026 г. в 05:02 UTCresolved

   This incident has been resolved.

1. 29 апреля 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 апреля 2026 г. в 06:35 UTCresolved

   This incident has been resolved.

1. 24 марта 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 марта 2026 г. в 08:36 UTCresolved

   A fix for this issue has been deployed.

1. 10 марта 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 марта 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 марта 2026 г. в 06:04 UTCidentified

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

4. 10 марта 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 марта 2026 г. в 06:53 UTCresolved

   This incident has been resolved.

1. 4 марта 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 марта 2026 г. в 06:05 UTCresolved

   This incident has been resolved.

1. 12 февраля 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 февраля 2026 г. в 02:46 UTCidentified

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

3. 12 февраля 2026 г. в 07:22 UTCresolved

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

1. 27 января 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 января 2026 г. в 00:37 UTCmonitoring

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

3. 28 января 2026 г. в 01:03 UTCresolved

   This incident has been resolved.

1. 27 января 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 января 2026 г. в 21:31 UTCidentified

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

3. 28 января 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 января 2026 г. в 01:24 UTCresolved

   This incident has been resolved.

1. 23 января 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 января 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 января 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 января 2026 г. в 03:27 UTCresolved

   This incident has been resolved.

1. 9 января 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 января 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 декабря 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 декабря 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 декабря 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 декабря 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 декабря 2025 г. в 23:27 UTCresolved

   This incident has been resolved.

1. 20 октября 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 октября 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 октября 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 октября 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 октября 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 октября 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 октября 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 октября 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.