My last comment was that I opened a ticket to Blizzard in order to get them to fix the issue. The problem is not with playing any of their games, but accessing the battle.net website with a regular browser.
My investigations led me to believe that this situation started around June 10th, and that this is impacting Asian IPs, mostly from Japan. One could think this is some kind of anti-cheater measures, that some IPs get banned from accessing the Blizzard games, but this really doesn’t impact the game itself, just the website. It’s also worth mentioning that I do have a battle.net account, but only played with it once a long time ago, so there would be no reason for my IP to be banned, and even less for the entire range of IPs owned by my provider.
As a matter of fact, I ended up buying the game through a VPN connection, and I could play the game fine from my regular connection, so there’s absolutely no problem here.
The symptom is an impossibility to connect to http://battle.net, with your browser spitting out a message in the form “Connection Refused”.
Some people are in the same situation as me, and managed to post about their issues on the Battle.net forums, through the use of proxies or VPNs:
If you stumble upon this page, most likely you cannot read these posts on battle.net (although google cache might be your friend, try the text version), so I am reproducing them here:
Although I can connect to battle.net by wow client or diablo3 client,
I always can’t connect to us.battle.net via web browser from my house.
If I access to us.battlnet via http proxy, As you see this post, I can access to us.battle.net by web browser.
What does this mean?
This means, my computer setting is not problem, ISP I am using also is not probrem.
Please see following “curl” command output from my house when I could not access to us.battle.net.
D:\>curl -v us.battle.net
* About to connect() to us.battle.net port 80 (#0)
* Trying 220.127.116.11… Connection refused
* couldn’t connect to host
* Closing connection #0
curl: (7) couldn’t connect to host
Dear blizzard, please forward above log to some proper network engineer.
An engineer who has network knowledge will understand this means,,
- DNS was ok because I could resolve us.battle.net as 18.104.22.168
- “Reset” packet was returned. When my computer sent “SYN” packet to us.battle.net, us.battle.net returned “RST” packet.
- This is not a timeout. Any firewall didn’t drop my TCP/IP packet.
This means, I can touch us.battle.net via TCP/IP but someone closed my connection by sending “RST” packet.
Usually IDS or WAF do this kind of behavior. So I guess blizzard’s IDS or WAF rejected my connection. This is a problem.
Thank you for reading,
Im connecting to my friend thru VPN in Canada right now to get access to the forums, the problem I have is that I live in Tokyo, Japan and I can’t get on the battle net website, it says connection refused. This is happening to 3 of my other friends in Japan and if you do a search on google on “can’t connect to battle.net from Japan” you’ll see massive thread on people who are also complaining about the same thing. This is the 11th day I’m playing diablo3 without being able to get on the website. We can play the game fine we just can’t access the website.
We did tracert to battle.net, the trace shows that our connection hops to 15 different locations until it arrives to att.net which is battle net west the we would get our connection refused. This means our connection is fine and our isp is not blocking blizzard. I believe blizzard is massively banning forum ips in suspection to rmt activities, how ever this is affecting us normal players too.
Please don’t leave stupid comments like “did you check your anti virus program or browser settings to see if it’s blocking?”. As im not an idiot. Reply if you know what you are talking about. I have an i got an iPad, iPhone, laptop and desktop to tell you that it’s not our software setup that’s causing this. This is happening Asia wide.
I also tried setting my DNs open DNs google and that’s no go.
Finally, here’s what was added:
I am typing this from the office and do not have access to my home machine here, but I did run a traceroute yesterday (although it is us.battle.net, not us.logon.battle.net, I will try this one tonight), which I am attaching as a txt file
I do not think there is a problem in the route.
As far as contacting my ISP, I have done that, which is why I am contacting you. They are 99% convinced that the problem is not on their end, but that battle.net is blocking some IPs. In particular, they told me they are not blocking your website on their end, and they couldn’t access battle.net from their test machines either.
Doing further research, a wget on my machine gives me this:
–2012-06-17 11:09:58– http://us.battle.net/
Resolving us.battle.net… 22.214.171.124
Connecting to us.battle.net|126.96.36.199|:80… failed: Connection refused.
wget other pages such as google works fine. wget on another machine on another network, works fine.
Finally, you have to take into account that my problem is not isolated. Several people in Japan are reporting the same issue.
It is very possible that Blizzard is not fully aware of the impact of this problem, simply because people who have the problem have no easy way to contact you (since they cannot access the site or the contact form). Not everybody can have access to a VPN like I do.
More people with the same issue:
People with the issue in Japan:
This last link is in Japanese, if you don’t speak Japanese, this is a thread with dozens of people complaining that they cannot access battle.net since sometime in June. Some people say it might be ipv6 related (again, a problem on Blizzard’s end rather than on the ISP, since I verified my ipv6/ipv4 compatibility with my ISP)
I could buy Diablo 3 from a VPN, and I can play it fine on my home network. So the issue is only with the website.
I’m hoping the length and details in my reply will help you find out a solution, and understand that I am not a regular user with a typical connection problem. There is a problem somewhere with your website, and you are preventing hundreds of people from even buying your game.
Hopefully there will be some move on Blizzard’s end soon enough