NY unemployment login issues - social security and PIN number not matching in system

yea this happens all the time with their crappy website. try clearing ur cookies and cache, sometimes that fixes it. or try a different browser. the system gets glitchy especially on sunday nights when everyone is certifying

I had this exact issue last month. The problem could be one of three things: 1. System maintenance - NYSDOL often does updates on Thursdays that can cause temporary login issues 2. Account security lock - after several failed attempts, your account gets a 24-hour security hold 3. PIN reset requirement - every 90 days the system requires a PIN update Try waiting a few hours and then selecting the "Forgot PIN" option. In my experience, you'll need to create a new PIN that's different from your last three. Make sure you're also entering your SSN without dashes.

OMG I'M HAVING THE SAME PROBLEM RIGHT NOW!!! I've been trying since 7am!!! What happens if we miss our certification window because their stupid system isn't working?? Will they backdate it?? I'm literally panicking because I can't afford to miss a payment. Has anyone gotten through to an actual person about this??

I experienced something similar and found that the NY unemployment system sometimes has these authentication glitches. What finally worked for me was using Claimyr to connect with an actual agent who fixed my account access on the spot. I tried for 3 days on my own before using their service at claimyr.com - they got me connected to an agent in about 20 minutes who reset something on their end. They have a video showing how it works: https://youtu.be/Rdqa1gKtxuE The agent mentioned that sometimes their system flags accounts for verification when there are multiple login attempts from different devices or locations.

This happened to me a few weeks back. Turned out I was typing my social wrong without realizing it! I was putting 6 instead of 0 (they're right next to each other on the keyboard). Double check that you're not making a typo - I felt so dumb when I realized what I was doing wrong lol

I work in IT and I've seen this issue come up with several government websites. There are a few technical things you can try: 1. Try incognito/private browsing mode 2. Disable any browser extensions you have 3. Try a completely different device if possible 4. Check if your keyboard has num lock enabled if you're using the numeric keypad The NYS unemployment site uses some outdated security protocols that don't play nice with certain browsers and settings. Also, their servers get overloaded during high traffic periods, especially Sunday evenings and Monday mornings.

Just wanted to update everyone - I had this EXACT same problem and finally got it resolved. The issue was that my account had been flagged for identity verification, even though I'd already completed that process. I had to call them, and after being on hold forever, the rep told me there was a note on my account requiring additional verification. Once they removed it, I could log in again immediately. The weird part was there was NOTHING indicating this on the website - it just kept saying my info didn't match.

did u try logging in with ur ny.gov ID instead? sometimes that works when the direct login fails. click the green ny.gov button instead of the regular login.

UPDATE: I finally got in! For anyone having the same issue - it wasn't anything I was doing wrong. I called using the Claimyr service someone mentioned above, got through to an agent in about 15 minutes, and they confirmed my account had been flagged for "additional security verification" but there was no notification sent to me about it. The agent was able to clear it immediately and I could log in right after. Apparently this is happening to quite a few accounts lately. Thanks everyone for your help!

So glad you got it resolved! This is really helpful info for everyone else dealing with the same issue. It's ridiculous that they're flagging accounts for "additional security verification" without sending any notification - how are we supposed to know that's what's happening? The system just makes it look like we're entering wrong info. Definitely saving this thread for future reference in case it happens to me too. Thanks for updating us with the solution!

This whole thread has been incredibly helpful! I've been having the exact same login issue for the past two days and was getting so frustrated thinking I was entering my info wrong. After reading everyone's experiences, especially Connor's update about the account being flagged for "additional security verification" with no notification, I'm pretty sure that's what's happening to me too. It's really disappointing that NY's unemployment system has such poor communication - they should at least tell you when your account is flagged instead of just giving a generic "information doesn't match" error. Going to try calling tomorrow morning, and if that doesn't work, I'll look into the Claimyr service. Thanks everyone for sharing your solutions!

Just joined this community and I'm so grateful to have found this thread! I've been dealing with the exact same login issue for the past 3 days - my SSN and PIN were working fine last week for my weekly certification, but now I keep getting that dreaded "information doesn't match" error. Reading through everyone's experiences has been such a huge relief because I was honestly starting to think I was going crazy or somehow forgetting my own information! The fact that Connor's issue turned out to be an invisible account flag for "additional security verification" with absolutely no notification from the system is both incredibly helpful and completely maddening. It's unacceptable that NY's unemployment system can silently flag accounts and leave people thinking they're entering wrong information when the real issue is on their end. I'm definitely going to try calling at 8:05 AM tomorrow morning as Amina suggested and will specifically ask about any verification flags or holds on my account. If that doesn't work quickly, I might look into the Claimyr service that helped Connor get through to someone faster. Thank you so much to everyone who shared their experiences and solutions - this community has been more helpful than any official resources I've found! Will update if I discover anything new in my troubleshooting journey.