Alpaca Outage History

Alpaca is up right now

Alpaca had 68 outages in the last 2 years totaling 91h 35m of downtime — averaging 2.8 incidents per month.

There were 68 Alpaca outages since September 4, 2025 totaling 91h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.alpaca.markets

Major October 29, 2025

OPRA Market Data Outage

Detected by Pingoru
Oct 29, 2025, 08:50 PM UTC
Resolved
Oct 30, 2025, 01:46 AM UTC
Duration
4h 56m
Affected: https://data.alpaca.markets/v1beta1/options/barshttps://data.alpaca.markets/v1beta1/options/quotes/latesthttps://data.alpaca.markets/v1beta1/options/trades/latesthttps://data.alpaca.markets/v1beta1/options/tradeshttps://data.alpaca.markets/v1beta1/options/snapshots
Timeline · 2 updates
  1. identified Oct 29, 2025, 08:50 PM UTC

    Our options market data provider, Exegy, is experiencing a system data feed outage at this time. We are currently working with our vendor to restore the system as soon as possible.

  2. resolved Oct 30, 2025, 01:46 AM UTC

    The issue has been resolved. Live data resumed normal operation around 3:15 PM EST, and historical data was backfilled and corrected shortly after. The Exegy team has confirmed resolution and will implement additional monitoring and safeguards to prevent recurrence.

Read the full incident report →

Minor October 23, 2025

Journal v2 status event endpoint is currently down

Detected by Pingoru
Oct 23, 2025, 06:05 AM UTC
Resolved
Oct 23, 2025, 03:45 PM UTC
Duration
9h 40m
Timeline · 8 updates
  1. investigating Oct 23, 2025, 06:05 AM UTC

    Client using SSE journal steam via API /v2beta1/events/journals/status will not be receiving the journal status due to ongoing issue.

  2. identified Oct 23, 2025, 06:06 AM UTC

    We have identified the issue. This has affected Prod and Sandbox. Recovery in sandbox is in progress

  3. identified Oct 23, 2025, 06:35 AM UTC

    We are still working on the recovery

  4. identified Oct 23, 2025, 07:30 AM UTC

    Sandbox events have resumed and system functionality is restored.

  5. monitoring Oct 23, 2025, 07:58 AM UTC

    Both Production and Sandbox environments have recovered and event flow is stable. We identified a gap of approximately 7 hours of journal events during the incident period. The missing data has been captured from another source and will be reconciled separately. We’ll continue to monitor to ensure no further impact.

  6. monitoring Oct 23, 2025, 01:35 PM UTC

    We have identified the issue is reoccurring again

  7. monitoring Oct 23, 2025, 03:44 PM UTC

    We are continuing to monitor for any further issues.

  8. resolved Oct 23, 2025, 03:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 22, 2025

Intermittent OPRA Market Data Outages

Detected by Pingoru
Oct 22, 2025, 06:28 PM UTC
Resolved
Oct 22, 2025, 07:31 PM UTC
Duration
1h 2m
Affected: https://data.alpaca.markets/v1beta1/options/barshttps://data.alpaca.markets/v1beta1/options/quotes/latesthttps://data.alpaca.markets/v1beta1/options/trades/latesthttps://data.alpaca.markets/v1beta1/options/snapshots
Timeline · 2 updates
  1. monitoring Oct 22, 2025, 06:28 PM UTC

    Our options market data provider, Exegy, experienced two intermittent data feed outages today during the following approximate times: 1:12 – 1:29 PM ET 1:39 – 1:50 PM ET During these periods, you may have noticed option data values showing as 0. We apologize for any inconvenience this may have caused. The data is now back online and functioning normally. We will continue to monitor the situation and provide updates if necessary.

  2. resolved Oct 22, 2025, 07:31 PM UTC

    Our market data vendor has confirmed that OPRA data is now back online and operating normally. We will continue to monitor the situation and issue a new update if any additional outages occur.

Read the full incident report →

Minor October 22, 2025

Brokerage trading partners unable to login to dashboard

