Groww outages: withdrawals, logins and cloud risks

Friday disruption: withdrawals briefly blocked

Groww users reported they could not withdraw funds during equity trading hours on Friday. Some posts also said deposits were failing at the same time. Groww attributed the withdrawal disruption to an incident at Google Cloud Platform. The brokerage said only a very small fraction of customers were affected. It said the issue was resolved promptly before market close. After the disruption ended, customers could access their funds again. Users also shared screenshots of in-app messages asking them to try later. The episode revived questions online about reliability during live market sessions.

Early market hours: login and trading impact

Alongside withdrawals, some Groww app users said they were unable to log in in early market hours. A few users also claimed they could not place trades during that window. Multiple reports described the app not loading or showing temporary error notifications. Others said transaction services were unreliable during market hours. Groww displayed a notification acknowledging a temporary issue. The message asked users to try again later. The situation eased later in the session after the disruption was resolved. The pattern matters to active traders because the first hour often has the highest activity.

Cloudflare outage: why Groww and peers went down

A separate bout of complaints came during a major global outage at Cloudflare. Users across India reported login failures, slow loading, and transaction errors that day. Groww confirmed the issue was not internal and was caused by Cloudflare. Cloudflare is an internet infrastructure provider used for routing, security, and traffic optimisation. When Cloudflare systems go down, dependent services can become temporarily unreachable. Social posts mentioned portfolio not refreshing, order placement delays, and charting issues. The same outage also hit other brokers including Zerodha and Angel One. Later updates said services returned to normal and users could trade again.

What users say: repeat glitches across two days

Beyond one-off incidents, users also reported a Groww technical glitch across two straight days. Complaints included unavailable Demat balances and login failures during peak hours. Some users said orders were rejected despite sufficient margin. Others pointed to problems specifically with charts, including “Groww chart not working” posts across platforms. App store reviews echoed similar frustrations about stability and responsiveness. These reports are user-reported and vary by device, network, and time of day. Still, the repetition across days is what drove the issue to trend. For many retail investors, reliability is part of risk management, not just convenience.

Common problems mentioned in posts and reviews

Several user-reported issues were shared repeatedly across Reddit, X, and app reviews. Some were trading-impacting, while others were data and display-related. A few posts referred to duplicate trades during Muhurat trading 2024. Others described delayed mutual fund NAV updates by about a day in the portfolio view. There were also reports of duplicate units appearing during NFOs. Separately, users noted Groww web being slow on Chrome even after clearing cache. These items do not confirm root cause, but they show what users experience on the front end. The table below summarises the recurring themes as described online.

What people think causes the outages

Some discussions referenced NSE audit trends and SEBI observations when discussing likely causes. The commonly cited factor is server overload during peak hours, especially on expiry days or major events. Another cited point is order routing delays to exchanges like NSE and BSE. Posts also claimed a lack of backup systems for high-volume trading days. Another theme was inadequate compliance logging during a tech failure. These points reflect what is being discussed publicly and are not a diagnosis of a specific incident. What is clearer from the Friday incidents is dependency on external infrastructure providers. When cloud or network layers fail, the brokerage experience can degrade even if core systems are intact.

SEBI and compliance context driving the discussion

Groww has previously settled a case with SEBI related to an outage in its trading app last year. Separately, media reports and posts referenced an hour-long outage on January 23, 2024, when users said they could not log in. SEBI’s order noted Groww did not publish key values to exchanges on Log Analytics and Monitoring Application (LAMA) on that date. SEBI also observed that Groww did not have telephone lines, trading terminals, and employees for attending trading calls of clients during glitches. The regulator described this as complete denial of service to clients during the glitch period. The order also noted issues including incorrect retention statements in 38 instances. It further mentioned the app did not provide the best available market price to investors and cited gaps like non-secured login and limited access when both app and web versions faced glitches. This regulatory backdrop is why even short disruptions now draw outsized scrutiny on social media.

What to do if Groww is down during market hours

Users sharing playbooks online emphasised documentation and fast escalation. The first step is taking screenshots of errors, missing balances, or duplicate orders. If the app is unstable, trying Groww Web or switching devices can help isolate the issue. Checking NSE and BSE sites can confirm whether it is exchange-wide or broker-specific. Raising a ticket through Groww’s official support system is the next step for an auditable trail. If needed, users said to escalate when the issue is at NSE or file a complaint with SEBI. Groww’s listed support channels include support@groww.in and its contact page at https://groww.in/contact-us. Users also shared phone support numbers 080 4748 1507 (Mon to Sat, 9 AM to 7 PM IST) and +91-9108800604. For outages tied to providers like Cloudflare or GCP, waiting for restoration is often the only immediate fix, but keeping records can matter if there is financial impact.