Tradier Outage History

Tradier is up right now

Tradier had 43 outages in the last 2 years totaling 46h 36m of downtime — averaging 1.8 incidents per month.

There were 43 Tradier outages since October 18, 2024 totaling 46h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.tradier.com

Minor August 17, 2026

Elevated 500 errors in Paper Trading

Detected by Pingoru
Aug 17, 2026, 06:51 PM UTC
Resolved
Aug 17, 2026, 02:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 17, 2026, 06:51 PM UTC

    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.

Read the full incident report →

Critical August 13, 2026

Paper tradier Unavailable

Detected by Pingoru
Aug 13, 2026, 01:00 PM UTC
Resolved
Aug 13, 2026, 03:30 PM UTC
Duration
2h 30m
Affected: Paper Trading
Timeline · 3 updates
  1. identified Aug 13, 2026, 02:23 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Aug 13, 2026, 04:20 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 13, 2026, 04:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 12, 2026

Increased Errors with Order Processing in Paper Trading

Detected by Pingoru
Aug 12, 2026, 04:45 PM UTC
Resolved
Aug 12, 2026, 11:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 12, 2026, 04:45 PM UTC

    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.

Read the full incident report →

Minor August 5, 2026

Increased Error Rate in Paper Trading

Detected by Pingoru
Aug 05, 2026, 12:00 PM UTC
Resolved
Aug 05, 2026, 03:30 PM UTC
Duration
3h 30m
Affected: Paper Trading
Timeline · 3 updates
  1. investigating Aug 05, 2026, 02:50 PM UTC

    We are currently investigating this issue.

  2. monitoring Aug 05, 2026, 03:07 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 05, 2026, 04:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 3, 2026

Elevated Errors in Paper Trading

Detected by Pingoru
Aug 03, 2026, 01:30 PM UTC
Resolved
Aug 03, 2026, 03:30 PM UTC
Duration
1h 59m
Affected: Paper Trading
Timeline · 3 updates
  1. investigating Aug 03, 2026, 02:34 PM UTC

    We are currently investigating this issue.

  2. monitoring Aug 03, 2026, 03:02 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 03, 2026, 04:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 28, 2026

Market Data Latency and Returns

Detected by Pingoru
Jul 28, 2026, 01:30 PM UTC
Resolved
Jul 28, 2026, 04:00 PM UTC
Duration
2h 30m
Affected: Market Data
Timeline · 3 updates
  1. investigating Jul 28, 2026, 02:49 PM UTC

    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.

  2. monitoring Jul 28, 2026, 05:43 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 28, 2026, 07:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 9, 2026

Website Intermittent iIssue

Detected by Pingoru
Jul 09, 2026, 03:19 PM UTC
Resolved
Jul 09, 2026, 03:42 PM UTC
Duration
22m
Affected: Web Sites
Timeline · 4 updates
  1. identified Jul 09, 2026, 03:28 PM UTC

    The issue has been identified and a fix is being implemented.

  2. identified Jul 09, 2026, 03:28 PM UTC

    Website and Balance issues have been identified and a fix is being implemented

  3. monitoring Jul 09, 2026, 03:39 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jul 09, 2026, 03:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 15, 2026

Performance Degradation

Detected by Pingoru
May 15, 2026, 05:00 PM UTC
Resolved
May 15, 2026, 06:20 PM UTC
Duration
1h 19m
Affected: Market Data
Timeline · 2 updates
  1. identified May 15, 2026, 06:20 PM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved May 15, 2026, 06:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 22, 2026

OMS Degrade Performance

Detected by Pingoru
Apr 22, 2026, 02:06 PM UTC
Resolved
Apr 22, 2026, 01:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 22, 2026, 02:06 PM UTC

    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.

Read the full incident report →

Major April 16, 2026

Degrade Performance in Order Submission and Modification

Detected by Pingoru
Apr 16, 2026, 04:36 PM UTC
Resolved
Apr 16, 2026, 04:53 PM UTC
Duration
17m
Affected: Trading
Timeline · 4 updates
  1. investigating Apr 16, 2026, 04:45 PM UTC

    We are currently investigating this issue.

  2. identified Apr 16, 2026, 04:47 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 16, 2026, 04:49 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 16, 2026, 04:53 PM UTC

    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.

Read the full incident report →

Notice March 6, 2026

Elevated API Errors

Detected by Pingoru
Mar 06, 2026, 08:44 PM UTC
Resolved
Mar 06, 2026, 09:20 PM UTC
Duration
35m
Timeline · 1 update
  1. resolved Mar 06, 2026, 08:44 PM UTC

    Between 15:20 and 15:31, the Tradier API experienced elevated errors for some users, which may have resulted in slow order response or some orders failing. This was resolved quickly by our team to minimize impact. If you have any trade-related issues that you need assistance addressing, please reach out to the brokerage support team at [email protected] or (980) 272-3880.

Read the full incident report →

Minor February 13, 2026

Paper trading orders remaining pending longer than expected

Detected by Pingoru
Feb 13, 2026, 02:30 PM UTC
Resolved
Feb 13, 2026, 03:53 PM UTC
Duration
1h 23m
Affected: Paper Trading
Timeline · 3 updates
  1. investigating Feb 13, 2026, 02:41 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 13, 2026, 03:20 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 13, 2026, 03:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 16, 2026

