VPN provider
TunnelBear
Exit infrastructure across 47 countries and 21 hosting networks.
Providers publish exits differently: some list individual addresses, others list ranges covering many. Entries counts what is published; IPv4 addresses counts how many IPv4 addresses those entries cover, so a provider publishing mostly IPv6 can show fewer addresses than entries.
What this tells you
- Exits are spread across 21 separate hosting networks including DigitalOcean, LLC, Zenlayer Inc and The Constant Company, LLC, which makes blanket blocking by network far less effective.
- No IPv6 exits are published. On an IPv6-capable connection, traffic may bypass the tunnel entirely unless the client blocks it.
- Exit locations across 47 countries.
Which networks the exits run on
Exit space on a network we hold a record for covers 100% of this provider's IPv4 space. The table below divides that space.
| Hosting network | IPv4 share | |
|---|---|---|
| DigitalOcean, LLC | 35% | |
| Zenlayer Inc | 18% | |
| The Constant Company, LLC | 14% | |
| Akamai Connected Cloud | 12% | |
| M247 Europe SRL | 8% | |
| Limestone Networks, Inc. | 8% | |
| Latitude.sh | 0.9% | |
| HostPapa | 0.9% | |
| Everything else (13 more) | 3% |
Exit locations
Space we can place in a country covers 100% of this provider's IPv4 space. The table below divides that space.
| Country | IPv4 share | |
|---|---|---|
| Germany | 18% | |
| United Kingdom | 15% | |
| United States | 11% | |
| Spain | 10% | |
| Japan | 9% | |
| Mexico | 5% | |
| Canada | 4% | |
| Brazil | 3% | |
| Everything else (39 more) | 24% |
Every figure on this page is also JSON: /api/v2/directory/vpn/tunnelbear. Breakdowns paginate from there, so a table showing the largest rows here returns all of them. Read the API.