Alpaca logo

Is Alpaca Down?

FinTech & PaymentsLive status, outages, and incident history

No. Alpaca is up right now.

Every monitored Alpaca system is operational as of October 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment Alpaca breaks

Alpaca is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Alpaca status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Alpaca Component Status

The main Alpaca systems on this page. All 102 are operational right now.

102operational
Accounts » Bank Links
Operational
Accounts » Buying Power
Operational
Accounts » New Account Onboarding
Operational

99 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Accounts » Non Tradable Activites, Accounts » Transfers, Accounts » Turbo Tax Integration, Broker API (Sandbox) » broker.accounts.account_id.documents.get, Broker API (Sandbox) » broker.accounts.account_id.recipient_banks.get, Broker API (Sandbox) » broker.accounts.account_id.transfers.get, Broker API (Sandbox) » broker.accounts.activities.get, Broker API (Sandbox) » broker.accounts.get, Broker API (Sandbox) » broker.assets.get, Broker API (Sandbox) » broker.events.accounts.status.get, Broker API (Sandbox) » broker.events.journals.status.get, Broker API (Sandbox) » broker.events.trades.get, and 87 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Alpaca Outages & Incidents

Incident history from the official Alpaca status page, including resolution updates.

Sandbox LatencyResolved Oct 10, 2026 · 43 minResolved

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. --- [2026-10-10T17:48:22.024-04:00] (monitoring) Service has been restored for affected sandbox requests, and we’re monitoring performance to confirm stability. --- [2026-10-10T17:38:13.558-04:00] (investigating) 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.

Scheduled Sandbox & Production maintenance on Saturday, October 10th, 2026.Scheduled for Oct 10, 2026 · 1h 0mScheduled

Verification is currently underway for the maintenance items. --- [2026-10-10T07:00:23.539-04:00] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-10-10T06:00:21.333-04:00] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-10-06T11:42:52.434-04:00] (scheduled) Dear Users, This is a notice regarding the upcoming system maintenance to the Sandbox & Production environment. With this 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. Sandbox & Production Maintenance Window When: Saturday, October 10th, 2026 Time: 7:00 AM ET to 8:00 AM ET Downtime: The Sandbox & Production environment may be unavailable for 30 minutes at the start of the maintenance window with increased latency or small periods of unavailability during the remaining time. Impact: During the maintenance windows, API connectivity and platform requests may experience brief intermittent errors or elevated latency while traffic is transitioned through upgraded infrastructure components. Once the maintenance is complete, all services will automatically resume normal operation. 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. Rationale: This maintenance window takes place during the period of lowest global trading activity. Action Required 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. For the most up-to-date information on this maintenance event, please refer to our Status Page and subscribe for updates. After 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, The Alpaca Team

Delays in End-of-Day Position Reporting for a Subset of AccountsResolved Oct 9, 2026 · 2h 8mResolved

All daily EOD sync have been completed. This incident is now resolved. --- [2026-10-09T04:01:57.639-04:00] (monitoring) 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. --- [2026-10-09T03:59:51.256-04:00] (identified) The sync processing job is currently running. EOD position synchronization remains delayed while the job completes. Cash balances and withdrawables are unaffected and available. We are actively monitoring the process. --- [2026-10-09T03:59:41.098-04:00] (investigating) We are currently experiencing a delay in our Beginning of Day (BOD) processing. As a result, EOD position (GET /v1/reporting/eod-positions) may temporarily reflect the previous business day's values.

Alpaca Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Alpaca incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Jul 13100.00% average · 14 days with incidentsOct 11

Going further back: Alpaca uptime by month and every recorded Alpaca outage.

Live Alpaca Outage Reports

Problems reported by engineers using Alpaca. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Alpaca problems reported yet.

Something wrong with Alpaca on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Alpaca

Alpaca is a commission-free stock trading API for developers, enabling algorithmic trading and brokerage applications. Track Alpaca status and outages here.

Over the past 30 days, PulsAPI has measured Alpaca uptime at 100.00%. Response times, incident history, and SLA tracking for Alpaca are available on the PulsAPI dashboard.

Alpaca Status FAQ

Is Alpaca down right now?

The verdict at the top of this page comes from the latest poll of the official Alpaca status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Alpaca is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Alpaca recovers.

How do I check Alpaca uptime history?

PulsAPI tracks Alpaca uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Alpaca changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Alpaca outages?

PulsAPI reads the official Alpaca status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Alpaca components?

Yes. PulsAPI monitors 102 individual Alpaca components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Alpaca goes down?

Yes. Create a free account and subscribe to Alpaca: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Alpaca to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Alpaca problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Alpaca?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Alpaca plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Alpaca with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services