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

1. 7 сентября 2026 г. в 22:16 UTCinvestigating

   Мы осуществляем внутреннюю миграцию. Ожидается минимальное отключение, и мы скоро вернемся к нормальному обслуживанию.

2. 8 сентября 2026 г. в 00:14 UTCresolved

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

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

1. 27 июля 2026 г. в 21:01 UTCinvestigating

   В настоящее время мы проводим плановое техническое обслуживание наших систем. В течение этого времени вы можете испытывать короткие перерывы или задержки при подключении к инфраструктуре ИИ.

2. 27 июля 2026 г. в 23:13 UTCresolved

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

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

1. 23 июля 2026 г. в 14:03 UTCinvestigating

   В настоящее время мы проводим плановое техническое обслуживание наших систем. В течение этого времени вы можете испытывать короткие перерывы или задержки при подключении к инфраструктуре ИИ.

2. 23 июля 2026 г. в 17:55 UTCmonitoring

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

3. 24 июля 2026 г. в 04:34 UTCresolved

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

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

1. 17 июля 2026 г. в 16:50 UTCinvestigating

   Мы заметили увеличение времени ожидания развертывания и в настоящее время расследуем этот вопрос.

2. 17 июля 2026 г. в 16:55 UTCidentified

   Мы определили причину задержки и реализуем исправление.

3. 17 июля 2026 г. в 20:34 UTCmonitoring

   Реализовано исправление, и мы следим за этим вопросом.

4. 18 июля 2026 г. в 14:01 UTCresolved

   Вопрос решен.

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

1. 8 июля 2026 г. в 16:49 UTCmonitoring

   We are currently conducting routine maintenance on our systems. During this time, you may experience brief interruptions or delays when connecting to the AI infrastructure.

2. 8 июля 2026 г. в 17:05 UTCresolved

   This incident has been resolved.

1. 1 июля 2026 г. в 14:03 UTCmonitoring

   There is a delay in log processing and recent logs for events generated since July 1st may not be available. Real time logs can be accessed through the Lagoon CLI: https://docs.amazee.io/cloud/logging/#real-time-container-logs-via-lagoon-cli

2. 1 июля 2026 г. в 17:09 UTCresolved

   This incident has been resolved.

1. 17 июня 2026 г. в 02:39 UTCinvestigating

   We are currently investigating this issue.

2. 17 июня 2026 г. в 03:37 UTCidentified

   The issue has been identified and we are working to address it.

3. 17 июня 2026 г. в 04:56 UTCmonitoring

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

4. 17 июня 2026 г. в 04:57 UTCmonitoring

   The access roles are resyncing and we are monitoring progress.

5. 18 июня 2026 г. в 02:00 UTCmonitoring

   We are continuing to monitor the resync progress.

6. 19 июня 2026 г. в 02:32 UTCresolved

   This incident has been resolved.

1. 1 июня 2026 г. в 14:44 UTCmonitoring

   TLS certificate provisioning and renewal may be delayed on affected clusters during this window. We are monitoring the upstream incident and will provide updates as the situation evolves. https://status.redhat.com/

2. 2 июня 2026 г. в 06:54 UTCresolved

   This incident has been resolved.

1. 1 июня 2026 г. в 14:07 UTCmonitoring

   There is a delay in log processing and recent logs for events generated since June 1st may not be available. Real time logs can be accessed through the Lagoon CLI: https://docs.amazee.io/cloud/logging/#real-time-container-logs-via-lagoon-cli

2. 1 июня 2026 г. в 17:33 UTCresolved

   This incident has been resolved.

1. 19 мая 2026 г. в 02:09 UTCidentified

   Drupal has announced an upcoming highly critical Drupal core security release affecting Drupal 10 and 11 (and EOL versions 8 and 9). Customer impact - Prepare now: Update to the latest patch release on your current supported Drupal version ahead of time to reduce time-to-patch. - Schedule a maintenance window: May 20, 17:00 - 21:00 UTC. Customers should be prepared to apply the security update immediately once released. - EOL Drupal versions: Drupal 8.9 and 9.5 will receive patch files only (temporary mitigation). Plan an urgent upgrade to a supported version. Drupal 7 is not affected. What we're doing We're treating this as a priority security event and preparing WAF/CDN mitigations ("virtual patches") where possible. These may provide partial/temporary protection; applying the upstream Drupal security update remains the primary mitigation. We’ll share updates here as more information becomes available. For more information, see the Drupal PSA: https://www.drupal.org/psa-2026-05-18

