The free server, in New York
The free plan runs on Veto's server in New York, United States. Veto set it up itself, from the operating system to the firewall, and Pro accounts can use it too.
| Item | New York server |
|---|---|
| Status | Open, on the free plan and on Pro |
| Tested | 15 November 2026, ten behaviour checks, all passed |
| Tunnel | WireGuard, on UDP |
| Addresses | One entry address for apps, a separate exit address for the internet, over IPv4 and IPv6 |
| Name lookups | Answered on the server itself, with no record of what was asked |
| Devices | One per free account, three per Pro account |
The ten checks it passed are listed on the home page. They cover the address a site sees, name lookups, the blocked ports and the handshake.
Why the New York server has two addresses
The New York server has an entry address and an exit address. Your app connects to the entry address. When your traffic leaves for the internet, it leaves from the exit address.
- A site can never learn the address your app talks to. In our test, none of the packets on the site's side carried the entry address or the device's own address.
- Complaints land on the exit address. If an exit address is ever blocked or reported, the server can move to a new one without changing anything in your app.
- Free and Pro leave through different exit addresses. What one plan's users do cannot get the other plan's address blocked.
Our rule for every exit address of the free plan: it is checked against public blocklists before any user reaches it, and an address with a history stays out of service.
The Pro locations
Pro reaches further: 95 servers in 55 countries, as listed on 15 November 2026. The app offers every city, and the tables below give each one, grouped by region.
Eight Pro cities we tested
On 15 November 2026 we connected to eight Pro cities from our New York server, one connection each, and downloaded a 40 MB test file through each. We also asked our own site where each connection appeared to be. Every city appeared where the list says it is, and name lookups worked in all eight.
| City | Sites saw the connection in | Download speed |
|---|---|---|
| Miami | Miami, United States | 399 Mbit/s |
| Amsterdam | Amsterdam, Netherlands | 148 Mbit/s |
| London | London, United Kingdom | 147 Mbit/s |
| Frankfurt | Frankfurt am Main, Germany | 129 Mbit/s |
| Sao Paulo | Sao Paulo, Brazil | 102 Mbit/s |
| Tokyo | Tokyo, Japan | 74 Mbit/s |
| Dubai | Dubai, United Arab Emirates | 59 Mbit/s |
| Singapore | Singapore | 52 Mbit/s |
Europe: 30 countries
| Country | Cities |
|---|---|
| Albania | Tirana |
| Austria | Graz, Vienna |
| Belgium | Brussels |
| Bulgaria | Sofia |
| Czech Republic | Prague |
| Denmark | Copenhagen |
| Estonia | Tallinn |
| Finland | Helsinki |
| France | Paris |
| Germany | Berlin, Dusseldorf, Frankfurt |
| Greece | Athens, Thessaloniki |
| Ireland | Dublin |
| Italy | Florence, Palermo |
| Latvia | Riga |
| Lithuania | Vilnius |
| Moldova | Chisinau |
| Netherlands | Amsterdam |
| Norway | Oslo |
| Poland | Warsaw |
| Portugal | Lisbon |
| Romania | Bucharest |
| Russia | Moscow, St Petersburg |
| Serbia | Belgrade |
| Slovenia | Ljubljana |
| Spain | Barcelona, Seville |
| Sweden | Stockholm |
| Switzerland | Zurich |
| Turkey | Bursa, Istanbul |
| Ukraine | Kyiv |
| United Kingdom | London |
The Americas: 10 countries
| Country | Cities |
|---|---|
| Argentina | Buenos Aires |
| Bolivia | La Paz |
| Brazil | Sao Paulo |
| Canada | Montreal, Toronto, Vancouver |
| Chile | Santiago |
| Colombia | Bogota |
| Costa Rica | San Jose |
| Ecuador | Quito |
| Mexico | Mexico City |
| United States | Atlanta, Chicago, Kansas City, Los Angeles, Miami, New York |
Asia and the Pacific: 9 countries
| Country | Cities |
|---|---|
| Australia | Sydney |
| Hong Kong | Hong Kong |
| India | Mumbai |
| Indonesia | Jakarta |
| Japan | Tokyo |
| Pakistan | Islamabad |
| Philippines | Manila |
| Singapore | Singapore |
| Thailand | Bangkok |
The Middle East and Africa: 6 countries
| Country | Cities |
|---|---|
| Israel | Tel Aviv |
| Kenya | Nairobi |
| Morocco | Fez |
| Nigeria | Lagos |
| South Africa | Johannesburg |
| United Arab Emirates | Dubai |
How to choose a VPN location
The right location depends on why you are connecting.
| Why you connect | Pick | Because |
|---|---|---|
| Privacy from your own provider | The nearest location | Any location hides your browsing from your provider, and a near one adds the least distance |
| An address in a particular country | A location in that country | Sites see the exit address and its place |
| A network that blocks some locations | Another location | Blocks are often by address, so a different server may get through |
Distance matters because every packet goes to the server and back before it goes anywhere else. A server on another continent adds the time it takes to cross that distance, twice. Our test above shows it: from New York, Miami gave the fastest download of the eight and Singapore the slowest.
What stays the same on every server
Picking a location changes the address that sites see. It does not change what Veto keeps about you.
- The same account record: a number, a plan, a paid until date and one key for each device.
- The same app, with the same kill switch and the same lookups inside the tunnel.
- The same checks after each connection: the app confirms your address changed before it says Protected.
One difference is worth naming. The New York server runs its own resolver, which refuses names known to serve malware, and the free plan's rules: no outgoing mail on port 25, no Windows file sharing ports and no port forwarding. The filter and those rules belong to the New York server, as the pricing page shows.
How the New York server is built
The New York server was set up by one script, step by step, so it can be built again exactly the same way.
- A clean system. A fresh install of Debian, with password logins switched off and logins by key only.
- Two addresses. One entry address for apps and one exit address for the internet, over IPv4 and IPv6.
- The tunnel. WireGuard, listening on the entry address and nowhere else.
- The resolver. A name resolver on the server itself, with its query log switched off. On the free plan it refuses names on a public list of malware sites, refreshed every day.
- The rules. The firewall rules: no outgoing mail on port 25, no Windows file sharing ports, no private addresses, no port forwarding and a cap on new connections.
- The check. The ten behaviour checks run against the finished server. A server that fails any of them does not take users.
The same checks run again after every change to a server. That is how the tables on this site stay true after the day they were written.
What a VPN server actually does
A VPN server is the far end of your tunnel. It receives your sealed packets, checks and opens them, and sends them on to the internet from its own exit address. When the replies come back, it seals them and sends them down the tunnel to you.
So the server you pick decides two things: the address and place that sites see, and the distance your traffic travels before it reaches the open internet. It does not change how the tunnel is sealed, which is the same on every server. Our guide How does a VPN work? follows one page load through the New York server, step by step.
Questions about servers
How many servers does Veto have?
96. The free plan uses the New York server, which passed its tests on 15 November 2026. Pro adds 95 servers in 55 countries, and we tested eight Pro cities ourselves on the same day.
Which VPN location should I pick?
For privacy from your own provider, any location works, so pick the closest one, which is usually the quickest. Pick a far location only when you need an address in that country.
Does the server location change what Veto keeps?
No. The account record is the same on every server and every plan: a number, a plan and a paid until date. A location changes the address that sites see, nothing else.
Which Pro location is the fastest?
Usually the nearest one. In our test from New York on 15 November 2026, Miami gave a 399 Mbit/s download and Singapore 52 Mbit/s. Pick the closest city unless you need an address in a particular country.
Why does the New York server have two addresses?
So that the address a site sees is never the address your app connects to. Abuse reports and blocks land on the exit address, and the entry address stays reachable for everyone using the server.
Can I get a dedicated address of my own?
No. Exit addresses are shared by everyone on a server, which is part of what keeps any one person from standing out.