CARE CODE: 205.2 [LU003] message

same issue here - been happening since 5/27/20.

Same issue - getting VERY frustrated!

Just talked to AT&T Again, they basically said there was nothing I can do and I have to wait 24 hours from the last failed attempt for it to unlock itself. Grrrr.

I am having the SAME problem and have been for the last 2 weeks. I called and they told me there was nothing they could do either just wait 24 hrs and try again, NOPE didn't work AGAIN. I'm so frustrated and can't not seem to get to anyone on the phone that can actually help

I'm having the same issue and error code. Just started this weekend for absolutely no reason. This is something ATT has done!!

I opened a ticket where they couldn't find an issue and eventually got a generic email saying 'we couldn't find any issue', and they basically closed out the ticket. Yet I still can't get in through a browser.

Let us look into this for you, @bwells27.

So that we can get started, please provide your email address, name and best contact number.
Looking forward to working with you.

**For your security, this thread is now private. Only the original poster will be able to access and post on this thread.**

Aminah, AT&T Community Specialist

I am following this as well...I have been unable to access email on a desktop but I can access through my iOS device. Does this have anything to do with 'sbdglobal.net' email addresses??? I heard that there may be something going on with email addresses ending in sbcglobal.net.

Can't access on Chrome, Safari or Edge. So it's not my user ID or password, but the error message always says "There have been too many failed sign in attempts. To get help, please visit att.com/myatt and use Forgot user ID or Forgot password links.

CARE CODE: 205.2 [LU003]"

Hi @Sheman, we are happy to help. 

I've reset my password several times and it appears to go through, yet I still get the password error message "There have been too many failed sign in attempts. To get help, please visit att.com/myatt and use Forgot user ID or Forgot password links. CARE CODE: 205.2 [LU003]" I truly think there is a network or server issue that is not related to everyone's failed password attempts. Everyone above is seeing the same issue.

Did you clear out your cache etc first?

Use a different browser to try currently.att.yahoo and try the routine again. Sorry it didn’t work for you.

I also get this error message. It's not a password problem. It doesn't matter what browser I use or whether or not the cache has been cleared. Deleted Chrome and Firefox browsers and reinstalled. I can log in on smart phone email app but not through a web browser. Sounds like a problem that has just developed.

I agree, I have used multiple browsers, cleared the cache, changed my password multiple times.  NO LUCK!  Thank God I can still access on my phone!  @ATTHelp please advise!

This is absolutely ridiculous!!!  It has been over a month with multiple LENGTHY conversations with online chat to no avail!!  AT&T should be ashamed!!

I too have not had access to my email on a desktop for about 5 weeks now. Multiple browsers, different laptops, clearing cache, changing passwords, nothing helps. Apparently they do not monitor these comments and just tell us to start over contacting customer support. Again. And actually I worked with one over 60 minutes, only to get transferred off and then I got disconnected!

This is ridiculous. I'm having the same problem with my email. Can access via iOS devices, but not from laptop/desktop/chromebook. 

In reading all these posts, it seems like AT&T is really dropping the ball on this.
WHAT is the issue ... and, more importantly, WHAT is the FIX?? 

FIX IT!  

I have been working on this for over a week.  So the suggestion to "wait an hour & try again" ... "wait 6 hrs & try again" ... "wait 24 hrs & try again" ........ are clearly not the answer.  

When I see how many people are posting to these forums (several similar forums out there), this is undoubtedly an AT&T issue and not something that we all are doing 'wrong'.  If dozens of people are posting about this, you can assume that hundreds are having the issue & not posting.