Unable to Access NY.gov for Unemployment Certification - Connection Reset Errors for Two Days Straight

tried that already 😩 still getting the same error message

its definitely a system wide issue, my cousin in Albany is having the same problem

sounds sketchy af, is this legit? 🤔

100% legit used it twice now. Worth every penny when ur desperate to talk to someone

can confirm, used it last week when the website was down too

facts 💯 system always down when rent due smh

MVP right here with the actual helpful info 🙌

thank you! gonna try early morning tomorrow

mobile site is down too rn

@Khalil Urso I m'in the same boat - been trying since Sunday with no luck. The 4 hour hold time is absolutely insane! I m'gonna try that claimyr service that @Zoe Papanikolaou mentioned if the early morning attempt doesn t work.'We really shouldn t have'to pay a third party service just to access our own benefits but here we are 🤦‍♀️

@Douglas Foster Great advice about documenting everything! I ve'been screenshotting every error message just in case. Also wanted to add - if anyone has a VPN, try connecting through a different location. Sometimes these government sites have weird routing issues that a VPN can bypass. I m'in Syracuse and gonna try the early morning approach too after reading everyone s'suggestions here 🤞

@Zara Shah Thank you so much for the update! That s'really encouraging to hear someone actually got through. I m'definitely setting my alarm for 5am tomorrow - fingers crossed the early morning window is still working. Did you notice if the site was completely down or just really slow during those early hours? Also wondering if anyone knows how long these system issues typically last with NYSDOL? This is my first time dealing with their website problems and the stress is real 😅

@Logan Scott The site was really slow but functional around 5:30am - took about 10 minutes to load each page but I was able to get through the whole certification process. From what I ve'seen on this forum and talking to friends who ve'dealt with NYSDOL before, these outages usually last 3-5 days when they re'this widespread. The good news is they typically extend deadlines if there are documented system issues, so definitely keep those screenshots! @Douglas Foster had great advice about that. Wishing you luck with the 5am attempt! 🤞

@Logan Scott The site was definitely slow but functional around 5:30am - took about 10 minutes to load each page but I was able to get through the whole certification process. From what I ve'experienced before, these NYSDOL outages usually last 2-4 days max before they get it sorted out. The early morning window seems to be the sweet spot because less people are trying to access it then. Good luck tomorrow morning and make sure you have your work search activities ready to input quickly! 🤞

@Logan Scott The site was super slow but functional around 5:30am - took about 10 minutes to load each page but it worked! From what I ve'seen in other threads, these outages usually last 3-5 days max. NYSDOL typically doesn t'announce maintenance windows which is frustrating, but they seem to fix major issues pretty quickly once enough people complain. Keep trying early mornings and you should get through soon! Also heard from a friend that weekends sometimes have better uptime if you can wait until Saturday morning 🤞

@Logan Scott The site was definitely slow but functional around 5:30am - took about 10 minutes to complete what usually takes 2-3 minutes. From what I ve'experienced with NYSDOL over the past couple years, these major outages usually last 2-4 days when they re'system-wide like this. The worst was last summer when it was down for almost a week during a routine "update 🙄" Good luck with the 5am attempt tomorrow! Just have patience and don t'refresh if it s'loading slowly - that s'what caused me to lose my session the first time I tried.

@Logan Scott In my experience the site was just really slow during those early hours, not completely down. It took about 10 minutes to fully load each page but I was able to get through the whole certification process. From what I ve'seen on this forum over the past year, these NYSDOL outages usually last 2-4 days max before they get it sorted out. The key is being persistent and trying at off-peak hours like super early morning or late night around (11pm-1am sometimes works too .)Good luck with the 5am attempt! 🤞

@Logan Scott The site was really slow but functional during those early hours - took about 10 minutes to load each page but it didn t'crash. From what I ve'seen in this community before, these NYSDOL outages usually last 2-4 days when they re'system-wide like this. The good news is that they typically don t'penalize people for late certifications when it s'their system that s'down, especially if you have those screenshots @Douglas Foster mentioned. Good luck with the 5am attempt tomorrow! 🤞

@Felicity Bud Thank you so much for sharing what worked! This gives me hope - I m'definitely trying the early morning approach tomorrow. Question though - when you say don "t'click anything twice even when it seemed frozen ,"how long did you typically wait before assuming the page was actually loading vs actually frozen? I m'worried about timing out but also don t'want to mess things up by being impatient. Also did you notice if the mobile version works any better during those early hours or should I stick with desktop? Really appreciate everyone sharing their experiences here! 🙏

@Javier Torres Great question! I waited about 2-3 minutes for each page to load completely - I know it sounds like forever but the system is just crawling right now. I could tell it was actually working because the little loading wheel kept spinning, vs when it s'truly frozen everything just stops. I stuck with desktop since that s'what I m'used to, but honestly at those early hours any version might work better than normal times. The key is just being super patient and not refreshing or clicking back. You got this! 💪

@Javier Torres I waited about 2-3 minutes on each page before assuming it was actually loading. The loading spinner or progress bar usually gave me a clue - if I could see ANY movement or change, I d'wait it out. For the mobile vs desktop question, I stuck with desktop because the mobile site seemed even more unstable when I tested it around 10pm the night before. The key is really just patience during those early morning hours - the system is struggling but functional. Good luck tomorrow morning! 🤞

@Javier Torres I waited about 2-3 minutes per page when it seemed frozen - I know it sounds like forever but it was actually loading just super slowly. I could see the little loading spinner in the browser tab so I knew something was happening. I stuck with desktop since that s'what I m'used to, but honestly the mobile version might be worth trying too since it could have less traffic. The key is just being really patient and not refreshing or clicking back. Good luck tomorrow morning! 🤞

@Javier Torres Good question! I waited about 2-3 minutes for each page to load completely - I know it sounds like forever but the system is just super overloaded right now. You ll'see a spinning wheel or loading indicator, so as long as that s'there don t'click again. I stuck with desktop since the mobile site seems even slower based on what others mentioned. Also pro tip - have a backup plan ready like that claimyr service people mentioned, just in case the early morning thing doesn t'work for you. The stress isn t'worth it if you re'cutting it close to your deadline! Good luck tomorrow morning 🤞

@Javier Torres Good question! I usually waited about 2-3 minutes if the page seemed frozen - I know it sounds like forever but the system is just super overloaded during these outages. I could tell it was actually loading because the browser tab would show a loading icon even when the page looked stuck. As for mobile vs desktop, I stuck with desktop since it seemed more stable, but a few people in other threads mentioned mobile working better for them. Maybe try desktop first and if that fails, switch to mobile? The key is really just being patient and not refreshing or clicking back. You got this! 💪