Leaderboard

Sao Paulo is as cental America as you can get. "Lite South" America would be something like Mexico/Panama in where it would be better getting a server in Miami instead, for both ping and bandwidth related performance. Geographical center: Panama/Mexico/Costa Rica - Most providers are limited to lease a shared 100mbit connection per customer. This is because they have max 5-10Gbit per datacenter or less. Because of that, their main peering happens to be with U.S. providers, so see the sentence above. "Southern South": Rest of the countries are not going to happen - Peru, Chile, Argentina. No sufficient datacenters to offer quality bandwidth for a reasonable price. Wholesale of 1Gbit almost unspoken of. Bolivia, Paraguay, Uruguay - the same reasons as above, + add at least 5 more years for their availability after the countries above. Most providers in those areas offer only shaped 10Mbit traffic (yes, in 2019) with a burstable option to 100Mbit with a very high premium. Those providers mostly offer local data as well as CDN to companies like Akamai, Cloudflare, Google which is their most profitable way of operation. Other Caribbean islands or countries with less than 5M residents - can be totally dismissed. Not a valid option even for large "Big 10" companies to operate. An exotic new location will not give you the privacy/performance you would probably assume from a service like Air. So this is a strategic point which is totally transparent and provable. Don't make other providers who sell fake GeoIP locations (this is possible and actually much cheaper) or sell VPS/Cloud connectivity with limited 100Mbit b/w make your decision here, test your own locations with your maximum speed before you buy a VPN service. And always remember: If AirVPN ever wanted to cross that grey area, there would probably be 50 available countries now. Or maybe 100. This is not an ethical way to do (VPN) business. Not flagging any competitors here since we all know who they are. // Finding even a single provider in South America with apparently enough bandwidth and acceptable prices (probably because they have more than utilized) is not an easy task by it's own. Right now no other country can probably overcome Brazil by price/performance, where even 3 years ago the situation was nearly as same as above. Same things happen is East Asia as well, where I am more native, and is directly linked to the country GDP. (The case has some exceptions in countries like Ukraine, Romania) because they are strategically and historically big EU transit points where AirVPN operates. But largely if it costs more than an average monthly salary to get a 100mbit connectivity, this country cannot be generally considered as a valid location.

Website: http://www.gazzetta.it La Gazzetta dello Sport, an Italian sport website and streaming. Status: OK Routing: All servers to IT route. Note: if you have an advertising blocker active (like Adblock or uBlock) try to disable it. This site detect use of this blocker and prevent to see the video.

Hello! We're very glad to inform you that a new 1 Gbit/s server located in São Paulo, BR, is available: Peony. Peony is our first server in South America and we are very proud to start operating there. Special thanks go to out moderator Zhang who helped us find a datacenter with particularly good connectivity The AirVPN client will show automatically the new server. If you use the OpenVPN client you can generate all the files to access it through our configuration/certificates/key generator (menu "Client Area"->"Config generator"). The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP. Just like every other "second generation" Air server, Peony supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.2 and tls-crypt. Full IPv6 support is included as well. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses. You can check the server status as usual in our real time servers monitor: https://airvpn.org/servers/peony Do not hesitate to contact us for any information or issue. Kind regards and datalove AirVPN Team

Hello! Answered here.

Hello! Answered here. I'm pinning this, as it's a slightly recurring issue, which there's no need to make many threads about :).

Because many users are here for Eddie, and I was one of them.

