Kevel 장애 기록

1. 2026년 10월 15일 오후 5:37 UTCresolved

   약 06:30 및 06:42 UTC 10 월 15, 2026, EU-Central-1의 광고는 결정 요청에 대한 높은 응답 시간과 간헐적 오류를 경험했습니다. 서비스 복구 및 고객 조치가 필요하지 않습니다.

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

1. 2026년 9월 17일 오후 10:13 UTCidentified

   Ad Server UI를 통해 Ads로 만든 일부 사용자 저장 변경에 영향을 미치는 이슈를 조사하고 있습니다. 관리 API를 통한 변경은 영향을받지 않습니다. 우리는 가능성이 원인을 확인하고 해결하기 위해 노력하고 있습니다.

2. 2026년 9월 17일 오후 10:48 UTCmonitoring

   Ad Server UI의 수정 및 저장 변경은 예상대로 작동합니다. 우리는 감시자를 계속합니다.

3. 2026년 9월 17일 오후 11:25 UTCresolved

   이 확인은 이제 해결되었습니다. 자주 묻는 질문 ~19:38 사이 ~22:35 UTC 9 월 17, 2026, Ad Server UI를 통해 광고를 저장하는 것은 변경이 성공적으로 적용되었더라도 오류를 반환 할 수 있습니다. 오류가 발생한 후 검색된 사용자는 중복 광고를 만들 수 있습니다. 우리는이 창에서 생성되거나 편집 된 모든 광고를 검토하고 복제하는 것이 좋습니다.

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

1. 2026년 9월 9일 오후 10:59 UTCresolved

   사이 21:36 그리고 21:54 UTC 에 9월 9, 2026, 광고 서빙에서 미국-동-1 경험 높은 응답 시간 및 간헐적인 오류 결정 요청에. 서비스 자체에 회복, 고객 행동이 필요하지 않습니다.

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

1. 2026년 7월 20일 오후 4:24 UTCinvestigating

   우리는 현재 EU Central 1 지역의 고객에게 고급 광고 봉사를 일으키는 문제점을 조사하고 있습니다.

2. 2026년 7월 20일 오후 4:25 UTCidentified

   문제는 식별되고 수정이 구현됩니다.

3. 2026년 7월 20일 오후 4:45 UTCidentified

   이 문제를 해결하기 위해 계속 노력하고 있습니다.

4. 2026년 7월 20일 오후 5:00 UTCmonitoring

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

5. 2026년 7월 20일 오후 5:31 UTCresolved

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

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

1. 2026년 6월 11일 오후 2:52 UTCresolved

   We identified an issue that may have delayed delivery of beta log data via Data Shipping for some customers between June 9, 2026 at 21:16 UTC and June 11, 2026 at 14:18 UTC. June 11, 2026, 14:18 UTC: This issue has been resolved. Beta logs are now being shipped as expected, and no log data was lost. We are actively working to deliver any delayed logs from the affected period. June 12, 2026, 12:30 UTC: Confirming the backfill of all delayed data from the impacted period is complete.

1. 2026년 3월 31일 오전 5:05 UTCinvestigating

   We are currently investigating degraded ad serving performance in the us-east-1 region.

2. 2026년 3월 31일 오전 6:25 UTCinvestigating

   We are continuing to investigate the root cause. In the meantime, we have scaled additional capacity in the affected region, which has restored stability to ad serving. We will provide further updates as we learn more.

3. 2026년 3월 31일 오전 9:00 UTCmonitoring

   A mitigation has been applied and we are currently monitoring the system to ensure continued stability.

4. 2026년 3월 31일 오전 10:09 UTCmonitoring

   System performance has remained stable following the applied mitigation. We are continuing to monitor to ensure ongoing reliability.

5. 2026년 3월 31일 오후 2:12 UTCresolved

   The issue has been resolved and system performance has remained stable. We will continue to monitor as a precaution.

1. 2026년 2월 26일 오후 7:47 UTCresolved

   Some reporting data did not process correctly between 2026-02-20 21:00:00 and 2026-02-20 22:00:00 UTC. We have since reprocessed the affected data. As a result, some reporting metrics for that time period may have increased. Additionally, in cases where clicks or conversions were fired late for ads delivered previously, the associated clicks and click-derived revenue were applied to the original delivery dates, resulting in updates to historical metrics.

1. 2026년 2월 3일 오후 9:09 UTCinvestigating

   We have identified an issue impacting ad serving. An investigation is underway with our team. We'll keep you updated along the way.

2. 2026년 2월 3일 오후 9:25 UTCmonitoring

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

3. 2026년 2월 3일 오후 9:38 UTCresolved

   This incident has been resolved. Issue began: 1:55 PM ET Issue resolved: 4:37 PM ET

1. 2025년 12월 3일 오후 2:09 UTCinvestigating

   We are investigating an issue with delayed reporting data ingestion that is causing degraded reporting performance. Some customers may experience missing data in reports for December 2 - 3.

