Prop-Firm Platform Status: A Pre-Trade Checklist

Systems verified: September 27, 2026, 7:07 AM MDT · Next review: September 28, 2026, or sooner if a monitored system changes

Short answer: Do not decide that a prop account is ready from one green badge. Before the session, check the prop firm, the actual execution platform or connection, the exchange session for the exact contract, and the account-specific dashboard. If those layers disagree, a status narrative says “resolved” while a component remains degraded, or the dashboard does not match the public rule, pause and preserve the evidence instead of testing the system with a live order.

Use this order:

firm → platform → exchange → account → decision

Each layer answers a different question. A functioning chart does not prove order routing is healthy. An operational platform does not prove the firm has enabled the account. A normal exchange session does not override a firm restriction.

1. Start with the prop firm’s official status surface

Use the firm’s status page or current support announcement, not a community screenshot or a trader’s isolated connection report. Record the check time and read both the overall label and any open incident detail.

Look for separate component states for:

• dashboard or login access;
• trading and order entry;
• market data;
• risk or liquidation controls;
• account provisioning;
• payouts or payment services;
• the specific platform integration you use.

An old incident can remain visible after service returns. That is why the incident timeline, current component table, and present incident state must agree before you call the issue closed. If they do not, classify the result as ambiguous, not operational.

2. Check the execution platform independently

Many firms depend on a platform or connection operated by another company. Open that provider’s official status page even when the firm reports no incident.

Tradovate’s first-party surface separates frontend access, execution, risk and routing, simulation, market data, reporting, symbol lookup, account creation, payment services, and named prop integrations. TradingView separates its website, data feeds, alerts, Pine studies and strategies, trading, charts, and other services. Those component lists matter because the symptom you see may affect only one layer.

At the September 27 check, Tradovate listed all monitored services and named prop integrations as UP, and TradingView reported all systems operational. Those are point-in-time observations, not a promise for the next session. Recheck close to the time you plan to trade.

3. Confirm the exchange session and exact contract

Platform health does not tell you whether a contract is open, paused, in pre-open, or closed. CME explains that:

• pre-open permits order entry, modification, and cancellation but no matching;
• open permits continuous matching;
• paused stops matching while allowing cancellation;
• closed ends the trade date and eliminates applicable day and GTD orders.

Check the exact product and source timezone. Holiday schedules, maintenance windows, new 24/7 products, and contract-specific sessions can differ from the normal weekly pattern. Do not convert a time until you have saved the source timezone and date.

Then verify the contract month and symbol supported by the firm. A chart for one contract can update while an old or unsupported symbol rejects an order.

4. Verify the account itself

Open the account dashboard and capture the current state before the session. Confirm:

1. account name and stage;
2. enabled platform or connection;
3. current balance and loss-limit reference;
4. maximum position size or scaling tier;
5. permitted products and session restrictions;
6. any banner, lock, compliance review, or pending adjustment;
7. open positions and working orders.

The public help center describes a program. The dashboard should identify what is assigned to the actual account. If a public table and account display conflict, do not choose the more favorable number. Save both and request written clarification.

5. Use one decision table

One green layer never cancels a red, degraded, locked, paused, or contradictory layer.

6. Save a small pre-trade evidence packet

Before a high-risk session, save:

• firm status page and timestamp;
• platform status page and component state;
• exchange hours or market-state source for the exact contract;
• dashboard account name, stage, balance, limits, and enabled connection;
• open positions and working orders;
• any firm banner, email, or support notice that changes the session.

Keep uncropped originals. If an incident later affects you, this packet establishes what the official systems and your account displayed immediately before the session.

What not to do

• Do not place a small order merely to test whether execution works.
• Do not repeatedly cancel and replace an order during degraded service.
• Do not infer that charts, login, and order routing share one status.
• Do not treat a social post as stronger than the firm, platform, or exchange source.
• Do not assume “resolved” in narrative text closes an incident when current component metadata says otherwise.
• Do not switch accounts or connections to work around a restriction without written firm approval.

If trouble begins after you trade, stop creating new exposure and move to the existing outage-response guide for position verification, evidence capture, and one factual support case.

A two-minute session check

The routine is deliberately short:

1. Read the firm status page.
2. Read the platform component page.
3. Confirm the exchange state and exact symbol.
4. Capture the account dashboard.
5. Resolve every mismatch before placing an order.

The goal is not to predict every outage. It is to avoid entering a session when the available first-party evidence already says the system, market, or account is not ready.

Frequently asked questions

Does a green chart mean I can trade?

No. Chart data, login, order entry, execution, risk controls, and the account itself can have different states. Verify the layer that actually routes and governs the order.

What if the incident text says resolved but a component still says degraded?

Treat the result as ambiguous. Save both signals and wait for a consistent first-party update before using the affected service.

Should I place a micro contract to test the platform?

No. A test order creates real account exposure and may be affected by the same execution problem. Use status sources and the account dashboard instead.

Which timezone controls the exchange schedule?

Use the timezone published by the exchange or firm. Convert it only after saving the exact date and source timezone, especially around holidays and daylight-time changes.

What if the firm and platform both show operational but my account is locked?

The account-specific state controls. Do not trade or try to bypass the lock; capture it and contact the firm through its official support path.

How often should I repeat this check?

Check before the trading week, before a high-impact or shortened session, after maintenance, after changing platforms, and whenever an official incident or account banner appears.

First-party sources

• Topstep system status — checked September 27, 2026, 7:07 AM MDT; no new September 27 incident, while the September 22 incident narrative and component metadata remained inconsistent. Used as an ambiguity example only, not proof of full recovery.
• Tradovate system status — checked September 27, 2026, 7:07 AM MDT; monitored access, execution, risk, data, reporting, account, payment, and named prop-integration services displayed UP.
• TradingView system status — checked September 27, 2026, 7:07 AM MDT; all listed systems displayed operational.
• CME Group trading hours — checked September 27, 2026, 7:07 AM MDT; official definitions for pre-open, open, paused, and closed states plus the 2026 holiday schedule.
• CFTC press releases — checked September 27, 2026, 7:07 AM MDT; no September 27 release and no new directly applicable prop-firm platform emergency found.