Get instant notifications when Netdata experiences issues. Stay informed with real-time alerts, incident updates, and resolution notifications.
Apr 2, 2025 10:00 AM
Apr 2, 10:00 UTC
Completed - The scheduled maintenance has been completed.
Apr 2, 08:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Mar 27, 09:59 UTC
Scheduled - During this maintenance window, we will:
- Switch to a new DDoS provider (the main driver for the extended duration). We have tested it in non-production environments and expect no downtime, but IP addresses will change. Please update firewalls to use DNS names. We will trigger Agent-Cloud link reconnection but it should be transparent for end users.
- Upgrade Elasticsearch, which forms the backbone of our Event Feed. We do expect Events tab to not work properly.
Apr 2, 2025 9:25 AM
Apr 2, 09:25 UTC
Resolved - Affected Agents can cause the creation of multiple duplicate nodes in Netdata Cloud. All but the last one will appear as offline, and the last one will be as if it was created from scratch with no data. Unfortunately, the previously stored metrics for the affected nodes can not be recovered.
The duplicate offline nodes can be safely deleted from Space Settings -> Nodes. Note that you may have to add the newest copy of these nodes to the appropriate rooms.
The fixed nightly static build is v2.3.0-102.
Apr 1, 09:00 UTC
Investigating - We have found that a recent change in the nightly static builds of Netdata Agent causes meta data on the Agent to be overwritten. Specifically the sqlite3 database that keeps meta data on which timeseries stored in dbengine correspond with which metrics, and the information on the Agent's "machine GUID" are overwritten with the same copy in the build package.
Not affected are:
- All stable releases
- Native packages (.deb and .rpm)
Affected are all nightly static builds with the following version numbers:
- 2.3.0-50-nightly
- 2.3.0-60-nightly
- 2.3.0-72-nightly
- 2.3.0-78-nightly
- 2.3.0-87-nightly
The initial impact is that all affected Agent installs, even though they still have the timeseries data stored on disk, have lost all meta data associated with it, so these timeseries become inaccessable. This is unrecoverable. Additionally, the main form of identification is overwritten, too.
We are assessing what the impact is for users of Netdata Cloud, and will update this incident with more information when the investigation is completed.
The bug itself has been fixed and merged. We will issue a new nightly build shortly.