Historial de interrupciones de Zuora

1. September 1, 2026 at 1:57 PM UTCinvestigating

   Actualmente nuestros entornos centrales de Sandbox están experimentando problemas de rendimiento. Nuestro equipo está trabajando en esto con la máxima prioridad. y proporcionaremos más actualizaciones a medida que estén disponibles.

2. September 1, 2026 at 2:05 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. September 1, 2026 at 2:54 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 28, 2026 at 8:59 PM UTCinvestigating

   Actualmente estamos investigando un problema causando retrasos en la sincronización de datos en la parte segura del copo de nieve Revenue

2. June 28, 2026 at 10:21 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 27, 2026 at 5:38 PM UTCinvestigating

   Nuestro equipo está actualmente buscando problemas de conectividad intermitentes que afectan a la API de Revenue REST

2. June 27, 2026 at 7:06 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. June 28, 2026 at 5:44 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 15, 2026 at 6:45 PM UTCinvestigating

   We are currently investigating this issue.

2. June 15, 2026 at 7:14 PM UTCresolved

   This incident has been resolved.

1. May 8, 2026 at 3:37 AM UTCidentified

   We are currently investigating an issue affecting Sandbox environments where users who have Japanese selected as their preferred language may encounter an Internal System Error when accessing the application settings.

2. May 8, 2026 at 10:17 AM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. May 8, 2026 at 12:53 PM UTCresolved

   This incident has been resolved.

1. April 29, 2026 at 4:39 AM UTCidentified

   This issue has been identified and a fix is being implemented.

2. April 29, 2026 at 4:44 AM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. April 29, 2026 at 6:48 AM UTCresolved

   This incident has been resolved.

1. April 24, 2026 at 10:39 AM UTCmonitoring

   A fix is implemented and RTS is now functioning as expected and we are currently monitoring.

2. April 24, 2026 at 2:09 PM UTCresolved

   This incident has been resolved.

1. March 10, 2026 at 7:53 AM UTCinvestigating

   We are currently investigating this issue.

2. March 10, 2026 at 10:03 AM UTCinvestigating

   We are continuing to investigate this issue.

3. March 10, 2026 at 10:22 AM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. March 11, 2026 at 7:59 AM UTCresolved

   This incident has been resolved.

1. February 28, 2026 at 7:24 PM UTCresolved

   During 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.

1. February 9, 2026 at 7:06 AM UTCinvestigating

   We are currently investigating this issue.

2. February 9, 2026 at 7:08 AM UTCinvestigating

   Sandbox Environments are currently down. Our team is working on this with the highest urgency

3. February 9, 2026 at 7:13 AM UTCidentified

   The issue has been identified and a fix is being implemented.

4. February 9, 2026 at 9:43 AM UTCresolved

   Issue is fixed and instances are up and running.

1. February 3, 2026 at 4:58 AM UTCinvestigating

   Our team is proactively investigating this issue on priority.

2. February 3, 2026 at 6:39 AM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. February 3, 2026 at 8:32 AM UTCresolved

   This incident has been resolved.

1. October 28, 2025 at 3:53 PM UTCinvestigating

   We are currently investigating this issue.

2. October 28, 2025 at 4:46 PM UTCinvestigating

   We are continuing to investigate this issue.

3. October 28, 2025 at 6:18 PM UTCidentified

   The issue has been identified and a fix is being implemented.

4. October 28, 2025 at 7:03 PM UTCmonitoring

   We’ve implemented the resolution and expect the full service to recover automatically over the next 2–8 hours. Our team will continue to monitor the situation closely and provide updates until all services are fully restored.

5. October 28, 2025 at 11:16 PM UTCmonitoring

   All systems behind Zuora-managed DNS are now fully operational. Some customers or integrations may still experience intermittent errors due to cached DNS records. If you manage infrastructure in front of Zephr, we recommend flushing DNS to help restore full connectivity.

6. October 31, 2025 at 12:02 PM UTCresolved

   This incident has been resolved.

1. October 17, 2025 at 8:31 PM UTCidentified

   Our Engineering teams have identified an issue where Zuora 360 sync is failing with “There has been an unknown internal error. (could not resolve property: generatedon of: com.zuora.zbilling.invoice.model.Invoice)” when Invoice and its child objects are attempted to sync. Customers who have the Invoice and its child objects disabled in 360 sync are not impacted. Customers using "Zuora Connector for Salesforce CRM are also not impacted

2. October 17, 2025 at 11:41 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. October 18, 2025 at 1:56 AM UTCresolved

   This incident has been resolved.

1. October 15, 2025 at 9:57 AM UTCmonitoring

   This incident impacted during 10/15/2025 2:20 AM PT until 10/15/2025 02:38 AM PT. We are continuing to monitor.

2. October 15, 2025 at 10:20 AM UTCresolved

   This incident is been resolved

1. September 3, 2025 at 10:02 PM UTCinvestigating

   We have observed that the Zuora to Salesforce sync is experiencing failures when attempting to get an SFDC OAuth token. Our internal team is currently investigating this issue with the highest priority.

2. September 3, 2025 at 11:29 PM UTCmonitoring

   We have published a Support article with steps, based on Salesforce's guidance, to help resolve this issue. Please refer to the link below: https://support.zuora.com/hc/en-us/articles/39308749618445-Failed-to-get-SFDC-oauth-token-code-400-message-error-invalid-grant-error-description-expired-access-refresh-token

3. September 4, 2025 at 2:11 AM UTCresolved

   This incident has been resolved.

1. August 6, 2025 at 8:08 PM UTCresolved

   We identified and resolved a Workflow UI issue that occurred between 3:57 AM and 4:29 AM PST. This may have also impacted other services like data query that tried to query on the workflow object.

1. July 23, 2025 at 6:49 PM UTCinvestigating

   We are having an Application issue with Service: Zephr. We are seeing elevated error rates in us-east-1. Our team is currently investigating the issue.

2. July 23, 2025 at 7:14 PM UTCmonitoring

   We have rolled out a mitigation and error rates have returned to normal. We are continuing to monitor for any further issues.

3. July 23, 2025 at 11:31 PM UTCresolved

   The application issue has been resolved as error rates continued to be normal.

1. July 21, 2025 at 6:33 PM UTCinvestigating

   We are actively investigating the issue.

2. July 21, 2025 at 7:11 PM UTCinvestigating

   We are continuing to investigate the issue on priority. Along with Data Source Exports and Aqua, we see an impact on Notifications and Invoice PDF.

3. July 21, 2025 at 7:30 PM UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. July 21, 2025 at 8:03 PM UTCresolved

   This incident has been resolved.

1. July 20, 2025 at 11:21 AM UTCmonitoring

   NA Production UI for Revenue was not accessible from 4 am PST. This is now resolved and we continue to monitor.

2. July 20, 2025 at 12:05 PM UTCmonitoring

   We have also identified v2 REST API errors during the impacted period. We continue to monitor.

3. July 20, 2025 at 2:29 PM UTCresolved

   This incident has been resolved.

1. June 12, 2025 at 7:26 PM UTCinvestigating

   We’re investigating intermittent 502 errors affecting some production sites. The issue appears to be related to ongoing Cloudflare outages impacting several services. We recommend that customers revert DNS records to CNAME to "cloudfront.cdn.zephr.com" where possible.

2. June 12, 2025 at 8:10 PM UTCmonitoring

   All Zephr services have been reverted at the DNS level to use AWS infrastructure while the Cloudflare incident is ongoing.

3. June 12, 2025 at 8:25 PM UTCresolved

   This incident has been resolved.