Back to New York Unemployment

KaiEsmeralda

NYSDOL unemployment site not working - anyone else locked out?

My weekly claim was due yesterday and the NYSDOL unemployment site not working issue is driving me absolutely insane. I log in fine, get to the weekly certification page, click submit and then it just... spins. Forever. No confirmation, no error message, nothing. I've tried Chrome, Firefox, even dusted off Edge. Cleared every cookie and cache file I could find. Same result every single time. Called the number on the site and have been on hold so long I've given up twice. I'm terrified my weekly claim is going to be marked late or skipped entirely because of a glitch on their end. Has anyone dealt with this? Did your payment still go through even when the site bugged out during submission?

Week 6 of my current claim and I hit this exact wall two weeks ago. The spin-of-death on submission is brutal. What ended up working for me was switching to a completely different network - I was on wifi and moved to mobile data, then the page actually submitted. Something about how their servers handle the session token gets weird on certain ISPs apparently.

0 coins

Trying the mobile data switch right now actually, hadn't even thought of that. My wifi is through one of the big cable providers so maybe that's the issue.

0 coins

My router was the culprit when this happened to me. Had to restart the whole thing and retry on a fresh session. Annoying but it got me through.

0 coins

Their servers do this every few months it feels like. The ISP thing is real - I've seen it come up before on here.

0 coins

Three letters into my appeal process when their portal went haywire on me last spring. Took me days to realize my submissions weren't going anywhere. The NYSDOL site has had recurring outages that never make it onto their official status page, which is infuriating. Check your Unemployment Services account inbox after any submission - if there's no confirmation message in there, it did not go through regardless of what the page showed you.

0 coins

Went into the inbox right now and there's nothing there from yesterday's attempt. So it definitely didn't process. This is such a mess.

0 coins

My inbox was empty too after mine froze - ended up having to call in my weekly claim instead. Didn't even know that was an option until I read it somewhere on here.

0 coins

They have a phone option for certifying weekly claims when the site is down. 1-888-209-8124 is the main line. The automated system can walk you through it.

0 coins

My fourth week in a row trying to reach someone at NYSDOL about a portal issue similar to this, and I finally got through to an actual agent using Claimyr - it waits on hold with NYSDOL for you so you end up talking to a live person instead of sitting there for three hours. claimyr.com has the signup and there's a video showing how it works at https://youtu.be/Rdqa1gKtxuE - honestly worth it when you're stressed about a missed weekly claim because of their own broken system.

0 coins

I've been burning through my lunch breaks every day trying to get through on that phone line. Might actually try this.

0 coins

My experience with their phone line lately has been disconnects after 45 minutes of hold. Anything that gets you past that nightmare sounds worth trying.

0 coins

My cousin went the Claimyr route when her adjudication dragged on for weeks and she said the agent she reached was actually helpful. Worth knowing about.

0 coins

Halfway through week 9 of my claim and I ran straight into this last Tuesday. Went into my Unemployment Services account the next morning and the weekly certification showed up as 'not filed' even though I had sat there watching it spin for twenty minutes. Filed it the next morning with no issue and my payment still processed on the normal schedule - the system seemed to have no record of my failed attempt so there was no duplicate submission problem or anything like that.

0 coins

That's genuinely reassuring to hear. So even if I file it a day late due to their outage it might not flag anything weird?

0 coins

Timing on weekly claims has a window, not a hard cutoff at a single minute. As long as you get it in within that filing week you're usually fine.

0 coins

My late filing one time triggered an adjudication issue though, so I'd still try to get it in ASAP just to be safe rather than assume it'll be fine.

0 coins

Day two of trying to reach anyone at NYSDOL by phone about this same portal problem. I had the wrong idea about how the weekly certification window worked for the longest time - I thought missing the first available day meant my claim was automatically disqualified. Turns out the window runs from Sunday through Saturday and you have that whole span to certify, not just the first day it opens. Still stressful when the site is down but at least it's not an instant disqualification if you're a day behind due to a technical issue on their end.

0 coins

My first claim I panicked so hard about the same thing. Knowing about the full week window would have saved me a lot of anxiety.

0 coins

Honestly didn't fully understand the window either, so thank you for spelling that out. At least I have a few more days to get this in.

0 coins

My rep at the career center mentioned that technical outages are documented and can sometimes be used to explain a late certification if it comes up in adjudication. Worth keeping a screenshot of any error or the spinning page just in case.

0 coins

Week 2 of my current claim and already hitting the site issues. I genuinely cannot believe that in 2025 this is still the state of the NYSDOL portal. It's not like they don't know it has problems - this comes up constantly. And their status page always says 'all systems operational' even when half the users can't submit their weekly claims. THEY KNOW. They just don't fix it.

0 coins

