Major incident

NetBird: Management service instability

Current status of NetBird: Operational — live NetBird status

Timeline

1. Jun 1, 2026, 09:26 UTC
   investigating
   We are currently investigating reports of an issue affecting the management service. Our team is working to determine the root cause and will provide an update as soon as more information is available.
2. Jun 1, 2026, 09:42 UTC
   identified
   We have identified the cause of the issue affecting the management service and implemented a temporary fix. The system is operational now and will continue working on the permanent fix. Updates will be shared as progress is made.
3. Jun 1, 2026, 10:49 UTC
   identified
   We still working on a permanent fix for the management issue. The system still operational. Updates will be shared as progress is made.
4. Jun 1, 2026, 11:07 UTC
   monitoring
   A permanent fix has been implemented for the issue affecting the management service, and we are monitoring the results to ensure everything is operating as expected. A new update will come in 30 minutes with more details of the issue.
5. Jun 1, 2026, 12:37 UTC
   resolved
   **Status Update** The issue affecting the Management Service has been fully resolved. All systems are operating normally, and we will continue to monitor the environment to ensure ongoing stability. **Incident Summary** A load balancer configuration change caused widespread peer reconnections across all clusters. The configuration inadvertently imposed a connection limit per load balancer node, reducing available capacity to less than 5% and preventing nodes from accepting new connections reliably. As an immediate mitigation, we rolled back the configuration, which restored normal service operation. After identifying the root cause and validating revised configuration parameters in a controlled manner, we re-applied the configuration with the necessary adjustments. The issue has been successfully resolved, and the system is now functioning as expected.

Updates as published by NetBird.