User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is zama down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → zama.org—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 79 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 99 ms | 0 |
| Tue 00 | 0 | 0.0 | 42 ms | 0 |
| Tue 02 | 0 | 0.0 | 86 ms | 0 |
| Tue 04 | 0 | 0.0 | 89 ms | 0 |
| Tue 06 | 0 | 0.0 | 49 ms | 0 |
| Tue 08 | 0 | 0.0 | 61 ms | 0 |
| Tue 10 | 0 | 0.0 | 121 ms | 0 |
| Tue 12 | 0 | 0.0 | 40 ms | 0 |
| Tue 15 | 0 | 0.0 | 117 ms | 0 |
| Tue 17 | 0 | 0.0 | 140 ms | 0 |
| Tue 19 | 0 | 0.0 | 59 ms | 0 |
| Tue 21 | 0 | 0.0 | 115 ms | 0 |
| Wed 00 | 0 | 0.0 | 47 ms | 0 |
| Wed 02 | 0 | 0.0 | 81 ms | 0 |
| Wed 04 | 0 | 0.0 | 58 ms | 0 |
| Wed 06 | 0 | 0.0 | 121 ms | 0 |
| Wed 09 | 0 | 0.0 | 44 ms | 0 |
| Wed 11 | 0 | 0.0 | 54 ms | 0 |
| Wed 13 | 0 | 0.0 | 84 ms | 0 |
| Wed 15 | 0 | 0.0 | 33 ms | 0 |
| Wed 17 | 0 | 0.0 | 61 ms | 0 |
| Wed 20 | 0 | 0.0 | 97 ms | 0 |
| Wed 22 | 0 | 0.0 | 192 ms | 0 |
| Thu 00 | 0 | 0.0 | 82 ms | 0 |
| Thu 02 | 0 | 0.0 | 74 ms | 0 |
| Thu 04 | 0 | 0.0 | 98 ms | 0 |
| Thu 06 | 0 | 0.0 | 59 ms | 0 |
| Thu 08 | 0 | 0.0 | 158 ms | 0 |
| Thu 10 | 0 | 0.0 | 155 ms | 0 |
| Thu 12 | 0 | 0.0 | 37 ms | 0 |
| Thu 15 | 0 | 0.0 | 73 ms | 0 |
| Thu 17 | 0 | 0.0 | 41 ms | 0 |
| Thu 19 | 0 | 0.0 | 124 ms | 0 |
| Thu 21 | 0 | 0.0 | 122 ms | 0 |
| Thu 23 | 0 | 0.0 | 83 ms | 0 |
| Fri 01 | 0 | 0.0 | 187 ms | 0 |
| Fri 03 | 0 | 0.0 | 370 ms | 0 |
| Fri 05 | 0 | 0.0 | 44 ms | 0 |
| Fri 07 | 0 | 0.0 | 35 ms | 0 |
| Fri 08 | 0 | 0.0 | 42 ms | 0 |
| Fri 10 | 0 | 0.0 | 27 ms | 0 |
| Fri 12 | 0 | 0.0 | 57 ms | 0 |
| Fri 14 | 0 | 0.0 | 66 ms | 0 |
| Fri 16 | 0 | 0.0 | 69 ms | 0 |
| Fri 17 | 0 | 0.0 | 112 ms | 0 |
| Fri 19 | 0 | 0.0 | 93 ms | 0 |
| Fri 21 | 0 | 0.0 | 61 ms | 0 |
| Fri 23 | 0 | 0.0 | 79 ms | 0 |
Reliability
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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live zama badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for zama yet. Outages of 10 minutes or more get their own page here.
Having trouble with zama?
One report per service every 10 minutes from this network. No account.
Follow zama
Get an email when zama goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send zama alerts to Slack, Discord or a webhook — free.
About zama
We track zama (zama.org) as part of the Cloud & developer group. Zama uses Fully Homomorphic Encryption (FHE) so institutions can issue, trade and manage confidential assets on public blockchains, fully verifiable.
zama publishes an official status page at status.zama.org; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 86 ms average, 19–370 ms range across 17 successful checks.
Questions
Is zama down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was zama last down?
We have not recorded a public zama incident since monitoring began 7 days ago.
What is zama's uptime?
From our own checks: 100% over 7 days of checks.
How fast does zama respond?
86 ms on average over the last 24 hours (19–370 ms).
Does zama have an official status page?
Yes, at https://status.zama.org.
zama not working for me but the status is fine. What now?
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 zama here at once, the problem is on zama'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 zama. 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.