Author: Skylar.W

If you are on Windows 11 and are using WireGuard to connect to our network for v4 access, you may need to change your address from x.x.x.x/32 to either x.x.x.x/28 or x.x.x.x/29 depending on which subnet size our volunteer techs setup for your use.

This appears to only be affecting Windows 11 machines where using a /32 causes the platform to fail to route traffic correctly. This is a new issue that we have been recently dealing with and this appears to be the fix. Oddly, using a /128 on the IPv6 does not cause this same issue. This is only affecting this platform and does not seem to affect Linux or Android.

Our team did not have enough time to process accounting task for the previous month. All services are still active, you do not need to worry about things. Also, no one came close to the 600GB soft limit for the previous month.

We are aware of some ongoing issues with the network that services our secondary host which runs our status page and slave name server. The data center has been contacted and has let us know that they are having internal issues and are working to resolve it. During this time secondary services might become unusable off and on.

Additionally, our volunteers are working off and on on some updates and changes to the hypervisor on the secondary. Expect some minor outages today caused by our team.