Update - 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, 2026 - 14:41 EDT
Update - 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, 2026 - 14:27 EDT
Update - 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, 2026 - 14:17 EDT
Update - 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, 2026 - 14:06 EDT
Update - 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, 2026 - 13:53 EDT
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, 2026 - 13:43 EDT
Update - 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, 2026 - 13:25 EDT
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, 2026 - 13:15 EDT
Update - 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, 2026 - 13:04 EDT
Update - Our team is continuing to work on the resolution. We will provide another update once the corrected trade events have been sent.
May 21, 2026 - 12:44 EDT
Update - We are now preparing to send the corrected trade events and will confirm once they have been processed.
May 21, 2026 - 11:46 EDT
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, 2026 - 11:22 EDT
Identified - All affected orders have been identified. Corrections are in progress and we will confirm once fully resolved.
May 21, 2026 - 10:40 EDT
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, 2026 - 10:33 EDT
Live Trading API Degraded Performance
90 days ago
100.0 % uptime
Today
Account API Operational
90 days ago
100.0 % uptime
Today
Orders API Degraded Performance
90 days ago
100.0 % uptime
Today
Positions API Operational
90 days ago
100.0 % uptime
Today
Assets API Operational
90 days ago
100.0 % uptime
Today
Trade Update Streaming Operational
Fractional Orders Operational
90 days ago
100.0 % uptime
Today
Paper Trading API Operational
Paper Account API Operational
Paper Order API Operational
Paper Positions API Operational
Paper Assets API Operational
Dashboard Operational
90 days ago
99.9 % uptime
Today
Accounts Operational
90 days ago
100.0 % uptime
Today
Transfers Operational
90 days ago
100.0 % uptime
Today
Bank Links Operational
90 days ago
100.0 % uptime
Today
New Account Onboarding Operational
90 days ago
100.0 % uptime
Today
Turbo Tax Integration Operational
90 days ago
100.0 % uptime
Today
Buying Power Operational
90 days ago
100.0 % uptime
Today
Non Tradable Activites Operational
90 days ago
100.0 % uptime
Today
Broker API (Sandbox) Operational
90 days ago
100.0 % uptime
Today
broker.accounts.get Operational
90 days ago
100.0 % uptime
Today
broker.accounts.account_id.transfers.get Operational
broker.assets.get Operational
broker.trading.accounts.account_id.account.get Operational
broker.trading.accounts.account_id.orders.get Operational
broker.accounts.account_id.documents.get Operational
broker.journals.get Operational
90 days ago
100.0 % uptime
Today
broker.ledgers.get Operational
broker.accounts.activities.get Operational
broker.accounts.account_id.recipient_banks.get Operational
broker.events.accounts.status.get Operational
broker.events.trades.get Operational
broker.events.journals.status.get Operational
Market Data Streaming API Operational
90 days ago
100.0 % uptime
Today
wss://stream.data.alpaca.markets/v2/sip Operational
90 days ago
100.0 % uptime
Today
wss://stream.data.alpaca.markets/v2/iex Operational
90 days ago
100.0 % uptime
Today
wss://stream.data.alpaca.markets/v1beta3/crypto/us Operational
90 days ago
100.0 % uptime
Today
wss://stream.data.alpaca.markets/v1beta1/news Operational
90 days ago
100.0 % uptime
Today
wss://stream.data.alpaca.markets/v1beta1/otc Operational
90 days ago
100.0 % uptime
Today
wss://stream.data.alpaca.markets/v1beta1/opra Operational
90 days ago
100.0 % uptime
Today
Market Data Stocks REST API Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v2/stocks/auctions Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v2/stocks/bars Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v2/stocks/trades Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v2/stocks/quotes Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v2/stocks/snapshots Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v2/stocks/trades/latest Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v2/stocks/quotes/latest Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v2/stocks/meta/conditions Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v2/stocks/meta/exchanges Operational
90 days ago
100.0 % uptime
Today
Market Data Crypto REST API Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta3/crypto/us/bars Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta3/crypto/us/latest/bars Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta3/crypto/us/latest/orderbooks Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta3/crypto/us/latest/trades Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta3/crypto/us/latest/quotes Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta3/crypto/us/trades Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta3/us/crypto/quotes Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta3/crypto/us/snapshots Operational
90 days ago
100.0 % uptime
Today
Market Data Options REST API Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta1/options/bars Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta1/options/quotes/latest Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta1/options/trades/latest Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta1/options/trades Operational
90 days ago
100.0 % uptime
Today
https://data.alpaca.markets/v1beta1/options/snapshots Operational
90 days ago
100.0 % uptime
Today
Broker Dashboard Operational
90 days ago
100.0 % uptime
Today
Broker API Degraded Performance
90 days ago
100.0 % uptime
Today
broker.accounts.get Operational
90 days ago
100.0 % uptime
Today
broker.accounts.account_id.transfers.get Operational
90 days ago
100.0 % uptime
Today
broker.assets.get Operational
90 days ago
100.0 % uptime
Today
broker.trading.accounts.account_id.account.get Operational
90 days ago
100.0 % uptime
Today
broker.trading.accounts.account_id.orders.get Degraded Performance
90 days ago
100.0 % uptime
Today
broker.accounts.account_id.documents.get Operational
90 days ago
100.0 % uptime
Today
broker.journals.get Operational
90 days ago
100.0 % uptime
Today
broker.ledgers.get Operational
90 days ago
100.0 % uptime
Today
broker.accounts.activities.get Operational
90 days ago
100.0 % uptime
Today
broker.accounts.account_id.recipient_banks.get Operational
90 days ago
100.0 % uptime
Today
broker.events.accounts.status.get Operational
90 days ago
100.0 % uptime
Today
broker.events.trades.get Operational
90 days ago
100.0 % uptime
Today
broker.events.journals.status.get Operational
90 days ago
100.0 % uptime
Today
Instant funding & Settlements Operational
90 days ago
100.0 % uptime
Today
Sweep and cash interest Operational
90 days ago
100.0 % uptime
Today
FPSL Program Operational
90 days ago
100.0 % uptime
Today
Funding Wallets Operational
90 days ago
100.0 % uptime
Today
Assets Operational
90 days ago
100.0 % uptime
Today
Calendar and Clock Operational
90 days ago
100.0 % uptime
Today
Accounts Events (SSE) Operational
90 days ago
100.0 % uptime
Today
Journal Events (SSE) Operational
90 days ago
100.0 % uptime
Today
Transfer Events (SSE) Operational
90 days ago
100.0 % uptime
Today
Trade Events (SSE) Operational
90 days ago
100.0 % uptime
Today
Admin Action Events (SSE) Operational
90 days ago
100.0 % uptime
Today
Non Trade Activities (NTAs) Events (SSE) Operational
90 days ago
100.0 % uptime
Today
Funding Status Events (SSE) Operational
90 days ago
100.0 % uptime
Today
OAuth endpoint Operational
90 days ago
100.0 % uptime
Today
Watchlist Endpoint Operational
90 days ago
100.0 % uptime
Today
Corporate Action Endpoint Operational
90 days ago
100.0 % uptime
Today
KYC Endpoint Operational
90 days ago
100.0 % uptime
Today
Logos Endpoint Operational
90 days ago
100.0 % uptime
Today
Reporting - Aggregate Position endpoint Operational
90 days ago
100.0 % uptime
Today
Reporting - EOD Cash Interest Details Operational
90 days ago
100.0 % uptime
Today
Portfolio History Endpoint Operational
90 days ago
100.0 % uptime
Today
Rebalancer Operational
90 days ago
100.0 % uptime
Today
Crypto Funding Operational
90 days ago
100.0 % uptime
Today
Funding Operational
90 days ago
99.99 % uptime
Today
JNLC Operational
90 days ago
99.98 % uptime
Today
Just in Time Operational
90 days ago
100.0 % uptime
Today
Withdrawable Cash Operational
90 days ago
100.0 % uptime
Today
Instant Funding Operational
90 days ago
100.0 % uptime
Today
Support Operational
90 days ago
100.0 % uptime
Today
Support Forum Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

