Alpaca Outage History

Alpaca is up right now

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

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

Source: https://status.alpaca.markets

Notice June 16, 2026

[RESOLVED] SPCX Fractional Trading Briefly Unavailable During Extended Hours

Detected by Pingoru
Jun 16, 2026, 01:30 PM UTC
Resolved
Jun 16, 2026, 01:30 PM UTC
Duration
—
Affected: Orders APIAssets
Timeline · 1 update
  1. resolved Jun 16, 2026, 01:30 PM UTC

    There was a brief disruption to fractional SPCX trading during today's extended hours session. We identified an issue that required us to temporarily suspend fractional EH trading at 8:41 AM EST. We are pleased to confirm it has been resolved as of 9:08 AM EST (~27 minutes). Fractional SPCX trading is now available. Whole-share SPCX orders were not impacted. We apologize for any inconvenience , Detailed root cause analysis is in progress and we'll share more details as available.

Read the full incident report →

Notice June 14, 2026

Funding Services Disruption - Resolved

Detected by Pingoru
Jun 14, 2026, 06:00 PM UTC
Resolved
Jun 14, 2026, 06:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 14, 2026, 06:26 AM UTC

    Time: June 14, 2026 | 04:11-06:00 AM UTC Identified (04:11 UTC): Funding services - funding wallets, instant funding, and deposits/withdrawals - were unavailable due to extended maintenance by an upstream payment provider. Resolved (06:00 UTC): Services recovered and are operating normally. Trading and all other account functionality were unaffected throughout. We apologize for the disruption.

Read the full incident report →

Notice June 11, 2026

[ Resolved ]Intermittent Order Rejections on One Execution Venue

Detected by Pingoru
Jun 11, 2026, 03:58 PM UTC
Resolved
Jun 11, 2026, 03:58 PM UTC
Duration
—
Affected: Orders APIbroker.trading.accounts.account_id.orders.get
Timeline · 1 update
  1. resolved Jun 11, 2026, 03:58 PM UTC

    Time: June 11, 2026 | 11:05 AM – 11:17 AM EDT Our connection to one of our execution venues experienced a brief disconnection. Orders submitted during this period that were pending routing were rejected by the venue upon reconnection. Fully resolved. The connection was restored at 11:17 AM EDT and all order routing is operating normally.

Read the full incident report →

Minor May 30, 2026

Broker API and Trading API Timeouts

Detected by Pingoru
May 30, 2026, 02:44 AM UTC
Resolved
May 30, 2026, 02:48 AM UTC
Duration
3m
Affected: Account APIPaper Account APIbroker.accounts.getOrders APIPaper Order APIbroker.accounts.account_id.transfers.getPositions APIPaper Positions APIbroker.assets.getAssets APIPaper Assets APIbroker.trading.accounts.account_id.account.getbroker.trading.accounts.account_id.orders.getTrade Update Streamingbroker.accounts.account_id.documents.getbroker.journals.getFractional Ordersbroker.ledgers.getbroker.accounts.activities.getbroker.accounts.account_id.recipient_banks.getbroker.events.accounts.status.getbroker.events.trades.getbroker.events.journals.status.getInstant funding & SettlementsSweep and cash interestFPSL ProgramFunding WalletsAssetsCalendar and ClockAccounts Events (SSE)Journal Events (SSE)Transfer Events (SSE)Trade Events (SSE)Admin Action Events (SSE)Non Trade Activities (NTAs) Events (SSE)Funding Status Events (SSE)OAuth endpointWatchlist EndpointCorporate Action EndpointKYC EndpointLogos EndpointReporting - Aggregate Position endpointReporting - EOD Cash Interest DetailsPortfolio History EndpointRebalancerCrypto Funding
Timeline · 2 updates
  1. investigating May 30, 2026, 02:44 AM UTC

    Our team is aware of an increase in timeout errors across Broker and Trading API. We are currently investigating and will provide updates as we progress. Thank you for your patience.

  2. resolved May 30, 2026, 02:48 AM UTC

    On May 29, 2026, at 10:05 PM ET, Alpaca experienced an increase in timeout errors for Broker and Trading API services for approximately nine minutes. Services were restored quickly and our team is continuing to monitor to ensure they remain operational.

