Quick Summary
Groww has faced three major documented app issues since January 2024. A January 2024 outage stopped all trading during morning hours. An August 2024 two-day glitch blocked demat balances and rejected orders. A May 12 2025 GTT glitch triggered orders at wrong prices, with one user losing Rs. 24,964. Groww paid Rs. 34.12 lakh to SEBI to settle a case related to a technical glitch without admitting fault. If the app caused you a financial loss, a formal complaint path exists and is free to use at every stage.
Is Groww down right now? Or did a Groww app issues cost you money?
Both situations need different responses, and this page covers both.
If you are here because the app just stopped working, the first section tells you how to check if it is a Groww server problem or a device problem in under two minutes.
If you are here because a past glitch caused you a financial loss, the incidents section and the complaint guide at the bottom are what you need.
Is Groww Down Right Now? How to Check in Two Minutes
Before you troubleshoot your device or panic, spend two minutes confirming whether the problem is on Groww’s side or yours.
Open X (formerly Twitter) and search “Groww not working” or “Groww down.” If dozens of users are posting about the same issue at the same time, the problem is on Groww’s servers and no amount of device troubleshooting will fix it. You need to wait.
If the search shows nothing recent, the issue is likely on your side. Try switching from mobile data to WiFi or vice versa. Force close the app and reopen it. If that does not work, try the Groww web platform on a browser while the app recovers.
The most common real-time Groww app glitch that bring users to this page are the app not opening, login failures during market hours, order placement failing, balance not showing, and the platform going completely unreachable during expiry days.
Three Major Groww App Issues That Made Headlines
These are the three documented incidents that affected the most users and resulted in formal complaints. Each one has specific details worth knowing if you are evaluating whether your situation qualifies for a complaint.
Incident 1: January 23 2024: Full App Outage During Morning Trading
Groww users were unable to log in or place trades during early market hours on January 23 2024. The outage hit intraday traders hardest because early price action is when the most time-sensitive trades happen.
Users on X posted repeatedly about being locked out while markets moved. One user wrote: “Groww app is not working. Everything is stuck. Who will compensate us?”
Groww CEO Lalit Keshre acknowledged the issue and apologized on X: “This time, it hurt a lot more. We are deeply sorry.”
The apology acknowledged the severity. What it did not include was a clear compensation mechanism for traders who lost money because they could not place orders during the outage.
Incident 2: August 7 2024: Two Consecutive Days of Glitches
The August 2024 issue was more specific and affected users in three ways simultaneously. Demat balances became unavailable, showing incorrect or zero figures. Orders were rejected despite sufficient margin in the account. Login failures occurred during peak morning hours.
The fact that it happened on two consecutive days, not just one, indicated a deeper infrastructure problem rather than a one-off server overload.
Users reported duplicate option orders during Muhurat trading 2024 as a related issue. Mutual fund NAVs showed with a one-day delay. New fund offer units appeared duplicated in some accounts.
Incident 3: May 12 2025: GTT Orders Triggered at Wrong Prices
This was the most financially damaging of the three incidents for retail investors.
On Monday, May 12 2025, a technical glitch in the Groww app caused Good Till Triggered orders to fire at completely incorrect share prices.
Some users saw their portfolio values appear to jump by thousands of percent, an illusion created by the app displaying wrong prices.
Others suffered real, immediate financial losses when their GTT orders executed at prices they never intended.
One user documented a loss of Rs. 24,964.73 from unintended GTT executions triggered by inflated prices. Another reported near 8,000 percent paper gains before the illusion collapsed and the actual position showed.
Users were angry enough to post on X in real time. One wrote: “Because of your UI glitch all my orders got triggered at much lower than what it was set. I’ll see you in court if I don’t get a refund for all my losses.”
Groww acknowledged the bug, called it temporary, and said the support team would reach out to affected users. No clear compensation timeline was given.
The full breakdown of this specific incident, what SEBI’s framework says about broker liability for GTT glitches, and how to document your case is covered on a separate page on this site.
Why Does Groww Keep Having These Problems?
Based on NSE audit patterns and SEBI observations, four structural reasons explain why these issues keep recurring.
- Server overload on peak days. Expiry days, budget announcements, and major IPO subscription windows bring sudden spikes in concurrent users. Groww’s infrastructure has repeatedly shown it cannot handle these spikes without degrading for some users.
- Order routing delays to exchanges. When the app’s internal processing slows, the delay between a user placing an order and the order reaching NSE or BSE creates a window where prices move against the intended execution.
- Insufficient backup systems. A trading platform with millions of active users needs redundant systems that take over instantly when the primary systems fail. The recurring nature of these incidents suggests those backups are either absent or insufficient.
- Compliance logging failures during tech events. When a glitch occurs, SEBI expects brokers to maintain complete records of what happened, which orders were affected, and what remediation was offered. The vague public responses from Groww after each incident suggest this logging was not comprehensive.
Also Read: Our Data Fetching Minions Ran Into an Error: What This Groww Error Means and What to Do
What SEBI Action Has Been Taken Against Groww for Such Technical Glitches?
These three incidents are not isolated. They are part of a documented pattern of infrastructure failures that SEBI on Groww has already taken action on.
Groww paid Rs. 34.12 lakh to SEBI in May 2025 to settle a case arising specifically from the January 23 2024 outage.
The settlement was not for the May 2025 GTT glitch. It was for what happened in January 2024.
The specific violations SEBI found were: Groww failed to report through SEBI’s LAMA logging system during the outage. Groww had no backup telephone lines, no backup trading terminals, and no staff assigned to handle client calls during the failure.
Groww settled without admitting or denying these findings.
What this means for you as an investor: SEBI investigates technical glitch complaints against Groww. They take them seriously enough to reach monetary settlements.
If a Groww glitch caused you a financial loss, a formal complaint is not a futile exercise. It has produced real outcomes.
If your GTT order fired at the wrong price on May 12 2025, or if you could not trade during the January 2024 outage, or if any other Groww platform failure cost you money, the formal complaint path runs from SEBI SCORES to SMART ODR to NSE arbitration.
Every stage is free for claims below Rs. 10 lakh.
The complete step-by-step refund claim process, what evidence SEBI requires, and how to calculate your loss claim is on the Groww technical glitch refund page on this site.
What to Do If Groww App Issues Caused You a Financial Loss
There are two situations. If you lost money because of a specific documented glitch and you can show the connection between the glitch and your loss, you have a formal complaint ground.
The first step is to take screenshots immediately. Capture the error message, the incorrect balance or order, and the timestamp. If the loss is from a GTT order that triggered incorrectly, screenshot the order history showing the trigger price versus the intended price.
Switch to the Groww web platform if the app is not responding, check NSE or BSE directly to confirm the price at the time of execution, and file a complaint against Groww app immediately through their official support channels.
Give Groww 15 to 30 days to respond. If the response is unsatisfactory or does not arrive, the formal complaint path escalates through SEBI SCORES and potentially to NSE or BSE arbitration.
For the specific step-by-step process of claiming a refund for a Groww technical glitch loss, what evidence holds up in a formal complaint, and how to file on SEBI SCORES, that is covered in full on a dedicated page on this site.
If you received a specific error message rather than a general outage, the fix guide for each error type is on its own page.
Lost money to a Groww technical issue and want someone to review your case and file the complaint on your behalf? We handle documentation, SEBI SCORES filing, NSE IGRC escalation, and arbitration representation.
Register with us for a free consultation.
Conclusion
Groww has had three major documented app failures since January 2024. Each one produced real financial losses for some investors. The platform paid Rs. 34.12 lakh to SEBI in settlement of a related complaint.
If the app is down right now, check X first to confirm whether it is a server issue. If it is, wait. If it caused you a financial loss, document it today and use the formal complaint path.
Your money in demat holdings is safe regardless of what happens to Groww as a platform. Your uninvested cash is more exposed and should be kept minimal.
Report. Recover. Stay Fraud Free.
Frequently Asked Questions
Check X or Twitter and search "Groww not working." If multiple users are reporting the same problem at the same time, it is a Groww server issue. If nothing appears, the problem may be on your device. Try switching networks or force closing and reopening the app.
Groww has faced recurring server overload issues during peak trading events. The platform's infrastructure has shown limitations on expiry days, major IPO windows, and budget announcement days when concurrent users spike suddenly. NSE audit patterns and the three documented incidents since 2024 point to insufficient backup systems and order routing delays as the root causes.
Groww said its support team would reach out to affected users but provided no clear compensation mechanism publicly. Groww has separately paid Rs. 34.12 lakh to SEBI to settle a technical glitch related case without admitting fault. Individual investors who lost money can file formal complaints through SEBI SCORES and NSE IGRC.
Your demat holdings, shares, mutual funds, and bonds are held by CDSL or NSDL, not by Groww. They would remain safe and transferable to another broker. Uninvested cash in your trading account is held by Groww and subject to SEBI's client fund segregation rules. Keep minimal cash in the trading account to reduce exposure.
Take screenshots of the error and the financial impact immediately. Raise a support ticket with Groww within 24 hours. Give them 15 to 30 days to respond. If unresolved, file on SEBI SCORES under the Stock Broker category. If SEBI SCORES does not produce a satisfactory outcome, escalate to SMART ODR and then to NSE or BSE arbitration. The full process is on the Groww technical glitch refund page on this site.
Add us as a preferred source on Google »
