Hello, Leonardo I will need more informations to find out why that's happened to you.  I will need to know when this happened, how many proxies did you had in this region before this happened?

Also how many proxy servers did you try to add before this happened.

Thanks for your reply, so I can simulate it.

Hi! thanks for the response.

i was trying to create I think from 2 to 10 proxies, tried everything. Had 0 proxies already created and before I get this error ii had these two problems:

https://createproxy.com/question/failed-to-list-subnets-in-virtual-network-on-azure/

https://createproxy.com/question/problem-with-microsoft-azure/

to solve one I followed this guide: https://stackoverflow.com/questions/36200143/the-subscription-is-not-registered-to-use-namespace-microsoft-datafactory-error

for the other I just create a subnet where he could not find one... 

then the error about ip ranges came up... 

Thanks a lot :D !!!

I belive all this problems are related to expired trial subscription / or not valid subscription. Please make sure, that you have valid subscription, If you dont, please Add subscription, select Pay as you Go.. Just make sure, that you have subscription with Active status as show on image bellow. Once you do this, remove your Azure Old Account from CreateProxy and Create New Azure Account (Profile) in CreateProxy with new SUBSCRIPTION ID - I hope, this wiíll fix your issue, because from what you are reporting here there is no evidence, that something is wrong with CreateProxy. 

Thanks a lot for your reply and explanation, ii will let u know gif that solve my problem. Really support your work.

Btw, is there any dc proxy from the available ones (was, GCloud, Azure, etc...) Which let u surf on supremenewyork? is every single one banned?

In few days there will be released future of this project, all cloud stuff stay, but Im going to shift this project by many new options and features. Stay tunned.

Oh i solved it btw, thanks a lot again!!

May you tell us how?

I solved. The first two issue but not the  IP address range is outside the IP address range issue.

So it seems the issue is what script or code createproxy is using is not working on all the regions. I tried central US and that fails while north Europe works.

Odd now it works on central US. Basically try all regions until one works then try the other regions again. It may have been the account too. I created and deleted a bunch of stuff on it. Maybe had to wait over 24 hours. IDK!

Hm, this can not be caused by selecting region that work, then selectiong other regions... Why? Simply because CreateProxy is going to create for each region own directory. So it may not have relationship, I think that there is something like interval, limits on Microsoft side etc. 

The problem with subnet calculation may still exist, to be clear about this, microsoft is little bit tricky, since I need to calculate things that others do automatically (amazon, google...).. So yes, there may be problem when you go over 250 instances in single region. I know that I need to write there some additional logic, but you should be generally fine if you go with up-to 250 instances in single region.