Read the full incident report →

Minor May 28, 2026

Alpaca Documentation Site Experiencing Intermittent Issues

Detected by Pingoru
May 28, 2026, 01:55 PM UTC
Resolved
May 28, 2026, 03:59 PM UTC
Duration
2h 4m
Affected: Doumentation
Timeline · 4 updates
  1. monitoring May 28, 2026, 01:55 PM UTC

    An outage at our vendor is causing intermittent issues at our documentation site, and a fix is being implemented. Our team is monitoring the situation and will provide updates as we learn more. Thank you for your patience.

  2. monitoring May 28, 2026, 02:18 PM UTC

    An outage at our vendor is causing intermittent issues at our documentation site, and a fix is being implemented. We are continuing to monitor the situation and will provide updates as we learn more. Thank you for your continued patience.

  3. monitoring May 28, 2026, 03:06 PM UTC

    We are no longer seeing intermittent issues. Our team will continue to monitor and provide updates. Thank you for your patience

  4. resolved May 28, 2026, 03:59 PM UTC

    This incident is resolved. Thank you for your patience.

Read the full incident report →

Minor May 27, 2026

Alpaca Documentation site is Offline

Detected by Pingoru
May 27, 2026, 03:02 PM UTC
Resolved
May 27, 2026, 03:58 PM UTC
Duration
56m
Affected: Doumentation
Timeline · 2 updates
  1. identified May 27, 2026, 03:02 PM UTC

    An outage at our vendor is preventing our documentation site from loading, and a fix is being implemented. Our team is monitoring the situation and will provide updates as we learn more. Thank you for your patience.

  2. resolved May 27, 2026, 03:58 PM UTC

    Our documentation site online and the issue has been resolved. Thank you for your patience.

Read the full incident report →

Minor May 26, 2026

Broker API Endpoints are receiving timeout errors

Detected by Pingoru
May 26, 2026, 03:54 PM UTC
Resolved
May 26, 2026, 05:11 PM UTC
Duration
1h 16m
Affected: broker.accounts.getPortfolio History Endpoint
Timeline · 7 updates
  1. investigating May 26, 2026, 03:54 PM UTC

    We are aware of an issue causing timeouts on Broker API endpoints. Our team is currently investigating and will provide updates as we learn more. Thank you for your patience.

  2. investigating May 26, 2026, 04:04 PM UTC

    We are continuing to investigate the issue causing timeouts on Broker API endpoints. We will provide additional updates as soon as more information is available. Thank you for your continued patience.

  3. monitoring May 26, 2026, 04:10 PM UTC

    Our team has identified a potential cause for the timeouts on Broker API endpoints. We are working to implement a fix and restore services to fully operational. We will continue to provide updates as we learn more. Thank you for your continued patience.

  4. monitoring May 26, 2026, 04:15 PM UTC

    Our team has identified a potential cause for the timeouts on Broker API endpoints. We are working to implement a fix and restore services to fully operational. We will continue to monitor and provide updates as we learn more. Thank you for your continued patience.

  5. monitoring May 26, 2026, 04:26 PM UTC

    We're seeing improved response times for Broker API endpoints. We're continuing to monitor the situation and will provide further updates as needed. Thank you for your continued patience.

  6. monitoring May 26, 2026, 04:44 PM UTC

    We're seeing improved response times for Broker API endpoints. We're continuing to monitor the situation and will provide further updates as needed. Thank you for your continued patience.

  7. resolved May 26, 2026, 05:11 PM UTC

    This issue has been resolved, and endpoint connections are now fully operational. Thank you for your patience.

Read the full incident report →

