EPFO portal not working? What each error means and what actually helps

The EPFO member portal fails in a small number of predictable ways. Almost every problem people describe as “the site is not working” is one of four distinct things, and they have different fixes. Working out which one you have takes about a minute and saves a lot of pointless retrying.

First, work out which failure you have

What you see	What it usually is	What helps
Page does not load at all, or times out	Server load, or a genuine outage	Wait, retry outside peak hours
Login rejects a password you know is right	Stale session, or load	Clear cookies, use a private window
Login works but the passbook is empty	Passbook service down, or employer has not filed	Try UMANG, or wait for the monthly return
An error appears mid-claim	Incomplete or mismatched KYC	Fix the underlying record, not the claim

The last row is the one that matters most, because retrying will never fix it and most people spend their time there.

Peak hours are real

EPFO publishes no status page, so the practical test of whether the site is down is simply whether the homepage loads at all. Load follows a predictable daily shape.

When	What to expect
Before 9am	Fastest, by a clear margin
10am to 2pm	Heaviest load of the day
2pm to 7pm	Moderate, improving through the afternoon
After 7pm	Usually good

Month end and the days around the annual interest credit are worse than any hour of a normal day. If your task is not urgent, an early morning attempt on an ordinary weekday is worth more than any browser trick.

Fixes that genuinely work

Use a private or incognito window. The single most effective step for login problems. The portal handles stale sessions poorly, and an old cookie will produce what looks exactly like a wrong password.

Try a different browser. Parts of the portal behave badly in browsers with strict tracking protection or an aggressive ad blocker. Not because anything is being blocked maliciously, but because the site depends on scripts those tools sometimes catch.

Use UMANG for the passbook. UMANG reaches the same backend through a different frontend, so it often works when passbook viewing on the website does not. It will not help during a real outage, because the data is coming from the same place.

Check your employer has filed. Your passbook cannot show a month your employer has not yet filed a return for. This is not a fault, and no amount of retrying will change it. If several months are missing, the problem is with the employer, not the portal.

Errors that are not outages

Some messages look like site problems but are records problems. Retrying will never clear them.

KYC not verified. Your PAN, Aadhaar or bank details are either missing, unverified by your employer, or do not match exactly. The name on your bank account matching your EPFO record exactly, including initials, is a frequent cause of silent claim rejection.

Details do not match. Typically a date of birth or name difference between EPFO and Aadhaar. Correcting this requires a joint declaration through your employer, and in some cases EPFO office approval. It cannot be self-served.

Claim rejected without a clear reason. The reason is recorded against the claim in your passbook view, not shown at submission. Look there before refiling, because refiling with the same defect simply produces the same rejection a few weeks later.

Multiple UANs. If you have worked at more than one employer and were issued a second UAN, balances and service history split across them. This needs merging before withdrawals or transfers behave correctly, and it is the underlying cause of a surprising share of “my service shows wrong” complaints.

What people get wrong about this

“My UAN is blocked.” Almost never true. A login failure during peak hours is load. A genuinely deactivated UAN produces a message that says so explicitly, and normally follows a duplicate UAN merge.

“UMANG is a workaround for outages.” It is a different door into the same building. Useful when the website’s own passbook page is struggling, useless when the backend itself is down.

“Raising a grievance will speed things up.” A grievance is the right route for something genuinely stuck, such as a claim sitting untouched for weeks. It does nothing for load, and filing one during an outage adds to the queue without helping your case.

“Clearing cookies loses my data.” It clears your session, nothing else. Your EPF record lives on EPFO servers and is entirely unaffected by anything your browser does.

When nothing works

If the portal is genuinely unreachable, the passbook is also available by giving a missed call to the EPFO number registered against your UAN, and by SMS to the same service. Both return a balance rather than a full statement, but they confirm your account is fine when the website suggests otherwise.

For anything that needs a person, your employer’s HR or PF desk can act on records the portal will not let you touch yourself, and the regional EPFO office handles what the employer cannot.

Never enter your UAN, password or OTP anywhere except the official portal. Sites offering to check your balance or speed up a claim on your behalf are not EPFO, whatever they look like.