Alpaca Outage History
Alpaca is up right nowPingoru has recorded 105 incidents for Alpaca: 95 in the last 12 months and 28 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 8 of 720 (1%) |
| May 2026 | 13 | 50 of 744 (7%) |
| June 2026 | 8 | 16 of 720 (2%) |
| July 2026 | 14 | 30 of 744 (4%) |
| August 2026 | 8 | 40 of 744 (5%) |
| September 2026 | 11 | 18 of 720 (3%) |
| October 2026 | 6 | 6 of 592 (1%) |
Incidents, newest first
Major October 13, 2025 New orders are rejected due to validation. – Orders API
Started Oct 13, 2025, 01:46 PM UTC· resolved Oct 13, 2025, 01:46 PM UTC
- investigating Oct 13, 2025, 01:37 PM UTC
We are able to see that the orders are getting rejected due to validation.
- investigating Oct 13, 2025, 01:40 PM UTC
We are continuing to investigate this issue.
- resolved Oct 13, 2025, 01:46 PM UTC
For a short period of time, roughly less than one minute, some new orders containing a fractional component may have been rejected. In addition, fractional orders which were queued prior to the regular market session opening Monday, 10/13, may also have been rejected. These orders were rejected and can be replaced if you have not done so already.
- postmortem Oct 14, 2025, 02:39 PM UTC
**Summary** On October 13, 2025, one of our automated risk controls activated during an unusually high wave of fractional buy orders just before the market opened. The control is designed to pause accepting new fractional orders for a short period to keep overall platform risk within preset limits. After the opening bell, the system rebalanced automatically and order acceptance returned to normal. * This was an operational / availability event related to risk thresholds. * No security or privacy incident occurred \(no data loss, no unauthorized access\). * The issue presented as order rejections, not incorrect executions. **Impact to Customers** * A subset of fractional orders submitted prior to market open were rejected between 9:27 AM and the market opened till 9:31 AM ET. * There was no ongoing impact after 9:31 AM ET. **Root Cause** * A higher-than-usual concentration of fractional buy orders pushed our risk exposure to a preset limit. * The platform temporarily stopped accepting new fractional buy orders as a safeguard until risk returned to normal at the open. **Risk Management and Mitigation StrategyCompleted** * Restored and tested alerts that warn well before limits are reached. * Increased the limit on the relevant risk threshold \(without relaxing our overall risk posture\). **In Progress** * Earlier pre-open processing to smooth order flow before the bell. * Dedicated pre-open monitoring so a human can intervene if thresholds approach. * Pre-open risk adjustments: enabling approved methods to adjust exposure before the open, where appropriate. **Timeline \(Eastern Time\)** * 9:21 AM — Event window begins. * ~9:27 AM — Some orders start rejecting due to protective controls. * 9:31 AM \(market open\) — System auto-rebalances; normal order acceptance resumes.
Notice October 11, 2025 Datase Migration : Postpone the scheduled maintenance due to potential disruption. 12m
Started Oct 11, 2025, 11:52 AM UTC· resolved Oct 11, 2025, 12:04 PM UTC
- 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.
- resolved Oct 11, 2025, 12:04 PM UTC
This incident has been resolved.
Notice October 9, 2025 Intermittent Database Connection Failure – Investigation Underway 1m Account API, Transfers, Orders API, Bank Links and 5 more
Started Oct 09, 2025, 11:21 AM UTC· resolved Oct 09, 2025, 11:23 AM UTC
- 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.
- resolved Oct 09, 2025, 11:23 AM UTC
This incident has been resolved.
- 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.