Scheduled Maintenance

Maintenance in Sandbox Today ( 21st May 2026) @ 6pm-8pm - EDT May 21, 2026 18:00-20:00 EDT

Dear Users,
This is a notice regarding the upcoming system maintenance to the Sandbox environment. Our goal is to accelerate the release of system fixes and improvements, ensuring you and your users benefit from a more stable and enhanced product more quickly.

Sandbox Maintenance Window
When: Thursday, May 21st, 2026
Time: 6 PM to 8 PM ET

Downtime: The Sandbox environment may be unavailable for up to 2 hours. Please note that maintenance windows are approximate. While we aim to complete work within the scheduled timeframe, maintenance may conclude earlier or occasionally extend if additional work is required to ensure system stability.
Once maintenance is complete (or if no maintenance was required), Alpaca will issue an "Scheduled Maintenance Complete" status update after the window has passed

Rationale: This maintenance window takes place during the period of lowest global trading activity.
Action Required

Partner Action: No action is required from you at this time and there will be no impact to Production environments. We simply ask that you are aware of this scheduled window and prepare your internal teams for the possibility of a brief downtime.

Recommendation: Please ensure your internal teams are aware of this scheduled window to account for the possibility of a brief outage that could temporarily affect all services, including deposits and withdrawals.

After the Maintenance:
No action is required on your part following the maintenance. All API endpoints, credentials, and integration configurations will remain unchanged.

