Resolved after 44 minutes, affecting broker.accounts.get and JNLC, on March 31, 2026.
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.
Affected components
Update timeline
- 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.
- 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.
- 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.
- 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.
- 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.
Your product runs on more than Alpaca
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services