Data collectors / Detection Issues
Affected: API and Users InterfaceAlertsData CollectionComposite MetricsAnomaliesForecasting Service
Anodot Outage History
Anodot is up right nowAnodot had 5 outages in the last 2 years totaling 275h 24m of downtime — averaging 0.2 incidents per month.
There were 5 Anodot outages since June 1, 2025 totaling 275h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.
EU (Frankfurt) Region - Anomaly Detection and Anomaly Alerts not working
Affected: AlertsAWS Frankfurt (eu-central-1)Anomalies
Timeline · 3 updates
- investigating Jan 22, 2026, 09:59 AM UTC
Anomaly detection and anomaly alerting in EU (Frankfurt) region are current not working. We've identified the issue and are working to resolve it
- monitoring Jan 22, 2026, 10:10 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 22, 2026, 10:27 AM UTC
This incident had been resolved
UI intermittently unavailable in US zone
Affected: API and Users Interface
Timeline · 3 updates
- investigating Dec 19, 2025, 02:03 PM UTC
We are currently investigating this issue.
- investigating Dec 19, 2025, 02:05 PM UTC
We are continuing to investigate this issue.
- resolved Dec 19, 2025, 02:22 PM UTC
This incident has been resolved.
Partial Data collection issue
Affected: Data CollectionAWS Frankfurt (eu-central-1)
Timeline · 3 updates
- identified Jul 10, 2025, 12:56 PM UTC
Partial data collection issue for data collectors.
- monitoring Jul 10, 2025, 01:26 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 10, 2025, 02:01 PM UTC
This incident has been resolved.
US Region - Errors in Processing Incoming Metrics - Data Loss with High Probability
Affected: AlertsData CollectionComposite Metrics
Timeline · 2 updates
- monitoring Jun 01, 2025, 04:23 AM UTC
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.
- resolved Jun 02, 2025, 12:38 PM UTC
This incident has been resolved.