What Should You Do If Your Platform Goes Down During a Trade?

What Should You Do If Your Platform Goes Down During a Trade?

By Rami Alame (Akylles) | Trade Feeld | Intermediate | Stocks, Forex, Options

If your trading platform goes down during a trade, stop submitting orders blindly. Check whether the problem is your connection or the broker’s system, try an approved backup channel, and verify your actual positions and working orders before doing anything else. If you cannot confirm your exposure, contact the broker’s emergency trading desk. Your priority is restoring reliable information and control—not guessing what the market or your last click has done. This article is educational only and is not financial advice.

Build your trading platform outage plan before you need it

A useful trading platform outage plan fits on one page and remains available without your trading computer. Save an offline copy on your phone and keep essential contact details somewhere accessible if that phone fails.

Include:

• Your broker’s verified emergency trading number, service hours, and account-identification requirements.
• Approved backup access, such as the broker’s mobile app or web platform.
• A separate internet connection, such as a mobile hotspot.
• Your account identifier, but not an exposed password or authentication code.
• Instructions for locating positions, executions, open orders, and order IDs.
• The broker’s rules for telephone orders, supported instruments, and applicable fees.

Test access while markets are quiet. A mobile app is not a true backup if it depends on the same failed connection. It may also share the broker’s backend, so switching devices will not fix every outage.

Ask the broker what happens to orders during disconnections. Record the answer by order type rather than assuming all orders behave alike. For broader background on brokerage accounts and investor protections, explore FINRA’s investor resources.

Diagnose the failure without multiplying orders

A frozen chart, a failed login, and a rejected order are different problems. Start by identifying what you can still trust.

1. Check whether unrelated websites load. If they do not, test another connection.
2. Open the broker’s approved app or website through a known bookmark—not an unsolicited support link.
3. Check the broker’s official service notices, if available.
4. Compare positions, order status, and executions across available broker channels.
5. Record the last confirmed event: an acknowledged order, a fill, a cancellation, or simply a submitted request.

An independent quote feed can help reveal a frozen display, but it cannot prove whether your order executed. Quotes may also be delayed or reflect a different venue.

A missing confirmation is not proof that an order failed. Your instruction might have reached the broker even though the response never reached you. Repeated clicks can create duplicate orders.

Treat an “internet failure open position” incident as a verification problem first. Restore a reliable route to the account before treating an empty or stale screen as an accurate statement of exposure.

Know which orders survive—and what they cannot guarantee

Ask specifically about server side stop orders. These are generally held away from your local device, at the broker or another supported execution layer. They may remain active when your computer disconnects, but their operation still depends on the systems holding and processing them.

Some conditional orders, trailing stops, scripts, and automated strategies run locally. Others are broker-hosted. The feature name alone does not tell you which arrangement applies.

Also distinguish an order being active from an outcome being guaranteed:

• A stop-market order generally becomes a market order after its trigger conditions are met. Its execution price is not guaranteed.
• A stop-limit order sets a limit on the acceptable execution price, but it may remain unfilled.
• A cancellation request does not establish that an order was canceled. The order may execute before the cancellation takes effect.
• Linked orders may have different rules for partial fills, cancellations, and supported sessions.

Instrument details matter. Stock orders may have session restrictions, and trading halts can prevent immediate execution. In retail forex, ask which broker prices trigger stops and how liquidation and financing rules apply. Another provider’s chart is not necessarily your broker’s executable market.

For options, verify the underlying, expiration, strike, call or put, quantity, and whether each leg opens or closes a position. Closing one leg can leave materially different exposure. Exercise, assignment, and broker cutoff rules still matter during an outage; consult the options disclosures and educational material available through OCC.

Use the broker emergency trade desk precisely

Save the broker emergency trade desk number before a problem occurs. During a widespread disruption, access may be delayed, and the desk may rely on systems affected by the same incident. It is a backup channel, not a promise of immediate execution.

