Infrastructure

NetBird Down? Real-Time Status & Outage Tracker (2026)

NetBird Down? Real-Time Status & Outage Checker (2026)

NetBird is an open-source zero-trust network platform that uses WireGuard to create secure peer-to-peer mesh networks. With 12K+ GitHub stars, NetBird connects distributed teams, servers, and cloud resources in a fully encrypted overlay network without requiring a central VPN gateway. NetBird Cloud provides managed signal and relay servers, while self-hosted deployments offer full control. When NetBird's management or signal service goes down, new connections cannot be established and disconnected peers cannot reconnect.

This page provides real-time NetBird status monitoring, historical uptime data, and instant outage alerts.

Current NetBird Status

Check live NetBird status now: ezmon.com/status/netbird

Our monitoring probes NetBird Cloud infrastructure every 60 seconds from multiple geographic regions:

  • NetBird Cloud Dashboard — Web UI at app.netbird.io
  • Management API — Peer registration and network policy API
  • Signal Server — WebRTC signaling for peer discovery (GRPC)
  • TURN/RELAY Servers — Fallback relay for peers behind strict NAT
  • STUN Servers — NAT traversal coordination

NetBird Live Monitoring Dashboard

SERVICE              STATUS    UPTIME (30d)  LAST CHECK
──────────────────────────────────────────────────────
NetBird Dashboard    ✅ UP     99.8%         30s ago
Management API       ✅ UP     99.7%         30s ago
Signal Server        ✅ UP     99.8%         30s ago
TURN/Relay           ✅ UP     99.9%         30s ago
STUN Servers         ✅ UP     99.9%         30s ago
──────────────────────────────────────────────────────
Multi-region checks: US-East, EU-West, AP-Southeast

Status updates every 60 seconds. Subscribe for instant alerts.

How to Check if NetBird Is Down

Quick Diagnosis Steps

  1. Check ezmon.com — Multi-region probes distinguish management from signal failures
  2. Test peer statusnetbird status
  3. Check management connectivitynetbird status --detail
  4. Check signal servercurl https://signal.netbird.io/
  5. NetBird Community Slack#help channel for real-time reports

NetBird CLI Health Checks

# Check NetBird peer status
netbird status

# Get detailed connection info
netbird status --detail

# Check all peers and their connectivity
netbird status --json | jq '.peers[] | {fqdn: .fqdn, status: .connStatus, latency: .latency}'

# Check management server connection
netbird status --json | jq '{management: .managementState, signal: .signalState}'

# Check WireGuard interface
sudo wg show netbird0

# Test connectivity to another peer
ping 100.x.x.x  # NetBird peer IP

# View NetBird logs
journalctl -u netbird -f --since "1 hour ago"

# Force reconnect
netbird down && netbird up

NetBird API Health Check

import requests
import os
import subprocess
import json

def check_netbird_status():
    """Check NetBird Cloud and local agent health."""
    api_key = os.environ.get("NETBIRD_API_KEY")
    
    # Check Management API
    try:
        resp = requests.get(
            "https://api.netbird.io/api/peers",
            headers={"Authorization": f"Token {api_key}"},
            timeout=10
        )
        peers = resp.json()
        connected = sum(1 for p in peers if p.get("connected"))
        print(f"Management API: OK ({len(peers)} peers, {connected} connected)")
    except Exception as e:
        print(f"Management API failed: {e}")
    
    # Check local agent status via CLI
    try:
        result = subprocess.run(
            ["netbird", "status", "--json"],
            capture_output=True, text=True, timeout=10
        )
        if result.returncode == 0:
            status = json.loads(result.stdout)
            mgmt = status.get("managementState", "unknown")
            signal = status.get("signalState", "unknown")
            peers = len(status.get("peers", []))
            print(f"Local agent: management={mgmt}, signal={signal}, peers={peers}")
        else:
            print(f"NetBird agent not running: {result.stderr}")
    except FileNotFoundError:
        print("NetBird CLI not installed")
    except Exception as e:
        print(f"Local status check failed: {e}")

check_netbird_status()

Common NetBird Issues and Fixes

Peer Cannot Connect / NAT Traversal Failure

# Check peer connection details
netbird status --detail | grep -A5 "peer_name"

# Force peer reconnection
netbird down
netbird up --management-url https://api.netbird.io

# Check if STUN is reachable
nc -u stun.netbird.io 3478 -v

# Check if TURN relay is being used
netbird status --json | jq '.peers[] | select(.relayed == true) | .fqdn'

# Enable verbose logging for NAT debugging
NETBIRD_LOG_LEVEL=DEBUG netbird up

# Check firewall rules (must allow UDP outbound)
sudo iptables -L OUTPUT -n | grep -E "(51820|3478|5349)"

Management API Connection Failures

# Test management API connectivity
curl -v https://api.netbird.io/api/peers \
  -H "Authorization: Token $NETBIRD_API_KEY" 2>&1 | grep -E "(HTTP|< )"

# Check DNS resolution
dig api.netbird.io +short

# Re-authenticate NetBird agent
netbird down
netbird up --management-url https://api.netbird.io \
  --setup-key $NETBIRD_SETUP_KEY

# Check certificate validity
openssl s_client -connect api.netbird.io:443 2>/dev/null | \
  grep -E "(subject|issuer|NotAfter)"

Self-Hosted NetBird Server Issues

# Check all NetBird services
docker-compose -f docker-compose.yml ps

# Check management service health
curl -s http://localhost:33073/health | jq .

# Check signal service health  
curl -s http://localhost:10000/  # Signal gRPC port

# View management logs
docker logs netbird-management --tail 50

# View signal logs
docker logs netbird-signal --tail 50

# Restart management service
docker-compose restart management

NetBird Architecture: What Can Go Down

Component Function Impact if Down
Management Server Peer registration, network policy, access control New peers cannot join; policy changes blocked (existing P2P connections survive)
Signal Server WebRTC signaling for peer-to-peer WireGuard setup New connections cannot be established between peers
TURN/Relay Server Fallback relay for peers behind symmetric NAT Relayed connections drop; strict-NAT peers isolated
STUN Server Discovers public IP/port for NAT traversal Peer-to-peer hole punching fails; falls back to TURN
WireGuard Interface (local) Local encrypted tunnel kernel module All NetBird connectivity fails on that node

NetBird Uptime History

Period Uptime Incidents Longest Outage
Last 7 days 99.9% 0
Last 30 days 99.8% 0
Last 90 days 99.6% 1 1h 15m
Last 12 months 99.4% 4 2h 30m

Historical data sourced from ezmon.com NetBird monitoring.

Get Instant NetBird Outage Alerts

Never miss a NetBird outage again. ezmon.com monitors NetBird 24/7 with multi-region probes and sends instant alerts via:

  • Email (with escalation policies)
  • Slack and Microsoft Teams webhooks
  • PagerDuty and Opsgenie integration
  • SMS and phone call alerts
  • Webhook for custom notification pipelines

Set up NetBird monitoring in 30 seconds: ezmon.com/monitor/netbird


This page is maintained by ezmon.com — independent uptime monitoring for developer infrastructure. Data is collected from our global probe network and updated in real time. We are not affiliated with NetBird Inc.

netbirdzero trustwireguardmesh vpnsecure networkstatus checkeroutagedowntime