2. 2025년 12월 3일 오후 2:33 UTCidentified

   The issue has been identified and a fix is in-progress. To further clarify the impact, some customers may be temporarily missing data from December 2 - 3, as the ingestion of this data is delayed.

3. 2025년 12월 3일 오후 4:48 UTCidentified

   Work is still in progress on the fix for delayed data ingestion. We will update again as soon as we have further progress to share.

4. 2025년 12월 3일 오후 7:22 UTCmonitoring

   A fix has been implemented and we are monitoring results. We expect that it will take around 8 hours for the ingestion of the delayed reporting data to be completed. Once completed, the temporarily missing reporting data from December 2 - 3 will be available.

5. 2025년 12월 3일 오후 10:01 UTCresolved

   Confirming the ingestion of the delayed reporting data is now complete and this is now resolved. Newly created reports will contain correct and up to date metrics from December 2 - 3.

1. 2025년 11월 26일 오후 8:27 UTCresolved

   Customers in the eu-central-1 region may have experienced periods of high decision response times between 06:10 and 08:05 UTC on November 24, 2025. This was caused by anomalous behavior while the Kevel system scaled in response to irregular traffic patterns. Kevel's core ad serving systems are designed to mitigate these situations and we've adjusted our scaling algorithms following this investigation to reduce the likelihood of recurrence.

1. 2025년 10월 20일 오전 10:13 UTCidentified

   US-East-1 services including ad serving in the region, authentication, campaign management and reporting have been impacting by an underlying incident with one of our infrastructure providers. We're taking remediation steps and are continuing to monitor.

2. 2025년 10월 20일 오전 11:03 UTCidentified

   Compute resources for ad serving on US-East-1 are still experiencing increased error rates while the underlying service is being restored. Authentication, Campaign Management and Reporting are operational, but you may see elevated response times while previous failed requests are retried.

3. 2025년 10월 20일 오후 1:05 UTCidentified

   Confirming we are still working to address the impact from an incident with one of our infrastructure providers. Ad serving on US-East-1 is still experiencing increased error rates while the underlying service is being restored. Authentication, Campaign Management and Reporting are operational, but may still experience elevated response times.

4. 2025년 10월 20일 오후 2:09 UTCidentified

   We are continuing to work with our infrastructure provider to fully resolve the incident. Ad serving in the US-East-1 region remains partially impacted, with elevated error rates still observed. Authentication, Campaign Management, and Reporting remain operational, though some customers may continue to experience higher-than-normal response times. Our teams remain actively engaged, and we’ll share another update as soon as more progress is made.

5. 2025년 10월 20일 오후 3:05 UTCidentified

   We are continuing to actively respond to this incident. Ad serving in the US-East-1 region remains impacted, with elevated error rates and latency still observed. Authentication and Campaign Management remain operational, though some customers may continue to experience higher-than-normal response times. Reporting, including Data Shipping, are continuing to experience degraded performance and customers may see reports failing. Completed reports may also lack recent data. Forecast is also experiencing degraded performance and recently completed forecasts may yield less accurate results.

6. 2025년 10월 20일 오후 5:34 UTCidentified

   We are continuing to work with our infrastructure provider to fully resolve the incident. Ad Serving is now stable. If you continue to experience issues with Ad Serving, please reach out to Support or your to Customer Success Manager. Authentication and Campaign Management remain operational, though customers may continue to experience elevated response times. Reporting, including Data Shipping, continue to experience degraded performance and customers may continue to see failed reports. Completed reports may also lack recent data. Forecast is also continuing to experience degraded performance and completed forecasts may yield inaccurate results. For Audience, event tracking is operational, however, purchase request syncing may be degraded for some customers.

7. 2025년 10월 20일 오후 8:45 UTCidentified

   We are continuing to engage with our infrastructure provider to resolve the incident. Ad Serving continues to be stable. Management is stable. Reporting, including Data Shipping, is still experiencing degraded performance and customers may continue to see failed reports. In addition, reports from today may lack recent data. Forecast is also experiencing degraded performance and forecasts from today may show inaccurate results. For Audience, purchase request syncing may be degraded for some customers.

8. 2025년 10월 20일 오후 10:19 UTCidentified

   We are continuing to work with our infrastructure provider to address the impact of the incident. Ad Serving continues to be stable. Management is operational, has returned to pre-incident status and has worked through the backlog of changes. Reporting and Data Shipping are still experiencing degraded performance and customers may continue to see failed reports. In addition, today's reports may lack recent data. Forecast is also experiencing degraded performance and today's forecasts may show inaccurate results. For Audience, purchase request syncing may continue to be degraded for some customers.

9. 2025년 10월 20일 오후 11:56 UTCidentified

   Ad Serving has now been returned to an operational status. Audience has also been returned to an operational status. Management also continues to be operational. We are continuing to work with our infrastructure provider to address the impact on Reporting, Data Shipping and Forecast. Reporting and Data Shipping are still experiencing degraded performance and customers may continue to see failed reports. In addition, today's reports may lack recent data. Forecast is also experiencing degraded performance and today's forecasts may show inaccurate results.

