Turbo VPN
Turbo VPN offers VPN applications for desktop and mobile devices, plus a Chrome extension.
- IPv4 prefixes
- 35
- IPv6 prefixes
- 0
- Public IP examples
- 12
Coverage: Connection endpoints returned by Turbo VPN's browser server list. Free, paid and extension groups are included; this does not establish the complete native app network. The IC VPN profile shows this Innovative Connecting service only. Only a subset of the published hostnames resolved; address counts are partial.Resolved 30 of 31 published hostnames
- Last successful capture
- 2026-11-22 02:20 UTC
- Last source check
- 2026-11-22 02:20 UTC
- Product category
- consumer vpn
- Catalog status
- active
This capture contains 35 IP prefixes. Single-address observations use /32 for IPv4 and /128 for IPv6. Counts describe listed network records, not active servers or users.
Published service locations
Country tags attached to the captured connection addresses by their source. These are service locations, not measured IP geography or the provider’s complete country list. An address may appear under more than one location.
20 of 20 service locations
| AustraliaAU | 1 |
| BrazilBR | 1 |
| BulgariaBG | 1 |
| CanadaCA | 1 |
| CzechiaCZ | 1 |
| FranceFR | 1 |
| GermanyDE | 2 |
| IndiaIN | 3 |
| IndonesiaID | 1 |
| ItalyIT | 1 |
| JapanJP | 2 |
| NetherlandsNL | 1 |
| PortugalPT | 1 |
| SingaporeSG | 2 |
| South KoreaKR | 1 |
| SpainES | 1 |
| SwedenSE | 1 |
| TürkiyeTR | 1 |
| United KingdomGB | 2 |
| United StatesUS | 12 |
Approximate sample locations
Basis: sampled IP geolocation. This is not a measure of Turbo VPN’s complete coverage or its users’ locations. Records without a country are omitted, so published locations may cover only part of the inventory.
12 country-tagged records
| Country | Sampled IPs | Relative record count |
|---|---|---|
| 4 | ||
| 1 | ||
| 1 | ||
| 1 | ||
| 1 | ||
| 1 | ||
| 1 | ||
| 1 | ||
| 1 |
Published prefix counts over time
Daily retained source observations. Counts describe network inventory, not connections, traffic or active servers.
View exact daily prefix counts
| UTC date | IPv4 prefixes | IPv6 prefixes |
|---|---|---|
| 2026-11-22 | 35 | 0 |
| 2026-11-21 | 35 | 0 |
| 2026-11-20 | 35 | 0 |
| 2026-11-19 | 35 | 0 |
| 2026-11-18 | 35 | 0 |
| 2026-11-17 | 35 | 0 |
| 2026-11-16 | 35 | 0 |
| 2026-11-15 | 35 | 0 |
| 2026-11-14 | 35 | 0 |
| 2026-11-13 | 35 | 0 |
| 2026-11-12 | 35 | 0 |
| 2026-11-11 | 35 | 0 |
| 2026-11-10 | 35 | 0 |
| 2026-11-09 | 35 | 0 |
| 2026-11-08 | 35 | 0 |
ASNs represented in the public sample
Network ownership can differ from the service brand. Counts are sampled addresses, not a provider’s complete ASN footprint.
IP address examples
Each address keeps its source role and its own location basis. Connection infrastructure and published range examples are not confirmed exits unless the source explicitly identifies them as exits. For prefix-list sources, an IP example is the first address in its range, not a measured reachable exit.
The example filter searches only the addresses shown here. Look up another IP · Check my public IP
12 of 12 public examples
The cited source reports these settings for individual examples, not every provider feature. Protocol and port lists are independent; their combinations and reachability were not tested.
| IP address and source role | Location evidence | ASN and network | Evidence |
|---|---|---|---|
| 45.79.221.35connectionPublished protocol: HTTPS proxyPublished port: 20501 | United StatesApproximate IPQuery geolocationAtlanta · Geo checked 2026-11-21 | AS63949Akamai Connected Cloud | provider-turbo |
| 64.23.129.94connectionPublished protocol: HTTPS proxyPublished port: 20501 | United StatesApproximate IPQuery geolocationSanta Clara · Geo checked 2026-11-21 | AS14061DigitalOcean, LLC | provider-turbo |
| 103.78.133.170connectionPublished protocol: HTTPS proxyPublished port: 20501 | South KoreaApproximate IPQuery geolocationSeoul · Geo checked 2026-11-21 | AS45996DAOU TECHNOLOGY | provider-turbo |
| 138.199.42.123connectionPublished protocol: HTTPS proxyPublished port: 443 | United StatesApproximate IPQuery geolocationChicago · Geo checked 2026-11-21 | AS212238Datacamp Limited | provider-turbo |
| 146.185.144.14connectionPublished protocol: HTTPS proxyPublished port: 20501 | The NetherlandsApproximate IPQuery geolocationAmsterdam · Geo checked 2026-11-21 | AS14061DigitalOcean, LLC | provider-turbo |
| 169.150.210.53connectionPublished protocol: HTTPS proxyPublished port: 443 | GermanyApproximate IPQuery geolocationFrankfurt am Main · Geo checked 2026-11-21 | AS212238Datacamp Limited | provider-turbo |
| 172.232.217.78connectionPublished protocol: HTTPS proxyPublished port: 20501 | ItalyApproximate IPQuery geolocationMilan · Geo checked 2026-11-21 | AS63949Akamai Connected Cloud | provider-turbo |
| 172.233.175.142connectionPublished protocol: HTTPS proxyPublished port: 20501 | United StatesApproximate IPQuery geolocationMiami · Geo checked 2026-11-21 | AS63949Akamai Connected Cloud | provider-turbo |
| 172.235.216.9connectionPublished protocol: HTTPS proxyPublished port: 20501 | JapanApproximate IPQuery geolocationOsaka · Geo checked 2026-11-21 | AS63949Akamai Connected Cloud | provider-turbo |
| 185.82.218.50connectionPublished protocol: HTTPS proxy | BulgariaApproximate IPQuery geolocationSofia · Geo checked 2026-11-21 | AS59729ROUTE 95 LLC | provider-turbo |
| 192.46.211.172connectionPublished protocol: HTTPS proxyPublished port: 20501 | IndiaApproximate IPQuery geolocationMumbai · Geo checked 2026-11-21 | AS63949Akamai Connected Cloud | provider-turbo |
| 209.38.18.149connectionPublished protocol: HTTPS proxyPublished ports: 443, 20501 | AustraliaApproximate IPQuery geolocationSydney · Geo checked 2026-11-21 | AS14061DigitalOcean, LLC | provider-turbo |
IP range examples
Single-address observations appear as /32 or /128 prefixes. A larger prefix is shown only when supported by the source. Listed addresses are not necessarily reachable, and source attribution alone is not a reason to block them.
| Network prefix | Source role | Evidence |
|---|---|---|
| 45.79.221.35/32 | connection | provider-turbo |
| 50.116.26.163/32 | connection | provider-turbo |
| 62.133.63.141/32 | connection | provider-turbo |
| 64.23.129.94/32 | connection | provider-turbo |
| 68.183.230.68/32 | connection | provider-turbo |
| 79.110.54.211/32 | connection | provider-turbo |
| 103.78.133.170/32 | connection | provider-turbo |
| 128.1.186.123/32 | connection | provider-turbo |
| 138.68.100.10/32 | connection | provider-turbo |
| 138.199.42.123/32 | connection | provider-turbo |
Sources and limits
Checked is the latest collection attempt. Captured is the last successful collection. Published is the publisher's date, when supplied. Inventory changed is when different source data was last observed. None of these dates confirms that an address is reachable. An unspecified license does not grant permission to redistribute a full dataset.
| Source and role | Checks and capture dates | Status and license |
|---|---|---|
| Turbo VPN official connection inventory ↗connectionResolved 30 of 31 published hostnames | Checked 2026-11-22 02:20 UTCCaptured 2026-11-22 02:20 UTCPublished 2026-11-22 02:18 UTCInventory changed 2026-11-08 15:16 UTC | currentPublic provider metadata; no dataset redistribution license asserted |
Official service references
Public previews contain up to 10 ranges, 12 IP examples and 10 ASN rows. Sample geolocation is approximate and does not describe the provider's entire network. Use the VPN checker to see the API's current classification for an address.
All VPN providers · Official crawler networks · IPQuery sources and methods