IPv6 proxies

saku82

Newbie
Joined
Jan 25, 2010
Messages
10
Reaction score
2
Does any of you already use ipv6 proxies or is everyone still on the mercy of ipv4? We are currently running around 240,000 ipv6 proxies with much success but I was a bit stunned to see so little info on ipv6 proxy providers. I knew that lime proxies did have them in the past, at least they advertised with it on their website but I had no luck getting a reply to my questions so I decided to set them up myself.
 
http://ipv6-proxies.com/ is the only site I know of that sells them, but I haven't tried them personally. I'm a bit intrigued as well because of the quantity that you can get for the price.
 
http://ipv6-proxies.com/ is the only site I know of that sells them, but I haven't tried them personally. I'm a bit intrigued as well because of the quantity that you can get for the price.

The low bandwidth limitations would be my first issue. I would burn thru their highest package in a day.
 
Can anyone foresee any major benefit or gain to having IPV6 proxies as opposed to IPV4 or socks proxies? While this might not have been intended as a sales inquiry thread, if a market opens up I'd be happy to jump on the supplier bandwagon.
 
I'm not sure if there'd be a huge market at the moment, but as more sites become functional with it there probably will be. I think the problem now is a lot of sites don't support it, so I don't know just how useful they'd be right now to most people. I would think that as more and more sites work with them though that will change.
 
Hi,

We discontinued the product due to less demand. We were too early for the market when we started offering this two years back. But the market will sure pick up in the future as more sites start supporting ipv6.
 
The handful websites supporting IPv6 is indeed the major reason why noone is offering this solution yet but I believe it has huge advantages over IPv4, availbility of virgin IP's being one. Hopefully more websites will start using IPv6 soon.
 
I really don't think IPv6 proxies are needed right now, globally IPv6 utilization is only around 5% and all those sites have an IPv4 address. The sites that only have an IPv6 address are probably less than 1% and I can't see why you would want to post to them. All IPv6 sites have an IPv4 address right now and it will be years until the net starts waning completely off IPv4s.

Reference: https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption
 
So the main reason I can see for using IPv6 proxies is price.

Although I run in to errors trying to buy them from ipv6proxies.com (and what looks like their sister site), "if" their prices are in the ballpark of what others would charge ($10/1000,...) then that's much cheaper than elite IPv4 proxies. :cool:

Also I would think that since Google search supports IPv6, using them for general purpose Google scraping would be great.
In fact, I'm trying to get a work-flow setup where I use lots of IPv6 in Scrapebox for my scraping, then pass results into GSA for posting/verifying using fewer (but more expensive) IPv4s.

But alas, all my attempts to find a provider of IPv6 proxies have failed.

So if anyone here has found a legit provider for IPv6 AND completed a recent purchase, please do post back
 
I'm trying to get a work-flow setup where I use lots of IPv6 in Scrapebox for my scraping

Do you use IPv6 proxies in scrapebox now? I was told by its developers this is not possible at the moment.

We plan to offer IPv6 proxies soon. Just because IPv6 addresses are abundant doesn't mean you should use thousands of IPv6 proxies for SEO work if you don't need that many, one single IPv6 addresses can visit a site just like an IPv4 address. Single IPv6 addresses and subnets can be blocked by websites just like IPv4 addresses can. That is why we will offer IPv6 proxies just like our IPv4 proxies with same amount of bandwidth behind them on multiple subnets. We will only offer dedicated IPv6 proxies at first and the prices will be somewhere in between our IPv4 dedicated and shared proxies.
 
Just keep in mind that on IPv6, sites block the whole /64 subnet, not single IPs. So you need 1 per /64.
 
Just keep in mind that on IPv6, sites block the whole /64 subnet, not single IPs. So you need 1 per /64.

If a site blocks a /64 they could be blocking millions of potential visitors since a /64 can have billions or trillions of IPv6 addresses in it. so I think this will be slightly less common than sites blocking /24s for IPv4 proxies, and IPv4 proxies don't use 1 per /24 even so that wouldn't be the case with IPv6 proxies. We plan to have around 500 single IPv6 proxies per unique subnet.
 
