08/31 - Laundry Saturday

Can anyone access the amazon payments page? Its shown me an error all day.

 

I'm not going to jinx myself by looking.
Amazon needs to disconnect this from our MTurk accounts since they are no longer used.

If you haven't already done this, it's the next step to resolving this issue:
https://blog.turkopticon.net/?page_id=653

 

this one statement is so informative thank you. I emailed TO back in response to a few questions they emailed me and I told them thank you so much too. we would be so lost without those people!

 

I am optimistic this will be resolved with the help of Turkopticon. I really don't care about Amazon investors and all their drama. I just want Amazon to fix everyone's MTurk accounts since this is on them, not us. It's clearly a snafu in their system.

 

This is from Reddit:

A little More Insight On What Might Have Happened With Mturk

So I know we've all been stressed out about this suspension fiasco, and we are all doing what we can to see that this issue is fixed as soon as it can. The issue has been bugging me for days, so I decided to ask a friend of mine that is an SRE (Site Reliability Engineer) for Chase bank.

I explained the situation to him, and he said it sounds like a system failure at worst, and a system glitch at best. He said there's no way the suspensions are purposeful if it's a wave of accounts over the course of days. He said it's likely people will continue to get suspended until the situation is fixed. He experienced something similar on the job which compromised over a million bank accounts over the course of three weeks.

So what caused the issue? He thinks there is a 90% chance that a recent update or maintenance on either MTurk or Amazon Payments caused an unexpected glitch, leading to mass suspensions. If he were a betting man, he would bet Mturk had an update over the weekend. Payment sites are rarely ever updated unless there is a serious problem.

He also said there is a 5% chance Amazon Payments might have implemented stricter compliance or security measures that inadvertently affected many accounts. He still thinks it's unlikely because most site owners have a "if it ain't broke don't fix it" mentality to payment sites but doesn't want to rule it out.

The remaining 5% chance is that all those accounts were legitimately flagged and suspended.

The solution? He said we'll have to talk to support. The poor guy assumed these sites weren't automated, so I had to explain that both sites are literally fully automated, and any human support isn't even in the country. His response was priceless.

" Lazy, corner cutting bums."

If that's the case we will have to go above support all together and start emailing people with some pull. The problem with that is we will need to get both Mturk and Payments to get their heads out of their asses and work together on the issue.

https://www.reddit.com/r/mturk/comments/1f62hmy/a_little_more_insight_on_what_might_have_happened/

 

this is what I suspected from the beginning. I think they tried to fix something and knocked a bunch of other stuff down by mistake.

also, when we can turk again, if TO does another fundraiser I am ordering a TO fundraiser pizza. if they do that again.

 

I think it's BOTH (Amazon Payments and MTurk) causing it whatever "it" is.
BOTH have disabled parts and/or errors on their sites related to the banking section.

It's nice to hear someone else's perspective and I appreciate his expertise and insight.

 

Does this mean MTurk is finally trying to fix the problem? Hopefully it is resolved for everyone soon.

 

Yes, I can access it, but it's not very helpful. I can't verify my bank account, the add a bank account button is diabled, and requesting a callback gives me an error.

 

Thanks for posting that. I didn't know it existed, but I found the location of it.

 

I don't think they're trying to do anything for us yet. Everything with AWS is on automatic AI pilot. The few people who work there seem to be the equivalent of the Stepford Wives.

 

Here's hoping, but also their definition of working vs. not working is drastically skewed in comparison to us.

 

I just found this, don't know if relevant -

AWS Identity and Access Management (Global) - August 29, 2024

https://health.aws.amazon.com/healt...E/AWS_IAM_OPERATIONAL_ISSUE_C9750_3CF4B9D9C39

 

I think so. The health status for the server issue showed it was fixed on 8/30.