10. 2025년 10월 21일 오전 1:01 UTCidentified

    Ad Serving, Management and Audience continue to be operational. Data Shipping has resumed normal operations, however, customers may be missing data from today, October 20th. Confirming we will evaluate backfilling this data. Reporting and Forecasting are still operating with degraded performance. We are waiting for recovery of the related service from our infrastructure provider to resume normal operations. We anticipate this will take hours.

11. 2025년 10월 21일 오전 9:07 UTCmonitoring

    All Kevel services are now operational including Ad Serving, Audience, Data Shipping, Management, Forecast and Reporting. We are continuing to monitor all services. We are also still working to backfill missing data from yesterday's incident for Data Shipping and Reporting.

12. 2025년 10월 21일 오후 5:02 UTCresolved

    We confirm that all Kevel services have remained operational for several hours, and we are moving the incident to resolved. Please note that we are still working to backfill missing data for Reporting and Data Shipping. We anticipate this will be completed by the end of the week. If you have any questions about the incident or the ongoing backfill, please reach out to your Customer Success Manager or Kevel Support.

1. 2025년 10월 14일 오후 6:37 UTCinvestigating

   We identified an issue impacting Reporting. Reports are processing through the system. We'll keep you updated along the way.

2. 2025년 10월 14일 오후 6:49 UTCmonitoring

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

3. 2025년 10월 14일 오후 7:42 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2025년 10월 14일 오후 8:12 UTCresolved

   This incident has been resolved.

1. 2025년 10월 9일 오후 12:22 UTCinvestigating

   We are currently investigating an issue that is causing degraded Ad Serving for customers in the EU Central 1 region.

2. 2025년 10월 9일 오후 12:44 UTCidentified

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

3. 2025년 10월 9일 오후 12:53 UTCmonitoring

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

4. 2025년 10월 9일 오후 1:41 UTCresolved

   This incident has been resolved.

1. 2025년 8월 12일 오후 4:39 UTCinvestigating

   We are currently investigating an issue impacting Kevel Ad Serving. We will keep you updating along the way.

2. 2025년 8월 12일 오후 5:13 UTCidentified

   We have identified the issue and are working on a fix.

3. 2025년 8월 12일 오후 7:48 UTCidentified

   A fix has been implemented for most impacted customers. We are deploying the fix to the remaining impacted customers and monitoring.

4. 2025년 8월 12일 오후 8:37 UTCresolved

   This incident has been resolved.

1. 2025년 7월 31일 오후 4:09 UTCmonitoring

   We identified an issue impacting Forecast. Some instances were not responding to Forecast requests or Forecast API requests from ~15:15 UTC to ~15:55 UTC on July 31, 2025. A fix has already been deployed and we are monitoring.

2. 2025년 7월 31일 오후 4:24 UTCresolved

   This incident has been resolved.

1. 2025년 7월 29일 오후 5:11 UTCresolved

   We identified an issue with our ad publication and balancing systems starting at 22:23 UTC on July 23, 2025. The issue was resolved at 17:12 UTC on July 24, 2025. Some customers may have experienced underdelivery on affected ads.

1. 2025년 7월 29일 오후 5:14 UTCresolved

   We identified an issue with our ad publication and balancing systems that began on July 21, 2025, at 16:55 UTC. The issue was resolved on July 28, 2025, at 21:41 UTC. As a result, some customers may have experienced overdelivery of affected ads.

1. 2025년 7월 2일 오후 9:02 UTCinvestigating

   We identified an issue impacting ad publication starting 2025-07-02 20:10 UTC. Users might experience issues starting, stopping, and pausing ads; however, ad balancing is not impacted. An investigation is underway with our team. We'll keep you updated along the way.

2. 2025년 7월 2일 오후 9:03 UTCidentified

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

3. 2025년 7월 2일 오후 9:13 UTCresolved

   This incident has been resolved.

1. 2025년 6월 8일 오후 6:09 UTCinvestigating

   We identified an issue impacting ad publication starting 2025-06-08 16:00 UTC. An investigation is underway with our team. We'll keep you updated along the way.

2. 2025년 6월 8일 오후 6:11 UTCinvestigating

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

3. 2025년 6월 8일 오후 6:30 UTCinvestigating

   We are continuing to monitor for any further issues.

4. 2025년 6월 8일 오후 6:31 UTCresolved

   This incident has been resolved.

1. 2025년 4월 25일 오후 7:09 UTCinvestigating

   We identified an issue with our ad publication & balancing systems starting 2025-04-25 18:29 UTC. This is being investigated with high priority. This impacts us-east only.

2. 2025년 4월 25일 오후 7:31 UTCidentified

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

3. 2025년 4월 25일 오후 7:42 UTCmonitoring

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

4. 2025년 4월 25일 오후 8:03 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2025년 4월 25일 오후 8:23 UTCresolved

   This incident has been resolved.