User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
alpaca.markets · Cloud & developer
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with Alpaca.
Estimated fix: Not enough Alpaca history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–9 h; 83 outages).
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 9 min ago. Last stored result reached it in 108 ms.
Minor incident
Some components degraded (no active incident posted) Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 05 | 0 | 0.0 | 110 ms | 0 |
| Tue 07 | 0 | 0.0 | 95 ms | 0 |
| Tue 09 | 0 | 0.0 | 104 ms | 0 |
| Tue 11 | 0 | 0.0 | 107 ms | 0 |
| Tue 13 | 0 | 0.0 | 121 ms | 0 |
| Tue 15 | 0 | 0.0 | 125 ms | 0 |
| Tue 18 | 0 | 0.0 | 118 ms | 0 |
| Tue 20 | 0 | 0.0 | 94 ms | 0 |
| Tue 22 | 0 | 0.0 | 83 ms | 0 |
| Wed 00 | 0 | 0.0 | 153 ms | 0 |
| Wed 02 | 0 | 0.0 | 115 ms | 0 |
| Wed 05 | 0 | 0.0 | 119 ms | 0 |
| Wed 07 | 0 | 0.0 | 99 ms | 0 |
| Wed 09 | 0 | 0.0 | 136 ms | 0 |
| Wed 11 | 0 | 0.0 | 109 ms | 0 |
| Wed 14 | 0 | 0.0 | 134 ms | 0 |
| Wed 16 | 0 | 0.0 | 87 ms | 0 |
| Wed 18 | 0 | 0.0 | 247 ms | 0 |
| Wed 20 | 0 | 0.0 | 94 ms | 0 |
| Wed 22 | 0 | 0.0 | 167 ms | 0 |
| Thu 00 | 0 | 0.0 | 133 ms | 0 |
| Thu 02 | 0 | 0.0 | 214 ms | 0 |
| Thu 05 | 0 | 0.0 | 145 ms | 0 |
| Thu 07 | 0 | 0.0 | 120 ms | 0 |
| Thu 09 | 0 | 0.0 | 100 ms | 0 |
| Thu 11 | 0 | 0.0 | 115 ms | 0 |
| Thu 13 | 0 | 0.0 | 77 ms | 0 |
| Thu 15 | 0 | 0.0 | 112 ms | 0 |
| Thu 17 | 0 | 0.0 | 121 ms | 0 |
| Thu 19 | 0 | 0.0 | 95 ms | 0 |
| Thu 21 | 0 | 0.0 | 105 ms | 0 |
| Thu 22 | 0 | 0.0 | 117 ms | 0 |
| Fri 00 | 0 | 0.0 | 155 ms | 0 |
| Fri 03 | 0 | 0.0 | 133 ms | 0 |
| Fri 05 | 0 | 0.0 | 108 ms | 0 |
| Fri 07 | 0 | 0.0 | 145 ms | 0 |
| Fri 09 | 0 | 0.0 | 57 ms | 0 |
| Fri 11 | 0 | 0.0 | 160 ms | 0 |
| Fri 13 | 0 | 0.0 | 60 ms | 0 |
| Fri 15 | 0 | 0.0 | 98 ms | 0 |
| Fri 17 | 0 | 0.0 | 102 ms | 0 |
| Fri 18 | 0 | 0.0 | 85 ms | 0 |
| Fri 19 | 0 | 0.0 | 111 ms | 0 |
| Fri 21 | 0 | 0.0 | 109 ms | 0 |
| Fri 22 | 0 | 0.0 | 104 ms | 0 |
| Sat 00 | 0 | 0.0 | 106 ms | 0 |
| Sat 02 | 0 | 0.0 | 93 ms | 0 |
| Sat 04 | 0 | 0.0 | 108 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Alpaca yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Alpaca goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Alpaca alerts to Slack, Discord or a webhook — free.
Alpaca is listed in our Cloud & developer category and checked at alpaca.markets. Alpaca's easy to use APIs allow developers and businesses to trade algorithms, build apps and embed investing into their services.
Alpaca publishes an official status page at status.alpaca.markets; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 105 ms average, 57–202 ms range across 16 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
We have not recorded a public Alpaca incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
105 ms on average over the last 24 hours (57–202 ms).
Yes, at https://status.alpaca.markets.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Alpaca here at once, the problem is on Alpaca's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Alpaca. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.