54 Zuora incidents · listopad 2024 — official updates, affected components, duration and resolution details.
Obecnie nasze centralne środowisko piaskowca doświadczają problemów z wydajnością. Nasz zespół pracuje nad tym z najwyższym priorytetem. i będziemy dostarczać dalsze aktualizacje, jak staną się dostępne.
Wprowadzono rozwiązanie i monitorujemy wyniki.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Obecnie badamy problem powodujący opóźnienia synchronizacji danych w bezpiecznym udziale płatka śniegu Revenue
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
Nasz zespół bada obecnie problemy przerywanej łączności wpływające na API Rest Result
Wprowadzono rozwiązanie i monitorujemy wyniki.
Ten incydent został rozwiązany.
Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.
We are currently investigating this issue.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
This issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
A fix is implemented and RTS is now functioning as expected and we are currently monitoring.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We are currently investigating this issue.
Sandbox Environments are currently down. Our team is working on this with the highest urgency
The issue has been identified and a fix is being implemented.
Issue is fixed and instances are up and running.
Our team is proactively investigating this issue on priority.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
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.
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.
This incident has been resolved.
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
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
This incident impacted during 10/15/2025 2:20 AM PT until 10/15/2025 02:38 AM PT. We are continuing to monitor.
This incident is been resolved
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.
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
This incident has been resolved.
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.
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.
We have rolled out a mitigation and error rates have returned to normal. We are continuing to monitor for any further issues.
The application issue has been resolved as error rates continued to be normal.
We are actively investigating the issue.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
NA Production UI for Revenue was not accessible from 4 am PST. This is now resolved and we continue to monitor.
We have also identified v2 REST API errors during the impacted period. We continue to monitor.
This incident has been resolved.
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.
All Zephr services have been reverted at the DNS level to use AWS infrastructure while the Cloudflare incident is ongoing.
This incident has been resolved.