Zerodha technical issue exchange exchange outage Kite error messages NSE BSE connectivity order not placed

The 'technical issue with the exchange' message on Zerodha Kite

From WebNotes, a public knowledge base. Last updated 21 June 2026. Reading time ~10 min.

Key facts

Typical message	Order could not be placed due to a technical issue with the exchange
What it means	An exchange-side or connectivity problem between Zerodha and NSE or BSE, not usually a fault in your own setup
First check	Whether the issue is your device or internet, the broker, or the exchange itself; try Kite web if the app fails and the reverse
When the exchange is down	All brokers are affected; there is very little a trader can do beyond waiting and checking the exchange status
If it cost you money	Notify the broker, verify execution in Console and the contract note, and file a grievance with the exact timestamps

“Order could not be placed due to a technical issue with the exchange” on Kite usually means an exchange-side or connectivity problem between Zerodha and the National Stock Exchange or the Bombay Stock Exchange , not a fault in your own device or internet; the wording points at the exchange, and when the exchange itself is down, all brokers are affected and there is very little any single trader can do until it is restored. The first job is to establish where the problem actually sits, because a local glitch, a broker issue, and an exchange outage each have a different response.

The message is unsettling because it lands at the worst moment: you are trying to place or exit an order and the order will not go through. The temptation is to hammer the button, which helps nothing and can produce duplicate orders if the issue clears mid-attempt. This article separates the three layers the failure can sit at, gives the diagnostic and the response for each, and sets out exactly how to verify whether an order executed and how to escalate if a confirmed exchange-side problem cost you money. It also flags the look-alike case, an order-specific rejection that mentions the exchange but is not an outage.

Conflict-of-interest disclosure. This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.

What the message means

The message tells you the order did not reach a tradeable state because of a problem on the exchange side or in the link between Zerodha and the exchange. Unless the issue is with your own computer, mobile, or internet connection, there is very little you can do when the problem is on the exchange side, because the order’s path runs through infrastructure neither you nor your broker controls in that moment.

Exchange outages are rare but they happen. When one does, it is not specific to your account or your broker; if the exchange is down, all brokers connected to it are affected at once. That is the defining feature of a genuine exchange-side problem: it is broad, not personal. An issue that affects only you, or only one stock, is more likely a local or order-specific problem wearing the same label, which is why the diagnostic below starts by establishing scope.

Step one: locate the layer

Three layers can produce this message, and the response differs at each. Establish which one you are in before doing anything else.

The local layer is your own device, app version, or internet. Rule it out by switching platforms: try Kite web at kite.zerodha.com if the Kite app is failing, and the app if the web is failing. If one works and the other does not, the problem was local to the failing client, not the exchange. A stale app, a dropped connection, or a browser glitch produces an exchange-flavoured error that is actually yours to fix.

The broker layer is Zerodha’s own gateway. Kite can slow during high-volatility days and around the market open and close, when order volume peaks. If both web and app fail for you but the exchange is plainly trading for others, the bottleneck may be at the broker; reloading and waiting a few minutes often clears a transient slowdown.

The exchange layer is NSE or BSE itself, or the connectivity to it. This is the case the message names directly. If the failure is broad, affecting many traders and brokers at once, the exchange or its connectivity is the cause, and the only realistic actions are to wait, monitor, and verify, because the fix is not in your or your broker’s hands.

Step two: switch platforms and verify

Once you suspect the exchange layer, do not keep retrying blindly. Switch platform first to rule out the local layer, then verify what state your orders are actually in, because a “failed” order during a glitch sometimes executed without the confirmation reaching your screen.

Double-check the order details, the order type, lot size, and trading window, in case the failure was a malformed order rather than an outage. Reload and wait, since UI glitches can resolve within minutes. Log in on both web and mobile to see whether the data syncs, which tells you whether the gap is in one client or in the account state itself. Then verify execution using independent records: check Zerodha Console for the order and trade status, read the contract note, and check the exchange website for timestamps. The point of verifying before re-placing is to avoid a duplicate position: if the original order quietly executed during the glitch, a re-placed order doubles your exposure.

Step three: when the exchange is genuinely down

If the problem is a confirmed exchange-side outage, accept that the immediate options are narrow. There is very little you can do when the problem is on the exchange side. Keep an eye on the news tab, as leading media cover such incidents quickly, and check Zerodha’s transparency and disclosures page, which logs exchange-related incidents with timestamps. An exchange that halts trading will resume it on its own schedule; orders you could not place were not placed, and orders that were resting may behave according to the exchange’s own recovery process when it comes back.

