Kickbox 中断历史

1. 2026年8月27日 UTC 03:49identified

   这些问题已经确定,我们正在设法解决问题

2. 2026年8月27日 UTC 03:50identified

   我们正在继续努力解决这个问题。

3. 2026年8月27日 UTC 05:04resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年1月19日 UTC 15:17resolved

   This incident has been resolved.

1. 2026年1月16日 UTC 02:13investigating

   Currently investigating issue with web application and batch API.

2. 2026年1月16日 UTC 02:21identified

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

3. 2026年1月16日 UTC 03:01identified

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

4. 2026年1月16日 UTC 03:24monitoring

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

5. 2026年1月16日 UTC 04:23resolved

   This incident has been resolved.

1. 2025年8月21日 UTC 19:30investigating

   Currently investigating issue.

2. 2025年8月21日 UTC 20:26investigating

   We are still investigating an intermittent issue with list downloads.

3. 2025年8月21日 UTC 22:02resolved

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

1. 2025年6月2日 UTC 14:42identified

   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日 UTC 21:03monitoring

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

3. 2025年6月3日 UTC 13:17resolved

   This incident has been resolved.

1. 2025年2月21日 UTC 12:24investigating

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

2. 2025年2月21日 UTC 13:14investigating

   We are continuing to investigate this issue.

3. 2025年2月21日 UTC 13:14resolved

   This incident has been resolved.

1. 2024年11月17日 UTC 10:54investigating

   Issue currently under investigation.

2. 2024年11月17日 UTC 18:07monitoring

   Fix implemented and results being monitored.

3. 2024年11月18日 UTC 17:41resolved

   Incident resolved.

1. 2024年10月24日 UTC 15:25investigating

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

2. 2024年10月24日 UTC 15:26identified

   Issue identified. Preparing deployment for fix.

3. 2024年10月24日 UTC 15:51monitoring

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

4. 2024年10月29日 UTC 17:18resolved

   This incident has been resolved.

1. 2024年9月14日 UTC 23:37investigating

   Partial outage. Investigating

2. 2024年9月14日 UTC 23:38investigating

   We are continuing to investigate this issue.

3. 2024年9月15日 UTC 00:07resolved

   This incident has been resolved.

1. 2024年8月21日 UTC 20:40resolved

   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日 UTC 17:15postmortem

   # 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日 UTC 20:23identified

   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日 UTC 12:56resolved

   This incident has been resolved.

1. 2024年3月5日 UTC 18:47resolved

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

1. 2024年3月5日 UTC 15:08investigating

   We are currently investigating an issue with the EU verification instance

2. 2024年3月5日 UTC 15:10investigating

   We are continuing to investigate this issue.

3. 2024年3月5日 UTC 15:29monitoring

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

4. 2024年3月5日 UTC 16:05resolved

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

1. 2024年1月21日 UTC 18:01resolved

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

1. 2024年1月8日 UTC 21:38resolved

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

2. 2024年1月10日 UTC 15:15postmortem

   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日 UTC 13:04investigating

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

2. 2023年9月22日 UTC 14:41resolved

   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日 UTC 20:38resolved

   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日 UTC 17:43investigating

   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日 UTC 21:02investigating

   Still investigating the case.

3. 2023年9月6日 UTC 19:53resolved

   This incident has been resolved.

1. 2023年8月17日 UTC 17:10identified

   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日 UTC 19:50identified

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

3. 2023年8月17日 UTC 19:50resolved

   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日 UTC 17:26resolved

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

2. 2023年8月8日 UTC 18:16postmortem

   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.