CheckUpstream does not yet run an independent probe against Alchemy, so no availability figure is published for it — only Alchemy's own disclosure record below. 132 incidents were recorded in the past 12 months; the most recent resolved earlier today after 1 hour. Status signals are polled from Alchemy's official Atlassian Statuspage status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against Alchemy yet, so we publish no availability figure for it. What follows is Alchemy's own disclosure record, which is a different thing.
Vendor disclosed: 116 incidents · 113 of 180 days with none posted · 23d 2h of declared impact
Fewer incidents in the last 30 days than 4% of 232 tracked services.
Share of each window with no impact declared by Alchemy
7d
93.104%
30d
85.553%
90d
94.432%
180d
87.175%
1y
93.675%
Downtime like this can be refundable
If you're a paying Alchemy customer, outages in these windows may count against Alchemy's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Alchemy entitlement →Does Alchemy actually matter to you?
A Alchemy outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 116 incidents Alchemy published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long Alchemy takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 31, 14:39 UTC · resolved in 1h · Resolved
Aug 31, 12:15 UTC · resolved in 1h 25m · Resolved
Aug 31, 12:15 UTC · resolved in 5m · Resolved
Live Alchemy status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/alchemy)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Alchemy is currently Operational. CheckUpstream tracks Alchemy in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Alchemy down" view? See the Alchemy Live status page.
Aug 29, 18:13 UTC · resolved in 1h 41m · Resolved
Aug 25, 13:31 UTC · resolved in 9m · Resolved
Aug 20, 00:36 UTC · resolved in 1h 14m · Resolved
Aug 19, 18:15 UTC · resolved in 21h 54m · Resolved
Aug 19, 06:00 UTC · resolved in 49m · Resolved
Aug 17, 14:18 UTC · resolved in 2h 2m · Resolved
Aug 13, 14:52 UTC · resolved in 11d · Resolved
Aug 13, 11:36 UTC · resolved in 6d · Resolved
Aug 12, 15:44 UTC · resolved in 26m · Resolved
Aug 12, 04:45 UTC · resolved in 11h 5m · Resolved
Aug 10, 12:29 UTC · resolved in 4h 51m · Resolved
Jul 31, 15:08 UTC · resolved in 56m · Resolved
Alchemy's last resolved incident started earlier today and lasted 1 hour (a complete outage).
We don't publish one. CheckUpstream runs no independent probe against Alchemy yet, and the only other figure available would be derived from Alchemy's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add Alchemy to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Alchemy's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.