My frustration hit a peak when I realized I'd spent more time dealing with their broken site than it would have taken to just walk into an office. The status page thing is infuriating - Claimyr was what finally got me in front of an actual agent who could note the outage on my account so my claim wouldn't sit in limbo.

0 coins

My patience for this system is completely gone. How is it this hard to file for benefits you're entitled to.

0 coins

My anger at NYSDOL is constant but I try to document everything - screenshots, timestamps, the whole thing - because if anything goes into adjudication you want a paper trail showing the site was broken.

0 coins

My job search log certification went fine last week but the weekly claim portion timed out exactly the way you're describing. I had a theory it was related to the number of job search entries I was submitting at the same time - when I went back and submitted the job search log first, saved it, then went back to do the weekly claim separately, both went through without an issue.

0 coins

Worth trying that order. I did try to do everything at once so maybe splitting them up would help.

0 coins

My weekly certification and my job search activities were definitely loading slower when I tried to submit them on the same page at once. Separate submissions fixed it for me too.

0 coins

Their portal handles simultaneous data loads really poorly. The job search log is a known sluggish section. Always do it in steps.

0 coins

My third attempt at reaching NYSDOL this month actually got somewhere - tried Claimyr after seeing it mentioned somewhere and ended up speaking with an agent within the same day I'd given up on the phone line. The agent was able to flag my account to show I'd had a portal error on the submission date, which protected my claim from any late-filing issues. That kind of account notation is only something a live agent can add.

0 coins

An account notation protecting against late filing issues is exactly what I need right now. Might be worth getting that on record before my claim week closes.

0 coins

My agent did something similar for me during an adjudication delay - a note on the account genuinely seems to move things along or at least protect you.

0 coins

Agents have more ability to annotate claims than people realize. Definitely worth getting it documented if you can reach one.

0 coins

My browser was the problem in my case - I had an older version of Chrome and the NYSDOL portal apparently requires a more recent build. Updated the browser and the submission worked on the first try. Sounds obvious but I'd been blaming my ISP for weeks before I checked.

0 coins

Browser version hadn't even crossed my mind. Going to check that right now.

0 coins

Their portal has had issues with older browser versions before. Good catch - I'd add that Safari on older macOS has problems too.

0 coins

My Firefox ESR build was causing submission failures for a while. Standard release version fixed it.

0 coins

My second week into an extended claim when I realized I'd been confusing the portal timeout issue with an actual adjudication hold. I thought the spinning page meant my claim was under review. Turns out those are completely different things - an adjudication hold shows up explicitly in your Unemployment Services account under a separate status flag, while a portal timeout just means the page failed and nothing was submitted at all. If your account shows no pending certification and no adjudication flag, the site just failed quietly and you need to refile.

0 coins

Checked my account and there's no adjudication flag anywhere, so you're right - it's just a failed submission with no record. That's actually weirdly better news than I thought.

0 coins

My sister confused the same two things and waited three weeks thinking her claim was under review when it had never been filed at all. That was a rough realization.

0 coins

The portal failing silently with no error message is genuinely one of the worst design choices on that site. At least show the user something went wrong.

0 coins

My current claim started in January and I've now hit three separate stretches where the NYSDOL portal was unusable for anywhere from a few hours to a full day. The most reliable workaround I've found is to try very early in the morning - like 6am or before - before the daily traffic load hits. Their server capacity clearly can't handle peak usage and early morning submissions go through more consistently.

0 coins

Setting an alarm for early tomorrow morning to try this. I've been trying mid-morning which is probably the worst possible time.

0 coins

My early morning submissions have almost never failed. Afternoons and evenings are when the site bogs down badly.

0 coins

I've read that Tuesday and Wednesday midday are the absolute worst for NYSDOL portal load. Monday mornings right when the week opens are surprisingly okay.

0 coins

My first time dealing with an extended claim and I had no idea the site even had a phone backup option until it went down on me. 1-888-209-8124 has an automated system that walks you through weekly certification over the phone, asks you the same questions as the online form. I completed mine that way during an outage and the payment came through on the exact same schedule as it would have online.

0 coins

Trying this right now honestly. If it goes through on the phone that solves the immediate problem while I figure out the site issue.

0 coins

My first phone certification felt weird because I kept expecting it to fail but it went through perfectly. The automated system is actually pretty smooth.

0 coins

Why do they not advertise this option more prominently. I've been using this system for months and didn't know you could certify by phone.

0 coins

My IT background makes me notice things others might not - the NYSDOL portal runs on a session management system that times out aggressively. If you've been logged in for more than about 15-20 minutes without active page changes, your session quietly expires and any submission after that point goes nowhere even though you're still visually on the page. Log out completely, log back in fresh, and submit your weekly claim as the very first thing you do before navigating anywhere else in the portal.

