Is Netdata down?
Last checked 5m agoNo incidents right now.
Netdata is operational right now. Last checked 5m ago; the most recent incident resolved 1d ago.
Real-time Netdata status, recent outages, and incident history — pulled directly from Netdata's official status page at https://status.netdata.cloud every 5 minutes. Pingoru tracks 8 Netdata services and has captured 5 incidents in the last 90 days (99.72% uptime). Get email, Slack, Discord, or webhook alerts the moment Netdata reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 1 update
- resolved · May 30, 2026, 11:21 AM UTC
Following a scheduled TLS certificate renewal, a subset of Netdata agents failed to reconnect to Netdata Cloud. The issue stems from outdated CA (Certificate Authority) trust stores on certain legacy Linux distributions, like: • CentOS 7 / RHEL 7 • Amazon Linux 2 • Debian 9 (Jessie) • Ubuntu 16.04 LTS • Oracle Linux 7 A quick way to test for this: curl -v https://app.netdata.cloud If the output shows an error indicating the certificate has expired, the system needs an updated CA bundle.
Latest: Following a scheduled TLS certificate renewal, a subset of Netdata agents failed to reconnect to Netdata Cloud. The issue stems from outdated CA (Certificate Authority) trust store…
-
- Cloud AlertsAgent - Cloud Connection (ACLK)
Timeline · 2 updates
- monitoring · May 08, 2026, 01:13 AM UTC
We are currently tracking an issue with our upstream cloud provider that is affecting a subset of our Kubernetes nodes. As a result, some customers may receive false-positive alerts regarding node reachability. Please be assured that your underlying services and workloads remain operational, and these alerts can be safely ignored at this time. We are closely monitoring the situation with our provider.
- resolved · May 08, 2026, 06:00 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Cloud AlertsAgent - Cloud Connection (ACLK)
Timeline · 3 updates
- monitoring · May 08, 2026, 12:11 AM UTC
We are currently tracking an issue with our upstream cloud provider that is affecting a subset of our Kubernetes nodes. As a result, some customers may receive false-positive alerts regarding node reachability. Please be assured that your underlying services and workloads remain operational, and these alerts can be safely ignored at this time. We are closely monitoring the situation with our provider.
- monitoring · May 08, 2026, 12:12 AM UTC
We are continuing to monitor for any further issues.
- resolved · May 08, 2026, 12:32 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 1 update
- resolved · Apr 15, 2026, 06:38 AM UTC
At ~02:20 UTC, a Kubernetes node running part of our ingress controller failed and was auto-replaced. Some clients experienced brief agent disconnections and false-positive node-unavailability alerts during the failover. Service has fully recovered after few minutes. We apologize for the inconvenience.
Latest: At ~02:20 UTC, a Kubernetes node running part of our ingress controller failed and was auto-replaced. Some clients experienced brief agent disconnections and false-positive node-un…
-
- Started May 30, 2026, 11:21 AM UTC · Resolved May 29, 2026, 06:00 AM UTC · —
- Started May 08, 2026, 01:13 AM UTC · Resolved May 08, 2026, 06:00 AM UTC · 4h 47m
- Started May 08, 2026, 12:11 AM UTC · Resolved May 08, 2026, 12:32 AM UTC · 20m
- Kubernetes node failure. ResolvedStarted Apr 15, 2026, 06:38 AM UTC · Resolved Apr 15, 2026, 06:38 AM UTC · —