Timeout Issues Affecting all Battle.net Sites

1 Undead Rogue
0
So, I sent an email to api-support@battle.net last Tuesday regarding some timeout issues I was having on a development server (no response to that email yet), but it appears to have become much more widespread since then and is now affecting users of the TradeSkillMaster Application (http://tradeskillmaster.com/tsm_app). For some perspective, by our estimates, there are about 10k unique (and actively running) installs of this application.

We've had many people come into our IRC channel saying they are seeing issues with the application which we've determined to be related to one of the battle.net API's timing out. There are also a bunch of people reporting issues on our forums:
http://stormspire.net/official-tradeskillmaster-development-forum/13289-tsm-desktop-app- auctiondb-not-updating.htm
http://stormspire.net/official-tradeskillmaster-development-forum/13301-setup-wont-allow-me-pick-sever.html

Here's an example of a curl timeout I am getting from an authenticated request:
URL: http://us.battle.net/api/wow/auction/data/Aegwynn?
* About to connect() to us.battle.net port 80 (#0)
* Trying 12.129.242.40... * connected
* Connected to us.battle.net (12.129.242.40) port 80 (#0)
> GET /api/wow/auction/data/Aegwynn? HTTP/1.1
Accept: */*
Accept-Encoding: deflate, gzip
Host: us.battle.net
Date: Tue, 07 Jan 2014 8:51:52 UTC

Authorization: BNET <SNIP>

* Operation timed out after 10001 milliseconds with 0 bytes received
* Closing connection #0
http Code: 0
URL: http://us.battle.net/api/wow/auction/data/Aegwynn?
* About to connect() to us.battle.net port 80 (#0)
* Trying 12.129.242.40... * Timeout
* connect() timed out!
* Closing connection #0
http Code: 0


It seems that if I retry urls which are timing out a few times and then stop whatever program is making these requests, I will still be consistently unable to connect for some time afterwards (usually around 10 minutes). Even if I try connection to http://us.battle.net/en in a browser (or these forums, or any other us.battle.net website), my browser will be unable to and eventually time out.

EDIT 1/11 4pm PST:
http://dev.tradeskillmaster.com/timeouts.php

That page will display how many people have run into this issue that we've detected. It is as of r209 of the TSM application that we are tracking this issue, which was just released ~1 hour ago.
Edited by Tsmsapu on 1/11/2014 4:09 PM PST
Reply Quote
90 Human Warlock
12265
TSM User here to confirm I'm getting timeout issues as well same as above poster.
Reply Quote
90 Pandaren Shaman
13170
I have received same timeout from TSM.
Reply Quote
90 Blood Elf Warlock
10565
Same problem.
Reply Quote
90 Blood Elf Paladin
16660
Patient Zero checking in, timing out when scanning for API update.
Reply Quote
90 Undead Mage
13000
Timing out when scanning for API update as well.
Reply Quote
90 Undead Priest
10585
I just received the timeout error as well.
Reply Quote
1 Undead Rogue
0
http://dev.tradeskillmaster.com/timeouts.php

That page will display how many people have run into this issue that we've detected. It is as of r209 of the TSM application that we are tracking this issue, which was just released ~1 hour ago.
Reply Quote
90 Draenei Death Knight
8005
received a timeout
Reply Quote
90 Pandaren Mage
7245
received a timeout

US-Turalyon hasn't updated in more than 2 hours
US-Bladefist seems fine
Edited by Shurething on 1/11/2014 4:26 PM PST
Reply Quote
90 Tauren Priest
9785
Same here. US-Azralon
Reply Quote
90 Night Elf Rogue
10715
Timeout - US-WrA
Reply Quote
90 Human Warrior
11960
Time out issues as well
Reply Quote
90 Tauren Druid
15215
I am also experiencing timeouts
Reply Quote
90 Undead Mage
14035
I started getting timeouts on my end a few days ago as well.

I (think) I solved it by slowing down my request rate, but it was the same problem, "connect() timed out!"

I have been running at my old request rate with no issues for months, so something must have changed on the API side.
Edited by Chaud on 1/11/2014 5:19 PM PST
Reply Quote
1 Undead Rogue
0
I started getting timeouts on my end a few days ago as well.

I (think) I solved it by slowing down my request rate, but it was the same problem, "connect() timed out!"

I have been running at my old request rate with no issues for months, so something must have changed on the API side.


We just tried with a 1 second sleep (plus processing time on the auction data) between any http request, and still hit timeouts.

Last weekend it was only happening from one IP address, but we could proxy to another one and it would work just fine. That doesn't seem to help anymore though.
Reply Quote
I started getting timeouts a few hours ago as well.
Reply Quote
90 Human Priest
8265
I had the same issue a little while ago.
Reply Quote
90 Gnome Rogue
TRI
3230
Just had that here too
Reply Quote
4 Worgen Druid
0
TSM user confirming timeout issue.
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]