If a site blocks a /64 they could be blocking millions of potential visitors since a /64 can have billions or trillions of IPv6 addresses in it

No. One /64 is the minimum quantity a SINGLE customer should get according the spec. So the sites are correct to block /64. It amazes me that you were going to "offer IPv6 proxies" and you were not aware of that.
 
No. One /64 is the minimum quantity a SINGLE customer should get according the spec. So the sites are correct to block /64. It amazes me that you were going to "offer IPv6 proxies" and you were not aware of that.


We will be offering IPv6 this is guaranteed, and it will be soon.


I'm not sure what spec or which customers you're referring to, we offer a /112 with our VPSs to our customers. A /64 is considered a Single End-user LAN but that doesn't mean you can't chop it up into several smaller parts and give those parts out for various usage.


I didn't say that sites won't block a /64, they surely will, they just might be more reluctant when they consider the vast amounts of IPs they will be blocking, and saying that you would only have 1 proxy per /64 with IPv6 is like saying you would only have one proxy per /24 with IPv4 and this isn't the case. You can use a lot less of the /64 for proxies of course but not just one.
 
I'm not sure what spec or which customers you're referring to

https://tools.ietf.org/html/rfc6177

Hence, it is strongly intended that even home sites be given multiple subnets worth of space, by default. Hence, this document still recommends giving home sites significantly more than a single /64, but does not recommend that every home site be given a /48 either.

Google and everyone else is absolutely right treating a /64 as 1 SINGLE entity.

, we offer a /112 with our VPSs to our customers.

You're not the only one doing this, I'm not singling you out, it's more of an awareness post. The confusion steps from the misunderstanding the IPv6 is a "bigger IPv4". Not really, it's a different address scheme in which the concept of "a single IP" is almost meaningless in comparison to the IPv4 IP. Considering that many hosts do it wrong, you can imagine how many end-users get it ... right.

A /64 is considered a Single End-user LAN but that doesn't mean you can't chop it up into several smaller parts and give those parts out for various usage.

You can. I've also seen hosts give 1 single IPv6 per VPS. The problem is that just because you can, doesn't mean you're doing it right. And right in this case is not about some abstract idea of correctness, no. It is a very practical thing.

For example, if your clients are sharing a /64 and only one of them has a mail server that spams, all your clients mail servers get blocked for spam. Similarly with proxies. If a single customer abuses 1 IP inside the /64, all your other customers in that subnet get blocked as well.

So, a host is punishing totally innocent clients in favor of the abuser. And for no real reason at all!

The solution is simple - give /64 per server (vps), as the rfc recommends. This will make sure your clients don't get banned because of a bad neighbor, because the big guys follow the rfc.

I didn't say that sites won't block a /64, they surely will, they just might be more reluctant when they consider the vast amounts of IPs they will be blocking, and saying that you would only have 1 proxy per /64 with IPv6 is like saying you would only have one proxy per /24 with IPv4 and this isn't the case. You can use a lot less of the /64 for proxies of course but not just one.

As you understand from above, there is absolutely no reason for "reluctance" of banning per /64. Actually there are probably "justified" in blocking per /60 or /48 in the future. But for now, /64 is the name of the game.
 
Thank you for the info, it is good to communicate with someone knowledgable. I do understand the idea behind a /64, and as far as us cutting one /64 up in to pieces, to protect our multiple customers using it we have a terms and conditions and acceptable use policy you must agree to before using our services. You can also split up a /24 of IPv4 addresses and give them out to several customers and one person using one of those IPs on that /24 can ruin it for everyone the same way as a /64 if the addresses are not monitored correctly.

The bottom line with IPv6 just like IPv4 is that one machine can browse the web with one IPv6 address, AT&T in the US gives out only one IPv6 address to their customers per service to connect to the web. With this being the case it would still be necessary to use multiple IPs from one /64 of IPv6 addresses for proxies. This is a new thing, when we have IPv6 proxies available to the public we'll test things out see how it goes and then adjust accordingly. Thanks again for taking the time.
 
Last edited:
Back
Top