wikass zabił Mythrax the Unraveler (Normal Uldir) po raz 2.     
kuturin zdobył 7th Legionnaire's Cuffs.     
Nikandra spełnił kryterium Loot 200,000 gold osiągnięcia Got My Mind On My Money.     
Tooly zdobył Fairweather Helm.     
Muattin zdobył osiągnięcie The Dirty Five.     
Yoozku zdobył Parrotfeather Cloak.     
Mlody89 zdobył Royal Apothecary Drape.     
Weakness zabił Dazar, The First King (Mythic King's Rest) po raz 6.     
liq spełnił kryterium osiągnięcia Saving for a Rainy Day.     
Osiol spełnił kryterium osiągnięcia Saving for a Rainy Day.     
Wuntu zabił Zek'voz, Herald of N'zoth (Heroic Uldir) po raz 1.     
Olsa zabił Vectis (Heroic Uldir) po raz 6.     
Sarenus spełnił kryterium osiągnięcia Saving for a Rainy Day.     
kajtasus zdobył osiągnięcie Come Sail Away.     
ossir spełnił kryterium osiągnięcia Saving for a Rainy Day.     
mcpablo spełnił kryterium Alliance players slain. osiągnięcia Frontline Slayer.     
Emmm zabił Taloc (Heroic Uldir) po raz 17.     
AsaGorth spełnił kryterium Big-Mouth Clam osiągnięcia The Oceanographer.     

Timeout Issues Affecting all Sites

blizz -> wysłany:
So, I sent an email to [email protected] 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 ( 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 API's timing out. There are also a bunch of people reporting issues on our forums: auctiondb-not-updating.htm

Here's an example of a curl timeout I am getting from an authenticated request:
* About to connect() to port 80 (#0)
* Trying * connected
* Connected to ( port 80 (#0)
> GET /api/wow/auction/data/Aegwynn? HTTP/1.1
Accept: */*
Accept-Encoding: deflate, gzip
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
* About to connect() to port 80 (#0)
* Trying * 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 in a browser (or these forums, or any other website), my browser will be unable to and eventually time out.

EDIT 1/11 4pm PST:

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.
blizz -> wysłany:
Timeouts are very odd to see. Can you guys let me know what ISP's and locations you are seeing timeouts from (city level is fine, don't need specifics). I'm also asking some server admins if they see anything on their end that could be causing this.
blizz -> wysłany:
The server admins said that until yesterday (and hearing about this) there was some DDos prevention migration stuff in place in front of our internet connection, but this has been removed now. Let me know if this continues or if that was it.

blizz -> wysłany:
I passed all of this along to the server team, will keep looking into it :-(
blizz -> wysłany:
I've downloaded this app and get the same timeouts that you guys do despite being able to hit the auction api urls's directly with no issues. My server team can't find any evidence that requests are being blocked at a level above us (our ISPs) but at the same time our logs are showing nothing about timeouts or errors.

When auction data is down or delayed we often get a huge amount of emails from other sites (Undermine journal, etc) and I haven't received any emails from any of them. I'm working with the TSM authors to try and figure this out... but please be aware we do care about this issue, but are no having no luck duplicating any api timeouts except via this app.
blizz -> wysłany:
TSM is looking into this from their end now since they also do not see any timeouts from their servers (They did during the DDOSing events two weeks ago but haven't seen anything since). It looks like they will be able to solve this with an app update. He'll let me know if they see any more issues from the API.
blizz -> wysłany:
01/31/2014 10:33 AMPosted by Yocoliah
I just noticed actual timeouts while querying the AH API for the first time starting less than an hour ago (I got a succesfull download 45 minutes ago still). Did something change in the past hour?

Edit: some more info: My last succesful download was at 17:46 UTC for Stormrage(EU). A download started at 17:57 UTC for Arathor(EU) failed because the data downloaded was malformed, another try for the same 10 minutes later hit a timeout (after 11 minutes). Note that the download for the initial key file for the AH data works, it is the big download with actual AH data that times out.

Was this within the TSM app or are you downloading it via curl/wget or something else?
blizz -> wysłany:
01/31/2014 11:18 AMPosted by Yocoliah
This was with my own homebrew application (Written in C#, so using the .NET infrastructure for networking). I just checked my computer at the office (using a different network and ISP), and there the exact same application seems to be still running without any trouble.

What I just observed here at home is that a transfer did complete, but only delivered the first 700k of the file, then got interrupted. I'll see if a computer and router reboot helps

I have never used C# so excuse any obvious questions, but is there some sort of system level limit on downloads, or timeout settings that can be played with? Could it just have a problem downloading the ~5-10 meg file?
blizz -> wysłany:
It might also be telling that when I google I immediate get links to wow and d3 posts from the past 2 years dealing with connection issues (to the games)... we might be hitting the same thing Yocoliah.