Kickbox の障害履歴

1. 2026年8月27日 3:49 UTCidentified

   問題は特定され、修正に取り組んでいます

2. 2026年8月27日 3:50 UTCidentified

   この問題の修正には引き続き取り組んでいます。

3. 2026年8月27日 5:04 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年1月19日 15:17 UTCresolved

   This incident has been resolved.

1. 2026年1月16日 2:13 UTCinvestigating

   Currently investigating issue with web application and batch API.

2. 2026年1月16日 2:21 UTCidentified

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

3. 2026年1月16日 3:01 UTCidentified

   We are continuing to work on a fix for this issue.

4. 2026年1月16日 3:24 UTCmonitoring

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

5. 2026年1月16日 4:23 UTCresolved

   This incident has been resolved.

1. 2025年8月21日 19:30 UTCinvestigating

   Currently investigating issue.

2. 2025年8月21日 20:26 UTCinvestigating

   We are still investigating an intermittent issue with list downloads.

3. 2025年8月21日 22:02 UTCresolved

   Incident resolved. Monitoring will take place for a time to ensure functionality.

1. 2025年6月2日 14:42 UTCidentified

   We are actively addressing an issue causing inconsistencies in the verification results for Yahoo and AOL emails. This problem has been traced to a breaking change in a recent update from Yahoo/AOL that affects our results. We have identified the issue and we are working towards a resolution.

2. 2025年6月2日 21:03 UTCmonitoring

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

3. 2025年6月3日 13:17 UTCresolved

   This incident has been resolved.

1. 2025年2月21日 12:24 UTCinvestigating

   Currently investigating an issue that is causing an outage on our EU instances.

2. 2025年2月21日 13:14 UTCinvestigating

   We are continuing to investigate this issue.

3. 2025年2月21日 13:14 UTCresolved

   This incident has been resolved.

1. 2024年11月17日 10:54 UTCinvestigating

   Issue currently under investigation.

2. 2024年11月17日 18:07 UTCmonitoring

   Fix implemented and results being monitored.

3. 2024年11月18日 17:41 UTCresolved

   Incident resolved.

1. 2024年10月24日 15:25 UTCinvestigating

   We are currently investigating and issue causing slower than normal API responses for a fraction of requests

2. 2024年10月24日 15:26 UTCidentified

   Issue identified. Preparing deployment for fix.

3. 2024年10月24日 15:51 UTCmonitoring

   A fix has been deployed. We are now monitoring services.

4. 2024年10月29日 17:18 UTCresolved

   This incident has been resolved.

1. 2024年9月14日 23:37 UTCinvestigating

   Partial outage. Investigating

2. 2024年9月14日 23:38 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024年9月15日 0:07 UTCresolved

   This incident has been resolved.

1. 2024年8月21日 20:40 UTCresolved

   Team is investigating the cause of a minor service degradation occurring between 2:30pm and 3:00pm (central time). Details to come.

2. 2024年8月22日 17:15 UTCpostmortem

   # August 21, 2024 Service Degradation Investigation **Date**: 08/21/2024 **Status**: Mitigated ### Summary A service degradation was detected by our monitoring services between 12:34 PST and 12:48 PST. We removed the impacted servers from rotation restoring full-service. We investigated and solved the issue before bringing the impacted servers back into production rotation. ### Impact API service degradation in 45-second bursts for a 12 minute period, beginning at 12:34 PST causing some requests to respond with a 502 ‘Bad Gateway’. The issue was limited to a small subset of our production servers, so fewer than 3% of global API requests during this time were affected. ### Root Cause\(s\) During a routine canary upstream service update, a small number of canary servers became unable to connect to an upstream internal service. Due to this problem, a fraction of requests to these servers caused a connection timeout, resulting in 502 Bad Gateway errors from our proxies.This problem was sporadic, so the proxies did not automatically remove these servers from rotation. ### Resolution Our internal monitoring systems detected this degradation and we worked to manually remove these servers from production rotation. This restored the API to full health. After our investigation, we resolved the communication issues with a full code re-deploy and service restart. We then ran a full suite of API health checks, confirmed the problem was resolved, and re-added the servers into production. ‌ ### Action Items We will perform a review of our internal monitoring systems to decrease the time to alert, and review our proxy health-check endpoints to see if they can be improved for partial service degradation. ‌ ## Timeline

