
Complete troubleshooting guide
USCIS online account not working: what to do next
Updated Sep 3, 2026
Written and checked by Walter Armani. Last checked September 3, 2026. Research and verification follow the QueueCheck editorial standards. How we verify information
A myUSCIS error screen can stop you from seeing a case, but the screen alone is not an approval, denial or other case notice. Do not guess at the case outcome from an empty list or an unknown error. Check the public Case Status Online tool with the receipt number, look for a mailed or account notice, and use USCIS technical support when the account problem persists.
This guide separates login trouble from data-retrieval errors and shows which official route fits each one. A shared outage, a browser problem and an account-specific access issue can look similar at first. None should trigger a duplicate filing or a second account. A response deadline still needs attention even when the portal does not load.
USCIS online account official timing and account context
OfficialUS Green Card: check the current Visa Bulletin and USCIS case updates
Reader timelines are being collected for this service. The tracker page keeps the current official figure and what people who applied in your month are reporting.
Working the problem, step by step
The steps assume the most common situation: an account that worked before and stopped. Brand-new accounts, representative access, and paper-only cases have their own wrinkles, covered in the sections below.
- 1Read the error precisely
- 2Check whether it is everyone or just you
- 3Try the public case status tool
- 4Rule out the boring local causes
- 5Wait, then verify after recovery
- 6Escalate only if the problem outlives the outage
Read the error precisely
First 30 secondsA failed login, a login that works followed by a data-retrieval error, a server error page, and an empty case list are different failures with different meanings. Note which one you have and whether it repeats; the distinction drives everything below.
Check whether it is everyone or just you
2 minutesUSCIS posts service problems on its alerts page, including a dedicated tools-outage notice when its online tools go down. Third-party outage trackers surging with reports point the same way, though they are crowd noise rather than confirmation. Many reports plus an alerts-page notice means close the laptop and wait.
Try the public case status tool
1 minuteUSCIS says its public Case Status Online tool and the online account display the same case-status information. Use the receipt-number lookup as an available official check when the account view will not load.
Rule out the boring local causes
5 minutesA different browser, a private window, or clearing the cache resolves a surprising share of login trouble, because sessions and cached scripts go stale. A password reset settles whether credentials are the issue.
Wait, then verify after recovery
Hours, occasionally a day or twoOnce the account loads again, confirm the cases, notices and pending responses shown there. If something still looks wrong, use the technical-support form instead of assuming the earlier error explains every discrepancy.
Escalate only if the problem outlives the outage
After the trackers go quietA failure that persists while everyone else recovered is an account problem. Use the account technical-support channel linked from the login page, and keep receipts: screenshots with timestamps, the exact error text, and the receipt numbers affected.
The error taxonomy: what each failure means
A rejected password points to authentication. A successful login followed by an unknown error retrieving data points to a failure after authentication. A server error or empty case list is another display or retrieval symptom. Those labels describe what the website failed to show; they do not state what USCIS decided on the underlying application.
Use the error only to choose the next check. The official Case Status Online tool can provide the latest public case status from a receipt number. The Documents tab and mailed notices carry the details of case actions. USCIS's account technical-support form covers account access, verification codes, uploads and other technical problems.
Outage or just you: the two-signal test
Two checks separate a system problem from an account problem. First, the official signal: the USCIS alerts page, which carries a dedicated notice when its online tools are down, is the only source that confirms an outage. Second, the crowd signal: outage-tracker sites and applicant forums lighting up with the same error at the same time make a system problem overwhelmingly likely even before an official notice appears, and official notices do not always appear for short incidents.
If both signals are quiet and the failure is only yours, work the local checklist: browser, cache, password reset, and then the account technical-support channel. If the signals are loud, the productive move is the least satisfying one: stop retrying and come back later, because hammering a struggling system tells you nothing new.
Deadlines, action emails, and what an outage cannot change
Deadlines to respond to a request for evidence or a notice run from the paper notice, not from portal visibility, so an outage neither pauses nor extends them. If a response is due and the portal is down, the deadline still governs; plan the response around the outage, and remember that mailed filings and the contact center exist independently of the web account.
An email saying USCIS took action is a prompt to look for the notice, not the notice itself. Keep the email and check the Documents tab and mail. If a notice does not appear or delivery is overdue, use the official missing-notice or technical-support route that fits the problem.
The mistakes that turn a glitch into a real problem
An error screen does not justify refiling. A duplicate filing can add fees and create a second record without solving the account problem. A second account can make access harder to untangle. USCIS provides an official technical-support form, so do not pay someone who claims to have private access to restore a case or account.
The cheapest response to a USCIS outage is patience plus a paper trail: screenshot the error with its timestamp, keep any action emails, and verify the account after recovery. That record costs a minute and covers the rare case where you later need to show what you saw and when.
The situations that send people searching
Login works, then "an unknown error occurred while retrieving your data"
What helps
Check the USCIS alerts page and whether many people are reporting the same symptom. Try Case Status Online with the receipt number, then retry the account later. The error text alone does not report a case decision.
Your cases vanished from the account
What helps
Do not treat the empty list as a deletion notice. Check each receipt number in Case Status Online, save a screenshot, and use account technical support if the list does not return after a shared incident ends.
You got an action email but the account shows nothing
What helps
Keep the email, then look for the actual notice in the Documents tab and mail. The email does not tell you what action USCIS took. Use the missing-notice or support route if the notice does not arrive.
A response deadline lands during the outage
What helps
The deadline runs on the paper notice regardless of portal health. Prepare the response, use mail or the contact center if the portal stays down, and document the outage with timestamped screenshots in case timing is ever questioned.
Everyone else recovered, your account still fails
What helps
That is an account problem, not an outage. Run the local checklist, then use the technical-support channel linked from the account login, with the exact error text, timestamps, and affected receipt numbers ready.
Someone offers to fix your access or your case for a fee
What helps
Decline. Outages end on their own, account problems route through the free official support channel, and no third party has a lever USCIS support lacks. Paying converts a temporary display problem into a permanent financial one.
Help readers with the same USCIS online account milestone
Official numbers cannot show what applicants actually experience month by month. Sharing your application and decision dates helps the next reader see the real pace. Under a minute, dates only, nothing personal.
Share my USCIS online account datesUSCIS online account status questions before you refresh again
Is USCIS down, and how do I check officially?
The USCIS alerts page is the official signal, including a dedicated notice when online tools are out. Outage-tracker sites and forums surging with identical reports are strong unofficial evidence, and short incidents sometimes end before any official notice appears.
Does a USCIS website glitch mean something happened to my case?
The error message alone does not say that USCIS approved, denied or deleted a case. Check the receipt number in Case Status Online and read any official notice before drawing a conclusion about the application.
My case status says error retrieving case status. Is that the same thing?
It is a separate symptom in an official lookup. Recheck the receipt number exactly as printed on the notice, retry later, and contact USCIS if the error persists. A simultaneous account outage can be useful context, but it does not diagnose an individual receipt number.
Can I get a deadline extension because the portal was down?
Do not plan on it. Deadlines run from the paper notice, and an outage does not pause them. Respond by mail or through the contact center if the portal stays down, and keep timestamped evidence of the outage with your records.
Should I create a new account if mine will not load?
No. A second account splits your filing history and creates matching problems that outlast any outage. Fix the first account through the technical-support channel; that is what it exists for.
How long do USCIS outages usually last?
USCIS does not publish a standard recovery time for every account incident. Check its alerts, retry later, and use technical support if your account remains inaccessible after a reported outage has ended.