Detected by Pingoru
Oct 22, 2025, 12:44 AM UTC
Resolved
Oct 22, 2025, 12:44 AM UTC
Duration
19s
Affected: Dashboard
Timeline · 2 updates
  1. investigating Oct 22, 2025, 12:44 AM UTC

    Brokerage trading partners were unable to login to portal (https://broker-app.alpaca.markets) for a short period of time.

  2. resolved Oct 22, 2025, 12:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025

Login Issues Due to AWS Outage

Detected by Pingoru
Oct 20, 2025, 08:37 AM UTC
Resolved
Oct 20, 2025, 11:53 AM UTC
Duration
3h 15m
Affected: Dashboard
Timeline · 4 updates
  1. identified Oct 20, 2025, 08:37 AM UTC

    We're currently experiencing a login issue due to a widespread outage affecting Amazon Web Services (AWS), which is impacting our authentication systems. Our team is actively monitoring the situation, and we will provide an update as soon as services are restored.

  2. monitoring Oct 20, 2025, 09:39 AM UTC

    As per AWS update - they have applied initial mitigations and observing early signs of recovery for some impacted AWS Services. During this time, requests may continue to fail as we work toward full resolution. We recommend customers retry failed requests. While requests begin succeeding, there may be additional latency and some services will have a backlog of work to work through, which may take additional time to fully process. We will continue to monitor and provide updates.

  3. monitoring Oct 20, 2025, 11:00 AM UTC

    According to the latest update from AWS, the underlying DNS issue has been fully resolved, and most AWS services are now operating normally. Trading API users can now log in via https://app.alpaca.markets/account/login without any issues.

  4. resolved Oct 20, 2025, 11:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 18, 2025

Delay in end of day balance and position availability for 17-OCT-2025.

Detected by Pingoru
Oct 18, 2025, 06:42 AM UTC
Resolved
Oct 18, 2025, 12:52 PM UTC
Duration
6h 10m
Timeline · 5 updates
  1. investigating Oct 18, 2025, 06:42 AM UTC

    There was a end of day job failure causing delay in balance and position computation availability. System is recovering and expected to be completed by 6:30 AM ET.

  2. monitoring Oct 18, 2025, 06:42 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Oct 18, 2025, 07:19 AM UTC

    Rerun of job is in progress

  4. monitoring Oct 18, 2025, 09:36 AM UTC

    Rerun of job is in progress

  5. resolved Oct 18, 2025, 12:52 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 16, 2025

Ledger system Issue

Detected by Pingoru
Oct 16, 2025, 02:05 PM UTC
Resolved
Oct 16, 2025, 02:32 PM UTC
Duration
27m
Affected: Account APIbroker.accounts.getOrders APIbroker.accounts.account_id.transfers.getPositions APIbroker.assets.getAssets APIbroker.trading.accounts.account_id.account.getbroker.trading.accounts.account_id.orders.getTrade Update Streamingbroker.accounts.account_id.documents.getbroker.journals.getbroker.ledgers.getbroker.accounts.activities.getbroker.accounts.account_id.recipient_banks.getbroker.events.accounts.status.getbroker.events.trades.getbroker.events.journals.status.get
Timeline · 3 updates
  1. investigating Oct 16, 2025, 02:05 PM UTC

    The team has identified some delays in processing some journals

  2. monitoring Oct 16, 2025, 02:23 PM UTC

    Our systems are stabilized now and our engineers are monitoring the performance

  3. resolved Oct 16, 2025, 02:32 PM UTC

    Systems are stabilized

Read the full incident report →

Minor October 16, 2025

End of day job to calculate balance and position is running longer than expected.

Detected by Pingoru
Oct 16, 2025, 07:06 AM UTC
Resolved
Oct 16, 2025, 10:44 AM UTC
Duration
3h 38m
Affected: New Account Onboarding
Timeline · 4 updates
  1. investigating Oct 16, 2025, 07:06 AM UTC

    This long running job would reconcile end of day balances and positions for 15-OCT-2025. This would also delay new account activation, margin call and end of day position and balance data.

  2. investigating Oct 16, 2025, 07:46 AM UTC

    We are monitoring

  3. identified Oct 16, 2025, 08:41 AM UTC

    We are creating the end of day balances and positions as of 15-OCT-2025

  4. resolved Oct 16, 2025, 10:44 AM UTC

    We’ve resolved the earlier delay with our End-of-Day (EOD) processing for October 15th. All jobs have now completed successfully, end-of-day balances and positions are now available, and funds from yesterday's sales are also now available for withdrawal. The delay was caused by a query that unintentionally blocked the EOD process. Once identified, it was safely terminated to allow processing to continue. We’re now reviewing the root cause and taking steps to help prevent similar issues in the future.

Read the full incident report →

Notice October 11, 2025

Datase Migration : Postpone the scheduled maintenance due to potential disruption.

Detected by Pingoru
Oct 11, 2025, 11:52 AM UTC
Resolved
Oct 11, 2025, 12:04 PM UTC
Duration
12m
Timeline · 2 updates
  1. investigating Oct 11, 2025, 11:52 AM UTC

    During the initial phase of the maintenance, and prior to any downtime, we identified an additional step that had not been part of our earlier scope. To prevent any potential disruption, we have decided to postpone the scheduled maintenance. We are reviewing this new requirement to ensure a smooth and timely rollout. An updated maintenance schedule will be shared once the necessary validations are complete. Thank you for your understanding and continued partnership.

  2. resolved Oct 11, 2025, 12:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 9, 2025

Intermittent Database Connection Failure – Investigation Underway

Detected by Pingoru
Oct 09, 2025, 11:21 AM UTC
Resolved
Oct 09, 2025, 11:23 AM UTC
Duration
1m
Affected: Account APITransfersOrders APIBank LinksPositions APINew Account OnboardingAssets APITurbo Tax IntegrationTrade Update Streaming
Timeline · 3 updates
  1. investigating Oct 09, 2025, 11:21 AM UTC

    On October 9, 2025, between approximately 09:48 UTC and 09:50 UTC, we experienced a short service disruption caused by an unexpected restart of production database. This may have resulted in connection errors for some users during this two-minute window. The database systems recovered automatically, and all services have been operating normally since. Our engineering team is actively investigating the root cause to prevent a recurrence.

  2. resolved Oct 09, 2025, 11:23 AM UTC

    This incident has been resolved.

  3. postmortem Oct 10, 2025, 11:05 AM UTC

    A change in our monitoring system resulted in an alert erroneously firing indicating the database was down. In order to resolve this quickly the database was restarted, resulting in the outage.

Read the full incident report →

Notice September 23, 2025

Intermittent Broker API Latency and Timeouts

Detected by Pingoru
Sep 23, 2025, 02:31 PM UTC
Resolved
Sep 23, 2025, 03:49 PM UTC
Duration
1h 17m
Affected: Account APIOrders APIPositions APIAssets APITrade Update Streaming
Timeline · 5 updates
  1. investigating Sep 23, 2025, 02:31 PM UTC

    Broker API Partners who leverage JNLC's may be experiencing intermittent latency and timeout on APIs. The team is actively investigating and isolating the issue

  2. identified Sep 23, 2025, 03:03 PM UTC

    The team has identified the root issue and is looking into the mitigation steps

  3. identified Sep 23, 2025, 03:30 PM UTC

    We are continuing to work on the fix

  4. monitoring Sep 23, 2025, 03:42 PM UTC

    The fix has been deployed and the team is monitoring performance

  5. resolved Sep 23, 2025, 03:49 PM UTC

    Traffic is back to normal and stabilized

Read the full incident report →

Notice September 10, 2025

Options Market Data Affected

Detected by Pingoru
Sep 10, 2025, 03:51 PM UTC
Resolved
Sep 11, 2025, 04:14 PM UTC
Duration
1d
Affected: https://data.alpaca.markets/v1beta1/options/barshttps://data.alpaca.markets/v1beta1/options/quotes/latesthttps://data.alpaca.markets/v1beta1/options/trades/latesthttps://data.alpaca.markets/v1beta1/options/tradeshttps://data.alpaca.markets/v1beta1/options/snapshots
Timeline · 6 updates
  1. identified Sep 10, 2025, 03:51 PM UTC

    We are currently investigating an issue with delayed options market data. Some options symbols are displaying outdated prices (bid/ask) and snapshots, which may not reflect real-time market conditions. This is impacting our indicative feeds and is affecting several of our partners. Our team has identified the root cause and is working with our data provider to resolve the issue as quickly as possible. We will provide another update as soon as more information is available. We apologize for any inconvenience this may cause.

  2. identified Sep 10, 2025, 04:11 PM UTC

    We are still working with our Market Data vendor, we have identified that Options symbols starting with H,J,K,L market data is stale. Please proceed trading with caution.

  3. identified Sep 10, 2025, 06:37 PM UTC

    We're currently experiencing a market data issue with our vendor. Some option symbols may be showing delayed data. Trades are still being accepted.

  4. monitoring Sep 11, 2025, 01:15 PM UTC

    We are continuing to work closely with our market data providers. We have restarted our market data service and will provide more updates if there are any. This does not affect our ability to place options trades.

  5. monitoring Sep 11, 2025, 01:43 PM UTC

    Our market data service has recovered. Our team will continue to monitor the feeds.

  6. resolved Sep 11, 2025, 04:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 5, 2025

API Request Delayed

Detected by Pingoru
Sep 05, 2025, 01:46 PM UTC
Resolved
Sep 05, 2025, 01:55 PM UTC
Duration
8m
Affected: Account APIPaper Account APITransferswss://stream.data.alpaca.markets/v2/siphttps://data.alpaca.markets/v1beta3/crypto/us/barshttps://data.alpaca.markets/v2/stocks/auctionshttps://data.alpaca.markets/v1beta1/options/barsbroker.accounts.getOrders APIPaper Order APIBank Linksbroker.accounts.getwss://stream.data.alpaca.markets/v2/iexhttps://data.alpaca.markets/v2/stocks/barshttps://data.alpaca.markets/v1beta3/crypto/us/latest/barshttps://data.alpaca.markets/v1beta1/options/quotes/latestbroker.accounts.account_id.transfers.getPositions APIDashboardPaper Positions APINew Account Onboardingbroker.accounts.account_id.transfers.getwss://stream.data.alpaca.markets/v1beta3/crypto/ushttps://data.alpaca.markets/v2/stocks/tradeshttps://data.alpaca.markets/v1beta3/crypto/us/latest/orderbookshttps://data.alpaca.markets/v1beta1/options/trades/latestbroker.assets.getAssets APIPaper Assets APIbroker.assets.gethttps://data.alpaca.markets/v2/stocks/quoteshttps://data.alpaca.markets/v1beta3/crypto/us/latest/tradesTurbo Tax Integrationwss://stream.data.alpaca.markets/v1beta1/newshttps://data.alpaca.markets/v1beta1/options/tradesbroker.trading.accounts.account_id.account.getbroker.trading.accounts.account_id.account.gethttps://data.alpaca.markets/v2/stocks/snapshotshttps://data.alpaca.markets/v1beta3/crypto/us/latest/quoteswss://stream.data.alpaca.markets/v1beta1/otchttps://data.alpaca.markets/v1beta1/options/snapshotsbroker.trading.accounts.account_id.orders.getTrade Update Streamingbroker.trading.accounts.account_id.orders.gethttps://data.alpaca.markets/v2/stocks/trades/latesthttps://data.alpaca.markets/v1beta3/crypto/us/tradeswss://stream.data.alpaca.markets/v1beta1/oprabroker.accounts.account_id.documents.getbroker.accounts.account_id.documents.gethttps://data.alpaca.markets/v2/stocks/quotes/latesthttps://data.alpaca.markets/v1beta3/us/crypto/quotesbroker.journals.getbroker.journals.gethttps://data.alpaca.markets/v2/stocks/meta/conditionshttps://data.alpaca.markets/v1beta3/crypto/us/snapshotsbroker.ledgers.getbroker.ledgers.gethttps://data.alpaca.markets/v2/stocks/meta/exchangesbroker.accounts.activities.getbroker.accounts.activities.getbroker.accounts.account_id.recipient_banks.getbroker.accounts.account_id.recipient_banks.getbroker.events.accounts.status.getbroker.events.accounts.status.getbroker.events.trades.getbroker.events.trades.getBroker Dashboardbroker.events.journals.status.getbroker.events.journals.status.get
Timeline · 4 updates
  1. investigating Sep 05, 2025, 01:46 PM UTC

    We are seeing intermittent issues that is causing slowing in API requests. The team is actively investigating the issue

  2. monitoring Sep 05, 2025, 01:48 PM UTC

    We have identified the issue and have addressed it. We are now monitoring

  3. resolved Sep 05, 2025, 01:55 PM UTC

    We have confirmed that we are stabilized

  4. postmortem Sep 05, 2025, 02:17 PM UTC

    We recently deployed an authentication related infrastructure change that got overwhelmed at market open due to high request rate on our api. This was triggering several alerts as well as customer complaints about partial HTTP 5xx error responses in our API. Once we identified the issue, we rolled back the change. Impact: In the first 17 minutes of the market open, we had approximately 10% global error rate in our API \(meaning 90% of the requests were still going through without impact\).

Read the full incident report →

Major September 4, 2025

Partial outage on the OPRA market data stream

Detected by Pingoru
Sep 04, 2025, 01:30 PM UTC
Resolved
Sep 04, 2025, 02:29 PM UTC
Duration
59m
Affected: wss://stream.data.alpaca.markets/v1beta1/opra
Timeline · 3 updates
  1. investigating Sep 04, 2025, 02:17 PM UTC

    We are currently investigating this issue.

  2. monitoring Sep 04, 2025, 02:17 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 04, 2025, 02:29 PM UTC

    This incident has been resolved.

Read the full incident report →