PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Alpaca is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Alpaca. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Alpaca issues today?

As of Oct 12, 2026 04:51 UTC, 0 users had reported issues with Alpaca in the previous 24 hours.

How can I report a Alpaca outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Finance

Is Alpaca down right now?

NormalOfficial status last polled Oct 12, 2026 04:33 UTCalpaca.markets Official status page

Are you on the Alpaca team and see something inaccurate? Report it to us. We respond within one business day.

Is Alpaca down right now?

No. Alpaca has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 04:51 UTC

Normal

Alpaca is operating normally

As of Oct 12, 2026 04:51 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

Oct 10, 2026 22:38 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Alpaca.

Incident days

No recorded incident

9h 8m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Alpaca. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

1 incident

Busiest day

9h 8m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Alpaca: vendor-reported minor incident on October 10 (tracked 17 minutes)

Oct 10, 10:21 PM → Oct 10, 10:38 PM · 17 minutes · medium

Alpaca reported a minor-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked this incident for 17 minutes, closing it on 2026-10-10T22:38:32.691Z.

Duration

17 minutes

tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The incident is known from Alpaca's status page.

Incident timeline

Oct 10, 10:21 PM
The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it
Oct 10, 10:21 PM
Status updated: possible issue
Oct 10, 10:38 PM
PulseWatch closed the incident

Official updates

Oct 10, 10:21 PM
Alpaca reported the incident on its status page.
View official source

Reliability

Detected by PulseWatch

30-day uptime

98.7%

90-day uptime

99.52%

Calculated from Alpaca's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other finance services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →

ResolvedMedium

Alpaca: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/10/2026, 10:21:06 PM · 17 min

10:21 PM10:38 PM

Detection10/10/2026, 10:21:06 PM · 1d ago

Detected — medium severity

Alpaca: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Alpaca: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/30/2026, 5:51:01 PM · 3h 0m

05:51 PM08:51 PM

Detection9/30/2026, 5:51:01 PM · 11d ago

Detected — medium severity

Alpaca: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedHigh

Alpaca: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch Alpaca or have an alert rule on it can be alerted, labelled vendor-reported.

9/19/2026, 7:33:57 PM · 1h 59m

07:33 PM09:33 PM

Detection9/19/2026, 7:33:57 PM · 22d ago

Detected — high severity

ResolvedMedium

Alpaca: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/18/2026, 7:13:29 AM · 3h 50m

07:13 AM11:03 AM

Detection9/18/2026, 7:13:29 AM · 23d ago

Detected — medium severity

Alpaca: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Alpaca incident correlated across 1 signal group: official/vendor.

8/31/2026, 10:58:48 AM · 1h 8m

10:58 AM12:07 PM

Detection8/31/2026, 10:58:48 AM · 1mo ago

Detected — medium severity

Alpaca incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Alpaca enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

0 reports aggregated in last 24h
Crowdsourced baseline detection
Official status page

Live signal

Status: Normal
Monitoring: Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage: Verified against the vendor's own incident history
Reports (24h): 0
Baseline / hour: 5
Open threshold: 3x

Official site

alpaca.markets

Related services

Addepar

Finance

Unknown

Airbase

Finance

Unknown

Airwallex

Finance

Vendor-reported issue