GST Portal Not Working? Causes and What to Do

Every month, a few days before a return is due, the same complaint shows up: the GST website is not working. Pages time out, the login screen keeps reloading, the OTP never arrives, or the DSC refuses to sign. Sometimes the GST portal really is struggling. Just as often the problem is on the user's side, in the browser, the network or the signing utility. This guide shows how to tell the two apart, what to fix locally, what GSTN usually does when the portal fails near a due date, and how to keep working when you cannot get in.

Is the GST website down, or is it just you?

Spend two minutes on this before anything else. It decides whether you should fix something or simply wait.

The quickest test is this: open gst.gov.in in a private window on your phone, on mobile data rather than office Wi-Fi. If it works there, the portal is up and the fault is in your browser, device or network. If it fails there too, check the News and Updates section on the portal's home page and GSTN's official social media handles. Planned maintenance is normally announced there in advance, and known glitches are often acknowledged while they are happening.

Fixing a problem on your side

Work through these in order. Most "GST site not working" problems that are not outages clear by step three.

1. Use a current, mainstream browser. The portal is built and tested for recent versions of Chrome, Edge and Firefox. Old browsers, and in-app browsers inside email or chat apps, cause layouts to break and buttons to do nothing.
2. Try a private window. It starts without cached files or old cookies. If the portal works there, clear the cache and cookies for the GST site in your normal browser.
3. Allow pop-ups for the site. Downloads, the DSC signing step and some confirmations open in a new window, and a pop-up blocker silently stops them.
4. Turn off extensions such as ad blockers, script blockers and some antivirus web shields for the GST domain. They can block the scripts the forms depend on.
5. Check the network. Office firewalls and VPNs sometimes filter government sites or break long-running sessions. Try a direct connection or mobile hotspot.
6. Check the system clock. A PC with the wrong date or time can fail secure connections and DSC signing.

If you are stuck on a search rather than a login, for example the portal keeps telling you a GSTIN does not exist, that is usually a different problem. See GST portal "no record found" for that diagnosis.

GST login not working: OTP, password and session

When the GST login is not working but the rest of the site loads, the cause is usually one of these:

• Expired captcha. The captcha is valid for a short time. If you typed the password slowly or switched tabs, refresh the captcha and try again.
• Expired or locked password. Passwords expire periodically, and several wrong attempts lock the account for a while. Use Forgot Password rather than guessing repeatedly.
• OTP not received. The OTP goes only to the mobile number and email registered for the authorised signatory. If the business changed its accountant or the signatory changed phone numbers, the OTP may be going somewhere no one is looking. Updating those details is a non-core amendment on the registration.
• OTP delayed. At peak times messages queue up. Requesting a fresh OTP every thirty seconds makes it worse, because each new request cancels the last one. Wait a few minutes, and check that the phone is not filtering messages from short codes.
• Session timed out. The portal logs you out after a period of inactivity. If a page you left open suddenly refuses to save, log in again. Save work in the return often rather than at the end.

DSC and emSigner errors

Companies and LLPs sign returns with a digital signature certificate, and the portal talks to the USB token through a small signing utility, emSigner, installed on your computer. Most DSC failures are between your browser and that utility, not on the portal.

• "Please start the emSigner" or the signing window never opens. The utility is not running, or it needs to be started with administrator rights. Start it, then reload the page.
• Browser cannot reach the utility. The utility runs a local service on your machine that the browser connects to. Some browsers ask you to allow that connection once; antivirus software can block it.
• Token not detected. Reinstall the token driver from the DSC vendor, try a different USB port, and make sure only one token is plugged in.
• Certificate expired or not registered. A renewed DSC has to be registered again on the portal against the authorised signatory before it can sign.
• Old version of the utility. GSTN updates emSigner from time to time. If signing stopped working after a portal change, download the current version from the portal's DSC registration page.

If DSC is the only blocker and the entity is allowed to use it, filing with EVC (an OTP-based verification) is often the faster way out. Proprietors and most partnerships can already file with EVC.

Why the GST site stops working near due dates

The portal serves crores of registered taxpayers, and a large share of them file in the same two or three days each month. The GSTR-1 and GSTR-3B deadlines, and the annual GSTR-9 deadline, create sharp peaks. The usual symptoms are slow pages, time-outs while saving or submitting, payment status that takes a while to reflect, and filed returns that show as "submitted" but not yet "filed" for some time.

The fix is unglamorous: do not file on the last day. Aim to finish two or three working days before the due date. Our return due dates guide and the compliance calendar list the dates. If a payment was debited but the challan still shows as pending, see checking GST payment status before paying again.

What GSTN does when the portal fails

GSTN, the company that runs the portal, has a fairly consistent practice when things go wrong:

• Advisories. Planned downtime, known glitches and their fixes are posted as advisories under News and Updates on the portal, and shared on GSTN's official social media.
• Due date extensions. When a widespread failure hits close to a deadline, the government has in the past extended the due date, or waived the late fee for the affected days, by notification. These decisions are made case by case, often at the last moment, and are not guaranteed. Do not stop trying to file because you expect one.
• Grievances for technical glitches. If you could not file because of a problem on the portal's side, raise a ticket through the grievance redressal facility linked from the portal's Help section, with screenshots showing the error, the date and the time. That ticket is your record if you later need to argue that a late fee or a lapsed claim was caused by the portal.

Keep your own evidence too. A screenshot with the system clock visible, the error message and the URL is far more useful later than a memory that "the site was down that night". Missing a deadline has real costs, set out in GST late fee and interest.

Alternatives when you cannot get in

You cannot file without GSTN, but you can stop the portal being the bottleneck for everything else.

• Offline tools. The portal offers offline utilities, such as the returns offline tool for GSTR-1, that let you prepare a return on your computer and generate a file to upload. Prepare while the portal is slow, and upload when it recovers.
• GST software that files through a GSP. Accounting and filing software connects to GSTN through a GST Suvidha Provider. It avoids the portal's web pages, so a front-end problem, a browser issue or a captcha loop does not stop you. But the GSP talks to the same GSTN back end, so a real back-end outage affects software users as well. The difference between the two kinds of intermediary is explained in GSP vs ASP.
• SMS filing for nil returns. If the month is genuinely nil, a nil return can be filed by SMS without logging in at all.

GSTIN lookups when the portal is down

Filing is not the only thing that stops when the GST site is not working. Accounts teams that check a vendor's GSTIN before paying, sales teams that check a customer's GSTIN before raising a B2B invoice, and onboarding flows that verify a GSTIN at signup all depend on the same government data. If those checks run through someone typing into the portal's Search Taxpayer page, they stop when the portal does.

A GSTIN verification API changes the failure mode rather than removing it. Our API keeps recent responses from GSTN for a window measured in hours, so a GSTIN that was verified recently can still be returned during an outage, with the time it was verified. A GSTIN no one has looked up recently still has to come from GSTN and will wait for it to recover. That is honest behaviour, and it is the right one: a payment to a new vendor should be held until a fresh check succeeds, not approved on an unverified number. How to design an integration that queues checks instead of failing is covered in GST API uptime and latency, and why an API holds up better than automating the portal's own pages is in GST API vs portal scraping.

Frequently asked questions