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 |
|---|---|---|---|
| May 2026 | 69.2% | 13 | 4 |
| April 2026 | 86.7% | 30 | 4 |
| March 2026 | 100% | 4 | 0 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 47 Days)
Mar 28
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
Delay in Journal Processing
Started: May 12, 3:43 PM
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