0 coins

That would explain everything. I had been poking around my payment history before trying to certify. Fresh session it is.

0 coins

My session timeout was absolutely the issue in my case too. The page doesn't warn you that you've been timed out, it just silently fails on submit.

0 coins

This is probably the most useful technical explanation I've seen on this board. Aggressive session timeouts plus no timeout warning plus silent submission failure is a genuinely terrible combination.

0 coins

Fresh login, do the certification first before anything else - pinning this in my brain for every future claim week.

0 coins

My certification for this week just went through about an hour ago after three failed attempts over two days. What finally worked: used an incognito/private browser window, went straight to the certification page without visiting any other part of the site, and submitted within about five minutes of opening the browser. No spinning, no timeout, confirmation message appeared immediately.

0 coins

Incognito window is my next thing to try before I resort to the phone certification. Thank you for the specific steps.

0 coins

My incognito window trick has worked for me twice now. Something about the stored session data in a regular browser window causes problems.

0 coins

Incognito + fast submission + fresh session. That's the full playbook for the NYSDOL portal honestly.

0 coins

My job search requirements got tangled up in the whole mess when I had a portal outage last fall - I was so focused on getting the weekly claim filed that I didn't realize my job search activities hadn't saved either. Ended up calling the NYSDOL line to sort it out and that's when I first heard about Claimyr from someone else waiting in line at the career center. Used it, got to an actual live NYSDOL agent, and they were able to confirm what had saved and what hadn't so I didn't accidentally underreport my job search contacts.

0 coins

The job search log not saving is something I hadn't even thought to worry about separately. Going to check that tab too.

0 coins

My job search entries have a separate save button from the weekly claim certification. Easy to miss if you're rushing through or the page is behaving badly.

0 coins

Glad you mentioned that. I've always assumed that because the certification went through the job search log did too. Not necessarily true apparently.

0 coins

My claim went into what I thought was a standard adjudication hold but it turned out to be a data discrepancy caused by a failed portal submission that partially wrote some fields but not others. NYSDOL had a half-completed certification on file and a half-missing one for the same week. It took weeks to unravel. If you ever get a portal error, don't just retry - check your account first to see what state your claim is actually in before submitting again.

0 coins

That's genuinely alarming. I'm going to fully audit my account before I attempt another submission. I don't want a partial record causing problems down the line.

0 coins

Partial write errors on their backend are more common than NYSDOL admits. The database clearly doesn't roll back cleanly when a session dies mid-submission.

0 coins

My adjudication nightmare last year might have started the same way and I never connected those dots until reading this. That is a really important warning.

0 coins

My weekly claims have gone through fine the last several months but I've seen enough threads like this to know the portal instability is completely real and not user error. The NYSDOL system does not handle high traffic gracefully and the failure modes are silent and confusing. Stick to early morning, use incognito, do a fresh login each time, and have the phone certification line ready as a backup. That combination gets most people through.

0 coins

Collecting all of this advice together has been genuinely helpful. Early morning incognito fresh-login phone-backup is now my strategy.

0 coins

My routine now after too many bad experiences: early morning, private window, certification first, phone number saved in my contacts. Never stressed about it anymore.

0 coins

Solid summary. The phone line backup being an option for weekly certification is the thing I wish I'd known from day one.

0 coins

My unemployment claim experience taught me one hard lesson about the NYSDOL portal: document every interaction with a screenshot. Date and timestamp everything. If something goes wrong and your claim ends up in adjudication, having screenshots of error states or spinning pages with visible timestamps is actual evidence you can reference in an appeal or when speaking with an agent.

0 coins

Already took screenshots of the spinning page last night - good to know that could actually be useful evidence if this escalates.

0 coins

Screenshots with visible system clocks or browser address bars showing the date and URL are the most useful format. It establishes both what you saw and when you saw it.

0 coins

My appeal went more smoothly because I had screenshots. NYSDOL agents seem to respond better when you can show them exactly what happened rather than just describe it.

0 coins

My situation from a few months back: portal froze during week 3 of my claim, I panicked, refiled the same day without checking my account first, ended up with a duplicate submission flag and a two-week adjudication delay. I wish someone had told me to check the account status before retrying. The fix was straightforward once I got an agent on the phone but those two weeks without payment were brutal.

0 coins

The duplicate submission warning is something I'm going to keep in mind. Checking my account status before any retry attempt.

0 coins

Duplicate submission flags are way more common than they should be. Their system should catch and reject the duplicate automatically but instead it creates an adjudication hold. Classic.

0 coins

My rule now is always check the account before submitting again after any kind of failure. Twenty seconds of checking saves potentially weeks of adjudication headache.

0 coins

Related posts

New York Unemployment AI

Expert Assistant
Secure