Groww app outage: chart freeze on expiry days

Groww was discussed heavily on Reddit and social media after users reported disruptions during market hours, especially in periods that typically see peak activity around expiry sessions and near the close. Multiple posts said charts froze, screens loaded slowly, and some transactions failed while traders were trying to track fast-moving prices. User reports in the same thread set a rough timeline, with the issue starting around 8:45 AM IST and easing by about 10:00 AM IST, though a few said glitches continued into late morning.

What users said happened during the latest freeze

Posts described the app feeling unstable during a window when traders expect high liquidity and rapid price changes. Several users said charts stopped updating or lagged, which made it difficult to confirm live prices. Others described login failures and intermittent errors when navigating watchlists or positions. The timing was repeatedly linked to expiry-day behaviour, where activity spikes for F&O traders. Users also highlighted that problems feel more damaging during the open and the final hour, when order flow accelerates. Some reports framed the incident as a platform-side disruption rather than a personal device issue. A small subset of posts said the problem was not fully uniform, with intermittent glitches for some users after the broader disruption eased. Across comments, the shared theme was uncertainty about whether it was broker-specific or exchange-wide.

Timeline shared online: 8:45 AM to 10:00 AM IST

The most repeated timeline in user discussions was that issues began around 8:45 AM IST. Posts then suggested services broadly recovered by around 10:00 AM IST for many users. Even after that window, some users said performance remained inconsistent into late morning. The idea of a sharp start and partial recovery was common across platforms, which is typical of capacity-related incidents. Several users noted that early market windows can be stress tests because many accounts log in and refresh charts simultaneously. Others pointed to the expiry-day effect, where rapid quote updates and frequent order modifications can intensify load. Users also compared their experience across devices, with some trying the web platform to check whether the mobile app was the bottleneck. While social posts are not a definitive incident report, the timing pattern was consistent in the conversation.

Why expiry sessions amplify reliability problems

The most commonly cited explanation in these discussions was server overload during peak market hours. Users repeatedly connected the freeze to expiry days and major market events, when traffic surges. In that environment, delayed chart updates can be more than cosmetic because traders rely on live data to manage entries and exits. Several commenters said the risk rises when positions are leveraged or time-sensitive, which is common in F&O strategies. People also pointed out that latency feels worse near the open and close, when many users place orders at once. A few posts noted that even if an exchange is functioning normally, a broker’s front end can still struggle under load. Others discussed how a single dependency, such as a cloud networking layer, can ripple into app performance. Overall, the user narrative centered on capacity pressure rather than a one-off device bug.

What Groww attributed a withdrawal disruption to

Alongside chart and login complaints, posts also circulated details about a separate withdrawal disruption discussed online. In those user-shared summaries, withdrawals were reported to fail during equity trading hours, and some deposits were also said to fail. Groww, in statements/posts referenced in the same context, attributed that withdrawal disruption to an incident at its cloud service provider, Google Cloud Platform. The brokerage also said only a very small fraction of customers were affected. It said the issue was resolved promptly before market close. Users interpreted this as evidence that cloud-provider incidents can translate quickly into retail trading friction. The emphasis from Groww’s side, as described in the context, was that the issue was temporary and contained.

A quick table of incidents cited in discussions

The threads frequently combined multiple past reliability moments into one narrative about risk during high-volume sessions. Users referenced both broker-side issues and broader infrastructure outages that hit many websites at once. The table below reflects incidents explicitly mentioned in the provided discussion context, not a complete history.

How traders tried to verify if it was broker-specific

A repeated suggestion was to check whether the issue was limited to Groww or part of an exchange-wide disruption. Users said checking the NSE and BSE websites can help confirm whether markets are updating normally. If exchange sites show normal updates while the app is frozen, traders inferred it is more likely broker-side. If exchange data itself appears delayed, they said the root could be broader infrastructure. Some users also recommended switching from the Groww app to Groww Web to isolate whether it is app-specific. Switching devices was also mentioned as a quick test to rule out device memory constraints or an outdated build. Another commonly shared step was changing networks, such as moving from Wi-Fi to mobile data. These checks were framed as fast triage, not a guarantee of immediate recovery.

The user playbook: document first, then escalate fast

Across posts, the first step was clear: document everything immediately. Users repeatedly advised taking screenshots or screen recordings of frozen charts, error messages, failed order attempts, missing balances, or duplicate orders, along with timestamps. Several commenters said this evidence matters most if a dispute later depends on timing and price levels. If the app is unstable, they suggested trying the web platform or another device, even if only to show you attempted alternatives. The next step discussed was raising a ticket through Groww’s official support system to create an auditable trail. Some users said to contact support within 24 hours, particularly if they believe a technical failure led to financial impact. If responses are unsatisfactory, discussions mentioned escalation through the broker grievance route and SEBI SCORES, and for large losses, arbitration through NSE or BSE. One post also suggested giving Groww 15 to 30 days to respond as part of a structured complaint process.

Support channels and contact details shared by users

Users circulated multiple official contact options that can be used during disruptions. The context included Groww support email as support@groww.in and its contact page at https://groww.in/contact-us. Users also shared phone numbers: 080 4748 1507 (Mon to Sat, 9 AM to 7 PM IST) and +91-9108800604. These were framed as useful when in-app chat is unavailable or tickets are not being created due to outages. Some users said written communication is preferable because it leaves a time-stamped record. Others emphasised including order IDs, screenshots, and the exact time of the issue to reduce back-and-forth. The context also listed an address: Vaishnavi Tech Park, South Tower, 3rd Floor, Sarjapur Main Road, Bellandur, Bengaluru – 560103, Karnataka. While social sharing of contacts can be noisy, the listed channels in the context align with a typical escalation path.

What users said about reliability trade-offs versus rivals

A separate line of discussion compared Groww’s trading experience to other platforms used by active traders. Users argued that Groww’s charting and order tools, including the newer 915 terminal, lag Zerodha’s Kite for serious F&O use. They also said Groww’s research and education content feels thinner than Zerodha Varsity, based on their personal experience. In the same breath, some users pointed to well-publicized reliability incidents, including the May 2025 GTT pricing glitch and periodic login or order failures during high-volume expiry days. The context also referenced a 2025 Cloudflare-linked outage, which users used as an example of dependency risk. Separately, one cited incident described a BSE glitch during weekly expiries, with orders on Zerodha shown as “open pending,” while Groww cited connectivity issues that were fixed by noon. Taken together, the discussion shows how traders judge brokers not only on pricing and UI, but also on uptime during high-stress sessions. For many commenters, the practical takeaway was to have a documented process ready for the next disruption.