Zuora System Status Page
All Systems Operational
Production UI ? Operational
Production API ? Operational
Production Integrations ? Operational
Production Batch Operations ? Operational
Production Reporting Operational
Sandbox UI ? Operational
Sandbox API ? Operational
Sandbox Integrations ? Operational
Sandbox Batch Operations ? Operational
Sandbox Reporting Operational
Connect Applications Operational
Connect - Production ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Production Response Time ?
Fetching
Sandbox Response Time ?
Fetching
Past Incidents
May 26, 2017

No incidents reported today.

May 25, 2017

No incidents reported.

May 24, 2017
Our technology team has resolved a brief service interruption on a production API endpoint at rest.zuora.com. Interruption occurred between 2.45pm-2.48pm PST.
May 24, 16:09 PDT
May 23, 2017

No incidents reported.

May 22, 2017

No incidents reported.

May 21, 2017

No incidents reported.

May 20, 2017

No incidents reported.

May 19, 2017
Postmortem - Read details
May 23, 12:40 PDT
Resolved - Production services remain stable as of 9:38am PST and the teams have put mitigations in place. We will provide an RCA once it's available.
May 19, 13:49 PDT
Update - We've engaged our Engineering Teams and are working on identifying the root cause. We will keep you posted with any progresses made.
May 19, 12:46 PDT
Update - Service was restored around 9:38am PST, and we are observing stable operations. We are still investigating root cause.
May 19, 10:01 PDT
Investigating - We are investigating a production service disruption as of 9:18 am PST and have all hands on deck investigating to restore service.
May 19, 09:26 PDT
Postmortem - Read details
May 23, 12:53 PDT
Resolved - We're glad to inform that this incident has now been fully resolved. We shall publish Root Cause Analysis when it becomes available.
May 19, 07:32 PDT
Monitoring - We have released a fix for this incident in all environments. Whilst we expect this incident to be fully resolved, we shall continue monitoring.
May 19, 05:38 PDT
Identified - We have managed to identify the root cause and a fix is undergoing testing before releases. We shall update again shortly.
May 19, 03:02 PDT
Investigating - Our Engineering Team is working actively on identifying the root cause.
May 19, 01:48 PDT
May 18, 2017
Resolved - Our internal teams have deployed fixes to APISandbox (at 1:25 pm PST ), Production and Performance Test (PT1) environments (at 2:28pm PST). We are monitoring to ensure all affected operations are proceeding normally.
May 18, 14:58 PDT
Identified - We have since managed to identify the root cause and developed a fix which is now undergoing testing processes.
May 18, 09:38 PDT
Investigating - We've engaged our Engineering Teams and are working on identifying the root cause. We shall keep you posted with any progresses made.
May 18, 07:41 PDT
May 17, 2017

No incidents reported.

May 16, 2017

No incidents reported.

May 15, 2017

No incidents reported.

May 14, 2017

No incidents reported.

May 13, 2017

No incidents reported.

May 12, 2017

No incidents reported.