Alpaca incident

Service degradation across multiple API's

Notice Resolved View vendor source →

Alpaca experienced a notice incident on March 31, 2026 affecting broker.accounts.get and JNLC, lasting 44m. The incident has been resolved; the full update timeline is below.

Started
Mar 31, 2026, 01:25 PM UTC
Resolved
Mar 31, 2026, 02:10 PM UTC
Duration
44m
Detected by Pingoru
Mar 31, 2026, 01:25 PM UTC

Affected components

broker.accounts.getJNLC

Update timeline

  1. investigating Mar 31, 2026, 01:25 PM UTC

    We are currently investigating a service degradation that is impacting account information access and transaction processing. Client Impact: Users may experience intermittent timeouts or delays when attempting to access their account details. Current Status: Our engineering teams are actively engaged and working to address the underlying issues related to processing capacity and system delays. We are prioritising a resolution and will provide an update when more information is available.

  2. identified Mar 31, 2026, 01:34 PM UTC

    We are seeing improvement in API response times, and journals are no longer getting stuck. We are continuing to monitor the situation and will post further updates as needed.

  3. monitoring Mar 31, 2026, 01:43 PM UTC

    The service has been restored to normal operation. We are no longer seeing issues with any API endpoints or journals. We will continue monitoring to ensure stability.

  4. monitoring Mar 31, 2026, 01:56 PM UTC

    All services are operating normally with no issues detected. We are continuing to monitor and will provide updates if anything changes.

  5. resolved Mar 31, 2026, 02:10 PM UTC

    The issue has been fully resolved and we are marking this incident as closed. If you observe any further issues, please don't hesitate to reach out to us.