Anodot の障害履歴

1. 2026年10月14日 4:18 UTCinvestigating

   問題を発見し、それをできるだけ早く修正する作業

2. 2026年10月14日 4:39 UTCmonitoring

   修正は適用されました、私達は結果を監視しています

3. 2026年10月14日 4:50 UTCresolved

   事件が解決された

公式のインシデント更新を自動翻訳しています。

1. 2026年4月4日 8:00 UTCinvestigating

   Snowflake Streams have encountered difficulties in retrieving data samples over the last few hours. This issue is not localized to a single region but is impacting all of our clusters across different geographical areas. Our team is actively conducting a thorough investigation to identify the root cause of this disruption and to implement a resolution as quickly as possible

2. 2026年4月4日 15:02 UTCinvestigating

   [CRUCIAL UPDATE] The following Data Collectors are currently affected and are not retreiving any samples: - Snowflake - S3 - Kinesis We are continuing to investigate the issue.

3. 2026年4月4日 21:32 UTCinvestigating

   All data collectors are currently not working. We are working on restoring them.

4. 2026年4月6日 8:18 UTCinvestigating

   We are experiencing issues in collecting data, and detecting and dispatching anomaly type alerts

5. 2026年4月11日 6:21 UTCinvestigating

   Starting 7:00 AM UTC. Expected downtime for Frankfurt Customers: ~3 hours

6. 2026年4月11日 10:33 UTCinvestigating

   Maintenance in Frankfurt Cluster is completed. Alerts are functional again, Data Collectors are still offline.

7. 2026年4月11日 10:36 UTCinvestigating

   Starting 11:00 AM UTC. Expected downtime for US Customers: ~3 hours

8. 2026年4月11日 15:43 UTCinvestigating

   Maintenance in US Cluster is completed. Alerts are functional again, Data Collectors are still offline

9. 2026年4月14日 9:16 UTCresolved

   This incident had been resolved

1. 2026年1月22日 9:59 UTCinvestigating

   Anomaly detection and anomaly alerting in EU (Frankfurt) region are current not working. We've identified the issue and are working to resolve it

2. 2026年1月22日 10:10 UTCmonitoring

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

3. 2026年1月22日 10:27 UTCresolved

   This incident had been resolved

1. 2025年12月19日 14:03 UTCinvestigating

   We are currently investigating this issue.

2. 2025年12月19日 14:05 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025年12月19日 14:22 UTCresolved

   This incident has been resolved.

1. 2025年7月10日 12:56 UTCidentified

   Partial data collection issue for data collectors.

2. 2025年7月10日 13:26 UTCmonitoring

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

3. 2025年7月10日 14:01 UTCresolved

   This incident has been resolved.

1. 2025年6月1日 4:23 UTCmonitoring

   We has an issue that caused missing a 4 hours of data. It may have caused many false No-Data alerts. A fix has been implemented and we are monitoring the results.

2. 2025年6月2日 12:38 UTCresolved

   This incident has been resolved.

1. 2025年4月19日 8:57 UTCinvestigating

   We're Investigating the issue

2. 2025年4月19日 15:33 UTCmonitoring

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

3. 2025年4月19日 16:16 UTCmonitoring

   Incident Resolved

4. 2025年5月4日 7:20 UTCresolved

   This incident has been resolved.

1. 2025年4月19日 8:53 UTCresolved

   We're experiencing an elevated level of data API errors and are currently looking into the issue.

1. 2024年9月26日 8:04 UTCinvestigating

   We are currently investigating this issue.

2. 2024年9月26日 8:27 UTCresolved

   This incident has been resolved.

1. 2024年8月7日 7:35 UTCidentified

   Anomaly detection and anomaly alerting in US region are currently unstable, we've identified the issue and are working to resolve it

2. 2024年8月7日 7:37 UTCidentified

   We are continuing to work on a fix for this issue.

3. 2024年8月7日 11:01 UTCmonitoring

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

4. 2024年8月7日 11:38 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2024年8月7日 11:39 UTCresolved

   This incident has been resolved.

1. 2024年4月30日 18:39 UTCinvestigating

   We're currently investigating an issue where small portion of metrics (the same constant metrics) are experiencing sample loss. As a result false-positive no-data alerts can be triggered and the metrics data shall not be shown in UI.

2. 2024年4月30日 20:16 UTCmonitoring

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

3. 2024年4月30日 20:30 UTCresolved

   This incident has been resolved.

1. 2024年1月17日 12:59 UTCidentified

   During the last 24 hours some alerts may have been missed by the system, we're deploying a hotfix in an hour time

2. 2024年1月17日 14:00 UTCmonitoring

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

3. 2024年1月17日 16:33 UTCresolved

   This incident has been resolved.

1. 2023年9月24日 10:35 UTCidentified

   We're experiencing connectivity issues since 5AM UTC time, this may result in degraded performance and reduced accuracy of alerts and composite calculations. There is also a minor chance of sample data loss. We have identified the problem and applied the necessary measures and are monitoring the system state.

2. 2023年9月24日 14:07 UTCresolved

   This incident has been resolved.

1. 2023年8月9日 16:37 UTCinvestigating

   Streams working with BigQuery does not retrieve new data, seems to be related to incompatible changes in BigQuery - Investigating. This is a cross region issue that impact all of our clusters.

2. 2023年8月9日 17:41 UTCmonitoring

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

3. 2023年8月9日 18:05 UTCresolved

   This incident has been resolved.

1. 2023年7月1日 6:21 UTCinvestigating

   Around 05:00 UTC we detected errors in samples receiving pipeline, issue is under investigation. Please be advised that at least some of the incoming metrics data was lost and false-positive alerts can be triggered

2. 2023年7月1日 6:21 UTCmonitoring

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

3. 2023年7月1日 6:46 UTCresolved

   This incident has been resolved.

1. 2023年2月2日 20:47 UTCinvestigating

   We are experiencing issues with the application effecting the ability to visualize metrics and anomalies.

2. 2023年2月2日 21:30 UTCresolved

   This incident has been resolved.

1. 2023年1月12日 13:51 UTCidentified

   We've identified the issue and working on a fix. Please note that alerts console is fully functional and no events are lost.

2. 2023年1月12日 18:34 UTCmonitoring

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

3. 2023年1月12日 19:40 UTCresolved

   This incident has been resolved.

1. 2023年1月6日 11:07 UTCidentified

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

2. 2023年1月6日 13:16 UTCmonitoring

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

3. 2023年1月6日 13:28 UTCresolved

   The incident was resolved. Alerts dispatching got delayed but no data was lost.

1. 2023年1月3日 9:50 UTCidentified

   Our alert data processing infrastructure is running behind which is causing delays in sending alerts. No data has been lost and the system should be caught up shortly.

2. 2023年1月3日 10:00 UTCmonitoring

   Alerts is now back to normal and we're investigating the root cause

3. 2023年1月3日 13:10 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2023年1月3日 18:48 UTCresolved

   This incident has been resolved.

1. 2022年9月20日 17:41 UTCidentified

   We are working on a mitigation with an ETA of 1-2 hours.

2. 2022年9月20日 18:35 UTCidentified

   Mitigation identified and is being rolled out to production clusters

3. 2022年9月20日 20:00 UTCmonitoring

   A fix has been implemented and applied globally, additional monitoring has been applied and we'll be monitoring it over the next few days

4. 2022年9月20日 22:12 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2022年9月21日 9:00 UTCresolved

   This incident has been resolved.