01/04 - Thriving Thursday!

This seems to be the new normal, unless we can convince Amazon everything isn't running fine.

 

is it a throttling thing? are the 12 people left on mturk using that much bandwidth?

 

I don't know what they're doing. Intentionally killing MTurk?

This is beyond wrong, serious disinfo:
https://requester.mturk.com/status/

Maybe if enough people call them and speak to an actual person, they'll finally get a clue.

 

mine's okay. my mturk.

 

I'm hamming a batch. only getting that error every once in a while, rough guess 1 out of every ten page loads.

 

I miss the days when everything ran smoothly, and we could max out our HITs.
Why has that changed?

 

I got 3,800 HITs a day for the past two weeks. Yesterday I did about 200. Now I can't get any to submit without 503ing. Lame.

 

I'm probably doing the same batch and it was messing up on every hit for me.


also. hai!

 

HAI!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I backed up and deleted literally every extension I had installed to try to avoid this problem for as long as possible. so now I have no idea how much or how little money I'm actually making, but I can do hits

 

Sucks that this is still happening. I got an email from them yesterday saying they were trying to troubleshoot it but it doesn't seem any better.

"Hello,

Thank you for providing us info about the current issue.

We are troubleshooting the 503 errors you are experiencing. To help us troubleshoot the issue, could you provide us the following information:

- What browser and browser version are you using?
- What time did the issue occur?
- Send a screenshot of the issue.

Thank you for your patience and understanding."

 

I'm using chrome and I haven't closed and reopened the browser for at least a few days, maybe not since before Christmas. the browser says "Relaunch to update." could a chrome update be conflicting with mturk and that's why the error is happening gradually to people?

 

I tried in Edge and Firefox as well, all running with no extensions or anything and still just 503'd over and over, or 3-5 seconds on the network waterfall of "Waiting for Server Response" before anything starts to load.

 

The best part is when both happen, you get the 3-5 seconds of "Waiting for Server Response" and then it 503s. Lol.

 

I have submitted 295 hits total this year. doesn't include a few expireds and returns. maybe there is a threshold that is making mturk freak out when people go over it?

 

as far as I can remember, I think I've only done hits for two requesters so far in jan. I have accepted and returned hits from maybe 1-4 other requesters. idk if that helps.

also I tend to turk slower than other people, including on batches. so there is probably a lot more space between page requests when I turk compared to other people doing the same hits as me.

 

also I have turked from two libraries in two towns and a house all in the last two days. sorry that's all I can think of that could be different rn.

 

I've only submitted a few hits this week. I got a 503 this morning just trying to log into my dash with nothing running. I believe this is an Amazon server issue and not something we can control or avoid on our end.

 

Yeah absolutely. Just getting logged in, or checking payments, or really any other part of the dashboard is affected by this problem as well.

 

Tell them to put it all back the way it was a couple years ago. This isn't new, just getting worse.
Do they even know what 503 errors are?
This isn't on our end, it's on them.

A 503 Service Unavailable Error is an HTTP response status code that indicates your web server operates properly, but it can't handle a request at the moment.