We started checking Netdata on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Netdata reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Netdata's own status page declared. Below it, any public chatter we saw about Netdata and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Netdata's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Netdata in the last 24 hours, which is not evidence that nothing is wrong.
Netdata's status page
Potential remote execution on Agents with an exposed web port (19999): minor incident
Potential remote execution on Agents with an exposed web port (19999): minor incident, from before this window to now, still open per their page.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Netdata's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Netdata next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
447
US-West
99.71%
344
Europe
100.00%
315
Asia-Pacific
100.00%
192
Their declared record
Netdata's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Potential remote execution on Agents with an exposed web port (19999)Ongoing, minor incident
Oct 22, 2026, 5:57 AM UTC, open for 14d 11h so farmonitoring
their latest update (Oct 23, 2026, 1:34 PM UTC): The version 2.12.2 patch release has been published to the stable release channel with a fix for the issue.
Agent connectivity issue on legacy systemsAll systems operational
May 29, 2026, 6:00 AM UTC to May 29, 2026, 6:00 AM UTC (0 min)resolved
their latest update (May 29, 2026, 6:00 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 (Jess…
May 8, 2026, 12:11 AM UTC to May 8, 2026, 12:32 AM UTC (20 min)resolved
their latest update (May 8, 2026, 12:32 AM UTC): This incident has been resolved.
Kubernetes node failure.All systems operational
Apr 15, 2026, 6:38 AM UTC to Apr 15, 2026, 6:38 AM UTC (0 min)resolved
their latest update (Apr 15, 2026, 6: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…
Unexpected Loadbalancer restartAll systems operational
Mar 8, 2026, 3:30 PM UTC to Mar 8, 2026, 3:30 PM UTC (0 min)resolved
their latest update (Mar 8, 2026, 3:30 PM UTC): Yesterday, 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 triggered false positive alerts notifying clients of node downt…
404 errors with Netdata RHEL 8.x repositories with latest repository configuration packages.Partial outage
Jan 22, 2026, 12:47 PM UTC to Jan 22, 2026, 3:20 PM UTC (2h 33m)resolved
their latest update (Jan 22, 2026, 3:20 PM UTC): 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 configuration packages, and as such no further issues are expe…
Services UnavailableMajor outage
Nov 18, 2025, 12:11 PM UTC to Nov 18, 2025, 7:22 PM UTC (7h 11m)resolved
their latest update (Nov 18, 2025, 7:22 PM UTC): This incident has been resolved.
Agent v2.7.0 on Windows doesn't start go.d pluginPartial outage
Sep 29, 2025, 11:36 AM UTC to Sep 30, 2025, 6:29 PM UTC (1d 6h)resolved
their latest update (Sep 30, 2025, 6:29 PM UTC): This incident has been resolved.
Package availability issues with native DEB/RPM packages.Partial outage
Aug 21, 2025, 7:35 PM UTC to Aug 21, 2025, 7:58 PM UTC (22 min)resolved
their latest update (Aug 21, 2025, 7:58 PM UTC): All repositories are functioning normally again.
Showing the 10 most recent of 50 incidents Netdata has declared in the history we hold.
These entries are Netdata's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Netdata's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.