Alpaca Outage History
Uptime record, past incidents, and downtime history for Alpaca.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 53.3% | 15 | 7 |
| July 2026 | 71% | 31 | 9 |
| June 2026 | 80% | 30 | 6 |
| May 2026 | 33.3% | 15 | 10 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
May 17
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
Incorrect position updates after sell orders
Started: Aug 12, 9:39 AM
investigating
We are investigating an issue affecting some partner accounts where positions may not update correctly after sell orders.
Aug 12, 9:39 AM
Investigating position update issue after sell orders issue
Started: Aug 12, 9:39 AM
monitoring
We are continuing to conduct validation to ensure all account positions are accurately reconciled across our systems. Thank you for your patience as we work to resolve this issue.
Aug 12, 4:45 PM
monitoring
We are continuing to conduct validation to ensure all account positions are accurately reconciled across our systems. Thank you for your patience as we work to resolve this issue.
Aug 12, 4:31 PM
monitoring
We are continuing to conduct validation to ensure all account positions are accurately reconciled across our systems. Thank you for your patience as we work to resolve this issue.
Aug 12, 4:10 PM
monitoring
We are continuing to conduct validation to ensure all account positions are accurately reconciled across our systems. Thank you for your patience as we work to resolve this issue.
Aug 12, 3:42 PM
monitoring
We are continuing to conduct validation to ensure all account positions are accurately reconciled across our systems. Thank you for your patience as we work to resolve this issue.
Aug 12, 1:52 PM
monitoring
We are currently conducting validation to ensure all account positions are accurately reconciled across our systems. We will provide a final update once these verification steps are complete.
Aug 12, 1:23 PM
monitoring
We have corrected the position display issue for affected accounts. We are now reviewing a limited number of accounts that may temporarily reflect short positions as a result of earlier incorrect position data.
Aug 12, 1:02 PM
monitoring
Recovery process is complete now ,accounts should not be seeing the open position of symbol they have sold.
Aug 12, 11:07 AM
identified
Recovery process is still in the progress , we will update once it is complete.
Aug 12, 10:54 AM
identified
We are taking correction actions on affected accounts and recovery process is in progress, we will update once process is finished.
Aug 12, 10:36 AM
identified
We have isolated the cause of the position data discrepancies and are currently preparing plan for a corrective reconciliation to update the affected accounts
Aug 12, 10:22 AM
investigating
We are still investigating the issue , will share the update soon.
Aug 12, 10:15 AM
investigating
We’re investigating an issue where some accounts may continue showing a position after it has been sold, which may allow an unintended second sell.
Aug 12, 9:39 AM
Order Status Disrepancies
Started: Aug 4, 3:37 AM
monitoring
Order event processing has been resolved. We are continuing to monitor and will provide further updates if needed.
Aug 4, 6:00 AM
identified
We are continuing to work on a fix for this issue.
Aug 4, 4:02 AM
identified
The issue has been identified, and we are working on remediation path
Aug 4, 3:57 AM
identified
Root cause identified: duplicate executions were triggered during OMS reset.
Aug 4, 3:55 AM
investigating
We are currently investigating order processing irregularities. We are actively working to identify all impacted orders and coordinate a resolution. Further updates will be provided as we gather more information.
Aug 4, 3:37 AM
Delays in Trade Confirmation Emails
Started: Aug 3, 10:40 PM
monitoring
A fix has been implemented and we are seeing emails being sent as normal. We will continue to monitor to ensure there are no more delays. Thank you for your continued patience.
Aug 3, 10:54 PM
identified
We have identified an issue with delays in trade confirmation/execution emails being sent. Order execution is still functioning as normal. Our team is working on implementing a fix for this issue. Thank you for your patience and we will update you as we work towards a resolution.
Aug 3, 10:40 PM
July 2026
Issue on Overnight Trading Availability
Started: Jul 31, 7:33 AM
monitoring
The issue was isolated to the overnight trading session, during which the venue rejected new orders after the notional trading limit was exceeded. With the transition to the pre-market session, the venue is now accepting new orders, and normal order processing has resumed.
Jul 31, 8:11 AM
identified
We have identified that the issue was caused by the notional trading limit for today's overnight trading session being exceeded. As a result, the trading venue began rejecting new order requests.
Jul 31, 8:03 AM
investigating
We have temporarily paused overnight trading. Please note that we cannot accept additional overnight orders at this time.
Jul 31, 7:33 AM
JMKE IPO Withdrawal Window Notification Delay
Started: Jul 30, 12:55 PM
monitoring
Users should now be seeing JMKE allocations in their accounts, as well as IPO events. We will continue to monitor through the opening cross to ensure proper IPO functionality.
Jul 30, 4:43 PM
identified
We are continuing to work to resolve this. In the meantime, some related IPO updates may be delayed while our team works to implement the solution. Thank you for your patience and understanding and we will continue to update as things progress.
Jul 30, 3:14 PM
identified
We have identified the issue and are continuing to work to resolve this. In the meantime, some related IPO updates may be delayed while our team works to implement the solution. Thank you for your patience and understanding and we will continue to update as things progress.
Jul 30, 2:47 PM
identified
We have identified the issue and are working to resolve this. In the meantime, some related IPO updates may be delayed while our team works to implement the solution. Thank you for your patience and understanding and we will continue to update as things progress.
Jul 30, 2:10 PM
investigating
We're continuing to investigate the issue,Some related IPO updates may be delayed while we investigate. We'll share further updates as soon as possible
Jul 30, 1:30 PM
investigating
We are aware that some users may not have received the expected notification for the 60-minute withdrawal window for the Jersey Mike's (JMKE) IPO. We are actively investigating and working to resolve this. Further updates will follow shortly.
Jul 30, 12:55 PM
"last_equity" Field Showing Stale Closing Prices for Some Accounts
Started: Jul 30, 9:33 AM
investigating
The "last_equity" field returned by the "GET /v2/account" endpoint may not reflect the most recent closing price for some accounts. Values derived from this field, such as day-over-day equity change, may be affected.
Real-time equity and buying power are calculated from current market prices and are not impacted. Order entry and execution are unaffected.
This is expected to correct automatically during daily processing, ahead of the market open on Friday, July 31. If this field is material to...
Jul 30, 9:33 AM
Paper Trading: Portfolio Service Degradation
Started: Jul 24, 3:21 AM
identified
The underlying issue has been identified as an inefficient database query. The team has implemented performance optimizations, and we are monitoring the service to ensure stability and continued recovery.
Jul 24, 4:57 AM
investigating
Our team is actively investigating the issue and working to restore normal service as quickly as possible. We will provide further updates as they become available.
Jul 24, 4:23 AM
investigating
We have identified an issue affecting the Portfolio service in the paper trading environment, resulting in API errors and preventing the portfolio graph from loading in the dashboard. Our team is actively investigating the issue and working to restore normal service as quickly as possible. We will provide further updates as they become available.
Jul 24, 3:21 AM
Issue in Portfolio History service for requests covering periods prior to June 1, 2026.
Started: Jul 21, 2:49 PM
monitoring
We have fixed the issue.
Jul 21, 7:42 PM
identified
Our team is working to make the data previous to June 1, 2026 available through Portfolio History. Thank you for your continued patience as we monitor progress. We expect this to be complete by 4pm ET.
Jul 21, 5:55 PM
identified
Our team is working to make the data previous to June 1, 2026 available through Portfolio History. Thank you for your continued patience as we monitor progress. We expect this to be complete by 4pm ET.
Jul 21, 3:26 PM
investigating
We are continuing to investigate this issue.
Jul 21, 2:49 PM
investigating
We have identified an issue affecting the Portfolio History service for requests covering periods prior to June 1, 2026. Our team has identified the underlying cause and is actively working to rectify the issue. We will continue to provide updates as progress is made.
Jul 21, 2:49 PM
Intermittent Portfolio History Availability
Started: Jul 21, 9:55 AM
identified
We have identified the root cause and currently working toward mitigation.
Jul 21, 10:16 AM
investigating
We’re investigating an issue causing intermittent errors and missing data for some Portfolio History requests.
The impact appears limited to a subset of recent-date queries, and we’re actively working on a fix.
Jul 21, 9:55 AM
Issues with Account Creation and Onboarding
Started: Jul 21, 6:59 AM
monitoring
A fix has been implemented, we are monitoring for stability.
Jul 21, 8:29 AM
identified
We have deployed a fix to address related service dependencies.
Please be advised that End-of-Day positions (/v1/reporting/eod/positions) may be delayed, while we complete the necessary system mitigation.
Jul 21, 8:15 AM
identified
We are continuing to work towards a resolution.
A recent mitigation attempt was rolled back to maintain overall system stability, and our engineering team is currently refining the strategy. We appreciate your patience and will provide further updates as we progress.
Jul 21, 7:42 AM
identified
We have identified the root cause.
Our team is actively working on a remediation, and we estimate that the service will be restored within the next 30 minutes.
Jul 21, 7:09 AM
identified
We are currently investigating reports of service disruptions affecting account creation and onboarding processes.
Jul 21, 6:59 AM
Cost basis for the asset SKHYV is currently set as 0
Started: Jul 11, 3:03 PM
monitoring
The cost basis for SKHYV has now been updated in the system and is reflected correctly for affected accounts. The issue has been resolved, and no further action is required. Thank you for your patience while we completed the remediation.
Jul 11, 4:59 PM
identified
We are actively working to update the asset price for SKHYV, which will restore the correct cost basis for affected accounts. We will provide additional updates as remediation progresses.
Jul 11, 4:49 PM
investigating
Team is actively working on the recovery
Jul 11, 4:11 PM
investigating
Our team has identified the underlying issue and is actively working on a remediation. This issue is limited to the cost basis and entry price values.
Jul 11, 3:03 PM
[RESOLVED] Duplicate DIVNRA (withholding) tax entries for the QQQ dividend
Started: Jul 10, 9:44 PM
investigating
we identified that a duplicate DIVNRA (withholding tax) corporate action for QQQ was processed on a subset of accounts.
We detected the issue and cancelled the duplicate withholding tax entries to prevent further impact. Each affected account has been updated, and the corresponding SSE has been submitted to complete the reversal.
There is no impact to account balances, settlements, or client obligations. We’re monitoring through completion and will post updates as needed.
Jul 10, 9:44 PM
some accounts May See incorrect Cost Basis for Crypto Positions
Started: Jul 7, 9:23 AM
monitoring
We have confirmed that the 0 cost basis issue affecting a subset of crypto positions is no longer present. We are correcting impacted accounts that had crypto trading activity since July 3 and are validating the remaining edge cases. We will share another update as soon as this work is complete.
Jul 7, 10:21 AM
identified
We identified a subset of accounts where crypto positions were showing an incorrect zero cost basis and have applied updates for those accounts. We are continuing to review additional edge cases and validate that all impacted accounts are corrected. We will share another update shortly.
Jul 7, 9:47 AM
identified
We are making progress on the investigation and continue to work toward a resolution. Further updates will follow as more information becomes available.
Jul 7, 9:43 AM
investigating
we are currently investigating an issue where crypto positions are displaying a cost basis of $0 for Some accounts. Team is already investigating the issue and We will provide further updates as the investigation progresses.
Jul 7, 9:23 AM
For Some Accounts, Cash Withdrawable Balance Displaying Up to $0.02 More Than Available
Started: Jul 3, 12:25 PM
identified
Our team has identified the underlying issue and is currently working through the remaining edge cases to fully restore normal service. We appreciate your continued patience and will share further updates as they become available.
Jul 3, 3:07 PM
identified
Our team remains engaged in remediating the issue and is working to restore normal service as quickly as possible. We appreciate your patience and will continue to share updates as progress is made.
Jul 3, 1:46 PM
investigating
Some accounts may display a cash withdrawable balance that is slightly inflated (by approximately $0.02). This is due to a temporary issue where REG and TAF fees are not being properly accounted for in certain edge cases
Jul 3, 12:25 PM
June 2026
Account balances display issue
Started: Jun 30, 8:25 AM
investigating
We are currently investigating an issue where some user equity and account balances are incorrectly displaying as $0. Our engineering team is actively diagnosing the root cause.
Jun 30, 8:25 AM
Increased Errors and Timeouts on Broker API Endpoints
Started: Jun 26, 3:28 PM
monitoring
We are continuing to monitor for any further issues.
Jun 26, 3:41 PM
monitoring
We have identified one of the replica was stale, causing intermittent issue. The services recovered itself with in 5 mins.
Jun 26, 3:40 PM
identified
We have identified an issue that caused errors and timeouts across multiple endpoints between 10:57 AM and 11:03 AM EDT. We are seeing systems recover but are continuing to monitor for delays.
Jun 26, 3:28 PM
Journal Processing Delays — June 1, 2026
Started: Jun 1, 2:28 PM
monitoring
We are now seeing journals processing as normal and will continue to monitor them. Thank you for your continued patience.
Jun 1, 4:03 PM
identified
A fix has been implemented to improve JNLC processing times, and we are monitoring to ensure journals are processing from the queue. We will continue to provide updates as we monitor. Thank you for your continued patience.
Jun 1, 3:57 PM
identified
Our team is working to implement a fix to improve JNLC processing times. We will provide updates as we progress. Thank you for your continued patience.
Jun 1, 3:46 PM
identified
Our team is working to implement a fix to improve JNLC processing times. We will provide updates as we progress. Thank you for your continued patience.
Jun 1, 3:33 PM
identified
Our team is working to implement a fix to improve JNLC processing times. We will provide updates as we progress. Thank you for your continued patience.
Jun 1, 3:18 PM
investigating
Our team is continuing to investigate the slower than normal processing times for JNLC transactions. We will provide updates as we progress. Thank you for your continued patience.
Jun 1, 3:08 PM
investigating
Our team is continuing to investigate the slower than normal processing times for JNLC transactions. We will provide updates as we progress. Thank you for your continued patience.
Jun 1, 2:58 PM
investigating
We are still investigating the issue. Update will follow shortly.
Jun 1, 2:46 PM
investigating
We are currently experiencing slower than normal processing times for JNLC transactions. Journals are processing successfully but at a reduced rate compared to typical performance.
Jun 1, 2:28 PM
May 2026
Broker API and Trading API Timeouts
Started: May 30, 2:44 AM
investigating
Our team is aware of an increase in timeout errors across Broker and Trading API. We are currently investigating and will provide updates as we progress. Thank you for your patience.
May 30, 2:44 AM
Alpaca Documentation Site Experiencing Intermittent Issues
Started: May 28, 1:55 PM
monitoring
We are no longer seeing intermittent issues. Our team will continue to monitor and provide updates. Thank you for your patience
May 28, 3:06 PM
monitoring
An outage at our vendor is causing intermittent issues at our documentation site, and a fix is being implemented. We are continuing to monitor the situation and will provide updates as we learn more. Thank you for your continued patience.
May 28, 2:18 PM
monitoring
An outage at our vendor is causing intermittent issues at our documentation site, and a fix is being implemented. Our team is monitoring the situation and will provide updates as we learn more. Thank you for your patience.
May 28, 1:55 PM
Alpaca Documentation site is Offline
Started: May 27, 3:02 PM
identified
An outage at our vendor is preventing our documentation site from loading, and a fix is being implemented. Our team is monitoring the situation and will provide updates as we learn more. Thank you for your patience.
May 27, 3:02 PM
Broker API Endpoints are receiving timeout errors
Started: May 26, 3:54 PM
monitoring
We're seeing improved response times for Broker API endpoints. We're continuing to monitor the situation and will provide further updates as needed. Thank you for your continued patience.
May 26, 4:44 PM
monitoring
We're seeing improved response times for Broker API endpoints. We're continuing to monitor the situation and will provide further updates as needed. Thank you for your continued patience.
May 26, 4:26 PM
monitoring
Our team has identified a potential cause for the timeouts on Broker API endpoints. We are working to implement a fix and restore services to fully operational. We will continue to monitor and provide updates as we learn more. Thank you for your continued patience.
May 26, 4:15 PM
monitoring
Our team has identified a potential cause for the timeouts on Broker API endpoints. We are working to implement a fix and restore services to fully operational. We will continue to provide updates as we learn more. Thank you for your continued patience.
May 26, 4:10 PM
investigating
We are continuing to investigate the issue causing timeouts on Broker API endpoints. We will provide additional updates as soon as more information is available.
Thank you for your continued patience.
May 26, 4:04 PM
investigating
We are aware of an issue causing timeouts on Broker API endpoints. Our team is currently investigating and will provide updates as we learn more. Thank you for your patience.
May 26, 3:54 PM
Delays in Cash Settlement Processing
Started: May 26, 8:44 AM
identified
We appreciate your patience. Remediation efforts are progressing and we expect to have a complete resolution soon. Updates will continue to follow
May 26, 11:50 AM
identified
Our team is actively working on the remediation and making steady progress. We will share a more detailed update as soon as we have a confirmed timeline.
May 26, 10:40 AM
identified
Investigation remains active. We are currently evaluating a targeted resolution approach and will provide an update once we have more clarity on timing
May 26, 10:22 AM
identified
Our engineers remain engaged on this issue. We appreciate your patience and will post an update shortly.
May 26, 10:00 AM
identified
We are continuing to investigate. No further impact has been identified at this time. Updates will follow as we learn more
May 26, 9:37 AM
investigating
We are aware that settled cash and withdrawable cash balances may not yet reflect trades that settled over the weekend due to the US market holiday on Monday, May 25th.
All trades and positions are unaffected. We are prepare to run our reconciliation process and expect balances to be fully updated later today.
May 26, 9:19 AM
investigating
We are currently experiencing delays in pending cash settlements. Our team is actively working on a resolution. We will provide updates as more information becomes available.
May 26, 8:44 AM
Investigating Issue with Double Executions
Started: May 21, 2:33 PM
monitoring
We are continuing to monitor to ensure the issue is resolved. We greatly appreciate your patience.
May 21, 8:30 PM
monitoring
Our team team has implemented a fix and we are monitoring to ensure services are restored. We will continue to update you as we monitor. Thank you for your patience.
May 21, 7:39 PM
monitoring
Our team is continuing to work on resolving this as quickly as possible. We will continue to update you as we progress. Thank you for your patience.
May 21, 7:15 PM
monitoring
We anticipate a fix to be complete shortly. We will continue to update you as we progress.
May 21, 6:57 PM
identified
Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we work towards a resolution. We greatly appreciate your patience.
May 21, 6:41 PM
identified
Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we work towards a resolution. We greatly appreciate your patience.
May 21, 6:27 PM
identified
Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we work towards a resolution.
May 21, 6:17 PM
identified
We have identified the issue which affected buying power. Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we investigate.
May 21, 6:06 PM
identified
We have identified the issue which affected buying power. Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we investigate.
May 21, 5:53 PM
identified
We have identified the issue which affected buying power. Our team is actively working on a fix for buying power and resolving duplicate orders as a high priority. We will continue to update you as we investigate.
May 21, 5:43 PM
investigating
We are continuing to investigate the buying power issue affecting accounts impacted by the earlier duplicate execution. Our team is actively working on a fix as a high priority. We will continue to update you as we investigate.
May 21, 5:25 PM
investigating
We are continuing to investigate the buying power issue affecting accounts impacted by the earlier duplicate execution. Our team is actively working on a fix as a high priority. We will continue to update you as we investigate.
May 21, 5:15 PM
monitoring
We have identified a buying power issue affecting accounts impacted by the earlier duplicate execution. Our team is actively working on a fix as a high priority. We will update you once resolved.
May 21, 5:04 PM
monitoring
Our team is continuing to work on the resolution. We will provide another update once the corrected trade events have been sent.
May 21, 4:44 PM
monitoring
We are now preparing to send the corrected trade events and will confirm once they have been processed.
May 21, 3:46 PM
monitoring
We have completed our corrections and the accurate filled quantities should now be reflected in customer accounts. Our teams are now finalising any outstanding data clean up and will provide a formal trade event notification and final update once this is completed.
May 21, 3:22 PM
identified
All affected orders have been identified. Corrections are in progress and we will confirm once fully resolved.
May 21, 2:40 PM
investigating
We are currently investigating a technical issue that caused some orders to receive duplicate executions following a restart of the principal engine. This may result in some customers temporarily seeing incorrect filled quantities or affected buying power. Our engineering team is actively working to resolve this We will provide an update once the corrections are complete.
May 21, 2:33 PM
End of Day reporting positions delayed
Started: May 19, 7:42 AM
monitoring
The position data processing job has now completed successfully. Position data should be fully up to date and reflected correctly. If you experience any discrepancies or have questions, please don't hesitate to reach out to us. Thank you for your patience.
May 19, 9:04 AM
identified
We are continuing to monitor the situation. The job is still in progress, and our team remains actively engaged. We will share an update as soon as there is further progress.
May 19, 8:43 AM
investigating
Our team is actively monitoring the job and investigating the delay. We will provide another update as soon as we have more information. Thank you for your patience.
May 19, 8:18 AM
investigating
End of day positions returned in /v1/reporting/eod/positions are delayed. Endpoint API Doc: https://docs.alpaca.markets/us/reference/get-v1-reporting-eod-positions
May 19, 7:55 AM
investigating
Gobroker BOD is running longer than expected today. You should see correct balances already; position data is delayed.
May 19, 7:46 AM
investigating
We are investigating above issue. Updates will follow.
May 19, 7:42 AM
Delayed EOD Balance & Position Snapshot
Started: May 16, 9:55 AM
identified
EOD Balance processing has completed. We are syncing position snapshots and expect completion before 7:00 AM EDT.
May 16, 10:10 AM
identified
End Of Day (EOD) position snapshots and balances for 15-May-2026 are still being processed. The team has identified the issue, and the rerun is currently in progress.
May 16, 9:55 AM
Overnight Trading Symbol Status Update Issue
Started: May 15, 5:14 AM
monitoring
Mitigation measures have been implemented, and services are showing signs of recovery. We are currently validating the overnight trading symbol set and transitioning into a monitoring phase while final verification checks are completed.
May 15, 6:02 AM
identified
We identified a likely root cause. The team is restoring the correct configuration. Investigation is ongoing, and we will share another update once recovery is confirmed.
May 15, 5:26 AM
investigating
We have identified an issue where certain securities available for overnight trading are incorrectly marked as restricted.
Impact Clients may be unable to place trades for specific newly listed overnight-tradable securities. Regular trading hours and other asset classes remain unaffected.
May 15, 5:14 AM
Delay in Journal Processing
Started: May 12, 3:43 PM
monitoring
Remediation measures were applied yesterday and journals have been flowing correctly since then. We will monitor today's market open to validate the changes and address any unforeseen issues. A final confirmation will follow, after which we will close this incident. Thank you for your patience.
May 13, 8:34 AM
monitoring
Journal processing seems to be normal at this moment. We are continuing to monitor.
May 12, 7:18 PM
monitoring
Testing is still under progress. Journal processing seems to be normal at this moment.
May 12, 6:22 PM
monitoring
Journal processing seems to be normal at this moment. Our team is working on fix and being tested in lower environment.
May 12, 5:38 PM
monitoring
We are continuing to monitor to ensure journals are processing as normal.
May 12, 5:35 PM
identified
Currently we are not seeing journals getting stuck, they are getting processed without any issue.
May 12, 4:56 PM
identified
We are seeing journals getting processed faster.
May 12, 4:36 PM
identified
Mitigation Plans are being evaluated currently for any unknown impact,We will continue to provide updates as we progress.
May 12, 4:18 PM
identified
We are continuing to work on a fix for this issue.
May 12, 4:06 PM
identified
We have identified the root cause and the engineering team is actively working on a mitigation plan. We will continue to provide updates as we progress.
May 12, 3:59 PM
investigating
We are currently investigating an issue causing slowness and queuing of journals.
Our engineering team is actively working on resolving this.
May 12, 3:43 PM
Accounts not activated due to ledgie timeout
Started: May 12, 4:21 AM
investigating
We are investigating above issue. Updates will follow.
May 12, 4:21 AM
Delayed availability of Settled Cash and EOD Positions
Started: May 5, 6:36 AM
monitoring
Settled cash has been updated across all accounts. Position data is expected to be updated within the next 15 minutes.
May 5, 11:58 AM
monitoring
The Beginning-of-day job is running smoothly and we expect it to complete by 8:00 AM EDT. We will confirm once processing is finished.
May 5, 11:24 AM
monitoring
Following the applied fix, the beginning-of-day job has progressed past the previously failed stage and is now running through the remaining phases. We will continue to monitor and provide updates as processing progresses.
May 5, 11:12 AM
monitoring
B.O.D. job has resumed and is progressing without issues. Our team continues to monitor closely and will share an update once complete.
May 5, 10:46 AM
monitoring
We have taken corrective measures and re-run the B.O.D. job. We are continuing to monitor for any further issues.
May 5, 10:24 AM
monitoring
we are still investigating this BOD job failure.
May 5, 10:04 AM
monitoring
We have encountered an issue during the beginning-of-day processing and are currently working with our engineering team to investigate. We will provide an update shortly.
May 5, 9:48 AM
monitoring
All phases of end-of-day processing have been completed successfully. Beginning-of-day processing is now underway, and we expect settled cash balances to be updated by 6:30 AM EDT. We will provide a further update once this is confirmed.
May 5, 8:58 AM
monitoring
We are continuously monitoring the final phase of the end-of-day processing and will provide an update upon completion.
May 5, 8:50 AM
monitoring
A critical component of the end-of-day processing has completed successfully. The remaining processes are in progress and advancing as expected. We will continue to provide updates as the situation develops.
May 5, 8:28 AM
monitoring
EOD Job is still running and we are monitoring the logs for any issue.
May 5, 8:07 AM
monitoring
We are continuing to investigate the EOD delay. The affected process has been rerun, and our team is closely monitoring logs and system metrics to assess the effectiveness of the applied fix. We will share an update once we have more clarity.
May 5, 7:54 AM
monitoring
We have identified and addressed the underlying cause of the issue. A corrective fix has been applied and the affected process has been restarted. Our team continues to monitor the situation, and we will provide further updates as needed.
May 5, 7:31 AM
identified
We've identified a long-running query as the source of this issue. Our engineering team is actively working on a resolution, and we'll provide an update once the fix is in place.
May 5, 7:08 AM
identified
We are currently experiencing a delay in our Beginning of Day (BOD) processing. As a result, settled cash and downstream updates, such as EOD positions, are expected to be available closer to 6:00 AM ET today (typically available around 4:00 AM ET).
We are actively monitoring the process and will provide update once processing is complete.
May 5, 6:36 AM
April 2026
Dashboard SMS 2FA
Started: Apr 27, 12:13 PM
monitoring
We believe the issue with SMS based two-factor authentication for the Trading Dashboard is resolved. We are currently monitoring the service to validate.
Apr 27, 7:20 PM
identified
The issue has been identified and a fix is being implemented.
Apr 27, 12:14 PM
investigating
We are currently experiencing issues with SMS two-factor authentication for the Trading Dashboard. If you cannot log in, please contact support.
This does not affect our APIs or Broker Dashboard.
Apr 27, 12:13 PM
JIT Reports are not available for 6-April-2026
Started: Apr 7, 2:45 AM
investigating
Team is still working to identify the root cause
Apr 7, 3:09 AM
investigating
Just In Time reports are not generated
Apr 7, 2:45 AM
March 2026
Service degradation across multiple API's
Started: Mar 31, 1:25 PM
monitoring
All services are operating normally with no issues detected. We are continuing to monitor and will provide updates if anything changes.
Mar 31, 1:56 PM
monitoring
The service has been restored to normal operation. We are no longer seeing issues with any API endpoints or journals. We will continue monitoring to ensure stability.
Mar 31, 1:43 PM
identified
We are seeing improvement in API response times, and journals are no longer getting stuck. We are continuing to monitor the situation and will post further updates as needed.
Mar 31, 1:34 PM
investigating
We are currently investigating a service degradation that is impacting account information access and transaction processing.
Client Impact:
Users may experience intermittent timeouts or delays when attempting to access their account details.
Current Status: Our engineering teams are actively engaged and working to address the underlying issues related to processing capacity and system delays. We are prioritising a resolution and will provide an update when more information is available.
Mar 31, 1:25 PM