Zuora Outage History

12 incidents recorded over the last 365 days, 12 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 Zuora status100.00% uptime history

Every Recorded Zuora Incident

Zuora incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026Zephr Admin Console not accessibleThis incident has been resolved.59 minResolved
Sep 1, 2026Central Sandbox Performance issue: 504 Gateway Time Out errorThis incident has been resolved.56 minResolved
Jun 28, 2026Data synchronization delays in Revenue snowflake secure shareThis incident has been resolved.1h 22mResolved
Jun 27, 2026Revenue Rest APIThis incident has been resolved.24h 6mResolved
Jun 15, 2026Currently the <www.zuora.com> is not accessible , we are investigating the issueThis incident has been resolved.29 minResolved
May 8, 2026Internal System Error for Users with Japanese Language SettingsThis incident has been resolved.9h 16mResolved
Apr 29, 2026Zuora Sandbox Environments UI are inaccessibleThis incident has been resolved.2h 8mResolved
Apr 24, 2026A subset of NA1 production tenants using legacy 360 Sync were triggering Turbo Sync instead of Real time syncThis incident has been resolved.3h 30mResolved
Mar 10, 2026On March 10, 2026, at approximately 12:30 AM PDT, an incident was detected affecting Zuora Revenue Service sandbox environments across regions.This incident has been resolved.24h 6mResolved
Feb 28, 2026Email / Notification Latency SpikeDuring month end monitoring, we observed spike in email/notification processing latency. Timeframe: 5:05 am PST ~ 8:00 am PST Latency has returned to normal levels and no ongoing impact observed.0 minResolved
Feb 9, 2026Zrevenue RC work bench data query Issue reported after the DB maintenanceIssue is fixed and instances are up and running.2h 36mResolved
Feb 3, 2026Performance degradation impacting Zuora Connector for Data Warehouses for a sub-set of NA Production and Sandbox tenants.This incident has been resolved.3h 33mResolved

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 Zuora 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 Zuora 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 Zuora 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 Zuora outage in this window ran 1d, against a mean recovery of 6h 5m. If you depend on Zuora 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.