We are committed to continuous improvement, and this process change will help us deliver stability and enhancements with greater speed.

If you have any questions or require further clarification, please reach out to your Customer Success Manager or our support team at brokersupport@alpaca.markets.

Best Regards,
Alpaca Team

Posted on May 21, 2026 - 12:23 EDT

Scheduled Maintenance: May 23, 2026 (7–8 AM EDT) May 23, 2026 07:00-08:00 EDT

Update - We will be undergoing scheduled maintenance during this time.
May 19, 2026 - 05:15 EDT
Update - Maintenance Date - Title Correction - Quick correction to the maintenance title notice sent earlier.
The actual maintenance window will be on May 23, 2026 (7–8 AM EDT).

May 15, 2026 - 08:19 EDT
Scheduled - Dear User,

This is a notice that Alpaca will perform scheduled maintenance on Saturday, May 23, 2026, from 7:00 AM to 8:00 AM EDT.

The maintenance window will last 60 minutes. During this period, we expect up to 15 minutes of total downtime, which may occur intermittently.

Some services may experience brief disruption, including temporary API request failures, dropped event-streaming connections, and brief outages for some production workloads.

No action is required from you at this time. Please ensure your internal teams are aware of this scheduled maintenance window and the possibility of brief service interruptions.

After maintenance is complete, all API endpoints, credentials, and integration configurations will remain unchanged.

Best regards,
Alpaca Team

May 15, 2026 - 06:02 EDT
May 21, 2026

Unresolved incident: Investigating Issue with Double Executions.

May 20, 2026

No incidents reported.

May 19, 2026
Resolved - The position data processing job has completed successfully. This incident is now resolved. If you notice any remaining discrepancies, please don't hesitate to reach out. Thank you for your patience during this time
May 19, 05:13 EDT
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, 05:04 EDT
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, 04:43 EDT
Update - 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, 04:18 EDT
Update - 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, 03:55 EDT
Update - Gobroker BOD is running longer than expected today. You should see correct balances already; position data is delayed.
May 19, 03:46 EDT
Investigating - We are investigating above issue. Updates will follow.
May 19, 03:42 EDT
May 18, 2026