Hello! Since this 6 years old thread has been linked on social networks, an update is due. What happened since 2013/2014 In mid January 2017, AirVPN developed growing concerns regarding Coinbase behavior and privacy policy AirVPN inquiries did not lead to a satisfactory resolution of the aforementioned concerns On January 26 2017, Coinbase informed AirVPN that "[AirVPN] has engaged in prohibited use in violation of our Terms of Service and we regret to inform you that we can no longer provide you with access to our service. " On January 27 2017, AirVPN asked Coinbase for clarifications and also asked to know exactly what Terms of Service points or articles AirVPN infringed. The request remained and remains currently unanswered. On January 27 2017, Coinbase, without mentioning any ToS violation, required a tax form document which AirVPN could not produce since it was a tax form exclusively reserved to USA taxpayers. AirVPN explained why such request was improper and what equivalent EU documents AirVPN could produce and re-iterated the previous request to disclose what part or articles of the Terms of Service AirVPN infringed. On January 28, 2017, Coinbase recognized that the tax form request for USA citizens or companies was an obvious mistake and that AirVPN could disregard it as a mistaken request by Coinbase. No mention of infringements of the Terms of Service was made and no reply to AirVPN previous questions was sent. On January 30, 2017, Coinbase threatened to cease service for AirVPN in 6 business days, reiterating the very same tax form request that was recognized by Coinbase itself as a mistake just two days earlier It was AirVPN understanding that Coinbase reiterating a mistaken and impossible to comply requirement, as well as its inability to specify which articles or parts of the ToS AirVPN infringed, had to be interpreted as actions aimed to find any justification, even irrational, to drop the service in any case. Such a behavior also contributed to further confirm previous AirVPN concerns. As a consequence, AirVPN stopped accepting payments via Coinbase on February 01, 2017, relying instead on BitPay and Coinpayments During February 2018, AirVPN founders decided that it was time to accept Bitcoin directly in order to cut out any intermediary, fully use Bitcoin potential and get rid of any current or future intermediary privacy intrusion and/or arbitrary decisions in Bitcoin transactions and/or Bitcoin accounts. Coinpayments remained and remains active to accept other cryptocurrencies (check https://airvpn.org/buy ) On March 26, 2018, AirVPN started to accept Bitcoin directly, without any intermediary In April 2018, Coinbase froze WikiLeaks account https://news.bitcoin.com/wikileaks-coinbase-shop-blocked/ In February 2019, Bitcoin Magazine published the following article https://bitcoinmagazine.com/articles/grim-stories-of-ethical-privacy-abuses-emerge-about-coinbases-new-partners/ In April 2019, Repubblica published the following article https://www.repubblica.it/esteri/2019/04/08/news/hacking_team_khashoggi-223556958/?refresh_ce Kind regards

Was having some serious issues this weekend with it, and watched my latency times to the servers here in my own backyard in LA shoot up to 1000+ms heh.

@zhang888 That's correct, in the European Union cooperating with a private entity in an attempt to disclose and transmit personal data (including an IP address, which is recognized under specific circumstances as "personal data") is a borderline operation which may configure civil and even criminal infringements. The transmission of personal data between private companies without the explicit and informed consent of the data subject is a serious infringement in every EU country. Just for information or curiosity, in Italy the attempt to disclose a person's identity through IP addresses harvesting and request to the provider (ISP in general, proxy, VPN...) has been recognized as an illegal act, which must be rejected, in the so called "Peppermint affair", a long dispute between 2005 and 2010, which ended with a resounding defeat of all copyright trolls. One of central roles defending the interests of the citizens whose identities could have been disclosed according to the improper or illegal requests of copyright trolls was covered by lawyer Carlo Blengino, who has been a source of inspiration to protect privacy and personal data for an AirVPN founder throughout the years, inspiration that is one of the leading AirVPN creation reasons. https://www.altalex.com/documents/news/2010/03/24/caso-peppermint-la-riservatezza-delle-comunicazioni-prevale-sul-diritto-d-autore Kind regards

I am on the VM 200M package. Speed test through AirVPN MANCHESTER server is 208M. (Yes I know what you are thinking but the 200 package is actually around 210). That’s using my iPad connected via WiFi to my ASUS AX-RT88U No complaints from me.

Are there any plans to replace them with 3 other servers on the East Coast?

I had the same error in the begin but when I select direct udp during making the confige files. and imported it again. Then it will connect well. I just wonder if I have to do more steps before I can use Sonarr for example.

I just started tinkering with VPN on my Synology as well. I have set it up succesfully using the above guide. But I have some connections that need to go around the VPN as well (mainly SSL connections to usenet servers). I have created a passthrough by adding static routes to the routing table in the Synology configuration that explicitly go to the specific usenet server (ranges). This seems to work quite well, but of course is not useful if the IP address of the destination servers do change.

I'm afraid you have same problem as kiwi in this post. This is Synology bug and I reported it to them so hopefully they will fix it. Just manualy disconnect and connect again.

I can't get the tunnel driver to install. I uninstalled both airvpn&driver, cleaned registry, and restarted windows. I am on W8.1 and installed the 64bit version and the ran airvpn as administrator, still getting the prompt message "Driver installation failed" after "installing tunnel driver" loading screen. Same with 32bit... Edit: It actually says "Driver installation failed", but if you look at programs installed, it is there. I just restarted Windows and everything is fine. You guys might want to fix that to "restart windows" or add a restart windows function with yes or no.

I'm getting the same thing right now, though it doesn't seem to ever allow me to connect at the moment (tried a range of servers around the world). Was working fine yesterday too.

Hi, I am running Buffalo WZR-600DHP on DD-WRT 20180. I successfully used the config generator to connect to Arrakis. I always *seem* to be connected (speedtests and other geolocations report me in Virginia and the OPENVPN status always says "connected" when I check). But I was sometimes getting erratic behaviour so I checked the logs and found what appears to be an unstable connection (see below for copy/paste of the OpenVPN status tab. The question is: Should I try other Open VPN servers? Downgrade my DD-WRT to the previous buffalo supported build (looks oldish) or install the only build on the DD-WRT web site that is made for my router (BrainSlayer-V24-preSP2/2013/04-01-2013-r21153/) I am looking for a) Confirmation that my VPN is "flapping" (I am not familiar with OpenVPN logging....for all I know this is normal and my issues are elsewhere) Advice on the OpenVPN c) Advice on how to "switch" OpenVPN servers easily...is there an easier way than changing the connection IP in my setup? Is the rest of my config valid across the opther servers? Thanks StateServer: : Local Address: Remote Address: Client: CONNECTED: SUCCESS Local Address: 10.4.25.150 Remote Address: 10.4.25.149 Status LogServerlog Clientlog 20130615 14:20:20 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:20:20 D MANAGEMENT: CMD 'log 500' 20130615 14:20:20 MANAGEMENT: Client disconnected 20130615 14:25:01 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:25:01 D MANAGEMENT: CMD 'state' 20130615 14:25:01 MANAGEMENT: Client disconnected 20130615 14:25:01 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:25:01 D MANAGEMENT: CMD 'state' 20130615 14:25:01 MANAGEMENT: Client disconnected 20130615 14:25:01 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:25:01 D MANAGEMENT: CMD 'state' 20130615 14:25:01 MANAGEMENT: Client disconnected 20130615 14:25:01 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:25:01 D MANAGEMENT: CMD 'log 500' 20130615 14:25:01 MANAGEMENT: Client disconnected 20130615 14:28:02 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:28:02 D MANAGEMENT: CMD 'state' 20130615 14:28:02 MANAGEMENT: Client disconnected 20130615 14:28:02 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:28:02 D MANAGEMENT: CMD 'state' 20130615 14:28:02 MANAGEMENT: Client disconnected 20130615 14:28:02 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:28:02 D MANAGEMENT: CMD 'state' 20130615 14:28:02 MANAGEMENT: Client disconnected 20130615 14:28:02 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:28:02 D MANAGEMENT: CMD 'log 500' 20130615 14:28:02 MANAGEMENT: Client disconnected 20130615 14:28:45 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:28:45 D MANAGEMENT: CMD 'state' 20130615 14:28:45 MANAGEMENT: Client disconnected 20130615 14:28:45 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:28:45 D MANAGEMENT: CMD 'state' 20130615 14:28:45 MANAGEMENT: Client disconnected 20130615 14:28:45 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:28:45 D MANAGEMENT: CMD 'state' 20130615 14:28:45 MANAGEMENT: Client disconnected 20130615 14:28:45 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:28:45 D MANAGEMENT: CMD 'log 500' 20130615 14:28:45 MANAGEMENT: Client disconnected 20130615 14:41:07 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:41:07 D MANAGEMENT: CMD 'state' 20130615 14:41:07 MANAGEMENT: Client disconnected 20130615 14:41:07 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:41:07 D MANAGEMENT: CMD 'state' 20130615 14:41:07 MANAGEMENT: Client disconnected 20130615 14:41:07 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:41:07 D MANAGEMENT: CMD 'state' 20130615 14:41:07 MANAGEMENT: Client disconnected 20130615 14:41:07 MANAGEMENT: Client connected from 127.0.0.1:5001 20130615 14:41:07 D MANAGEMENT: CMD 'log 500' 19700101 00:00:00

