based on user reports and queries over the last 24 hours
WireGuard outage statistics
- Official website: https://www.wireguard.com
- Email: team@wireguard.com
- Mailing list: wireguard@lists.zx2c4.com
- X: https://x.com/wireguard
- Verify that the 'Address' field contains a valid IP address and subnet mask in CIDR notation
- Ensure that the 'PrivateKey' and 'PublicKey' values are correctly generated and match between peers
- Confirm that the 'AllowedIPs' field properly specifies the network ranges that should be routed through the VPN
- Check that the 'Endpoint' field includes the correct public IP address or domain name and port number
- Configure proper DNS servers in the 'DNS' field of the configuration file
- Use fully qualified domain names instead of IP addresses for endpoints when possible
- Verify that the system's resolver can reach the configured DNS servers
- Consider using static IP addresses if DNS resolution is unreliable
- Ensure that the required UDP port (typically 51820) is open and forwarded on the firewall
- Check that both endpoints have proper internet connectivity and can reach each other
- Verify that NAT traversal is working correctly, especially for peers behind firewalls
- Test connectivity using basic network tools like ping and traceroute
- Regenerate keys if they become compromised or lost
- Use strong cryptographic keys generated with 'wg genkey' and 'wg pubkey'
- Implement proper key rotation policies for enhanced security
- Store private keys securely with appropriate file permissions
- Monitor network bandwidth and latency to identify potential bottlenecks
- Adjust the 'MTU' setting if experiencing packet fragmentation issues
- Consider using persistent keepalive for connections behind NAT
- Update to the latest version of WireGuard for bug fixes and performance improvements
WireGuard
Your message will be published in about
5 minutes
Service administration will see your message