Short answer: TradingView says some users may have trouble loading charts and lists the Chart component in a partial outage. The incident was identified at 13:44:23 GMT on November 10, 2026—6:44:23 AM MST—and was still active at our 7:18 AM MST verification. TradingView separately listed Website, Data feeds, Alerts, Trading, and Watchlist as operational. If your chart does not load or update normally, pause chart-dependent decisions, confirm positions and working orders in the execution provider's own ledger, and preserve timestamps before reconnecting or escalating.
What TradingView has confirmed
TradingView's official status page labels the event “Loading issue.” Its identified update says users might experience issues with charts loading and that the team is working on a fix.
At 7:18 AM MST, the component list showed:
- Chart: Partial outage
- Website: Operational
- Data feeds: Operational
- Alerts: Operational
- Trading: Operational
- Watchlist: Operational
That is the entire verified public scope. The page did not identify a root cause, region, device, browser, symbol, exchange, broker, prop firm, or number of users affected. It also did not say that orders failed or fills changed.
Do this before your next order
If your workflow depends on TradingView's chart, use this sequence:
- Check TradingView's status page for a new update.
- Confirm the exact symbol, exchange, and contract month in the chart.
- Verify whether the chart loads and whether its displayed time and price are advancing normally.
- Open the connected execution provider's native order view or account dashboard.
- Reconcile open positions, working orders, order IDs, fills, balance, and risk fields there.
- Do not place a market order merely to test whether a chart has recovered.
- If the chart remains impaired, stop using it for trade decisions and save evidence before changing layouts, connections, or devices.
An operational Trading component does not make an impaired chart suitable for decisions. It only means TradingView reported that component operational at the time checked.
Chart evidence and execution evidence answer different questions
A loading chart can interrupt visibility without proving an order-routing or fill problem. Keep the records separate:
| Question | Best record to preserve |
|---|---|
| Did the chart fail to load or refresh? | Chart capture, full symbol, exchange, timeframe, device/browser, and local timestamp |
| Was an order submitted? | Execution provider's order ID and submitted timestamp |
| Was it accepted, rejected, canceled, or filled? | Provider order history and execution report |
| What quantity and price filled? | Provider fill record, commissions, and position ledger |
| Did an account limit or rule flag change? | Firm dashboard balance, risk fields, rule event, and support response |
| Did an alert fire incorrectly? | TradingView alert log, source symbol, condition, and timestamp |
Do not infer the execution result from a loading spinner or a later recovered chart. Use the provider ledger for the account record.
If you had an open position when the chart stopped loading
Do not assume that a frozen or missing chart means the position stopped changing. Check the execution provider's position and working-order records first. If you cannot reliably view or manage the position through an approved interface, document the state and use the provider's current incident or support process.
Capture the smallest complete evidence set:
- TradingView status-page state and update timestamp;
- chart symbol, exchange, contract month, timeframe, and visible time;
- browser/app and connection used;
- account, position, and working-order state at the provider;
- order IDs, sides, quantities, types, and timestamps;
- any fill, rejection, cancellation, balance, or risk-limit change;
- the exact local time you noticed the problem and the time it recovered for you.
Avoid repeatedly reconnecting, changing symbols, or clearing layouts before the initial state is saved. Those actions can make the timeline harder to reconstruct.
What the control checks show
At 7:18 AM MST, Topstep's status page showed all systems operational. Tradovate's current page showed its listed live, demo, execution, risk, market-data, account, payment, and named prop integrations as UP.
Those results are point-in-time controls, not proof about every account or connection. They do not expand or narrow TradingView's public incident scope. If your provider record disagrees with what you saw, preserve both records and ask each provider about the part of the workflow it controls.
When to contact TradingView versus the firm or provider
Contact TradingView when the issue is the chart loading, chart display, symbol mapping, alert, data entitlement, or TradingView connection state. Contact the execution provider or prop firm when the issue is an order ID, fill, rejection, cancellation, liquidation, balance, risk limit, or account rule.
If both systems are involved, send each party the evidence relevant to its system. A short timeline with exact timestamps is more useful than a broad claim that “the platform was down.”
Frequently asked questions
Is the TradingView chart-loading incident still active?
Yes at the November 10, 2026, 7:18 AM MST verification. TradingView listed Chart as a partial outage and said its team was working on the fix.
When did TradingView identify the issue?
The official status page shows 13:44:23 GMT on November 10, which is 6:44:23 AM MST.
Are TradingView data feeds or trading also down?
TradingView listed Data feeds and Trading as operational at verification. Its public incident message specifically described charts loading, so do not broaden the claim without a first-party update.
Does a chart-loading problem prove my fill was wrong?
No. Save the chart evidence, then use the execution provider's order ID, fill report, and account ledger to determine what happened.
Should I trade from another chart immediately?
Only after confirming the correct symbol and contract, the provider connection, account state, working orders, and the alternate chart's current data. Switching screens does not by itself reconcile an open position.
What should I check after TradingView marks the incident resolved?
Reload the status page, confirm the chart clock and price advance, verify the exact symbol and contract, and reconcile positions and working orders at the execution provider before resuming.
First-party sources
- TradingView status — checked November 10, 2026, 7:18 AM MST; “Loading issue” identified at 13:44:23 GMT, Chart partial outage, Website/Data feeds/Alerts/Trading/Watchlist operational.
- Topstep status — checked November 10, 2026, 7:18 AM MST; all systems operational.
- Tradovate status — checked November 10, 2026, 7:18 AM MST; listed services UP.
Current Firm Offers and Direct Links
Open the firm in a new tab with the recorded ComparePropFirms commercial link. Use the displayed code when applicable, and confirm the final price and terms before paying.
VAULT
Use code VAULT for the current best displayed deal.
Commercial terms verified November 2, 2026 · Recheck at checkout
Visit Lucid Trading →
EdgeProp Trading
Current code TRADE60
Use code TRADE60 for the currently displayed 60% off all EdgeProp plans; confirm the plan-specific price at checkout.
Commercial terms verified November 2, 2026 · Recheck at checkout
Visit EdgeProp Trading →
TradeDay
Current code SALE60
Use code SALE60 for the currently displayed 60% off; TradeDay 2.0 accounts are now one-time fees (no subscription), advertised from $39. Confirm the plan-specific price at checkout.
Commercial terms verified November 12, 2026 · Recheck at checkout
Visit TradeDay →
