zama Outage History

33 incidents recorded over the last 365 days, 33 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live zama status95.93% uptime history

Every Recorded zama Incident

zama incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 3, 2026The relayer is down.41h 40mResolved
Nov 3, 2026Coprocessor - Testnet is down43h 7mResolved
Oct 30, 2026Coprocessor - Testnet is down135h 4mResolved
Oct 22, 2026Zama Protocol mainnet configuration update2h 0mResolved
Oct 20, 2026MPC - Testnet is down368h 54mResolved
Oct 15, 2026Zama Protocol mainnet configuration update5 minResolved
Oct 13, 2026Coprocessor - Testnet and Gateway-Chain RPC are down533h 43mResolved
Oct 13, 2026Relayer down533h 52mResolved
Oct 12, 2026Coprocessor - Testnet is degraded566h 18mResolved
Sep 23, 2026Zama Protocol Mainnet — Listener v2 Deployment486h 0mResolved
Sep 21, 2026Mainnet Relayer Maintenance — Hotfix v0.13.429h 43mResolved
Sep 18, 2026Some services are down5h 26mResolved
Sep 17, 2026Test maintenance0 minResolved
Sep 17, 2026Update: The service is still experiencing issues1168h 58mResolved
Sep 16, 2026Update: The service is still experiencing issues1194h 54mResolved
Sep 11, 2026Mainnet Reliability Testing116h 6mResolved
Sep 7, 2026Testnet Coprocessor Unavailable1407h 25mResolved
Sep 7, 2026Testnet MPC Maintenance – Relayer Resilience Testing212h 20mResolved
Sep 2, 2026Testnet User Decryption Issues1525h 38mResolved
Aug 18, 2026Mainnet Upgrade Maintenance (Extended)691h 16mResolved
Aug 18, 2026Upgrade Maintenance Window (v0.13.0)691h 49mResolved
Aug 7, 2026Coprocessor - Testnet is degraded2053h 52mResolved
Jul 30, 2026Coprocessor Mainnet 0.12 Upgrade30 minResolved
Jul 28, 2026[Testnet] Coprocessor Upgrade In Progress0 minResolved
Jul 23, 2026Coprocessor - Testnet is degraded1662h 43mResolved
Jul 13, 2026KMS User Decryption Degraded, affecting Portfolio and Zama App1902h 20mResolved
Jul 10, 2026Coprocessor - Testnet is down1979h 53mResolved
Jun 29, 2026[Testnet] Coprocessor Upgrade In Progress30 minResolved
Jun 23, 2026Relayer upgrade v0.13.01h 27mResolved
Jun 19, 2026Relayer - Mainnet Service outage1753h 29mResolved
Jun 10, 2026Coprocessor - Testnet is down1985h 59mResolved
Jun 7, 2026Coprocessor - Testnet and MPC - Mainnet are down2059h 57mResolved
Jun 5, 2026Coprocessor - Testnet is down2099h 23mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next zama incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This zama Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before zama acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single zama outage in this window ran 87d 11h, against a mean recovery of 31d 21h. If you depend on zama in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.