User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 17 min ago. Last stored result reached it in 127 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 512 ms | 0 |
| Mon 18 | 0 | 0.0 | 163 ms | 0 |
| Mon 20 | 0 | 0.0 | 78 ms | 0 |
| Mon 22 | 0 | 0.0 | 61 ms | 0 |
| Tue 00 | 0 | 0.0 | 123 ms | 0 |
| Tue 02 | 0 | 0.0 | 256 ms | 0 |
| Tue 04 | 0 | 0.0 | 56 ms | 0 |
| Tue 06 | 0 | 0.0 | 183 ms | 0 |
| Tue 08 | 0 | 0.0 | 106 ms | 0 |
| Tue 11 | 0 | 0.0 | 159 ms | 0 |
| Tue 13 | 0 | 0.0 | 58 ms | 0 |
| Tue 15 | 0 | 0.0 | 79 ms | 0 |
| Tue 17 | 0 | 0.0 | 212 ms | 0 |
| Tue 20 | 0 | 0.0 | 143 ms | 0 |
| Tue 22 | 0 | 0.0 | 200 ms | 0 |
| Wed 00 | 0 | 0.0 | 61 ms | 0 |
| Wed 02 | 0 | 0.0 | 60 ms | 0 |
| Wed 05 | 0 | 0.0 | 197 ms | 0 |
| Wed 07 | 0 | 0.0 | 215 ms | 0 |
| Wed 09 | 0 | 0.0 | 110 ms | 0 |
| Wed 11 | 0 | 0.0 | 175 ms | 0 |
| Wed 13 | 0 | 0.0 | 160 ms | 0 |
| Wed 15 | 0 | 0.0 | 62 ms | 0 |
| Wed 18 | 0 | 0.0 | 232 ms | 0 |
| Wed 20 | 0 | 0.0 | 104 ms | 0 |
| Wed 22 | 0 | 0.0 | 178 ms | 0 |
| Thu 00 | 0 | 0.0 | 125 ms | 0 |
| Thu 02 | 0 | 0.0 | 143 ms | 0 |
| Thu 04 | 0 | 0.0 | 176 ms | 0 |
| Thu 06 | 0 | 0.0 | 161 ms | 0 |
| Thu 08 | 0 | 0.0 | 182 ms | 0 |
| Thu 10 | 0 | 0.0 | 64 ms | 0 |
| Thu 13 | 0 | 0.0 | 141 ms | 0 |
| Thu 15 | 0 | 0.0 | 183 ms | 0 |
| Thu 17 | 0 | 0.0 | 171 ms | 0 |
| Thu 19 | 0 | 0.0 | 87 ms | 0 |
| Thu 21 | 0 | 0.0 | 73 ms | 0 |
| Thu 23 | 0 | 0.0 | 168 ms | 0 |
| Fri 01 | 0 | 0.0 | 155 ms | 0 |
| Fri 03 | 0 | 0.0 | 95 ms | 0 |
| Fri 05 | 0 | 0.0 | 151 ms | 0 |
| Fri 07 | 0 | 0.0 | 61 ms | 0 |
| Fri 08 | 0 | 0.0 | 61 ms | 0 |
| Fri 10 | 0 | 0.0 | 136 ms | 0 |
| Fri 12 | 0 | 0.0 | 122 ms | 0 |
| Fri 14 | 0 | 0.0 | 190 ms | 0 |
| Fri 16 | 0 | 0.0 | 127 ms | 0 |
| Fri 17 | 0 | 0.0 | 73 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Tradier yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Tradier goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Tradier alerts to Slack, Discord or a webhook — free.
We track Tradier (tradier.com) as part of the AI group. Tradier brings traders, developers, and partners together with tools, infrastructure, and pricing for trading stocks, options, futures, crypto, and forex, or build on our API.
Tradier publishes an official status page at status.tradier.com; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 122 ms average, 61–242 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Tradier incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
122 ms on average over the last 24 hours (61–242 ms).
Yes, at https://status.tradier.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Tradier here at once, the problem is on Tradier's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Tradier. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.