Live / Alpaca / Incident
Alpaca: 3rd Party Outage affecting Market Data
Alpaca · alpaca.marketsCritical outageResolved2026-10-15 18:46 UTC
Public — what happened
Summary
Alpaca reported a critical problem starting at 17:32 UTC on 2026-10-15 in which its IEX and SIP market data feeds stopped delivering reliably, so new bars and trades might not refresh for affected symbols. By 17:39 UTC, Alpaca said it had traced the problem to a network disruption at an outside data vendor rather than its own systems. As a safeguard against orders filling at outdated prices, the company briefly blocked opening new positions through fractional and dollar-amount trades at 18:09 UTC, while whole-share trading and closing positions stayed available. Alpaca said the feeds were back by 18:15 UTC, fractional and dollar-amount trading was turned back on at 18:18 UTC, and the incident was marked resolved at 18:46.
Affected
wss://stream.data.alpaca.markets/v2/sip, wss://stream.data.alpaca.markets/v2/iex
Timeline
- Started — 2026-10-15 17:32 UTC
- Investigating — 2026-10-15 17:32 UTC
- Identified — 2026-10-15 17:39 UTC (4 updates)
- Monitoring — 2026-10-15 18:15 UTC (2 updates)
- Resolved — 2026-10-15 18:46 UTC · 1h 13m 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 43, 2026, our weekly internet health report.