Minor May 23, 2026

Disruption of Trading API services

Detected by Pingoru
May 23, 2026, 04:52 AM UTC
Resolved
May 23, 2026, 02:06 AM UTC
Duration
—
Timeline · 1 update
  1. resolved May 23, 2026, 04:52 AM UTC

    On May 22, 2026, at 10:06 PM ET, Alpaca experienced a partial outage of Trading API services for approximately five minutes. Services were restored quickly and our team is continuing to monitor Trading API services to ensure they remain operational.

Read the full incident report →

Critical May 19, 2026

End of Day reporting positions delayed

Detected by Pingoru
May 19, 2026, 07:42 AM UTC
Resolved
May 19, 2026, 09:13 AM UTC
Duration
1h 30m
Affected: Positions APIReporting - Aggregate Position endpoint
Timeline · 7 updates
  1. investigating May 19, 2026, 07:42 AM UTC

    We are investigating above issue. Updates will follow.

  2. investigating May 19, 2026, 07:46 AM UTC

    Gobroker BOD is running longer than expected today , You should see correct Balances already , position data is delayed.

  3. investigating May 19, 2026, 07:55 AM UTC

    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

  4. investigating May 19, 2026, 08:18 AM UTC

    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.

  5. identified May 19, 2026, 08:43 AM UTC

    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.

  6. monitoring May 19, 2026, 09:04 AM UTC

    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.

  7. resolved May 19, 2026, 09:13 AM UTC

    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

Read the full incident report →

Notice May 16, 2026

Delayed EOD Balance & Position Snapshot

Detected by Pingoru
May 16, 2026, 09:55 AM UTC
Resolved
May 16, 2026, 10:48 AM UTC
Duration
53m
Affected: Reporting - EOD Cash Interest Details
Timeline · 3 updates
  1. identified May 16, 2026, 09:55 AM UTC

    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.

  2. identified May 16, 2026, 10:10 AM UTC

    EOD Balance processing has completed. We are syncing position snapshots and expect completion before 7:00 AM EDT.

  3. resolved May 16, 2026, 10:48 AM UTC

    EOD balance and position batch processing has completed successfully.

Read the full incident report →

Notice May 15, 2026

Overnight Trading Symbol Status Update Issue

Detected by Pingoru
May 15, 2026, 05:14 AM UTC
Resolved
May 15, 2026, 06:30 AM UTC
Duration
1h 16m
Affected: Orders APIbroker.assets.getAssets APIbroker.assets.getTrade Update StreamingNon Tradable ActivitesFractional Ordersbroker.accounts.activities.get
Timeline · 5 updates
  1. investigating May 15, 2026, 05:14 AM UTC

    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.

  2. identified May 15, 2026, 05:26 AM UTC

    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.

  3. monitoring May 15, 2026, 06:02 AM UTC

    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.

  4. resolved May 15, 2026, 06:30 AM UTC

    After monitoring we are no longer seeing issues. Overnight trading symbol eligibility appears to be operating normally.

  5. postmortem May 15, 2026, 06:06 PM UTC

    On May 15, we identified an issue affecting overnight trading. Some securities that are generally eligible for overnight trading were temporarily ineligible for overnight trading, preventing clients from placing or modifying orders for those symbols during the overnight session. ‌ Our engineering team identified an issue resulting from receiving an erroneous source file form our execution venue and manually updated the system restoring overnight trading for the impacted symbols... Regular market-hours trading, other asset classes, account balances, positions, and prior transactions are not impacted. ‌ Thank you for your patience and understanding as we worked to restore services.

Read the full incident report →

Minor April 27, 2026

Dashboard SMS 2FA