Elevated errors and pending orders

Detected by Pingoru
Jan 16, 2026, 03:30 PM UTC
Resolved
Jan 16, 2026, 05:10 PM UTC
Duration
1h 39m
Affected: Paper Trading
Timeline · 4 updates
  1. investigating Jan 16, 2026, 03:47 PM UTC

    We are currently investigating this issue.

  2. identified Jan 16, 2026, 03:47 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jan 16, 2026, 04:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jan 16, 2026, 05:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 9, 2026

Elevated Errors

Detected by Pingoru
Jan 09, 2026, 04:00 PM UTC
Resolved
Jan 09, 2026, 11:32 PM UTC
Duration
7h 32m
Affected: Paper Trading
Timeline · 4 updates
  1. investigating Jan 09, 2026, 07:01 PM UTC

    We are currently investigating this issue.

  2. identified Jan 09, 2026, 07:01 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jan 09, 2026, 08:53 PM UTC

    We are continuing to work on a fix for this issue.

  4. resolved Jan 09, 2026, 11:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 9, 2026

Processing Delays - Orders

Detected by Pingoru
Jan 09, 2026, 03:40 PM UTC
Resolved
Jan 09, 2026, 06:42 PM UTC
Duration
3h 1m
Affected: Trading
Timeline · 5 updates
  1. investigating Jan 09, 2026, 03:48 PM UTC

    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.

  2. identified Jan 09, 2026, 04:00 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jan 09, 2026, 04:00 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Jan 09, 2026, 04:00 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jan 09, 2026, 06:42 PM UTC

    We are continuing to monitor for any further issues.

Read the full incident report →

Minor January 6, 2026

Paper Trading orders stuck in pending status

Detected by Pingoru
Jan 06, 2026, 05:44 PM UTC
Resolved
Jan 06, 2026, 04:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jan 06, 2026, 05:44 PM UTC

    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.

Read the full incident report →

Major January 2, 2026

Paper Trading experiencing elevated errors and pending order status.

Detected by Pingoru
Jan 02, 2026, 03:30 PM UTC
Resolved
Jan 02, 2026, 05:16 PM UTC
Duration
1h 46m
Affected: Paper Trading
Timeline · 3 updates
  1. identified Jan 02, 2026, 05:00 PM UTC

    The issue has been identified

  2. monitoring Jan 02, 2026, 05:09 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 02, 2026, 05:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 29, 2025

Index data outage

Detected by Pingoru
Dec 29, 2025, 01:43 PM UTC
Resolved
Dec 29, 2025, 06:13 PM UTC
Duration
4h 30m
Affected: Market Data
Timeline · 4 updates
  1. investigating Dec 29, 2025, 04:43 PM UTC

    We are currently investigating a loss in index data.

  2. identified Dec 29, 2025, 04:44 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Dec 29, 2025, 06:00 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Dec 29, 2025, 06:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 10, 2025

Pending orders in Paper Trading

Detected by Pingoru
Dec 10, 2025, 07:45 PM UTC
Resolved
Dec 10, 2025, 08:30 PM UTC
Duration
45m
Affected: Paper Trading
Timeline · 2 updates
  1. investigating Dec 10, 2025, 08:06 PM UTC

    We are currently investigating this issue.

  2. resolved Dec 10, 2025, 08:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 7, 2025

Paper Trading Pending Orders

Detected by Pingoru
Nov 07, 2025, 04:31 PM UTC
Resolved
Nov 07, 2025, 05:03 PM UTC
Duration
31m
Affected: Paper Trading
Timeline · 3 updates
  1. investigating Nov 07, 2025, 04:53 PM UTC

    We are currently investigating this issue.

  2. monitoring Nov 07, 2025, 04:53 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 07, 2025, 05:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 22, 2025

Paper trading orders pending

Detected by Pingoru
Oct 22, 2025, 03:15 PM UTC
Resolved
Oct 22, 2025, 04:33 PM UTC
Duration
1h 18m
Affected: Paper Trading
Timeline · 4 updates
  1. investigating Oct 22, 2025, 03:39 PM UTC

    We are currently investigating this issue.

  2. identified Oct 22, 2025, 03:39 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 22, 2025, 04:05 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 22, 2025, 04:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025

AWS Outage effecting market data servers

Detected by Pingoru
Oct 20, 2025, 04:45 PM UTC
Resolved
Oct 20, 2025, 08:42 PM UTC
Duration
3h 57m
Affected: Market Data
Timeline · 2 updates
  1. identified Oct 20, 2025, 05:03 PM UTC

    The issue has been identified and a fix is being implemented.

  2. resolved Oct 20, 2025, 08:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 14, 2025

Elevated API Errors in Sandbox

Detected by Pingoru
Oct 14, 2025, 05:00 PM UTC
Resolved
Oct 14, 2025, 06:26 PM UTC
Duration
1h 25m
Affected: Paper Trading
Timeline · 2 updates
  1. investigating Oct 14, 2025, 06:25 PM UTC

    We're experiencing an elevated level of API errors and are currently looking into the issue.

  2. resolved Oct 14, 2025, 06:26 PM UTC

    This incident has been resolved.

Read the full incident report →