2. 20 мая 2026 г. в 19:26 UTCmonitoring

   We’ve reviewed today’s Drupal-related release and do not currently anticipate deploying WAF/CDN mitigations ("virtual patches"). Based on our assessment, overall exposure appears more limited than initial thoughts. Customers should review the security release notes to determine their potential impact and update as soon as practical: https://www.drupal.org/sa-core-2026-004. We will continue monitoring the situation and provide updates necessary.

3. 2 июня 2026 г. в 06:54 UTCresolved

   This incident has been resolved.

1. 7 мая 2026 г. в 18:08 UTCidentified

   We are currently experiencing an issue with cert-manager in affected clusters. The cert-manager controller pod is failing to start due to an image pull failure from quay.io (502 Bad Gateway), which is an external registry. Impact: New TLS certificates cannot be issued or renewed while cert-manager is unavailable. Existing certificates remain valid until their expiry. Services relying on automatic certificate provisioning may be affected if certificates expire during this window. https://status.redhat.com/

2. 7 мая 2026 г. в 18:24 UTCmonitoring

   All clusters are able to pull cert-manager image, we are currently monitoring statuspage https://status.redhat.com/

3. 7 мая 2026 г. в 21:14 UTCresolved

   This incident has been resolved.

1. 30 апреля 2026 г. в 01:33 UTCidentified

   We are aware of CVE-2026-31431 / "Copy Fail" and have completed an initial assessment. We have not identified evidence of customer impact, service compromise, or active exploitation at this stage. We are prioritizing Linux kernel upgrades and will provide further updates if our assessment changes or if maintenance becomes necessary.

2. 13 мая 2026 г. в 06:01 UTCresolved

   Mitigations at the Linux kernel level have been rolled out across all regions.

1. 29 апреля 2026 г. в 09:19 UTCinvestigating

   We are currently investigating a high error rate on the Fastly management API. This impacts deployments of new domains that are routed through Fastly. Existing setups on Fastly or traffic routing are not impacted.

2. 29 апреля 2026 г. в 09:58 UTCinvestigating

   Fastly is investigating the API issues and updating their status page at: https://www.fastlystatus.com/incident/378511 Impact: Deployments with new domains that are routed through Fastly will continue to work, but the actual domain setup in Fastly will be delayed.

3. 29 апреля 2026 г. в 11:15 UTCmonitoring

   Fastly resolved the issue with their management API and we'll keep monitoring the situation.

4. 29 апреля 2026 г. в 12:51 UTCresolved

   This incident has been resolved.

1. 21 апреля 2026 г. в 12:09 UTCinvestigating

   We are currently investigating this issue.

2. 21 апреля 2026 г. в 13:03 UTCresolved

   This incident has been resolved.

1. 15 апреля 2026 г. в 04:19 UTCidentified

   There was an issue with an EKS rollout during maintenance, we are actively addressing this issue.

2. 15 апреля 2026 г. в 06:16 UTCmonitoring

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

3. 15 апреля 2026 г. в 07:24 UTCresolved

   This incident has been resolved.

1. 7 апреля 2026 г. в 16:18 UTCidentified

   We have identified an issue causing Lagoon builds to fail and are actively working to resolve.

2. 7 апреля 2026 г. в 17:27 UTCmonitoring

   We have applied a fix for this issue and are monitoring deployments.

3. 8 апреля 2026 г. в 21:54 UTCresolved

   The incident has been resolved.

1. 18 марта 2026 г. в 13:41 UTCinvestigating

   We are investigating increased error rates on the Lagoon API.

2. 19 марта 2026 г. в 03:27 UTCidentified

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

3. 19 марта 2026 г. в 14:52 UTCresolved

   This incident has been resolved.

1. 17 марта 2026 г. в 06:42 UTCinvestigating

   We are currently investigating this issue.

2. 17 марта 2026 г. в 07:45 UTCidentified

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

3. 17 марта 2026 г. в 07:45 UTCmonitoring

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

4. 17 марта 2026 г. в 20:48 UTCresolved

   This incident has been resolved.

1. 18 февраля 2026 г. в 07:01 UTCmonitoring

   In the latest release of Google Chrome (v145) the handling of HTTP 425 responses was changed. Should you see this affecting your sites, please reach out to our support and we'll look into applying mitigations for your specific use-case. Related status page from Fastly: https://www.fastlystatus.com/incident/378300#

2. 8 апреля 2026 г. в 08:10 UTCresolved

   This incident has been resolved.

1. 9 февраля 2026 г. в 19:38 UTCmonitoring

   Fastly has reported elevated errors affecting Fastly Applications. Existing certificates do not appear to be impacted; however, some services are experiencing issues when adding new domains. We are monitoring the Fastly status page: https://www.fastlystatus.com/

2. 10 февраля 2026 г. в 07:52 UTCresolved

   This incident has been resolved.