Tradier had 43 outages in the last 2 years totaling 43h 7m of downtime — averaging 1.8 incidents per month.
There were 43 Tradier outages since March 3, 2025 totaling 43h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Order submission, update, and deletion operations in the sandbox environment are experiencing elevated levels of errors.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Before the opening of the delayed market session, and continuing for the first few hours of the session, some users received elevated levels of errors related to account balances in the paper trading environment. The inability to confirm balances in some accounts led to buying power rejections and some orders remaining in a pending state longer than expected.
Paper trading is seeing intermittent increased error levels
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
The paper trading system suffered server-side issues in relation to order processing, leading to users getting elevated levels of 500 errors when submitting, modifying, and cancelling paper trades. This did not affect live trading, and all other simulation environment endpoints such as balances, market data, etc remain accessible. The errors reduced significantly, and the issue was marked resolved as of 11:38 ET.
We are currently investigating this issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
During the first part of the morning session, we observed elevated errors in the paper trading system, with some users receiving HTTP 500 errors when submitting or modifying orders and others having orders remain in a pending state longer than expected. We worked with our OMS partner to resolve this issue and clear all pending paper trading orders. Live trading was not affected.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are seeing higher-than-normal latency on market data services and some impact on updates for /options/chains and /markets/timesales/ data. These services are not down but are showing slower response times and some lagging updates to their data while subsequent calls retrieve fully updated data. Streaming and Quotes have shown no indication of impact. We are investigating the root cause of this issue and working to resolve it for all users. If you need assistance with a trading impact, please reach out to the brokerage support team at [email protected] or (980) 272-3880.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
Website and Balance issues have been identified and a fix is being implemented
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
During the premarket session, some users may have experienced stuck orders that were either unable to be submitted or unable to be modified due to an OMS issue. The Issue was resolved by 9:17 ET, and queued orders were processed by our brokerage team. If you need any assistance with your account or any orders that were unable to be resolved, please reach out to the brokerage support team at [email protected] or (980) 272-3880.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
Trading has been fully restored. If you need any assistance with a trade that was stuck during the partial outage, please reach out to the brokerage support team at [email protected] or (980) 272-3880.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
Our OMS infrastructure is running behind, which is causing orders to show as pending for longer than expected. No data has been lost and the system should be caught up shortly.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
The paper trading system was experiencing an abnormally high load, and some users experienced orders stuck in a pending status. We reinforced the paper trading servers and worked to address the underlying issues in order to resolve the problem. Any orders that have not cleared on their own can be cleared by the brokerage support team. Please contact them at [email protected] or (980) 272-3880.
The issue has been identified
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating a loss in index data.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.