Once authenticated, first ask the representative to confirm:

• Current positions and quantities.
• Working, partially filled, canceled, and rejected orders.
• Recent executions and any unresolved submission you identify.
• Whether the requested instrument can currently be handled by phone.

Then communicate one instruction at a time. Specify the account, instrument, side, quantity, order type, and any applicable limit or duration. For options, identify every contract detail and whether the instruction concerns a complete spread or individual legs.

Ask the representative to read the instruction back. Request an order reference and distinguish received, accepted, and executed. These are not interchangeable statuses.

Keep a written record of the contact time, instructions, and confirmations. Never give an unsolicited caller remote access or authentication codes because they claim to be resolving an outage.

Worked example: a frozen stock position

Hypothetical example: all quantities and prices below are invented round numbers for education, not live market data.

A trader holds 100 shares bought at $50. The broker previously confirmed a server-held sell stop-market order for 100 shares with a $48 trigger. The trader clicks a separate market sell for 100 shares just as the platform freezes. No confirmation appears.

The dangerous assumption is that nothing happened. Submitting another sell could create an unintended short position where permitted, or lead to a rejection or another order conflict. The existing stop also needs attention if it is not linked to the exit instruction.

A disciplined response is:

1. Note the approximate submission time and any visible order reference.
2. Connect through the broker’s mobile app using mobile data.
3. Check positions, executions, and both sell orders—not just the chart.
4. If records remain unclear, ask the emergency desk to reconcile them before submitting another exit.
5. If the market sell filled, verify whether the original stop remains working and arrange cancellation if needed. Confirm the cancellation rather than assuming it succeeded.

The $48 stop trigger does not guarantee a $48 execution. The outage does not establish that either sell order failed. The lesson is to reconcile position plus orders together: a flat position with an unintended working order is not a fully resolved incident.

Common mistakes that make outages worse

Repeatedly pressing buy, sell, or cancel. Each request may reach the broker. Use order IDs and confirmed statuses to resolve uncertainty.

Assuming another account provides a clean exit. An opposite trade elsewhere does not close the original position. It can introduce basis differences, margin requirements, borrowing constraints, and separate liquidation risks.

Trusting a displayed balance over execution records. Screens can update at different times. Ask the broker to reconcile discrepancies rather than choosing whichever screen looks reassuring.

Ignoring residual options legs or pending orders. A partial execution can leave a different position from the one intended. Review each leg and every remaining instruction.

Assuming the broker will reimburse a loss. Preserve evidence and use the broker’s complaint process, but do not treat compensation as certain. General investing education and fraud-awareness resources are available at Investor.gov.

Step-by-step outage checklist

1. Pause new submissions. Do not repeat an instruction whose status is unknown.
2. Capture evidence. Note the time, error message, last confirmed position, and relevant order IDs. Avoid exposing account details in public screenshots.
3. Test the connection. Try a separate network and an approved backup interface.
4. Verify exposure. Reconcile positions, executions, pending orders, and linked orders.
5. Escalate uncertainty. Contact the verified emergency desk if account state or order status remains unclear.
6. Give precise instructions. Confirm instrument, side, quantity, order type, and any cancellation dependency.
7. Confirm the result. Obtain execution or cancellation confirmation, not merely acknowledgment of receipt.
8. Review after recovery. Check residual orders, options legs, buying power, and broker records. Document discrepancies promptly through the broker’s official process.

Rehearse this sequence without submitting live orders. Check login recovery and authentication backups as carefully as internet access. A working network is not enough if you cannot authenticate.

The bottom line

An outage response starts with verified account information, not faster clicking. Know where your orders live, maintain independent access where possible, and have a clear route to the broker’s emergency desk. No backup eliminates execution risk, but preparation helps prevent avoidable operational mistakes.

After an incident, update your plan around what actually failed. Keep learning free on Trade Feeld, and follow @tradefeeld on X for more trading education. The practical goal is a repeatable process you can follow under pressure.