No incidents reported.

May 17, 2026

No incidents reported.

May 16, 2026
Resolved - EOD balance and position batch processing has completed successfully.
May 16, 06:48 EDT
Update - EOD Balance processing has completed. We are syncing position snapshots and expect completion before 7:00 AM EDT.
May 16, 06:10 EDT
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, 05:55 EDT
May 15, 2026
Postmortem - Read details
May 15, 14:06 EDT
Resolved - After monitoring we are no longer seeing issues. Overnight trading symbol eligibility appears to be operating normally.
May 15, 02:30 EDT
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, 02:02 EDT
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, 01:26 EDT
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, 01:14 EDT
May 14, 2026

No incidents reported.

May 13, 2026
Postmortem - Read details
May 14, 12:27 EDT
Resolved - Journals have been processing normally through today's market open with no further issues observed. We consider this incident fully resolved and are closing it out. Thank you for your patience.
May 13, 11:28 EDT
Update - 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, 04:34 EDT
Update - Journal processing seems to be normal at this moment. We are continuing to monitor.
May 12, 15:18 EDT
Update - Testing is still under progress. Journal processing seems to be normal at this moment.
May 12, 14:22 EDT
Update - Journal processing seems to be normal at this moment. Our team is working on fix and being tested in lower environment.
May 12, 13:38 EDT
Monitoring - We are continuing to monitor to ensure journals are processing as normal.
May 12, 13:35 EDT
Update - Currently we are not seeing journals getting stuck, they are getting processed without any issue.
May 12, 12:56 EDT
Update - We are seeing journals getting processed faster.
May 12, 12:36 EDT
Update - Mitigation Plans are being evaluated currently for any unknown impact,We will continue to provide updates as we progress.
May 12, 12:18 EDT
Update - We are continuing to work on a fix for this issue.
May 12, 12:06 EDT
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, 11:59 EDT
Investigating - We are currently investigating an issue causing slowness and queuing of journals.
Our engineering team is actively working on resolving this.

May 12, 11:43 EDT
May 12, 2026
May 11, 2026

No incidents reported.

May 10, 2026

No incidents reported.

May 9, 2026
Completed - The scheduled maintenance has been completed.
May 9, 08:48 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 9, 07:00 EDT
Scheduled - Dear Users,
This is a notice regarding the upcoming system maintenance. Our goal is to accelerate the release of system fixes and improvements, ensuring you and your users benefit from a more stable and enhanced product more quickly.

Maintenance Window
When: Saturday, May 9th, 2026
Time: 7 AM to 9 AM EDT
Downtime: The system may be unavailable for up to 2 hours. However, the downtime is expected to be 30 minutes or less. Please note that maintenance windows are approximate. While we aim to complete work within the scheduled timeframe, maintenance may conclude earlier or occasionally extend if additional work is required to ensure system stability.
Once maintenance is complete , Alpaca will issue an "Scheduled Maintenance Complete" status update after the window has passed
Rationale: This maintenance window takes place during the period of lowest global trading activity.
Action Required
Partner Action: No action is required from you at this time. We simply ask that you are aware of this new scheduled window and prepare your internal teams for the possibility of a brief downtime.
Recommendation: Please ensure your internal teams are aware of this scheduled window to account for the possibility of a brief outage that could temporarily affect all services, including deposits and withdrawals.
After the Maintenance
No action is required on your part following the maintenance. All API endpoints, credentials, and integration configurations will remain unchanged.

We are committed to continuous improvement, and this process change will help us deliver stability and enhancements with greater speed.

If you have any questions or require further clarification, please reach out to your Customer Success Manager or our support team at brokersupport@alpaca.markets.

Best Regards,
Alpaca Team

May 4, 11:58 EDT
May 8, 2026

No incidents reported.

May 7, 2026

No incidents reported.