Is Alpaca down?

Last checked 2m ago
Current status
Alpaca is up

No incidents right now.

Official status page: https://status.alpaca.markets · Polled every 5 minutes · 101 components tracked

Alpaca is operational right now. Last checked 2m ago; the most recent incident resolved 2d ago.

Real-time Alpaca status, recent outages, and incident history — pulled directly from Alpaca's official status page at https://status.alpaca.markets every 5 minutes. Pingoru tracks 101 Alpaca services and has captured 28 incidents in the last 90 days (99.28% uptime). Get email, Slack, Discord, or webhook alerts the moment Alpaca reports a new incident — free for 5 monitors, no credit card.

Users who monitor Alpaca also follow these APIs services: Vonage Make Vonage Business Retool Telnyx Mapbox Vonage API EasyPost Celigo Olo View all 6,000+ providers
Alpaca uptime 99.28% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jun 11, 2026, 03:58 PM UTC · Resolved Jun 11, 2026, 03:58 PM UTC
    Orders APIbroker.trading.accounts.account_id.orders.get
    Timeline · 1 update
    • resolved · Jun 11, 2026, 03:58 PM UTC

      Time: June 11, 2026 | 11:05 AM – 11:17 AM EDT Our connection to one of our execution venues experienced a brief disconnection. Orders submitted during this period that were pending routing were rejected by the venue upon reconnection. Fully resolved. The connection was restored at 11:17 AM EDT and all order routing is operating normally.

    Latest: Time: June 11, 2026 | 11:05 AM – 11:17 AM EDT Our connection to one of our execution venues experienced a brief disconnection. Orders submitted during this period that were pending…

  2. Resolved 1h 42m
    Started Jun 01, 2026, 02:28 PM UTC · Resolved Jun 01, 2026, 04:10 PM UTC
    JNLC
    Timeline · 11 updates
    • investigating · Jun 01, 2026, 02:28 PM UTC

      We are currently experiencing slower than normal processing times for JNLC transactions. Journals are processing successfully but at a reduced rate compared to typical performance.

    • investigating · Jun 01, 2026, 02:46 PM UTC

      We are still investigating the issue. Update will follow shortly.

    • investigating · Jun 01, 2026, 02:58 PM UTC

      Our team is continuing to investigate the slower than normal processing times for JNLC transactions. We will provide updates as we progress. Thank you for your continued patience.

    • investigating · Jun 01, 2026, 03:08 PM UTC

      Our team is continuing to investigate the slower than normal processing times for JNLC transactions. We will provide updates as we progress. Thank you for your continued patience.

    • identified · Jun 01, 2026, 03:18 PM UTC

      Our team is working to implement a fix to improve JNLC processing times. We will provide updates as we progress. Thank you for your continued patience.

    • identified · Jun 01, 2026, 03:33 PM UTC

      Our team is working to implement a fix to improve JNLC processing times. We will provide updates as we progress. Thank you for your continued patience.

    • identified · Jun 01, 2026, 03:46 PM UTC

      Our team is working to implement a fix to improve JNLC processing times. We will provide updates as we progress. Thank you for your continued patience.

    • identified · Jun 01, 2026, 03:57 PM UTC

      A fix has been implemented to improve JNLC processing times, and we are monitoring to ensure journals are processing from the queue. We will continue to provide updates as we monitor. Thank you for your continued patience.

    • monitoring · Jun 01, 2026, 04:03 PM UTC

      We are now seeing journals processing as normal and will continue to monitor them. Thank you for your continued patience.

    • resolved · Jun 01, 2026, 04:10 PM UTC

      Journals are now processing as normal. Thank you for your patience during this time.

    • postmortem · Jun 02, 2026, 06:02 PM UTC

      On June 1, 2026, our platform experienced a processing delay affecting journal cash transfers \(JNLCs\). The issue originated from a surge in journal volume at market open, which caused unexpected delays. However, no transactions were lost, rejected, or duplicated, and there was no impact to funds or positions. All queued journals were processed in order once throughput was restored. Our engineering teams deployed a fix and continued to monitor the situation for 24 hours post deployment. There have been no issues since and the incident is now closed. We know timely processing is critical to your operations, and we thank you for your understanding as we restored services.

    Latest: On June 1, 2026, our platform experienced a processing delay affecting journal cash transfers \(JNLCs\). The issue originated from a surge in journal volume at market open, which c…

  3. Resolved 3m
    Started May 30, 2026, 02:44 AM UTC · Resolved May 30, 2026, 02:48 AM UTC
    Account APIPaper Account APIbroker.accounts.getOrders APIPaper Order APIbroker.accounts.account_id.transfers.getPositions APIPaper Positions APIbroker.assets.getAssets API
    Timeline · 2 updates
    • investigating · May 30, 2026, 02:44 AM UTC

      Our team is aware of an increase in timeout errors across Broker and Trading API. We are currently investigating and will provide updates as we progress. Thank you for your patience.

    • resolved · May 30, 2026, 02:48 AM UTC

      On May 29, 2026, at 10:05 PM ET, Alpaca experienced an increase in timeout errors for Broker and Trading API services for approximately nine minutes. Services were restored quickly and our team is continuing to monitor to ensure they remain operational.

    Latest: On May 29, 2026, at 10:05 PM ET, Alpaca experienced an increase in timeout errors for Broker and Trading API services for approximately nine minutes. Services were restored quickly…

  4. Resolved 2h 4m
    Started May 28, 2026, 01:55 PM UTC · Resolved May 28, 2026, 03:59 PM UTC
    Doumentation
    Timeline · 4 updates
    • monitoring · May 28, 2026, 01:55 PM UTC

      An outage at our vendor is causing intermittent issues at our documentation site, and a fix is being implemented. Our team is monitoring the situation and will provide updates as we learn more. Thank you for your patience.

    • monitoring · May 28, 2026, 02:18 PM UTC

      An outage at our vendor is causing intermittent issues at our documentation site, and a fix is being implemented. We are continuing to monitor the situation and will provide updates as we learn more. Thank you for your continued patience.

    • monitoring · May 28, 2026, 03:06 PM UTC

      We are no longer seeing intermittent issues. Our team will continue to monitor and provide updates. Thank you for your patience

    • resolved · May 28, 2026, 03:59 PM UTC

      This incident is resolved. Thank you for your patience.

    Latest: This incident is resolved. Thank you for your patience.

  5. Resolved 56m
    Started May 27, 2026, 03:02 PM UTC · Resolved May 27, 2026, 03:58 PM UTC
    Doumentation
    Timeline · 2 updates
    • identified · May 27, 2026, 03:02 PM UTC

      An outage at our vendor is preventing our documentation site from loading, and a fix is being implemented. Our team is monitoring the situation and will provide updates as we learn more. Thank you for your patience.

    • resolved · May 27, 2026, 03:58 PM UTC

      Our documentation site online and the issue has been resolved. Thank you for your patience.

    Latest: Our documentation site online and the issue has been resolved. Thank you for your patience.

See the full Alpaca outage history

15 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Alpaca outage history →

Or sign up free to get alerts when Alpaca breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 20 incidents View full outage history →