The server doesn´t appear to be very popular but I wouldn´t want it to disappear completely.

I tried to use Qubes yesterday, but apparently my HP Z600 is not compatible. Oh well, Fedora it remains!

FINAL UPDATE 19 SEP 2018 Migration has been completed and tests have been successful. All the mentioned servers are now available and connectivity is very good from major USA residential ISPs. IPv4 addresses remain the same, while IPv6 addresses have been changed. The servers operate in a new Dallas datacenter. EDIT 18 Sep 2018: migration has been completed to a new Dallas datacenter and servers have passed the tests. All the 10 servers will be again available soon. Hello! We regret to inform you that we will soon start a migration and potential relocation of the following servers currently located in Dallas: Chamaeleon Equuleus Helvetios Leo Mensa Pegasus Ran Scutum Volans Vulpecula The reason is that Cogent (our transit provider in Dallas) will not renew the contract on the current 10 Gbit/s line. Unfortunately they let us know very late, just a few days before the natural expiration and normal renewal of the contract itself. It's not a price problem, they do not want to renew with us and/or with our counselor in the USA. The mentioned servers are our property but disconnecting, packaging, moving (or shipping), reconnecting and reconfiguring may take a long time (probably a month or more). Therefore, we have decided to set up a small battery of new servers, five in Phoenix and five in Dallas itself, that will run during all the time which will be necessary to complete the migration. Such servers are being connected and set up in different datacenters as we write and after a brief 24/48 hours testing period we will make them available. All the new, mentioned servers have 1 Gbit/s ports. We deeply apologize for the inconvenience and at the same time we are confident that you can understand that this sudden and unexpected issue was and is totally out of our control. Kind regards and datalove AirVPN Staff

