Is TradingView Down? How to Check Status and Troubleshoot
Check the official TradingView status page for current incidents, then identify which function is failing: charts, data, login, alerts or a broker connection. This article is a troubleshooting workflow, not a live assertion that TradingView is up or down.
![Is TradingView Down? How to Check Status and Troubleshoot [Keyword: is tradingview down]](https://r2.pineify.app/img/1760853249479799180307)
First protect the order workflow
If you have live orders or positions, check them through your broker's own supported access method. A TradingView display problem does not prove the broker is unavailable, and it does not establish that an order was rejected or canceled. Verify the order status before submitting a duplicate request.
A separate broker app can help only if that broker and connection are available. Installing an unrelated platform does not give it access to your existing account. A Pine indicator on another TradingView chart is not an independent backup for a TradingView outage.
Interpret the status page carefully
Read the affected component, incident timestamp and latest update. An “operational” status is useful evidence, but a new or local issue may not yet be reflected there. Third-party reports can indicate a pattern; they do not confirm the root cause or prove that every user is affected.
Do not assume a monthly maintenance schedule, a particular weekday or a typical recovery time. Use the specific published incident or maintenance notice. If no recovery estimate is posted, none is established by this guide.
Isolate the symptom
| Symptom | Useful comparison |
|---|---|
| Entire site fails to load | Another known-working site, then another connection |
| One chart has stale prices | Another symbol and feed; check market hours and delay status |
| One custom indicator fails | Open its error message and compare a built-in indicator |
| Broker login fails | Broker's native service and its incident notices |
| Alerts appear missing | Alert status/log, expiration and device notification permissions |
A difference between Wi-Fi and mobile data narrows the problem to a path or environment. It does not uniquely identify the ISP: DNS, VPN, firewall, local software and routing are possible causes.
Try local checks in a reversible order
- Record the time, error message and affected function. Save accessible work.
- Reload the page or reopen the app. Avoid repeatedly submitting an order as part of a reload test.
- Compare the same task in an updated browser or app, and if practical on another network.
- Test extensions or VPN configuration only if the comparison points to that environment, following your device/network rules.
- If troubleshooting suggests local stored state, consider clearing TradingView-specific site data after recording settings and ensuring you can sign in again. Clearing cookies can end sessions.
Ordinary reload and hard reload shortcuts differ by browser and operating system. Use the browser's documented controls rather than treating every Command+R as a cache-bypassing reload. DNS changes and system-level commands should follow a diagnosed network issue, not be the default response to every server error.
Report enough evidence for support
Include the timezone, timestamp, device, browser/app version, exact symbol or affected component, error text and comparisons already performed. Redact credentials and unrelated account details. Check the official page for incident updates and use any notification options it currently provides.
If only one script fails, the missing-indicator troubleshooting guide separates script errors from display and data issues.