Historial de interrupciones de Zuora

1. 1 de septiembre de 2026 a las 13:57 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. 1 de septiembre de 2026 a las 14:05 UTCmonitoring

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

3. 1 de septiembre de 2026 a las 14:54 UTCresolved

   Este incidente ha sido resuelto.

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

1. 28 de junio de 2026 a las 20:59 UTCinvestigating

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

2. 28 de junio de 2026 a las 22:21 UTCresolved

   Este incidente ha sido resuelto.

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

1. 27 de junio de 2026 a las 17:38 UTCinvestigating

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

2. 27 de junio de 2026 a las 19:06 UTCmonitoring

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

3. 28 de junio de 2026 a las 17:44 UTCresolved

   Este incidente ha sido resuelto.

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

1. 15 de junio de 2026 a las 18:45 UTCinvestigating

   We are currently investigating this issue.

2. 15 de junio de 2026 a las 19:14 UTCresolved

   This incident has been resolved.

1. 8 de mayo de 2026 a las 3:37 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. 8 de mayo de 2026 a las 10:17 UTCmonitoring

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

3. 8 de mayo de 2026 a las 12:53 UTCresolved

   This incident has been resolved.

1. 29 de abril de 2026 a las 4:39 UTCidentified

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

2. 29 de abril de 2026 a las 4:44 UTCmonitoring

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

3. 29 de abril de 2026 a las 6:48 UTCresolved

   This incident has been resolved.

1. 24 de abril de 2026 a las 10:39 UTCmonitoring

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

2. 24 de abril de 2026 a las 14:09 UTCresolved

   This incident has been resolved.

1. 10 de marzo de 2026 a las 7:53 UTCinvestigating

   We are currently investigating this issue.

2. 10 de marzo de 2026 a las 10:03 UTCinvestigating

   We are continuing to investigate this issue.

3. 10 de marzo de 2026 a las 10:22 UTCmonitoring

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

4. 11 de marzo de 2026 a las 7:59 UTCresolved

   This incident has been resolved.

1. 28 de febrero de 2026 a las 19:24 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. 9 de febrero de 2026 a las 7:06 UTCinvestigating

   We are currently investigating this issue.

2. 9 de febrero de 2026 a las 7:08 UTCinvestigating

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

3. 9 de febrero de 2026 a las 7:13 UTCidentified

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

4. 9 de febrero de 2026 a las 9:43 UTCresolved

   Issue is fixed and instances are up and running.

1. 3 de febrero de 2026 a las 4:58 UTCinvestigating

   Our team is proactively investigating this issue on priority.

2. 3 de febrero de 2026 a las 6:39 UTCmonitoring

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

3. 3 de febrero de 2026 a las 8:32 UTCresolved

   This incident has been resolved.

1. 28 de octubre de 2025 a las 15:53 UTCinvestigating

   We are currently investigating this issue.

2. 28 de octubre de 2025 a las 16:46 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 de octubre de 2025 a las 18:18 UTCidentified

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

4. 28 de octubre de 2025 a las 19:03 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. 28 de octubre de 2025 a las 23:16 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. 31 de octubre de 2025 a las 12:02 UTCresolved

   This incident has been resolved.

1. 17 de octubre de 2025 a las 20:31 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. 17 de octubre de 2025 a las 23:41 UTCmonitoring

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

3. 18 de octubre de 2025 a las 1:56 UTCresolved

   This incident has been resolved.

1. 15 de octubre de 2025 a las 9:57 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. 15 de octubre de 2025 a las 10:20 UTCresolved

   This incident is been resolved

1. 3 de septiembre de 2025 a las 22:02 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. 3 de septiembre de 2025 a las 23:29 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. 4 de septiembre de 2025 a las 2:11 UTCresolved

   This incident has been resolved.

1. 6 de agosto de 2025 a las 20:08 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. 23 de julio de 2025 a las 18:49 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. 23 de julio de 2025 a las 19:14 UTCmonitoring

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

3. 23 de julio de 2025 a las 23:31 UTCresolved

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

1. 21 de julio de 2025 a las 18:33 UTCinvestigating

   We are actively investigating the issue.

2. 21 de julio de 2025 a las 19:11 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. 21 de julio de 2025 a las 19:30 UTCmonitoring

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

4. 21 de julio de 2025 a las 20:03 UTCresolved

   This incident has been resolved.

1. 20 de julio de 2025 a las 11:21 UTCmonitoring

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

2. 20 de julio de 2025 a las 12:05 UTCmonitoring

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

3. 20 de julio de 2025 a las 14:29 UTCresolved

   This incident has been resolved.

1. 12 de junio de 2025 a las 19:26 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. 12 de junio de 2025 a las 20:10 UTCmonitoring

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

3. 12 de junio de 2025 a las 20:25 UTCresolved

   This incident has been resolved.