As of approximately 10 minutes ago, from the date/time of this post, it seems there is either some type of weird IP thing going on from the gateway/data centers, or some type of changes being made, or something has failed somewhere, within the PIA VPN network. I tried other gateways also, same basic results. If you disconnect then reconnect and run a dns leak test from one of the various leak test sites (and have dns leak protection enabled), you get something like this below now (I used the ipleak.net web site where its clear to see).This change happened suddenly with no warning or notification, the IP for me changed while I was still connected. There were no changes on my end for configuration or anything else, just the IP suddenly changed. Things slowed down for a few seconds, so I happen to notice the app I have running that checks the VPN public IP address and for DNS leaks every 30 seconds and it was in an alarm status and showed the 'new' public VPN IP and with further checks it kept coming back with this address, once the IP changed things went back to normal speed.In the below notice the IP address at the top vs the one at the bottom assigned by the gateway. Notice it still says "DNS Address - 1 server" which indicates no DNS leak (because it indicates that the gateway assigned IP is making the queries), however, the IP address at the top is the IP address web sites will see when you visit them (for now at least - the IP at the top belongs to LogicWeb Inc which is something that PIA has used before I think). The difference between the 'new' public VPN IP and that resolved for the DNS are different with the lower IP (162.216.46.117) being the IP assigned by the gateway but the public IP on the internet side of the gateway is different. Normally this would indicate a DNS leak because the gateway assigned address and the Public IP address on the internet side should be the same for no DNS leak to exist. Thus DNS leak tests, all of the commonly used web site tests, are either failing (unlikely) or there is something wrong/different in the PIA VPN network, maybe with the PIA dns servers used while using DNS Leak protection which points back to part of an issue I posted about before here > https://www.privateinternetaccess.com/forum/discussion/23789/pia-intentionally-breaks-windows-10#latest , so maybe PIA is making some changes but we should have been notified of this by PIA I think if they are making changes that affect what the public IP change would be vs the gateway assigned IP. The 'new' VPN public IP (in the example below 173.239.232.117) still seems to point to the gateway as geo-location remains the same as the gateway, if one plugs this new IP into the PIA speed test link it comes back to the same gateway indicated as being connected to (e.g. http://173.239.232.117:8888/speedtest ) so maybe we are seeing an exit node IP with this. Maybe PIA is making some changes, who knows at this point as with this screwy VPN anything could happen. Some of you may or may not see this same thing depending on the gateway and data center. Before anyone jumps in and starts diverting this thread from its notification and same subject discussion intention - NO, it is not an anomaly, or a DNS leak caused on the user end, or anything to do with the OS, this one is pure PIA caused. Before anyone gets excited over this lets see what PIA has to say about it. I suspect we will not hear anything about it from them real soon.