Alpaca Status

Resolved: This incident has been resolved.

Monitoring: The BOD job completed successfully. We are monitoring for any additional issues.

Identified: The BOD job is running smoothly. It should complete within the next hour.

Identified: There is a delay in batch data processing. Users may experience delayed memo post credits to their accounts, proceeds from previous business day sales may be unavailable for withdrawal for 1.5h.

Resolved: Cloudflare has resolved their incident and we have migrated our domains back to Cloudflare.

Monitoring: We have bypassed Cloudflare after regaining access to the Cloudflare dashboard for now while they continue having issues.

Investigating: Cloudflare is having an outage which is affecting Alpaca's UI. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

Our APIs are available.

Resolved: This incident has been resolved.

Monitoring: The BOD job completed successfully. We are monitoring for any additional issues.

Identified: The BOD job is running smoothly. It should complete within the next hour.

Identified: There is a delay in batch data processing. Users may experience delayed memo post credits to their accounts, proceeds from previous business day sales may be unavailable for withdrawal for 1.5h.

Postmortem: We are providing an update on a service interruption that impacted transaction processing on November 18, 2025.

What Happened

During a period of heavy transaction load, a specific internal maintenance process temporarily blocked data synchronization between our core accounting and reconciliation systems. This blockage caused a backlog, temporarily delaying the completion status for a segment of executed financial transactions (journals).

Impact

• Approximately 40,000 transactions were processed but temporarily showed an intermediary, "stuck" status.
• Partners who rely on real-time transaction status updates or derived balance fields may have experienced brief delays or temporary inconsistencies in reporting.
• No customer funds or executed transactions were lost. All transactions were successfully processed by our core ledger system.

Resolution

Our engineering team identified the degradation in our database synchronization immediately. We performed a controlled remediation process to reconcile the data, manually updating the status of the backlogged transactions and verifying consistency across all affected systems.

The issue has been fully resolved, and normal transaction processing is fully restored.

Preventative Measures

We have identified the root cause—a long-running internal job that held a database resource for too long—and are implementing immediate fixes to ensure this does not recur:

• Process Optimization: Hardening the internal job to prevent future resource contention.
• Resilience and Monitoring: Enhancing our tools for faster recovery and strengthening alerts around transaction backlogs and database health to detect similar issues instantly.

We appreciate your understanding and thank you for your patience. We remain committed to the highest standards of reliability.

Resolved: Manual batches are cleared and system back to normal

Monitoring: We have processed the large batches and we are back to normal. All backlogs are cleared.

Investigating: JNLCs are getting delayed due to the high volume of batches being processed in our ledger system. We are continuously monitoring the system during this period.

Resolved: Cloudflare has resolved their incident and we have migrated our domains back to Cloudflare.

Monitoring: We have bypassed Cloudflare after regaining access to the Cloudflare dashboard for now while they continue having issues.

Investigating: Cloudflare is having an outage which is affecting Alpaca's UI. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

Our APIs are available.

Resolved: This incident has been resolved.

Monitoring: The BOD job completed successfully. We are monitoring for any additional issues.

Identified: The BOD job is running smoothly. It should complete within the next hour.

Identified: There is a delay in batch data processing. Users may experience delayed memo post credits to their accounts, proceeds from previous business day sales may be unavailable for withdrawal for 1.5h.

Postmortem: We are providing an update on a service interruption that impacted transaction processing on November 18, 2025.

What Happened

During a period of heavy transaction load, a specific internal maintenance process temporarily blocked data synchronization between our core accounting and reconciliation systems. This blockage caused a backlog, temporarily delaying the completion status for a segment of executed financial transactions (journals).

Impact

• Approximately 40,000 transactions were processed but temporarily showed an intermediary, "stuck" status.
• Partners who rely on real-time transaction status updates or derived balance fields may have experienced brief delays or temporary inconsistencies in reporting.
• No customer funds or executed transactions were lost. All transactions were successfully processed by our core ledger system.

Resolution

Our engineering team identified the degradation in our database synchronization immediately. We performed a controlled remediation process to reconcile the data, manually updating the status of the backlogged transactions and verifying consistency across all affected systems.

The issue has been fully resolved, and normal transaction processing is fully restored.

Preventative Measures

We have identified the root cause—a long-running internal job that held a database resource for too long—and are implementing immediate fixes to ensure this does not recur:

• Process Optimization: Hardening the internal job to prevent future resource contention.
• Resilience and Monitoring: Enhancing our tools for faster recovery and strengthening alerts around transaction backlogs and database health to detect similar issues instantly.

We appreciate your understanding and thank you for your patience. We remain committed to the highest standards of reliability.

Resolved: Manual batches are cleared and system back to normal

Monitoring: We have processed the large batches and we are back to normal. All backlogs are cleared.

Investigating: JNLCs are getting delayed due to the high volume of batches being processed in our ledger system. We are continuously monitoring the system during this period.

Postmortem: We are providing an update on a service interruption that impacted transaction processing on November 18, 2025.

What Happened

During a period of heavy transaction load, a specific internal maintenance process temporarily blocked data synchronization between our core accounting and reconciliation systems. This blockage caused a backlog, temporarily delaying the completion status for a segment of executed financial transactions (journals).

Impact

• Approximately 40,000 transactions were processed but temporarily showed an intermediary, "stuck" status.
• Partners who rely on real-time transaction status updates or derived balance fields may have experienced brief delays or temporary inconsistencies in reporting.
• No customer funds or executed transactions were lost. All transactions were successfully processed by our core ledger system.

Resolution

Our engineering team identified the degradation in our database synchronization immediately. We performed a controlled remediation process to reconcile the data, manually updating the status of the backlogged transactions and verifying consistency across all affected systems.

The issue has been fully resolved, and normal transaction processing is fully restored.

Preventative Measures

We have identified the root cause—a long-running internal job that held a database resource for too long—and are implementing immediate fixes to ensure this does not recur:

• Process Optimization: Hardening the internal job to prevent future resource contention.
• Resilience and Monitoring: Enhancing our tools for faster recovery and strengthening alerts around transaction backlogs and database health to detect similar issues instantly.

We appreciate your understanding and thank you for your patience. We remain committed to the highest standards of reliability.

Resolved: Manual batches are cleared and system back to normal

Monitoring: We have processed the large batches and we are back to normal. All backlogs are cleared.

Investigating: JNLCs are getting delayed due to the high volume of batches being processed in our ledger system. We are continuously monitoring the system during this period.

Investigating: MEMOPOST that are submitted on 18-NOV-2025 should settle by 19-NOV. Missed settlements should have been cancelled by 19-NOV 8:00 PM ET. However internal service that cancels the missed settlement has failed to cancel the MEMO

Resolved: This incident has been resolved.

Monitoring: The BOD job completed successfully. We are monitoring for any additional issues.

Identified: The BOD job is running smoothly. It should complete within the next hour.

Identified: There is a delay in batch data processing. Users may experience delayed memo post credits to their accounts, proceeds from previous business day sales may be unavailable for withdrawal for 1.5h.