Live / Alpaca / Incident
Alpaca: Issues with options order confirmations
Alpaca · alpaca.marketsMajor incidentResolved2026-11-13 15:55 UTC
Public — what happened
Summary
Alpaca said some options orders were delayed in reaching the market starting around 12:40 PM ET on November 12, which it attributed to a disruption at an outside trading venue; other order types were not affected. The company said it moved options order flow to a different venue and that orders were processing again by about 18:18 UTC. Later that day Alpaca reported that some options orders that had already been filled were wrongly shown as cancelled or rejected, which it linked to invalid messages from an execution venue. It said filled orders and customers' positions were correct, reported finishing the status corrections around 22:10 UTC, and marked the incident resolved on November 13.
Affected
Orders API
Timeline
- Started — 2026-11-12 18:05 UTC
- Identified — 2026-11-12 18:05 UTC (2 updates)
- Monitoring — 2026-11-12 18:18 UTC
- Investigating — 2026-11-12 20:28 UTC
- Identified — 2026-11-12 20:52 UTC (4 updates)
- Monitoring — 2026-11-12 22:10 UTC
- Resolved — 2026-11-13 15:55 UTC · 21h 50m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Alpaca against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Alpaca: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Alpaca report →
More from Alpaca
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.