Detected by Pingoru
Apr 27, 2026, 12:13 PM UTC
Resolved
Apr 27, 2026, 07:54 PM UTC
Duration
7h 40m
Affected: Dashboard
Timeline · 4 updates
  1. investigating Apr 27, 2026, 12:13 PM UTC

    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.

  2. identified Apr 27, 2026, 12:14 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 27, 2026, 07:20 PM UTC

    We believe the issue with SMS based two-factor authentication for the Trading Dashboard is resolved. We are currently monitoring the service to validate.

  4. resolved Apr 27, 2026, 07:54 PM UTC

    Login for Trading Dashboard is working normally again..

Read the full incident report →

Minor April 7, 2026

JIT Reports are not available for 6-April-2026

Detected by Pingoru
Apr 07, 2026, 02:45 AM UTC
Resolved
Apr 07, 2026, 03:30 AM UTC
Duration
44m
Affected: Just in Time
Timeline · 4 updates
  1. investigating Apr 07, 2026, 02:45 AM UTC

    Just In Time reports are not generated

  2. investigating Apr 07, 2026, 03:09 AM UTC

    Team is still working to identify the root cause

  3. identified Apr 07, 2026, 03:22 AM UTC

    We have identified the underlying cause. We are working on the recovery.

  4. resolved Apr 07, 2026, 03:30 AM UTC

    We have fixed the issue and reports are now available

Read the full incident report →

Notice March 31, 2026

Service degradation across multiple API's

Detected by Pingoru
Mar 31, 2026, 01:25 PM UTC
Resolved
Mar 31, 2026, 02:10 PM UTC
Duration
44m
Affected: broker.accounts.getJNLC
Timeline · 5 updates
  1. investigating Mar 31, 2026, 01:25 PM UTC

    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.

  2. identified Mar 31, 2026, 01:34 PM UTC

    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.

  3. monitoring Mar 31, 2026, 01:43 PM UTC

    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.

  4. monitoring Mar 31, 2026, 01:56 PM UTC

    All services are operating normally with no issues detected. We are continuing to monitor and will provide updates if anything changes.

  5. resolved Mar 31, 2026, 02:10 PM UTC

    The issue has been fully resolved and we are marking this incident as closed. If you observe any further issues, please don't hesitate to reach out to us.

Read the full incident report →

Major March 23, 2026

Journals Delayed

Detected by Pingoru
Mar 23, 2026, 07:45 PM UTC
Resolved
Mar 23, 2026, 08:10 PM UTC
Duration
25m
Affected: JNLC
Timeline · 4 updates
  1. investigating Mar 23, 2026, 07:45 PM UTC

    We are seeing issue with journal processing due to redpanda.

  2. identified Mar 23, 2026, 07:48 PM UTC

    We have identified an issue with redpanda cluster and we are in the process of restart.

  3. monitoring Mar 23, 2026, 07:55 PM UTC

    The cluster is up and journals are getting processed

  4. resolved Mar 23, 2026, 08:10 PM UTC

    Journal processing are back to normal

Read the full incident report →

Notice March 17, 2026

marketing website down

Detected by Pingoru
Mar 17, 2026, 04:03 PM UTC
Resolved
Mar 17, 2026, 04:17 PM UTC
Duration
13m
Timeline · 2 updates
  1. investigating Mar 17, 2026, 04:03 PM UTC

    We are investigating above issue. Updates will follow.

  2. resolved Mar 17, 2026, 04:17 PM UTC

    Website is back up and there was no impact.

Read the full incident report →

Minor February 9, 2026

Timeouts on Options Market Data Snapshots

Detected by Pingoru
Feb 09, 2026, 05:01 PM UTC
Resolved
Feb 09, 2026, 05:36 PM UTC
Duration
35m
Affected: https://data.alpaca.markets/v1beta1/options/snapshots
Timeline · 3 updates
  1. investigating Feb 09, 2026, 05:01 PM UTC

    We are currently investigating this issue.

  2. investigating Feb 09, 2026, 05:16 PM UTC

    We are continuing to investigate this issue.

  3. resolved Feb 09, 2026, 05:36 PM UTC

    This issue has been resolved.

Read the full incident report →