Is Alpaca down?

Overnight trading and market data delivery (BOATS / overnight REST endpoints and streaming feeds) are currently unavailable due to an exchange-wide trading halt declared by our third-party overnight venue, Blue Ocean ATS (BOATS), as of 11:46 PM ET. We are actively monitoring for updates.

As a precaution due to the ongoing 3rd overnight venue trading halt, we are temporarily disabling overnight fractional share trading.

We have turned off fractional overnight trading. Whole share orders remain unaffected and continue to process normally. Our team is in direct contact with the market data vendor to investigate and resolve the issue.

We're writing to let you know about an ongoing incident that affects overnight trading. What happened Blue Ocean ATS (BOATS), our third-party overnight venue, declared an exchange-wide trading halt at 11:46 PM ET on October 20 after network connectivity issues at its provider. Because of the halt, overnight market data (BOATS and overnight streaming and REST feeds) is currently unavailable or stale. BOATS has given no ETA for resolution. What we've done As a precaution, we've temporarily disabled overnight fractional share trading for all correspondents. Without reliable overnight market data, we can't accurately trigger or price certain order types (e.g., limit and stop orders). What this means for you -Overnight fractional/notional orders will not be accepted until further notice. -Overnight market data from the BOATS and overnight feeds may be stale. Please don't rely on it. -Whole-share overnight orders are unaffected because they’re routed to multiple ATSs for execution. -Pre-market and core-session orders are unaffected at this time.

We've resumed receiving overnight market data from Blue Ocean ATS (BOATS). We have re-enabled overnight fractional share trading for all correspondents.

From 6:15 PM to 6:22 PM ET, some API requests experienced elevated timeouts. Most affected requests were retried successfully. The issue is resolved, and all services have been operating normally since.

We are investigating an 3rd party outage affecting market data delivery for IEX and SIP feeds. New bars and trades may not be updating for impacted symbols. We are actively working to restore the feed and will post updates soon.

We have identified the cause of the market data delivery issue as a vendor-side network disruption affecting third-party data feeds (IEX and SIP). This is not caused by an issue on our end. We continue to work with the vendor to restore the feed and will post updates as the situation progresses.

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

We’re continuing to investigate the issue and will share an update as soon as we have more information.

As a precaution during this outage, we are temporarily disabling notional and fractional share trading to open new positions to prevent orders from executing at stale prices. Whole-share trading remains available. Liquidation will still be available. We will restore fractional trading once the underlying market data feed issue is resolved.

Market Data Feeds are receiving quotes and restored. We are continuing to monitor the performance

We have re-enable notional and fractional share trading

The incident has been resolved. Connectivity to our market data provider has been restored, and market data (IEX and SIP feeds) is updating normally. Fractional and notional share trading have been re-enabled. We apologize for any inconvenience this caused.

We’re investigating an issue affecting some users in the sandbox environment. Requests to multiple services may be returning errors or failing to complete. Our teams are working to restore normal service and will provide another update as more information becomes available.

Service has been restored for affected sandbox requests, and we’re monitoring performance to confirm stability.

Elevated latency affecting multiple sandbox services has been resolved. Service performance has returned to normal, and monitoring confirms recovery. Production services were not affected. We apologize for the disruption.

We are currently experiencing a delay in our Beginning of Day (BOD) processing. As a result, EOD position via the Reporting API (GET /v1/reporting/eod-positions) may temporarily reflect the previous business day's values.

The sync processing job is currently running. EOD position synchronization via the Reporting API remains delayed while the job completes. Cash balances and withdrawables are unaffected and available. We are actively monitoring the process.

The job for EOD positions continues to progress as expected. We anticipate processing to complete by approximately 09:30 UTC (5:30 AM EDT). We will provide our next update once processing is complete or if the timeline changes.

All daily EOD sync have been completed. This incident is now resolved.