Is Alpaca down?

We have temporarily paused overnight trading. Please note that we cannot accept additional overnight orders at this time.

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.

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.

This incident has been resolved.

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.

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

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.

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.

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.

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.

This issue has been resolved. We will continue to monitor through opening cross to ensure proper IPO functionality. Thank you for your patience and understanding as our team worked to implement the fix.

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 your workflow and you need it sooner, please contact support.

This issue has been resolved. Thank you for your patience as our team worked to reflect the most recent close prices.

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.

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.

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.

We are seeing improvements following the database query optimization. API response times have returned to normal, and the portfolio graph is loading successfully on the dashboard. We continue to monitor the service closely.

Resolved: All affected services have returned to normal operation. API response times have normalized, and the portfolio graph is loading successfully on the dashboard. We will continue monitoring to ensure continued stability.

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.

We are continuing to investigate this issue.

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.

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.

We have fixed the issue.

This incident has been resolved.

On July 21, 2026, between approximately 4:33 AM and 3:18 PM ET, Portfolio History requests covering periods before June 1, 2026 may have returned inaccurate or unavailable data while historical records were being restored. Our engineering teams completed the historical data restoration and validated access to the affected information. Portfolio History is operating normally.