Netdata Outage History
11 incidents recorded over the last 365 days, 7 of them resolved, 1 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Netdata Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 23, 2026 | Potential remote execution on Agents with an exposed web port (19999)The version 2.12.2 patch release has been published to the stable release channel with a fix for the issue. | — | Investigating |
| Jun 12, 2026 | Database upgradeThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| May 30, 2026 | Agent connectivity issue on legacy systemsFollowing 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… | -1761 min | Resolved |
| May 8, 2026 | False-Positive Node Reachability AlertsThis incident has been resolved. | 4h 47m | Resolved |
| May 8, 2026 | False-Positive Node Reachability AlertsThis incident has been resolved. | 20 min | Resolved |
| Apr 15, 2026 | Kubernetes node failure.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… | 0 min | Resolved |
| Mar 24, 2026 | Scheduled maintenance on MQTT BrokerThe scheduled maintenance has been completed. | 1h 30m | Scheduled |
| Mar 9, 2026 | Unexpected Loadbalancer restartYesterday, a brief infrastructure incident occurred due to certain processes on our load balancer failing (exactly at 16:34 UTC). This caused more than half of our globally connected nodes to reconnect, which in turn… | -1339 min | Resolved |
| Jan 22, 2026 | 404 errors with Netdata RHEL 8.x repositories with latest repository configuration packages.In addition to the fix for the repository configuration packages, a fix has been deployed to the repositories themselves that will enable affected systems to update successfully to the latest version of the repository… | 2h 32m | Resolved |
| Dec 2, 2025 | MQTT Broker upgradeThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Nov 18, 2025 | Services UnavailableThis incident has been resolved. | 7h 11m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Netdata incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Netdata Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Netdata acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Netdata outage in this window ran 7h 11m, against a mean recovery of 2h 25m. If you depend on Netdata in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.