Alpaca experienced a notice incident on May 15, 2026 affecting Orders API and broker.assets.get and 1 more component, lasting 1h 16m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.
- 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.
- 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.
- 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.
- 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.