Leaderboard

Ok, I ended up solving this myself with option 2), I made a script that "decrypts" and "encrypts" the file on demand so it can be edited manually. For it to work, the encyption/password in Eddie must be set to "Plain (no password asked)" (at least temporarily, after writing it back to the source, password protection can be turned back on). In case anybody else ever needs it, I attached the script (you need python and pycryptodome preinstalled). python eddie_profile.py decrypt --help python eddie_profile.py decrypt --outfile Eddie.xml # edit the XML, then make sure Eddie is not running before doing python eddie_profile.py encrypt --help python eddie_profile.py encrypt --infile Eddie.xml eddie_profile.py.txt

@jcpingu Hello! Yes, your mtr output shows that the what you experience is not strictly related to some Atlanta datacenter problem. Generally speaking, it's how the Internet works with "best effort" routing, which in turn is determined (also, among other factors) by peering agreements. See also. https://en.wikipedia.org/wiki/Peering and https://en.wikipedia.org/wiki/Tier_1_network#Routing_through_peering If your ISP [transit provider] (SBCGlobal?) does not offer low round trip times to/from "our" datacenter in Atlanta, don't be too upset or discouraged, it may happen: as you have seen, you can get excellent round trip times with other datacenters, geographically farther away, but nearer in terms of "network distance" (round trip time). Compare the mtr output by @go558a83nk whose packets go directly to Cogent to see an example difference. "Our" Atlanta datacenter traffic is served by Internap, which (at least in Atlanta) in turn interconnects directly with Lumen (former Level3, tier1), so we have operated well here in the best interest of our customers. There's nothing we can do under this respect in this datacenter. Since you get a lower round trip time with servers in other datacenters, use them! We offer a variety of options for peering and load alternatives and redundancy: for example in the USA we have servers in datacenters which (globally) have PoP either in to major tier1 networks (AT&T, Lumen (Level3)) or major tier2 networks (Cogent, Verizon, Hurricane). By doing so we maximize the likelihood that an AirVPN user can find a datacenter with a "good peering" with his/her residential ISP (or at least with his/her residential ISP's transit provider(s)). Trust us, it's not easy to operate a really agnostic and neutral network in USA datacenters, due to the widespread hostility against specific protocols. Kind regards