Website: Swisscom TV Switzerland streaming television from Swisscom, Live and On Demand. Status: OK Native: CH servers. Routing: All other servers.

Just checked again and had this. The early part seems to be different/more informative Serverlog Clientlog 20130616 00:25:50 Data Channel MTU parms [ L:1558 D:1450 EF:58 EB:135 ET:0 EL:0 AF:3/1 ] 20130616 00:25:50 Local Options String: 'V4 dev-type tun link-mtu 1558 tun-mtu 1500 proto UDPv4 comp-lzo cipher AES-256-CBC auth SHA1 keysize 256 key-method 2 tls-client' 20130616 00:25:50 Expected Remote Options String: 'V4 dev-type tun link-mtu 1558 tun-mtu 1500 proto UDPv4 comp-lzo cipher AES-256-CBC auth SHA1 keysize 256 key-method 2 tls-server' 20130616 00:25:50 Local Options hash (VER=V4): '22188c5b' 20130616 00:25:50 Expected Remote Options hash (VER=V4): 'a8f55717' 20130616 00:25:50 I UDPv4 link local: [undef] 20130616 00:25:50 I UDPv4 link remote: 192.96.200.18:443 20130616 00:25:50 TLS: Initial packet from 192.96.200.18:443 sid=5a02be17 512abe92 20130616 00:25:50 VERIFY OK: depth=1 /C=IT/ST=IT/L=Perugia/O=airvpn.org/CN=airvpn.org_CA/emailAddress=info@airvpn.org 20130616 00:25:50 VERIFY OK: nsCertType=SERVER 20130616 00:25:50 NOTE: --mute triggered... 20130616 00:25:50 6 variation(s) on previous 3 message(s) suppressed by --mute 20130616 00:25:50 I [server] Peer Connection Initiated with 192.96.200.18:443 20130616 00:25:52 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1) 20130616 00:25:52 PUSH: Received control message: 'PUSH_REPLY redirect-gateway def1 dhcp-option DNS 10.4.0.1 comp-lzo no route 10.4.0.1 topology net30 ping 10 ping-restart 60 ifconfig 10.4.25.150 10.4.25.149' 20130616 00:25:52 OPTIONS IMPORT: timers and/or timeouts modified 20130616 00:25:52 NOTE: --mute triggered... 20130616 00:25:52 4 variation(s) on previous 3 message(s) suppressed by --mute 20130616 00:25:52 I TUN/TAP device tun1 opened 20130616 00:25:52 TUN/TAP TX queue length set to 100 20130616 00:25:52 I /sbin/ifconfig tun1 10.4.25.150 pointopoint 10.4.25.149 mtu 1500 20130616 00:25:52 /sbin/route add -net 192.96.200.18 netmask 255.255.255.255 gw 72.53.115.105 20130616 00:25:52 /sbin/route add -net 0.0.0.0 netmask 128.0.0.0 gw 10.4.25.149 20130616 00:25:52 /sbin/route add -net 128.0.0.0 netmask 128.0.0.0 gw 10.4.25.149 20130616 00:25:52 /sbin/route add -net 10.4.0.1 netmask 255.255.255.255 gw 10.4.25.149 20130616 00:25:52 I Initialization Sequence Completed 20130616 00:29:17 MANAGEMENT: Client connected from 127.0.0.1:5001 20130616 00:29:17 D MANAGEMENT: CMD 'state' 20130616 00:29:17 MANAGEMENT: Client disconnected 20130616 00:29:17 MANAGEMENT: Client connected from 127.0.0.1:5001 20130616 00:29:17 D MANAGEMENT: CMD 'state' 20130616 00:29:17 MANAGEMENT: Client disconnected 20130616 00:29:17 MANAGEMENT: Client connected from 127.0.0.1:5001 20130616 00:29:17 D MANAGEMENT: CMD 'state' 20130616 00:29:17 MANAGEMENT: Client disconnected 20130616 00:29:18 MANAGEMENT: Client connected from 127.0.0.1:5001 20130616 00:29:18 D MANAGEMENT: CMD 'log 500' 20130616 00:29:18 MANAGEMENT: Client disconnected 20130616 00:31:53 Replay-window backtrack occurred [1] 20130616 00:33:58 MANAGEMENT: Client connected from 127.0.0.1:5001 20130616 00:33:58 D MANAGEMENT: CMD 'state' 20130616 00:33:58 MANAGEMENT: Client disconnected 20130616 00:33:58 MANAGEMENT: Client connected from 127.0.0.1:5001 20130616 00:33:58 D MANAGEMENT: CMD 'state' 20130616 00:33:58 MANAGEMENT: Client disconnected 20130616 00:33:58 MANAGEMENT: Client connected from 127.0.0.1:5001 20130616 00:33:58 D MANAGEMENT: CMD 'state' 20130616 00:33:58 MANAGEMENT: Client disconnected 20130616 00:33:58 MANAGEMENT: Client connected from 127.0.0.1:5001 20130616 00:33:58 D MANAGEMENT: CMD 'log 500' 19700101 00:00:00