1. 2024年3月11日 20:23 UTCidentified

   We’re currently experiencing reduced performance with several of our integrations, including Iterable, HubSpot, and Klaviyo within Kickbox, specifically affecting functionality; our team is actively working to resolve these issues to restore full service. Users can still actively leverage our email verification services through list verification or API. If you have any additional questions, please reach out to [email protected].

2. 2024年6月12日 12:56 UTCresolved

   This incident has been resolved.

1. 2024年3月5日 18:47 UTCresolved

   A 7 minute unexpected partial outage occurred. Root cause still under investigation.

1. 2024年3月5日 15:08 UTCinvestigating

   We are currently investigating an issue with the EU verification instance

2. 2024年3月5日 15:10 UTCinvestigating

   We are continuing to investigate this issue.

3. 2024年3月5日 15:29 UTCmonitoring

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

4. 2024年3月5日 16:05 UTCresolved

   A networking error caused a severed connection to the EU verification engine. Manual reconnection has restored services.

1. 2024年1月21日 18:01 UTCresolved

   A DNS change with an Amazon service temporarily broke sign-in for some users Sunday morning (API unaffected.

1. 2024年1月8日 21:38 UTCresolved

   There was a small outage 10 minute outage due to an unforeseen network issue during a routine deployment.

2. 2024年1月10日 15:15 UTCpostmortem

   A minor configuration change \(adding an alias to a Redis instance\) caused an unexpected error and prevented the Kickbox app from restarting after deployment. The issue was quickly detected and resolved by the engineering team. The total outage was 11 minutes. The misconfiguration was identified quickly and a rollback tag was deployed to restore service within minutes.

1. 2023年9月22日 13:04 UTCinvestigating

   We're investigating a period of degraded service beginning at 5:54AM CST and lasting until 7:30AM CST.

2. 2023年9月22日 14:41 UTCresolved

   We had degraded service due to a partial datastore service degradation. We repaired and restarted the datastore. No data was lost.

1. 2023年9月20日 20:38 UTCresolved

   An issue with a upstream service provider created a window of unplanned downtime for a small fraction of EU users (smaller than 1%). The partial service outage lasted from 3pm September 19th until about 3pm the next day.

1. 2023年9月5日 17:43 UTCinvestigating

   In the deliverablity tools suite, DMARC data has stopped populating as of September 1st. Engineering is investigating the issue and we hope to have more information and a resolution to this issue soon.

2. 2023年9月5日 21:02 UTCinvestigating

   Still investigating the case.

3. 2023年9月6日 19:53 UTCresolved

   This incident has been resolved.

1. 2023年8月17日 17:10 UTCidentified

   Our system failed to properly log and summarized inbound aggregate DMARC reports. Our engineers are aware of the issue and are actively working to address this issue as soon as possible.

2. 2023年8月17日 19:50 UTCidentified

   We are continuing to work on a fix for this issue.

3. 2023年8月17日 19:50 UTCresolved

   We’ve corrected the issue with DMARC that was preventing ongoing data collection. Ongoing, inbound DMARC reports should be properly received, parsed, logged and displayed in reporting. If you have any questions, please don’t hesitate to reach out to us at [email protected]

1. 2023年8月8日 17:26 UTCresolved

   Just after 11:00 am (central) a routine TLS certificate update caused a misconfiguration. Some users experienced a partial outage.

2. 2023年8月8日 18:16 UTCpostmortem

   The new SSL cert that was implemented did not support `TLS1.2` . This resulted in issues for only some users where that support was required.