Europe · Frankfurt
VPN servers in Germany: the Frankfurt exit server
WrapVPN's exit server in Germany is in Frankfurt, a city with a particular place in European routing. DE-CIX operates there, and a large share of European networks exchange traffic with one another across it. A route that ends in Frankfurt is therefore usually a short route onward to the rest of the continent.
This page covers the distances behind the latency figures, what changes when websites see a German IP address, and what the exit server can and cannot see. It also explains when Frankfurt is the wrong choice.
- Server location
- Frankfurt
- Area
- Europe
- Typical latency
- Not yet measured
Frankfurt as a meeting point for European networks
Internet traffic does not travel in straight lines; it travels between networks. It moves fastest where two networks hand packets directly to each other, with no paid third party in between.
Frankfurt is one of the European cities built around that exchange. DE-CIX operates there and a very large number of networks connect across it, while carriers, mobile operators, hosting companies and content delivery caches keep equipment within a few streets of one another.
As a result, traffic leaving the tunnel in Frankfurt usually has a short onward path to the network of the site you are loading, without a detour through another country. Several large cloud providers also operate data centres in or near the city, so many of the services that users in Europe rely on are hosted close to where the tunnel ends.
None of this makes a connection faster than using no VPN at all, because the route out to an exit server and back always adds distance. A well-placed exit server keeps that addition small for the destinations you use, and Frankfurt does so for most European destinations.
What a German IP address is useful for
Few of the common uses involve appearing to be in Germany. Most depend on having one stable address in central Europe that stays the same while everything around you changes.
- A consistent route while travelling: during a week spent across several countries, the local network can change every few hours. An exit server that stays in Frankfurt keeps your apparent location constant throughout. On iPhone, iPad and Mac, check the selected location before you connect: when the app opens while disconnected, it selects whichever location measured fastest.
- Hotel, café and conference Wi-Fi: these are the shared networks travellers meet most often. With the tunnel up, the network operator sees one encrypted session rather than the list of hosts your devices contacted.
- Work hosted in EU data centres: when file shares, dashboards and internal tools are hosted in Europe, an exit server inside Europe keeps each round trip short. Your requests then do not cross an ocean and back.
- Services that expect a stable address: some services re-check a signed-in session when the address behind it moves to another continent. Staying on one server location for the whole trip reduces those interruptions.
The distances behind Frankfurt's latency
Distance sets a minimum latency that no software on your device can reduce. A signal in optical fibre travels roughly 200 km in a millisecond, and a round trip covers the distance twice. The one-way distance in kilometres divided by 100 therefore gives a floor in milliseconds, before any router, queue or tunnel is involved. Applying this calculation to the main routes out of Frankfurt shows where the German server location performs well and where it does not.
Two qualifications apply to these figures. First, real fibre follows rights of way rather than the straight line on a map, so a measured figure always sits above the floor.
Second, the server list in the app shows a latency figure beside each location, measured from your device when the app starts. After moving to a different network, disconnect, then close the app fully and open it again to measure afresh. Treat the figures on this page as floors and the figures in the app as a rough comparison between locations.
- Frankfurt to Amsterdam, roughly 400 km, and to Zurich, roughly 300 km: floors in the low single digits.
- Frankfurt to Paris, roughly 480 km, to Milan, roughly 520 km, and to London, roughly 650 km: floors still under 10 ms.
- Frankfurt to Stockholm, roughly 1,200 km, and to Madrid, roughly 1,450 km: floors in the low double digits, comfortable for a call.
- Frankfurt to New York, roughly 6,200 km: a floor above 60 ms, acceptable for a call and imperceptible while reading.
- Frankfurt to Sydney, roughly 16,500 km: a floor above 160 ms, which is why no engineering can make that pairing feel local.
Frankfurt is inland, which costs time on transatlantic routes
This is the main argument against the German server location. Many transatlantic cables come ashore on the Cornish and French coasts. Frankfurt lies roughly 900 km overland from those landing stations, whereas London and Paris are only a few hundred kilometres from them.
A session from North America to Frankfurt therefore pays for the ocean crossing plus an overland backhaul, which an exit server nearer the coast largely avoids. The difference is a few milliseconds in each direction, not a different kind of experience. For destinations inside Europe the balance reverses, because the density of peering in Frankfurt usually recovers more than the backhaul costs.
As a rule, if most of what you use is hosted in Europe, Frankfurt is the better default. If your working day is spent on calls with North America, compare it with a European server location nearer the coast before deciding. Where the two disagree, trust the latency the server list reports over this reasoning.
What the Frankfurt exit server can and cannot see
The connection uses WireGuard. Each time you connect, our server sends your device its configuration for Frankfurt, keys included, and the WireGuard handshake then completes in a single round trip. Changing networks does not stop the tunnel, so moving from hotel Wi-Fi to a mobile hotspot during a journey does not mean starting again.
Between your device and Frankfurt, all traffic is encrypted. The network you joined, and anyone else on it, sees one session to one endpoint, not the list of hosts you contacted.
Beyond Frankfurt, your traffic is ordinary traffic from a German IP address, and the exit server is necessarily the point that knows which addresses it forwards to on your behalf. It cannot read the content of traffic protected by HTTPS, which covers most of what browsers and current apps send. Traffic that is not encrypted can be read on the exit server.
Ad and tracker blocking, which we call Clean Web, works one step earlier, at DNS. It is a switch that is on by default on Android and off on iPhone, iPad, Mac and Windows until you turn it on.
With Clean Web on, a lookup for a domain on a public advertising and tracking blocklist is answered as a name that does not exist. An app that uses the resolver WrapVPN sets therefore does not open that connection. Clean Web also enforces SafeSearch on the major search engines and YouTube. It works on domain names only: it does not read pages, and it does not protect against malware.
The side effects of a German IP address
An IP address is a location signal, and a great deal of software reads it. While you are connected through Frankfurt, websites commonly switch to German, quote prices in euros, centre maps and weather on German cities, and favour German-language pages in search results.
Some of these effects are useful. Package managers, container registries and software updaters choose a mirror or an edge cache by apparent location. With a German IP address they tend to download from a German mirror or a Frankfurt cache, which is a nearby copy for most users in Europe.
The app stores are not affected. Apple and Google take the store country from your account, so connecting through Frankfurt does not move you into the German storefront or change which catalogue you see.
The remaining effects are a matter of preference. Most sites offer a visible language control, and many remember the choice in a cookie. If you want the tunnel only to protect your traffic on a shared network, without German localisation, choose a server location in a country whose language you read.
How to set up WrapVPN
- 1
Install the app and sign in
Install WrapVPN on the device you travel with and sign in. One account covers iPhone, iPad, Mac, Android, Android TV and Windows, so the Frankfurt server location is available on whichever of them you use.
- 2
Choose Frankfurt in the server list
There is no entry named Germany. Look for the German flag and Frankfurt: the entry shows the city together with the DE country code. The list displays a latency figure beside each location, measured when the app started, which gives a rough idea of what Frankfurt costs from where you are before you connect.
- 3
Connect, then check two signs
Open any page that reports your IP address; it should show a German address. The second sign is localisation: if a search engine starts answering in German, websites are reading the exit server's location as expected. If a site still behaves as though you were at home, it is usually showing an earlier cached answer, so reload the page or clear that site's data.
Plans and prices
Weekly and monthly plans renew automatically until cancelled, and there is no annual commitment. You can cancel at any time in your App Store or Google Play subscription settings.
$1.99per week
$3.99per month
There is no annual or multi-year plan.
The monthly plan may include a 7-day free trial for eligible new subscribers.
See all plansCommon questions
Where exactly is the German exit server?
In Frankfurt, the city where DE-CIX operates. Traffic you send through the German server location leaves the tunnel there, in a city where a large share of European networks interconnect. That is the main reason the onward route is short for most of the continent.
Will the Frankfurt exit server slow me down if I am not in Europe?
Yes, by roughly the time it takes to cover the distance twice. Frankfurt to New York is about 6,200 km, which puts a round trip above 60 ms before any equipment is involved. Compare Frankfurt with a nearer server location using the latency figures in the server list before you settle on one.
Is Frankfurt the right European exit server for reaching North America?
Often not. Frankfurt lies roughly 900 km inland from the Atlantic cable landing stations, so a transatlantic route through it pays for that overland stretch on top of the ocean crossing. An exit server on the coast pays much less of it, while for European destinations the peering density in Frankfurt usually makes up the difference.
Do I need a long-term plan to use the German server location?
No. WrapVPN has no annual plan: the weekly plan costs $1.99 and the monthly plan $3.99, and a $0.99 one-day plan is sold through Google Play only. Every plan, including the free plan, gives access to every server location, Frankfurt among them. The monthly plan may include a seven-day free trial for eligible new subscribers, and weekly and monthly plans renew until you cancel them in your store's subscription settings.
Does connecting through Germany switch websites to German?
Often, yes. Localisation usually follows the exit server's IP address, so expect German-language pages and prices in euros while you are connected through Frankfurt. Language controls on websites still work, and choosing a server location in a country whose language you read avoids switching back and forth.
Can WrapVPN see what I do through the Frankfurt exit server?
The exit server forwards your packets, so it necessarily knows which addresses they are going to. It cannot read the content of traffic protected by HTTPS, which covers most traffic inside the tunnel, although unencrypted traffic can be read there.
Download WrapVPN
One account works on your phone, tablet and computer, with no device limit on any plan. Every server location is available on every plan, including the free plan.
Further reading
The following pages cover topics related to this one.
Location
VPN server in Japan: what the Tokyo exit server does
This page explains how WrapVPN's Tokyo exit server affects latency, why Tokyo routes differently from other Asian hubs, and how to use the app on Japanese Wi-Fi.
Travel
Public Wi-Fi attacks explained: what a VPN stops and what it can't
Follow one morning on café Wi-Fi: snooping, fake hotspots, tampered lookups and fake sign-in pages, and which of them a VPN actually stops.
Plans
A weekly VPN plan for trips with an end date
The $1.99 weekly VPN plan compared with the $3.99 monthly plan and the one-day plan on Google Play, and the trip lengths for which each is the better choice.
Location
VPN server in the United Kingdom: the London exit server
WrapVPN's UK exit server is in London. Distances to Dublin, Paris and New York, British localisation, station, café and library Wi-Fi, and what the exit sees.