Market Insight
Zerodha Down? Traders Say BSE F&O Orders Froze Today
Quick Answer: Is Zerodha Down Today?
Status: Resolved. Yes, there was a brief, exchange-wide issue today (September 10, 2026) affecting price updates and order placement for select BSE F&O contracts — not just on Zerodha, but across multiple brokers. Zerodha's official bulletin marked it resolved by 12:34 PM IST. Some traders reported longer disruption (15-20 minutes) on specific contracts like SENSEX 75000 CE. Full details, timeline, and what to do if it happens again are below.
What Happened, According to the Official Bulletin
For a brief window today, traders attempting to place or modify orders on select BSE F&O contracts ran into a problem that had nothing to do with their specific broker's app or servers. According to Zerodha's official market bulletin, an issue affecting price updates and order placement on the BSE hit "across brokers" — meaning multiple trading platforms, not just one — for some F&O contracts, before being resolved a short time later.
Zerodha posted the issue on its bulletin at 12:20 PM IST on September 10, 2026, describing it plainly: "There is an issue with price updates and order placement across brokers for some F&O contracts on BSE. We're in touch with the exchange to resolve this at the earliest." A follow-up update at 12:34 PM marked the issue as resolved — a total disruption window of approximately 14 minutes.
The critical detail in that initial post is the phrase "across brokers." This wasn't described as an issue specific to Zerodha's own systems — it was framed, from the outset, as an exchange-side problem affecting multiple brokers simultaneously, which is a meaningfully different situation from a single platform's app crashing or its servers going down.
A Gap Between the Official Timeline and Trader Reports
Zerodha's bulletin frames the issue as resolved within roughly 14 minutes, based on the gap between its 12:20 PM alert and its 12:34 PM resolution update. However, separately, traders posting on X reported that the SENSEX 75000 CE contract specifically — the same contract examined in this platform's earlier coverage of expiry-day option pricing — remained frozen for approximately 15-20 minutes, a window that does not cleanly align with the company's stated resolution time.
This kind of gap between an official company timeline and individual trader reports is not unusual during exchange-connectivity incidents, and it's worth understanding why rather than treating either figure as simply wrong. A broker's bulletin typically reflects when the underlying systemic issue was addressed at the infrastructure level — the point at which the exchange or connectivity problem causing the disruption was fixed. That is not always the same moment every individual trader's screen, price feed, or specific contract's order book actually reflects normal, live data again. Cached prices, feed propagation delays, or contract-specific liquidity conditions can mean a resolved system-wide issue still leaves visible effects — a frozen quote, a stale price — on specific contracts for some additional period after the official "resolved" timestamp.
It's also worth noting that trader reports on social media during live incidents, while often genuinely reflecting real, frustrating experiences, are inherently harder to independently verify than an official company bulletin with a timestamped record. Neither source should be dismissed, but they answer subtly different questions: the bulletin describes when Zerodha considered the systemic issue fixed; trader reports describe when specific individuals experienced normal functionality returning on their own screens.
Why "Across Brokers" Matters
When a trading issue is confined to a single broker's platform, the usual troubleshooting options exist: switch to a different device, try the web interface instead of the app, or in some cases route the same order through a different broker account entirely, if a trader happens to maintain one.
When the issue originates at the exchange level — or in the connectivity layer between multiple brokers and the exchange — none of those individual workarounds help, because the underlying problem sits upstream of any single broker's own infrastructure. This is precisely why Zerodha's bulletin specifically flagged the issue as affecting "brokers" in the plural, rather than describing an internal, Zerodha-specific fault.
This Is Not a New or Isolated Pattern
Exchange-side or connectivity-layer disruptions affecting BSE F&O order placement across multiple brokers have happened before, and examining that history offers useful context for how seriously to weigh today's brief incident.
In July 2023, Zerodha experienced a BSE F&O order-placement issue tied to leased-line connectivity — the physical data lines connecting the broker's systems to the exchange. During that incident, some pending orders were left in an ambiguous state (shown as "Open pending," "Cancel pending," or "Modify pending"), requiring manual reconciliation with the exchange once connectivity was restored. That same year, a separate BSE-specific outage was traced to an issue at the systems of Refinitiv, a third-party vendor providing exchange-empanelled risk-management and order-management infrastructure used by multiple brokers — again, a shared point of failure affecting more than one platform simultaneously.
Further back, in August 2019, Zerodha experienced a widely-reported outage on an F&O expiry day, when its execution management system connecting to exchanges went down for 35-40 minutes, leaving traders unable to place fresh orders during a period when the underlying market itself moved meaningfully (Nifty fell around 0.4% and Bank Nifty around 0.6% during the outage window).
Today's disruption — brief by Zerodha's own account, though trader reports suggest it may have run somewhat longer on specific contracts — fits a recognisable pattern: technical failures in the connectivity chain between brokers and exchanges do recur periodically, and when they originate at a shared point (an exchange system, a common vendor, a leased line), they tend to affect multiple brokers' clients at once rather than isolating to a single platform.
Why This Matters More on Some Days Than Others
The practical impact of a brief order-placement outage depends heavily on timing. An outage occurring during a calm, low-volatility period is a minor inconvenience for most traders — a delayed order, a few minutes of uncertainty. The same outage occurring during a high-volatility session, or specifically around an options expiry (as the 2019 Zerodha incident illustrates), can have real financial consequences: traders unable to exit or adjust positions while the underlying market continues moving, potentially locking in losses they would otherwise have managed differently.
This is a genuinely important distinction for RAs to communicate to F&O clients: technical outages are a real, recurring operational risk in derivatives trading, entirely separate from the market risk of the position itself — and their potential impact scales with how time-sensitive the trader's position happens to be at that specific moment.
What Traders Can Do When This Happens
Check official broker bulletins immediately, rather than relying solely on the app's own error messages, which may not clearly communicate whether an issue is broker-specific or exchange-wide. Most major brokers maintain a public bulletin or status page for exactly this purpose.
Recognise the difference between exchange-side and broker-side issues when deciding how to respond — if a bulletin explicitly states the issue affects multiple brokers, switching platforms is unlikely to help, and the more productive step is monitoring for the resolution update.
Avoid panic-driven actions during the outage window itself, particularly attempting to force through orders via alternative channels that may create duplicate or conflicting positions once systems are restored — a pattern that contributed to reconciliation complications in the 2023 incident referenced above.
Understand that brief exchange-side outages, while disruptive, are generally addressed and resolved by the broker and exchange working directly together, as reflected in Zerodha's own swift resolution timeline today — though, as noted above, some individual traders reported the practical disruption lasting somewhat longer on specific contracts.
Frequently Asked Questions
Is Kite (Zerodha's app) down right now?
No — as of the latest update, the issue has been marked resolved by Zerodha. The disruption was specific to price updates and order placement for select BSE F&O contracts, not a full platform outage.
Why is Zerodha showing an error for BSE F&O orders?
Today's specific error was traced to an exchange-side or connectivity-layer issue affecting multiple brokers simultaneously, not a fault within Zerodha's own app or servers. If you see a similar error again, check Zerodha's official bulletin at zerodha.com/marketintel/bulletin first to confirm whether it's a known, broader issue.
Does this outage affect NSE trading too?
No — today's reported issue was specific to select F&O contracts on the BSE. Zerodha's bulletin did not report a parallel issue on NSE.
What happened with BSE F&O trading today?
An issue affecting price updates and order placement for some F&O contracts on the BSE occurred across multiple brokers, according to Zerodha's official bulletin, starting at approximately 12:20 PM IST on September 10, 2026, and resolved by 12:34 PM IST — a duration of about 14 minutes.
Was this a Zerodha-specific problem? No. Zerodha's own bulletin described the issue as occurring "across brokers," indicating it originated at the exchange or connectivity level rather than within Zerodha's specific platform infrastructure.
How long did the issue last?
Approximately 14 minutes according to Zerodha's official bulletin, based on the gap between the 12:20 PM alert and 12:34 PM resolution update. However, traders reported on X that the SENSEX 75000 CE contract specifically remained frozen for approximately 15-20 minutes, a discrepancy that likely reflects the difference between a system-wide fix and individual price feeds normalizing.
Has this type of issue happened before?
Yes. Similar exchange-side or connectivity-layer disruptions affecting BSE F&O order placement across multiple brokers have occurred previously, including incidents in 2019 and 2023, with varying causes ranging from leased-line failures to third-party vendor system issues.
What should a trader do if they encounter a similar issue in the future?
Check the broker's official bulletin or status page to determine whether the issue is platform-specific or exchange-wide, avoid attempting workarounds that could create duplicate or conflicting orders, and monitor for the official resolution update before assuming normal trading has resumed.
Does a brief exchange outage like this indicate a systemic problem with BSE?
Not necessarily. Brief, quickly-resolved technical issues occur periodically across financial market infrastructure globally and are not unique to BSE specifically — the relevant factors are typically the duration of the disruption and how it's communicated and resolved, both of which were favourable in today's specific incident.
At a Glance
Aspect | Detail |
|---|---|
Date | September 10, 2026 |
Issue | Price updates and order placement disrupted for select BSE F&O contracts |
Scope | Across multiple brokers (exchange-side/connectivity issue, not broker-specific) |
Start time | 12:20 PM IST |
Resolved | 12:34 PM IST |
Duration (per Zerodha bulletin) | Approximately 14 minutes |
Duration (per trader reports on X, specific to SENSEX 75000 CE) | Approximately 15-20 minutes |
Source | Official Zerodha market bulletin |
Historical precedent | Similar multi-broker BSE F&O issues occurred in 2019 and 2023 |
Sources:
Zerodha — [Resolved] Issue with Price Updates and Order Placement on BSE
Business Standard — F&O Traders Blindsided by Technical Glitch on Zerodha's Digital Platform (2019)
Disclosure: Published by KuberHunt for informational purposes only. KuberHunt is a research distribution platform, not a Research Analyst, Investment Adviser, or broker, and does not provide investment advice. Technical outages are an operational risk separate from market risk — check your broker's official bulletin for real-time status during any disruption.
Data Accuracy / Fact-Check Note: Core incident details (timing, description) are sourced from Zerodha's official bulletin. The 2019 and 2023 historical incidents are cross-verified against Business Standard and Zerodha's own archive. The 15-20 minute trader claim on SENSEX 75000 CE could not be independently verified and is reported as attributed, unconfirmed social media commentary. The original Moneycontrol article was inaccessible; Zerodha's bulletin was used as the primary verified source instead.
Educational content, not investment advice. Markets carry risk; read the disclosures on any Reco before you act on it.