Exit node benchmark feature
Systems and methods for effectively managing exit nodes are provided. The exemplary systems and methods use a Supernode to examine an Exit Node through sending and receiving a request to a Target. Information about the exit node is then stored into the Supernode. According to the information provided from the Supernode, the Exit Nodes Database systemizes the proxies according to availability and provides available exit nodes to a User Device.
1. A computer-implemented method of checking suitability of exit nodes for proxying comprising:
connecting to a supernode;
sending a benchmark request to an exit node;
implementing the benchmark request at the exit node;
sending a response for the benchmark request to the supernode;
measuring an exit node response quality;
storing exit node metadata to an exit node database; and
wherein the measuring of the exit node response quality identifies whether the exit node is suitable for proxying or not suitable for proxying;
wherein the exit node indicated as suitable for proxying can be stored in exit node groups categorizing as random proxying, proxying of requests to specific geolocation, proxying of requests to specific target, or any combination thereof.
2. The method of claim 1 , wherein the response of the exit node is stored in the supernode.
3. The method of claim 1 , wherein a number of the exit nodes connected to the supernode at the same time is unlimited.
4. The method of claim 1 , wherein the benchmark request is applied to the exit node during the initial registration of the exit node with the service provider infrastructure or is applied to an exit node that has been previously registered and stored in the exit node database and is exhibiting performance inadequate corresponding to the thresholds configured at the service provider infrastructure.
5. The method of claim 1 further comprising:
wherein benchmark targets are changed dynamically according to results of analyzing a customer's request as monitored, registered, and aggregated by a service provider infrastructure.
6. The method of claim 5 further comprising:
wherein the benchmark request target is a resource submitted to the exit node as an IP address or URL/URI.
7. The method of claim 1 further comprising:
wherein the benchmark request target is a resource submitted to the exit node as an IP address or URL/URI.
8. The method of claim 1 wherein response quality measurements are stored with the storing exit node metadata to the exit node database.
9. A non-transitory computer readable medium for checking availability of proxy servers comprising instructions which, when executed by a computing device within a service provider infrastructure, cause the corresponding computing device to:
accept a connection from an exit node;
send a benchmark request to the exit node;
accept a response to the benchmark request from the exit node;
measure an exit node response quality;
store exit node metadata to an exit node database;
compare the benchmark response quality measurements to the quality thresholds configured;
place the exit node in a corresponding group based on the exit node metadata and a quality of the response provided by the exit node;
provide the exit node registered in the exit node database;
wherein the measuring of the exit node response identifies whether the exit node is suitable for proxying or not suitable for proxying.
10. The non-transitory computer readable medium of claim 9 wherein the benchmark request is performed against a specific selected target, geolocation, IP address, or HTTP link.
11. The non-transitory computer readable medium of claim 9 wherein the exit node suitable for proxying is stored in the exit node database and categorized as intended for random proxying, or proxying against a specific geolocation, proxying of requests to a specific target, any combination thereof, or not suitable for proxying.
12. The non-transitory computer readable medium of claim 9 wherein the benchmark request is applied to the exit node during the initial registration with a proxy service provider or is applied to an exit node, already stored in the proxy pool, that has response measurements marked as less than thresholds configured at the service provider infrastructure.
13. The non-transitory computer readable medium of claim 9 wherein the response of the exit node is stored in the supernode.
14. The non-transitory computer readable medium of claim 9 wherein a number of the exit nodes connected to the supernode at the same time is unlimited.
15. The non-transitory computer readable medium of claim 9 wherein the benchmark request is applied to the exit node during the initial registration of the exit node with the service provider infrastructure or is applied to an exit node that has been previously registered and stored in the exit node database and is exhibiting performance inadequate corresponding to the thresholds configured at the service provider infrastructure.
16. The non-transitory computer readable medium of claim 9 further comprising:
wherein benchmark targets are changed dynamically according to results of analyzing a customer's request as monitored, registered, and aggregated by a service provider infrastructure.
17. The non-transitory computer readable medium of claim 9 further comprising:
wherein the benchmark request target is a resource submitted to the exit node as an IP address or URL/URI.
18. The non-transitory computer readable medium of claim 9 further comprising:
wherein the benchmark request target is a resource submitted to the exit node as an IP address or URL/URI.
19. The non-transitory computer readable medium of claim 9 wherein response quality measurements are stored with the storing exit node metadata to the exit node database.