Groww app outage: withdrawals failed before market close

Groww users took to Reddit and social media to report disruptions during market hours, especially when liquidity and activity typically peak near expiry sessions and close. The most discussed issue was an inability to withdraw funds during equity trading hours on a Friday. Some posts claimed deposits were failing at the same time, adding to the urgency for traders trying to manage margins. Separately, users also reported login failures and unreliable transaction services in early market hours. A few said they could not place trades during that window, though the user reports varied by time and device. Groww acknowledged disruptions and attributed them to third-party infrastructure incidents, not internal systems. The episode has pushed a practical question to the top of retail investor discussions: what should you do when the broker app fails during a live session.

What users reported during Groww’s Friday disruption

Many Groww users said they could not withdraw funds during equity trading hours on Friday. Some posts also said deposits were failing at the same time. Users described the experience as intermittent rather than a complete blackout, with some being able to access services while others could not. A separate set of posts said login was failing in early market hours. A few users also claimed trade placement was affected during that early window. Others broadly described transaction services as unreliable during market hours. The common thread in these discussions was timing, with reports clustering around peak usage hours. The social posts framed it as a high-stakes problem because trading decisions and margin needs often move quickly late in the session.

Groww’s response: Google Cloud Platform incident

Groww attributed the withdrawal disruption to an incident at Google Cloud Platform. In response to an email query cited in reports, a Groww spokesperson said the platform experienced a temporary disruption. The spokesperson said it prevented a very small fraction of customers from making withdrawals. Groww also said the incident was resolved promptly before market close. After the disruption ended, customers could access their funds again. The messaging from Groww focused on two points: limited customer impact and quick restoration. Users discussing the incident focused less on the fraction affected and more on the practical difficulty of not being able to move funds during market hours. The incident also amplified concerns about whether infrastructure dependencies can create single points of failure during busy sessions.

A separate thread: Cloudflare-linked login and trading issues

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. Groww confirmed that at least one set of issues was not internal and was caused by Cloudflare. Posts around this incident were not limited to Groww, as multiple broker apps and websites were discussed as being affected around the same time. A widely shared message referenced a global outage at Cloudflare impacting multiple apps and services worldwide. Users reported symptoms like login failures and errors, including “500 internal server error” messages in some cases across platforms. Reports said the issue began around 8:45 AM IST and was resolved by around 10:00 AM IST, with some users still seeing intermittent glitches into late morning. The National Stock Exchange (NSE) reported no broader market-wide issues beyond platform access, which reinforced the view that this was a broker and infrastructure access problem, not an exchange halt.

Why expiry days and market close amplify outages

The commonly cited factor in user discussions is server overload during peak hours, especially on expiry days or major events. Even when the root cause is external infrastructure, peak-hour demand can make failure modes more visible to end users. Traders often try to log in at the same time around the open, and many also cluster activity closer to close to square off positions. That combination increases stress on authentication, order routing, and payment workflows. Users also pointed to IPO-related spikes and other event-driven surges as moments when platforms can become unstable. In the Groww-related discussions, the concern was not just price execution but also basic access to funds and margin. Expiry sessions matter because open positions may need active management, and delays can create risk for individuals even if the platform restores later. Separately, social media also referenced a Sensex expiry-day technology glitch where brokers pointed to BSE, highlighting that disruptions can originate from different points in the trading stack. The practical takeaway from the discussion is that retail investors treat peak windows as the time to be most prepared for disruptions.

What Groww users saw inside the app during the incident

Users shared that Groww displayed a notification acknowledging problems and asking them to try again later. Such in-app notices became a key signal for whether the broker recognised the issue. Some users relied on repeated attempts, while others switched devices or moved between mobile and web. The varied reports suggest the experience differed by user, region, and time window, which is consistent with partial outages or degraded service. Users also reported missing balances, delayed updates, and transaction failures, though these were shared as individual experiences rather than a single confirmed symptom. The broader social conversation also included frustration about uncertainty during live market hours. Some users said they could not determine quickly whether the problem was broker-specific or exchange-wide. That uncertainty is why many users recommended checking official exchange sites during disruption windows. It also explains why an auditable support trail, like a ticket number, was repeatedly recommended.

Quick reference: incidents and what was affected

The posts and company statements clustered around two infrastructure-linked incidents, plus a mitigation move announced by Groww later. The table below summarises what was stated in public posts and responses shared in the trending context. It is not a complete outage log, but it captures the most repeated claims and the broker’s stated causes. Users should treat timing as indicative because social reporting is often fragmented across accounts. The key distinction is between a funds movement disruption (withdrawals, and some deposit failures) and an access and transaction disruption (login and trading functions). Both types of failures can feel similar to users but may require different fixes internally and at vendors. The most consistent operational advice from users was to document errors and escalate quickly through official channels.

The playbook users shared for handling broker outages

Users sharing playbooks online emphasised documentation and fast escalation. The first step repeatedly mentioned was taking screenshots of errors, missing balances, or duplicate orders. If the app is unstable, users suggested trying Groww Web or switching devices to isolate whether it is app-specific or network-specific. Checking NSE and BSE sites was recommended to confirm whether the disruption is exchange-wide or limited to particular brokers. Raising a ticket through Groww’s official support system was positioned as the next step because it creates an auditable trail. If the user believes the issue sits at the exchange or remains unresolved, some posts suggested escalation, including filing a complaint with SEBI if required. Groww’s listed support channels shared in discussions include support@groww.in and the 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. The underlying theme was to avoid relying only on social media posts for resolution and to use official support workflows for record-keeping.

Groww Lite: a backup route to close positions

Against the backdrop of outage discussions, Groww said it launched ‘Groww Lite’, a web-based emergency trading portal. The broker positioned it as a safeguard for users during platform outages and technical glitches. According to Groww’s statement shared in the trending context, the portal enables users to close or exit open trading positions even if the main Groww app or website is temporarily inaccessible. For active traders, this addresses the most time-sensitive need during disruptions, which is to manage risk by exiting positions. It does not change the fact that withdrawals, deposits, and logins can still be impacted by third-party infrastructure, but it adds a practical fallback. Users evaluating such a feature typically focus on whether the backup path remains reachable when primary services fail. The broader Cloudflare episode discussed online reinforced why brokers are adding alternate access channels, such as WhatsApp or web fallbacks, to reduce single points of failure. For retail investors, the presence of a documented backup method can reduce panic during peak market minutes. The real-world value will depend on whether users know about it beforehand and can access it quickly under pressure.

What this episode signals for retail investors

The Groww outage discussions show how quickly operational reliability becomes a top concern when markets are open. Even when brokers attribute issues to large infrastructure providers like Google Cloud Platform or Cloudflare, the user experience is the same: inability to access money, log in, or place orders. The social conversation also highlighted that disruptions can happen at different layers, including broker systems, cloud vendors, internet infrastructure, or even exchange connectivity. Retail users tended to separate two questions: “Is my broker down?” and “Is the exchange down?”, and they used NSE and BSE sites to answer the second one. Another pattern was the push for evidence, with screenshots and ticket numbers seen as essential for disputes around missing balances or duplicate orders. Users also discussed the importance of testing alternate access ahead of time, such as web logins and backup portals, rather than waiting for an outage. While Groww said only a very small fraction of customers were affected in the GCP-linked withdrawal disruption, the incident still became widely discussed because outages are most visible during expiry days and close. For investors, the actionable takeaway is preparation: know official support channels, keep a checklist ready, and do not wait to escalate when a disruption blocks critical actions.