Feeds
Version: 2.0.0 Website: https://spur.us/data-feeds/ Support and FAQs
About
Our Feed products provide IP Context data in bulk for your on-prem environment. Visit our website for more information on how our feeds can help you. The base feed update cadence is daily. Updates are typically available by 0500 UTC.
Quick Start
Get up and running without reading about all of the details.
Set variables:
export FEED_TYPE=<subscription level> # e.g. anonymous, anonymous-residential
export TOKEN=<your token> # provided in trial or welcome docs
Fetch the most recent feed:
curl -o latest.json.gz -L -H "Token: $TOKEN" "https://feeds.spur.us/v2/$FEED_TYPE/latest.json.gz"
Feed Data
ip The IP address queried
as Autonomous System Details
client.behaviors Behaviors of clients on this IP
client.concentration Location concentration of clients on this IP
client.count Average number of clients observed per day
client.countries Number of countries clients have come from
client.proxies Call-back proxies running from devices on this IP
client.spread The geographic spread of clients (km^2)
client.types Types of client devices observed
infrastructure The classification of infrastructure this IP is in
organization The organization operating the IP address
location Maxmind GeoLite2 location data
services Protocols and services running on this IP (e.g. OpenVPN)
tunnels VPN/Proxy/Anonymization details and operator information
risks Risks and threats from this IP address
Authentication
As part of your setup process (or trial) you were provided a token directly or generated one using your account dashboard online at spur.us. Authentication with the Feed API service is performed by passing your token in an HTTP header named Token. For example, using the cURL utility, an authenticated request would look like:
curl -o latest.json.gz -L -H "Token: $TOKEN" https://feeds.spur.us/v2/$FEED_TYPE/latest.json.gz
Responses
The Feed API will return information about the specific feed requested in the response headers:
x-feed-generation-date: The date this specific feed was generated
The API also includes HTTP status codes:
200: The request succeeded
302: The request succeeded and issued a redirect to a signed Google Cloud Storage URL hosting the feed
403: Access is denied, your token is most likely invalid
Downloading
GET /v2/:FEED_TYPE
An entire feed snapshot can be downloaded via a GET request to our feed URL. Your access token must be provided in a header or query parameter named Token
. If your account has historical feed access you may also use this API to list other available feed dates. To improve delivery speeds, we leverage Google's Content Delivery Network (CDN). As a result, your client must support redirects in order to complete the download.
Latest
Download the latest version of the feed:
# Using the anonymous feed as an example
export FEED_TYPE=anonymous
# Make your token available
export TOKEN=YOUR_FEED_ACCESS_TOKEN
# Download the latest compressed feed using cURL
curl -L -O -H "Token: $TOKEN" "https://feeds.spur.us/v2/$FEED_TYPE/latest.json.gz"
# Decompress the feed
gunzip latest.json.gz
# Download the latest documentation (this document) as a PDF
curl -L -O -H "Token: $TOKEN" "https://feeds.spur.us/v2/$FEED_TYPE/README.pdf"
# Get metadata regarding the latest feed including the
# time of the data included in the feed (generated_at)
# and the time the file was available for download (available_at)
curl -L -H "Token: $TOKEN" "https://feeds.spur.us/v2/$FEED_TYPE/latest"
Historical
If your account also has access to historical data, the following options are available:
# List Available Runs
curl -H "Token: $TOKEN" "https://feeds.spur.us/v2/$FEED_TYPE/"
# List available files for a specific date
curl -H "Token: $TOKEN" "https://feeds.spur.us/v2/$FEED_TYPE/20211101/"
# Download a specific date
curl -L -H "Token: $TOKEN" -O "https://feeds.spur.us/v2/$FEED_TYPE/20211101/feed.json.gz"
Realtime
If your account also has access to "realtime" data, the following options are available:
# List Available 5 Minute update files for a day
curl -H "Token: $TOKEN" "https://feeds.spur.us/v2/$FEED_TYPE/realtime/20211101/"
# Download a specific 5 minute window
curl -L -H "Token: $TOKEN" -O "https://feeds.spur.us/v2/$FEED_TYPE/realtime/20211101/1815.json.gz"
# Download the latest 5 minute window
curl -L -H "Token: $TOKEN" -O "https://feeds.spur.us/v2/$FEED_TYPE/realtime/latest.json.gz"
Realtime access via 5 minute files will de-duplicate observations over the 5 minute window. Many optional schema fields will not be available. Consult the schema for information on what fields are optional.
Check out a sample project that ingests the realtime data into Redis.
Example Record
{
"as": {
"number": 30083,
"organization": "AS-30083-GO-DADDY-COM-LLC"
},
"client": {
"behaviors": [ ... ],
"concentration": {
"city": "Weldon Spring",
"country": "US",
"density": 0.202,
"geohash": "9yz",
"skew": 45,
"state": "Missouri"
},
"count": 14,
"countries": 1,
"proxies": [ ... ],
"spread": 4941431,
"types": [ ... ]
},
"infrastructure": "DATACENTER",
"ip": "148.72.164.186",
"location": {
"city": "St Louis",
"country": "US",
"state": "Missouri"
},
"risks": [ ... ],
"services": [ ... ],
"tunnels": [
{
"anonymous": true,
"entries": [ ... ],
"exits": [ ... ],
"operator": "NORD_VPN",
"type": "VPN"
}
]
}
SCHEMA NOTE: The Version 2 schema inconsistently used uppercase Organization
instead of organization
in the as
field. This field was corrected as of the 2023-04-20 feed export. Please note that historical v2 feeds prior to 2023-04-20 still contain the field as.Organization
. If you are not ingesting data prior to 2023-04-20, or are using a JSON utility that automtically lowercases the first letter of JSON fields (or ignores it completely), then you can ignore this discrepancy.
IPv6 Network Support (BETA)
Spur feeds currently include a mix of IPv4 (/32) and IPv6 (/128) addresses. While we believe this approach is the most accurate way to perform IP based analysis, we also realize that this format will present scaleability challenges as IPv6 usage grows. To accomidate this, Spur has broken out IPv6 into it's own distinct feeds. Our approach to IPv6 is to distill our knowledge to the most relevant block of IPv6 addresses possible using a new network
field.
All existing feeds are also being produced available in BETA with dedicated IPv6 formats. To download the entirety of IPv6 address blocks by adding -ipv6
to the base feed name. For example:
# Download the anonymous feed ipv6 netblocks
curl -L -O -H "Token: $TOKEN" "https://feeds.spur.us/v2/anonymous-ipv6/latest.json.gz"
# Download the anonymous-residential feed ipv6 netblocks
curl -L -O -H "Token: $TOKEN" "https://feeds.spur.us/v2/anonymous-residential-ipv6/latest.json.gz"
SCHEMA NOTE: IPv6 feeds use our IP Context data structure EXCEPT address
is replaced with network
. The network
field provides an IPv6 address in CIDR notation.
Here are some additional details regarding IPv6 feeds:
- The size of the network reported may vary depending on the Spur's analysis. Some observations may be made about large networks, and other observations about smaller networks. Invidual IPv6 addresses (/128) are still possible.
- The existence of a large network (e.g. /48) does not preclude the existence of a smaller network in the same space (e.g. a /64 or /128).
- Each record will still indicate the most applicable information available for that network, you do not have to merge data up or down.
- Spur isolates the common patterns and behavior for each network based on how it is being used. For example, if a single IPv6 address is actually NATing traffic, or performing IPv6 to IPv4 tunnelling, the data will be representative of all of the traffic behind that NAT.
Custom Feeds
Spur offers several custom feeds and export utilities as optional add-ons to our enterprise subscriptions. These feeds return different data or subsets of data than our IP Context feed products. If you have questions about whether or not you have access to a custom feed, please contact your account representative for more information.
Datacenter-Hosting (DCH)
Our DCH Feed is a collapsed summary of all IP Address netblocks that Spur has identified as being part of "datacenter" infrastructure. These networks contain IPs that are leased as part of some infrastructure service and are typically hosted in a facility that is distinct from the physical location of its users. This commonly includes IPs assigned to virtual private servers (VPS), shared hosting, cloud infrastructure, and/or dedicated Colo rack space.
The Spur DCH Feed provides a base level of knowledge to facilitate rules and security policies outside of specific anonymity services that Spur tracks. Additionally, the DCH Feed:
- Collapses known Datacenter IPs into digestible network blocks in CIDR notation
- Does not filter for any notable activity, or any sub-leased hosting infrastructure
- Does not have historical availability and is provided as a snapshot based on query time
- Is available in CSV or JSON format
Download DCH Feed
Here are some examples of how to pull the DCH Feed:
# Download the default feed to a file named dch.csv
curl -o dch.csv -H "Token: $TOKEN" "https://exports.spur.us/v1/feeds/dch"
# Download the feed in JSON format
curl -H "Token: $TOKEN" "https://exports.spur.us/v1/feeds/dch?output=json"
# Only download DCH Network CIDRS
curl -H "Token: $TOKEN" "https://exports.spur.us/v1/feeds/dch?fields=network"
# Download the network and organization fields in JSON
curl -H "Token: $TOKEN" "https://exports.spur.us/v1/feeds/dch?fields=network,organization&output=json"
DCH Request Parameters
output
- Type:
STRING
- Required:
false
- Description: The data output format as
csv
,json
, ormmdb
. Default:csv
- Example:
json
includeCSVHeader
- Type:
BOOL
- Required:
false
- Description: Include CSV headers as the first row in the output; only applicable if
output
iscsv
. Default:false
- Example:
true
fields
- Type:
STRING
- Required:
false
- Description: Only fetch the provided fields (comma separated). Available values are
network
,organization
, andasn
. Default:network,organization,asn
- Example:
asn,organization
DCH Response Codes
Code | Description |
---|---|
200 |
The request succeeded. |
403 |
Access is denied, your token is most likely invalid. |
500 |
An error occurred. |
DCH Output Fields
Data is provided as CSV or JSON with the fields network
, organization
(optional), asn
(optional) by default.
network
- Type:
STRING
- Required:
true
- Description: The netblock designated as part of Datacenter/Hosting Provider IP Space.
- Example:
8.8.8.8/30
organization
- Type:
STRING
- Required:
false
- Description: The ownership organization for the netblock. This is optional.
- Example:
M247 Europe SRL
asn
- Type:
INT
- Required:
false
- Description: The current Autonomous System Number for this network. This is optional.
- Example:
9009
DCH Example Data
network,organization,asn
2.56.151.0/24,M247 Europe SRL,9009
2.56.188.0/22,Clouvider Limited,62240
2.57.20.0/23,M247 Europe SRL,9009
2.58.64.0/23,Kirino LLC,41378
2.58.95.0/24,ASN-QUADRANET-GLOBAL,8100
2.58.172.0/24,M247 Europe SRL,9009
65.20.98.0/23,"Vultr Holdings, LLC",
198.27.102.160/30,Ownage Hosting,
46.20.120.103/32,P1SB-04580aed335cb8342b7b4f575423d11a6938569c,
50.116.81.229/32,WEBSITEWELCOME.COM (gator1630.hostgator.com),
74.63.142.84/30,Flexential Colorado Corp.,
51.38.166.44/30,OVH SAS,
148.251.56.192/29,HOS-168117,
173.233.74.212/30,TurnKey Internet Inc.,
69.93.159.0/24,SoftLayer Technologies Inc.,
94.130.172.224/27,Hetzner Online GmbH,
158.69.100.236/30,"OVH Hosting, Inc."
NOTE: includeCSVHeader=true
must be set in the request to receive the headers as the first row.
{"asn":null,"network":"156.38.209.120/29","organization":"xneelo-tscolo"}
{"asn":null,"network":"169.60.21.16/28","organization":"QRadar on Cloud - Staging"}
{"asn":null,"network":"217.182.232.240/29","organization":"OVH SAS"}
{"asn":null,"network":"83.222.240.171/32","organization":"P1SB-7801017dab6a769c6008daa4e12f04d9f5897496"}
{"asn":null,"network":"83.170.115.65/32","organization":"UK2 Customer"}
{"asn":null,"network":"217.61.12.0/25","organization":"Aruba S.p.A."}
{"asn":null,"network":"83.170.90.154/31","organization":"UK2 Customer"}
{"asn":null,"network":"108.178.10.56/29","organization":"SG Hosting Inc."}
{"asn":null,"network":"78.46.26.8/32","organization":"Timme Hosting GmbH \u0026 Co. KG"}
{"asn":null,"network":"83.170.109.180/32","organization":"UK2 Customer"}
NOTE: format=json
must be set in the request to get a JSON response.
Feed Export Utility
An export utility for the Anonymous and Anonymous +Residential daily feeds to facilitate integration with third-party platforms such as SIEMs, IDS, and Firewalls. This utility allows a customization of fields, format, size, and location. It is not intended as a replacement for the full feed downloads. If the number of results exceeds the provided limit, the busiest IPs will be selected. The default record limit is 2,000,000 records. Only a subset of fields are available for this export utility. This utility also supports the generation of a diff file for the previous day's data (or a specified date). The xport utility does support our IPv6 BETA functionality for IPv6 specific feeds.
NOTE: Anonymous +Residential does not support daily diffs and is still considered a Beta feature. All IPv6 results will use "network" instead of "ip"
Using the Feed Export Utility
Here are some example commands to use the feed export utility:
# Download All EXPRESS_VPN IPs in CSV format
curl -H "Token: $TOKEN" "https://exports.spur.us/v1/feeds/anonymous?tags=EXPRESS_VPN"
# Download max limit LUMINATI_PROXY IPs in the US
curl -H "Token: $TOKEN" "https://exports.spur.us/v1/feeds/anonymous-residential?tags=LUMINATI_PROXY&ccs=US"
# Download All of the attributed VPN Exits in Italy
curl -H "Token: $TOKEN" "https://exports.spur.us/v1/feeds/anonymous?ccs=IT&attributed=true"
# Download all IPs in the US,CA, or MX from NORD_VPN or EXPRESS_VPN. Limit the data to ip, tag, and clientCount
curl -H "Token: $TOKEN" "https://exports.spur.us/v1/feeds/anonymous?ccs=US,CA,MX&tags=NORD_VPN,EXPRESS_VPN&fields=ip,tag,clientCount"
# Download a diff file from the previous day
curl -H "Token: $TOKEN" "https://exports.spur.us/v1/feeds/anonymous?diff=true"
# Download a diff file from a specific date (2023-02-01)
curl -H "Token: $TOKEN" "https://exports.spur.us/v1/feeds/anonymous?diff=true&diffDate=2023-02-01"
# Download all Private Internet Access (PIA_VPN) CIDR blocks
curl -H "Token: $TOKEN" "https://exports.spur.us/v1/feeds/anonymous?tags=PIA_VPN&fields=tag,network"
# Download data in MMDB format
curl -o anon.mmdb -H "Token: $TOKEN" "https://exports.spur.us/v1/feeds/anonymous?fields=network,tag,infrastructure,clientCount&output=mmdb"
Feed Export Utility Request Parameters
The available feed types in the request are:
anonymous
anonymous-ipv6
anonymous-residential
anonymous-residential-ipv6
output
- Type:
STRING
- Required:
false
- Description: The data output format as
csv
,json
, ormmdb
. Default:csv
- Example:
json
includeCSVHeader
- Type:
BOOL
- Required:
false
- Description: Include CSV headers as the first row in the output; only applicable if
output
iscsv
. Default:false
- Example:
true
fields
- Type:
STRING
- Required:
false
- Description: Only fetch the provided fields (comma separated). Options are
ip
,tag
,infrastructure
,services
,clientCount
,locationCity
,locationState
,locationCountry
, ornetwork
. Defaults to all fields. NOTE: ifnetwork
is requested, all IPs will be collapsed to CIDR notation under the fieldnetwork
. If thenetwork
field is requested, neitherip
norservices
may also be requested. Additionally,diff
is disabled for network notation. Expect queries withnetwork
to take significantly longer to process. - Example:
ip,tag,clientCount
limit
- Type:
INT
- Required:
false
- Description: A maximum number of output results. By default, no more than 2 million results will be returned.
- Example:
5000
tags
- Type:
STRING
- Required:
false
- Description: A comma separated list of service tags that you wish to include in the output. Default: all tags.
- Example:
EXPRESS_VPN
callbackProxies
- Type:
STRING
- Required:
false
- Description: A comma separated list of service tags in the
client.proxies
section of the data. Only works for Anonymous + Residential. - Example:
OXYLABS_PROXY
ccs
- Type:
STRING
- Required:
false
- Description: A comma separated list of country codes that you wish to include in the output.
- Example:
US,DE,FR
attributed
- Type:
BOOL
- Required:
false
- Description: Specify if only named and attributed VPNs should be included.
- Example:
true
diff
- Type:
BOOL
- Required:
false
- Description: Create a diff file between the current date and yesterday. This adds a new output field "diff". This cannot be combined with the
network
field. - Example:
true
diffDate
- Type:
DATE STRING
- Required:
false
- Description: Sets the date for the diff to be created. It will diff the provided date with the previous day's data.
- Example:
2023-02-01
Feed Export Utility Response Codes
Code | Description |
---|---|
200 |
The request succeeded. |
403 |
Access is denied, your token is most likely invalid. |
500 |
An error occurred. |
Feed Export Utility Fields
Data is provided in CSV or JSON formats with the following fields:
ip
- Type:
STRING
- Required:
true
- Description: The IP Address for this record. This can be IPv4 or IPv6. For IPv6 feeds, this is
network
and presented in CIDR notation. - Example:
8.8.8.8
tag
- Type:
STRING
- Required:
false
- Description: The name of the anonymization service. Full list
- Example:
NORD_VPN
callbackProxy
- Type:
STRING
- Required:
false
- Description: The name of a callbackProxy service on the IP. Full list
- Example:
OXYLABS_PROXY
infrastructure
- Type:
STRING
- Required:
false
- Description: The type of infrastructure.
- Example:
DATACENTER
services
- Type:
ARRAY
- Required:
false
- Description: An array of listening services on that IP Address
- Example:
[OPENVPN, IPSEC]
clientCount
- Type:
INT
- Required:
false
- Description: The daily average number of devices on this IP Address
- Example:
15
locationCity
- Type:
STRING
- Required:
false
- Description: The MaxMind GeoLite2 city location of the IP Address
- Example:
San Jose
locationState
- Type:
STRING
- Required:
false
- Description: The MaxMind GeoLite2 state location of the IP Address
- Example:
California
locationCountry
- Type:
STRING
- Required:
false
- Description: The MaxMind GeoLite2 country location of the IP Address
- Example:
US
diff
- Type:
ENUM
- Required:
false
- Description: Only present if generating a diff file. This marks a record to be added or removed.
- Example:
add
,del
NOTE: For additional descriptions, please see the IP Context data structure with the fields network, organization (optional), asn (optional) by default.
Feed Export Utility Example Data
ip,tag,infrastructure,services,clientCount,locationCity,locationState,locationCountry
193.37.33.161,EXPRESS_VPN,DATACENTER,[],4,Seattle,Washington,US
37.9.41.76,FINE_VPN,DATACENTER,[],,,,RU
104.227.25.216,NEWIPNOW_PROXY,DATACENTER,[],,Baie-D'Urfe,Quebec,CA
154.51.182.35,OXYLABS_PROXY,,[],,London,England,GB
95.214.191.224,OXYLABS_PROXY,DATACENTER,[],,,Hyōgo,JP
155.50.185.118,SPEEDYHUB_PROXY,,[],,,,US
38.15.158.27,RAYOBYTE_PROXY,DATACENTER,[],,Los Angeles,California,US
154.44.84.192,HYPE_PROXY,,[],1,Palatine,Illinois,US
154.40.3.47,OXYLABS_PROXY,,[],,,,US
142.111.166.18,OXYLABS_PROXY,DATACENTER,[],1,,,US
NOTE: includeCSVHeader=true
must be set in the request to receive the headers as the first row.
{"clientCount":null,"infrastructure":"DATACENTER","ip":"45.138.205.143","locationCity":"Chisinau","locationCountry":"MD","locationState":"Chișinău Municipality","services":null,"tag":"OXYLABS_PROXY"}
{"clientCount":null,"infrastructure":"DATACENTER","ip":"104.194.195.136","locationCity":"Temecula","locationCountry":"US","locationState":"California","services":null,"tag":"OXYLABS_PROXY"}
{"clientCount":5,"infrastructure":"DATACENTER","ip":"172.225.251.21","locationCity":"Atlanta","locationCountry":"US","locationState":"Georgia","services":null,"tag":"ICLOUD_RELAY_PROXY"}
{"clientCount":1,"infrastructure":null,"ip":"38.95.190.117","locationCity":"Clinton","locationCountry":"US","locationState":"Maryland","services":null,"tag":"OXYLABS_PROXY"}
{"clientCount":1,"infrastructure":"DATACENTER","ip":"69.58.12.196","locationCity":"The Bronx","locationCountry":"US","locationState":"New York","services":null,"tag":"WEBSHARE_PROXY"}
{"clientCount":null,"infrastructure":"DATACENTER","ip":"92.223.89.152","locationCity":"Luxembourg","locationCountry":"LU","locationState":"Luxembourg","services":null,"tag":"PROTON_VPN"}
{"clientCount":null,"infrastructure":null,"ip":"154.29.10.120","locationCity":"Charlotte","locationCountry":"US","locationState":"North Carolina","services":null,"tag":"OXYLABS_PROXY"}
{"clientCount":null,"infrastructure":null,"ip":"37.72.189.239","locationCity":"Athens","locationCountry":"GR","locationState":"Attica","services":null,"tag":"DRSOFT_VPN"}
{"clientCount":null,"infrastructure":null,"ip":"181.214.51.241","locationCity":"Melbourne","locationCountry":"AU","locationState":"Victoria","services":["OPENVPN","IPSEC"],"tag":"PIA_VPN"}
{"clientCount":null,"infrastructure":"DATACENTER","ip":"172.245.206.194","locationCity":"Newport News","locationCountry":"US","locationState":"Virginia","services":null,"tag":"DRSOFT_VPN"}
NOTE: format=json
must be set in the request to get a JSON response.
ip,tag,infrastructure,services,clientCount,locationCity,locationState,locationCountry,diff
193.37.33.161,EXPRESS_VPN,DATACENTER,[],4,Seattle,Washington,US,add
37.9.41.76,FINE_VPN,DATACENTER,[],,,,RU,add
104.227.25.216,NEWIPNOW_PROXY,DATACENTER,[],,Baie-D'Urfe,Quebec,CA,add
154.51.182.35,OXYLABS_PROXY,,[],,London,England,GB,del
95.214.191.224,OXYLABS_PROXY,DATACENTER,[],,,Hyōgo,JP,add
155.50.185.118,SPEEDYHUB_PROXY,,[],,,,US,add
38.15.158.27,RAYOBYTE_PROXY,DATACENTER,[],,Los Angeles,California,US,add
154.44.84.192,HYPE_PROXY,,[],1,Palatine,Illinois,US,del
154.40.3.47,OXYLABS_PROXY,,[],,,,US,add
142.111.166.18,OXYLABS_PROXY,DATACENTER,[],1,,,US,add
NOTE: includeCSVHeader=true
must be set in the request to receive the headers as the first row.
Service-Metrics Feed
An export utility for metadata and information on all of the services Spur tracks. This is updated daily and does not provide history. This feed contains new-line separated JSON of the tag metadata object. The service metric feed is useful for filtering Spur feeds based on other criteria. For example: any FREE_VPN services that accept crypto payments.
Using the Service-Info Export Utility
Here are some example commands to use the service-info export utility:
# Download all service tag metrics and information
curl -L -H "Token: $FEED_TOKEN" "https://feeds.spur.us/v2/service-metrics/latest.json.gz"
Service-Metrics Example Data
{"allowsCrypto":"true","allowsFreeAccess":"true","allowsMultihop":"false","allowsTorrents":"true","allowsWhiteLabel":"false","categories":[],"description":"","isAnonymous":"true","isCallbackProxy":"false","isEnterprise":"false","isInactive":"true","isNoLog":"true","metrics":{"averageDeviceCount":null,"churnRate":null,"distinctASNs":null,"distinctCountries":null,"distinctIPs":null,"distinctISPs":null},"name":"","platforms":[],"protocols":[],"tag":"PROVPN_MOBILE_VPN","targetingTypes":[],"website":""}
{"allowsCrypto":null,"allowsFreeAccess":null,"allowsMultihop":null,"allowsTorrents":null,"allowsWhiteLabel":null,"categories":[],"description":null,"isAnonymous":null,"isCallbackProxy":null,"isEnterprise":null,"isInactive":"false","isNoLog":null,"metrics":{"averageDeviceCount":"8.664853312609283","churnRate":"0.02728820535847927","distinctASNs":"43","distinctCountries":"26","distinctIPs":"6758","distinctISPs":"84"},"name":null,"platforms":[],"protocols":[],"tag":"KOBZ_VPN","targetingTypes":[],"website":null}
{"allowsCrypto":"true","allowsFreeAccess":"true","allowsMultihop":"false","allowsTorrents":"true","allowsWhiteLabel":"false","categories":[],"description":"","isAnonymous":"true","isCallbackProxy":"false","isEnterprise":"false","isInactive":"true","isNoLog":"true","metrics":{"averageDeviceCount":null,"churnRate":null,"distinctASNs":null,"distinctCountries":null,"distinctIPs":null,"distinctISPs":null},"name":"","platforms":[],"protocols":[],"tag":"NIMBLEWAY_PROXY_USER","targetingTypes":[],"website":""}