There is documented precedent for the confusion an exchange-side problem creates. In one case, traders reported losses from pending BSE derivatives orders, and the broker clarified it was an exchange-side pending status that the exchange later fixed; the public messaging was along the lines of orders that “executed but [were] not showing in position,” an issue subsequently resolved. The lesson is procedural: during an exchange-side incident, your screen may not reflect the true state, so verify against Console, the contract note, and the exchange before acting, and do not assume an order failed just because its confirmation did not arrive.

Step four: if it cost you money

If a confirmed delay or glitch caused a financial loss, the path is to document, notify, and escalate. First, establish what actually happened from the independent records: Console, the contract note, and the exchange timestamps, so you have the facts and not just the screen state. Then notify the broker, by email or phone, explaining the concern with the exact timestamps. If the matter is not resolved, file a formal grievance through the Zerodha grievance redressal framework, and for an unresolved regulatory complaint, escalate to SEBI SCORES .

Keep the loss claim precise. Name the instrument, the intended action, the time, the message you saw, and the records that show the actual outcome. A grievance grounded in timestamped records from Console and the contract note carries weight; a general complaint that “the app was down and I lost money” does not, because it cannot be reconciled against the exchange’s own log of what happened.

The look-alike: an order error that mentions the exchange

Not every exchange-flavoured error is an outage. Some are order-specific rejections that the exchange returns and that happen to mention the exchange. The clearest example is a series mismatch : a scrip that moved from one series to another is rejected when you place an order in the series it no longer trades in, and the exchange returns the rejection. That looks exchange-related but is fixed by placing the order in the live series, not by waiting out an outage.

The diagnostic is scope. A genuine technical issue with the exchange is broad: it affects many instruments and many traders at once. An error that appears only for one stock, or only for your order, is almost certainly order-specific, a series or segment error, a rejection the exchange logged, or a price-band or circuit-limit block, and is resolved by fixing the order, not by waiting. Read whether the failure is broad or narrow before deciding you are in an outage.

What to do, in order

Switch platforms first. Try Kite web if the app fails and the reverse. If one works, the problem was local, not the exchange.
Do not hammer the order. Repeated retries during a glitch help nothing and can produce a duplicate position if the original executed. Verify state first.
Verify execution independently. Check Console, the contract note, and the exchange timestamps before re-placing, because a “failed” order can have executed silently.
Confirm scope before assuming an outage. A genuine exchange issue is broad. An error for one stock only is order-specific, often a series or segment mismatch you can fix.
Document before you escalate. A loss claim needs the instrument, time, message, and the records showing the actual outcome. Notify the broker, then file a grievance with the timestamps.

External references

References

Zerodha support, Kite error messages, “technical issue with the exchange” and platform-switch guidance (accessed 21 June 2026).
Zerodha transparency and disclosures, exchange-related incident log (accessed 21 June 2026).
SEBI circulars on broker grievance redressal and the SCORES escalation framework.
NSE India and BSE India operational notices on trading-system availability.

Frequently asked questions

What does 'technical issue with the exchange' mean on Kite?

It usually means an exchange-side or connectivity problem between Zerodha and NSE or BSE, so the order could not be placed. The wording points to the exchange rather than your own device or internet, though both should be ruled out first.

What should I do when Kite shows a technical issue with the exchange?

Check whether the problem is your device, the broker, or the exchange. Try Kite web if the app is failing and the reverse, wait a few minutes and reload, verify order details, and confirm any execution in Console and the contract note before re-placing.

Is a technical issue with the exchange Zerodha's fault?

Not usually. The message points to the exchange or the connectivity between Zerodha and the exchange. When the exchange itself is down, all brokers are affected, and there is very little any single broker or trader can do until it is restored.

How do I know if NSE or BSE is actually down?

Check the exchange status and the news tab, as media cover such incidents quickly, and review Zerodha’s transparency and disclosures page, which logs exchange-related incidents with timestamps. If the exchange is down, the issue will affect brokers broadly, not just you.

What if a technical issue caused me a loss?

Notify the broker and file a grievance. Verify what actually executed in Console, the contract note, and the exchange records, then raise the matter with Zerodha by email or phone and escalate through the grievance framework with the exact timestamps if needed.

Could a technical-issue message actually be an order error?

Yes. Some errors that mention the exchange are order-specific rejections, such as a scrip that moved series. If the message appears only for one stock rather than broadly, check the series and segment rather than assuming an outage.

Reviewed and published by

WebNotes Editorial Team

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed: 21 June 2026
Conflicts of interest: WebNotes is independent. No relationship with any broker, registrar or bank named in this article.