Live  /  Alpaca  /  Incident

Alpaca: Delays in End-of-Day Position Reporting for a Subset of Accounts

Alpaca · alpaca.marketsResolved2026-10-09 09:25 UTC
Public — what happened

Summary

Alpaca said that on 2026-10-09 at 07:16 UTC a hold-up in its start-of-day processing meant end-of-day position reports for some accounts might show figures from the prior business day. By 07:47 UTC the company said the synchronization job was underway, and that cash balances and withdrawable amounts were not affected. Alpaca later estimated the job would finish around 09:30 UTC, and the incident was marked resolved at 09:25.

Affected

Reporting - Aggregate Position endpoint

As listed on Alpaca’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 42, 2026, our weekly internet health report.

The full archive is on the Alpaca status & history page.

Related: Alpaca status & history. SquidGrid is not affiliated with Alpaca.