Trading Platform Outage: Build a Contingency Plan Before Access Fails

Trading Platform Outage: Build a Contingency Plan Before Access Fails

বাংলায় পড়ুন

Learning objective

Build a practical response plan for the moment a broker app, trading terminal, internet connection or market-data feed becomes unavailable. The aim is to preserve control: verify what is live, avoid duplicate orders and act in a fixed priority order.

An outage is an operational-risk event. It can interrupt order entry, cancellation, position visibility, funding or withdrawals while prices continue to move. The Financial Conduct Authority says operational disruption can prevent consumers from accessing accounts and can threaten market integrity. Its resilience guidance stresses severe-but-plausible testing, clear communication plans and up-to-date contact details.

Your personal plan is much smaller than a firm's resilience programme, but the logic is useful: identify critical functions, map dependencies, prepare alternatives and rehearse the response.

Step 1: map the single points of failure

Write down every dependency between you and the market:

• broker account and execution venue;
• desktop platform, web portal and mobile app;
• market-data source;
• internet connection, mobile data and electricity;
• authentication device, email and password manager;
• broker dealing desk, support line and status page;
• cash, margin and settlement arrangements.

Two apps on the same phone and network are not independent backups. A second device helps only if it can authenticate and connect. A second broker may reduce access concentration, but it creates separate funding, tax, margin and reconciliation work.

Step 2: define the order of action

Use a written sequence so urgency does not turn into random clicking:

1. Confirm the failure. Check another device, connection and the broker's official status channel.
2. Record the evidence. Note the time, symbols, positions, order references and error messages. Take screenshots if possible.
3. Verify authoritative order status. A frozen screen does not prove that an order failed, filled or cancelled.
4. Contact the broker through a pre-verified route. Use the number or channel stored before the event, not a number found in a rushed social-media search.
5. Prioritise risk. Deal first with orders or positions that can breach a predefined loss, margin or exposure limit.
6. Reconcile after access returns. Compare confirmations, fills, cash and open orders before placing anything new.

Do not keep pressing submit or cancel while the status is unknown. Every retry can become another live instruction when connectivity returns.

Worked example

A hypothetical trader holds three open positions and has two resting orders before a volatile session. At 09:17, the web platform freezes. One cancellation request shows as pending and the mobile app will not load.

The trader follows the prepared plan:

• switches from home broadband to mobile data and checks the broker's official status page;
• opens the offline position sheet containing quantities, average prices and order references;
• calls the broker's pre-saved dealing number and asks for the authoritative status of both resting orders;
• avoids sending replacement orders until the original instructions are confirmed;
• handles the position nearest its loss limit first;
• logs the name or reference of the support contact, time and instructions given;
• after recovery, downloads the execution report and reconciles positions, cash and fees.

Suppose the first order had already filled although the frozen screen showed it as pending. Sending the same order through a second channel would have doubled the exposure. The useful backup was verified information and a fixed decision sequence, not simply another order button.

Step 3: set outage-specific risk limits

Normal stop-loss logic assumes the trading system can receive and execute instructions. Add limits for impaired access:

• maximum position size you can tolerate without live monitoring;
• maximum aggregate exposure during known maintenance;
• minimum free margin and cash buffer;
• instruments you will not hold through illiquid periods;
• a time threshold for escalating to the dealing desk;
• a rule for cancelling stale orders after reconciliation.

A stop order is not a guaranteed exit price, and an outage may delay your ability to change it. Size the position so that a gap beyond the stop remains survivable.

Step 4: prepare an offline recovery pack

Keep a secure, regularly updated record that remains usable when the platform is unavailable:

• broker legal name and account identifier;
• official dealing, support and complaints contacts;
• open positions, contract specifications and order references;
• authentication recovery method;
• backup power and connectivity instructions;
• personal exposure limits and response sequence;
• a blank incident log.

Protect this information. Do not store plain-text passwords or recovery codes in the same sheet. Confirm whether telephone dealing is available, what identity checks apply and whether additional charges may be imposed.

Step 5: test a severe-but-plausible scenario

Run a short drill outside market stress. Assume the main screen and home internet fail together. Check whether you can:

• reach the broker's official status and contact channels;
• identify every live position and order from independent records;
• authenticate on an alternate device;
• explain clearly which instruction you want confirmed or changed;
• distinguish broker failure from a local data-feed problem;
• document the result and fix any gap.

The FCA's operational-resilience observations emphasise testing, mapping dependencies, communication plans and post-incident learning. Those are firm-level expectations, but traders can use the same habits at a personal scale.

Hedging elsewhere can add a second problem

Opening an opposite position at another broker may appear to neutralise risk, but it can create basis risk, different contract sizes, funding costs and two-sided execution uncertainty. If the original position has already closed, the new hedge becomes a fresh directional trade. Treat cross-venue hedging as a pre-designed procedure with position mapping and limits, not an improvised response.

Common mistakes

• Assuming a frozen screen means an order did not reach the market.
• Repeatedly submitting or cancelling the same instruction.
• Searching social media for an unverified support number.
• Depending on one device, one network or one authentication method.
• Holding position sizes that require continuous access to remain tolerable.
• Opening a hedge elsewhere without checking the original fill.
• Trading again before reconciling orders, positions, cash and fees.
• Keeping a plan that has never been tested.

Practical checklist

• Save official broker contacts and the status-page address offline.
• Record open positions and order references at defined intervals.
• Maintain tested backup internet, power and device access.
• Set maximum outage exposure, margin and escalation limits.
• Verify order status before resubmitting through another channel.
• Log times, instructions, confirmations and support references.
• Reconcile the full account after service returns.
• Review the incident and update the plan.

Sources

• FCA: Operational resilience
• FCA: CrowdStrike outage lessons for operational resilience
• FCA: Operational resilience insights and observations one year on

This tutorial was prepared with AI-assisted research and writing under The Money Man editorial workflow. It is educational information, not personalised investment advice. Broker procedures, protections, market rules and telephone-dealing availability vary; verify them directly with your provider. Trading losses can exceed planned levels during gaps, outages and illiquid conditions.