Zuora 장애 기록

1. 2026년 9월 1일 PM 1:57 UTCinvestigating

   현재 우리의 중앙 Sandbox 환경은 성능 문제를 경험하고있다. 우리의 팀은 가장 높은 우선권과 함께 이것을 일하고 있습니다. 우리는 더 많은 업데이트를 제공 할 것입니다.

2. 2026년 9월 1일 PM 2:05 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 9월 1일 PM 2:54 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 28일 PM 8:59 UTCinvestigating

   우리는 현재 Revenue Snowflake 보안 공유에서 데이터 동기화 지연을 일으키는 문제를 조사하고 있습니다

2. 2026년 6월 28일 PM 10:21 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 27일 PM 5:38 UTCinvestigating

   우리의 팀은 Revenue REST API에 영향을 미치는 간헐적 연결 문제로 현재 찾고 있습니다

2. 2026년 6월 27일 PM 7:06 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 6월 28일 PM 5:44 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 15일 PM 6:45 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 6월 15일 PM 7:14 UTCresolved

   This incident has been resolved.

1. 2026년 5월 8일 AM 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. 2026년 5월 8일 AM 10:17 UTCmonitoring

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

3. 2026년 5월 8일 PM 12:53 UTCresolved

   This incident has been resolved.

1. 2026년 4월 29일 AM 4:39 UTCidentified

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

2. 2026년 4월 29일 AM 4:44 UTCmonitoring

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

3. 2026년 4월 29일 AM 6:48 UTCresolved

   This incident has been resolved.

1. 2026년 4월 24일 AM 10:39 UTCmonitoring

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

2. 2026년 4월 24일 PM 2:09 UTCresolved

   This incident has been resolved.

1. 2026년 3월 10일 AM 7:53 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 3월 10일 AM 10:03 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 3월 10일 AM 10:22 UTCmonitoring

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

4. 2026년 3월 11일 AM 7:59 UTCresolved

   This incident has been resolved.

1. 2026년 2월 28일 PM 7: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. 2026년 2월 9일 AM 7:06 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 2월 9일 AM 7:08 UTCinvestigating

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

3. 2026년 2월 9일 AM 7:13 UTCidentified

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

4. 2026년 2월 9일 AM 9:43 UTCresolved

   Issue is fixed and instances are up and running.

1. 2026년 2월 3일 AM 4:58 UTCinvestigating

   Our team is proactively investigating this issue on priority.

2. 2026년 2월 3일 AM 6:39 UTCmonitoring

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

3. 2026년 2월 3일 AM 8:32 UTCresolved

   This incident has been resolved.

1. 2025년 10월 28일 PM 3:53 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 10월 28일 PM 4:46 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025년 10월 28일 PM 6:18 UTCidentified

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

4. 2025년 10월 28일 PM 7: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. 2025년 10월 28일 PM 11: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. 2025년 10월 31일 PM 12:02 UTCresolved

   This incident has been resolved.

1. 2025년 10월 17일 PM 8: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. 2025년 10월 17일 PM 11:41 UTCmonitoring

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

3. 2025년 10월 18일 AM 1:56 UTCresolved

   This incident has been resolved.

1. 2025년 10월 15일 AM 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. 2025년 10월 15일 AM 10:20 UTCresolved

   This incident is been resolved

1. 2025년 9월 3일 PM 10: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. 2025년 9월 3일 PM 11: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. 2025년 9월 4일 AM 2:11 UTCresolved

   This incident has been resolved.

1. 2025년 8월 6일 PM 8: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. 2025년 7월 23일 PM 6: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. 2025년 7월 23일 PM 7: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. 2025년 7월 23일 PM 11:31 UTCresolved

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

1. 2025년 7월 21일 PM 6:33 UTCinvestigating

   We are actively investigating the issue.

2. 2025년 7월 21일 PM 7: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. 2025년 7월 21일 PM 7:30 UTCmonitoring

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

4. 2025년 7월 21일 PM 8:03 UTCresolved

   This incident has been resolved.

1. 2025년 7월 20일 AM 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. 2025년 7월 20일 PM 12:05 UTCmonitoring

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

3. 2025년 7월 20일 PM 2:29 UTCresolved

   This incident has been resolved.

1. 2025년 6월 12일 PM 7: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. 2025년 6월 12일 PM 8:10 UTCmonitoring

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

3. 2025년 6월 12일 PM 8:25 UTCresolved

   This incident has been resolved.