Snapsheet 장애 기록

1. 2026년 7월 23일 오후 4:22 UTCidentified

   우리는 미국 생산 환경에 있는 역사/audits 테이블을 위한 자료 복제 지연을 경험하고 있습니다. 우리는 성과를 개량하기 위하여 원인과 만드는 증진을 확인했습니다. 정상적인 복제 속도의 resumption를 위한 현재 ETA는 18 - 24 시간이고, 우리는 더 최적화에 일하기 위하여 계속됩니다. 우리는 4 시간 안에 갱신을 제공할 것입니다.

2. 2026년 7월 23일 오후 5:31 UTCidentified

   데이터 복제 지연은 미국 생산 환경에서의 역사/audits 테이블에만 적용됩니다. 다른 테이블은 일반적으로 복제됩니다. 우리는 가능한 최적화를 조사하고 4 시간 이내에 업데이트를 제공합니다.

3. 2026년 7월 23일 오후 10:01 UTCmonitoring

   시스템 성능 향상 및 미국 생산 환경에서의 역사/오직 테이블에 대한 대기 시간을 최소화하기 위해 업데이트를 계속하고 있습니다. 정상적인 복제 속도의 resumption를 위한 현재 ETA는 대략 10 시간입니다. 우리는 업데이트 내일 아침 상태를 확인합니다.

4. 2026년 7월 24일 오후 6:02 UTCresolved

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

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

1. 2026년 6월 17일 오후 11:23 UTCidentified

   We are experiencing a delay in US UAT data replication of approximately 2.5 hours. We are actively working on resolving the issue and will provide another update within 2 hours.

2. 2026년 6월 18일 오전 2:21 UTCidentified

   We are continuing to progress on the fix for the issue and performance is improving. We will provide another update by 9am central.

3. 2026년 6월 18일 오전 11:26 UTCresolved

   The delay in US UAT data replication has been resolved, and performance and returned to normal levels.

1. 2026년 6월 10일 오후 9:34 UTCinvestigating

   We have identified an issue within the UAT environment that is impacting user access. We are investigating the issue as a high priority and will provide an update within one hour.

2. 2026년 6월 10일 오후 9:57 UTCresolved

   This incident has been resolved and access restored. Please reach out to Snapsheet Support with any further questions or concerns.

1. 2026년 5월 7일 오후 7:10 UTCidentified

   We are currently experiencing data replication latency in the production environment. We are aware of the issue and working to improve performance. We will provide another update within the next two hours.

2. 2026년 5월 7일 오후 8:51 UTCresolved

   Data replication latency has returned to normal levels. We will review the incident and follow up with a post-mortem within the next business week. Please contact the Snapsheet support team if you experience any further issues.

3. 2026년 5월 21일 오후 5:18 UTCpostmortem

   On May 7, 2026, a data pipeline component responsible for replicating production data to the warehouse entered a silent failure state due to an internal schema inconsistency. This caused data replication to stall for over 4 hours, resulting in missing or delayed data for affected clients. The issue was not caught by automated alerting because the pipeline continued to report a healthy status despite being inactive. Once identified, the problem was resolved by removing the affected table from the pipeline configuration, restoring normal data flow. We are in the process of updating our alerting to report this kind of issue going forward.

1. 2026년 4월 14일 오후 2:38 UTCidentified

   We have identified some remaining data inconsistencies from the replication delay experienced on April 13. We are working to address the issue with an ETR of end of business today. We will provide another update by 2pm CDT today.

2. 2026년 4월 14일 오후 7:03 UTCidentified

   We are continuing to address the data inconsistencies. We will provide another update at 5pm CDT.

3. 2026년 4월 14일 오후 10:29 UTCidentified

   We are continuing to address the data inconsistencies. We will provide another update by 8pm CDT.

4. 2026년 4월 15일 오후 2:30 UTCresolved

   The data inconsistencies have been addressed, and the incident is resolved.

5. 2026년 4월 23일 오후 4:44 UTCpostmortem

   ### **Incident Summary** On the afternoon of **April 13**, a technical capacity limit in our data pipeline caused a temporary halt in data updates. This resulted in a delay of real-time data replication to customer databases. ### **Resolution & Recovery** * **System Fix:** Our engineering team identified the bottleneck and upgraded our database infrastructure to prevent this limit from being reached again. * **Data Restoration:** We performed a comprehensive data reconciliation over the following 48 hours to ensure all missing records were recovered and accurately synced. * **Current Status:** All services are fully restored, and all backfilled data has been verified for accuracy. * **Enhanced Monitoring:** We are taking measures to improve our alerting and response process  **Note:** You may have experienced replication delay and data inconsistencies during this window, but no data was lost. We appreciate your patience while we worked to resolve this. If you notice any remaining discrepancies in your specific reports, please reach out to our support team.

1. 2026년 4월 13일 오후 8:02 UTCinvestigating

   We have identified a delay in data replication, and we are are working to address it as a high priority. We will provide an update by 5pm CDT.

2. 2026년 4월 13일 오후 9:40 UTCmonitoring

   We have resolved the data replication latency. All new data is replicating, and we are working to confirm data integrity for the time during which the issue occurred. We will provide another update within two hours.

3. 2026년 4월 14일 오후 12:45 UTCresolved

   This incident has been resolved.

1. 2026년 2월 25일 오후 5:39 UTCinvestigating

   We have observed an issue with Sendgrid that is causing some customers to experience degraded performance of Microsoft Outlook. This issue is resulting in pending deliveries of some emails from Snapsheet to the impacted Microsoft accounts.

2. 2026년 2월 25일 오후 6:40 UTCinvestigating

   We have engaged Sendgrid to remediate the issue that is causing the delays in email deliveries. The next update will be no later than 4pm CST.

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

   We have identified the issue that is causing delayed email deliveries to some recipients with Microsoft associated inboxes. We are seeing some improved performance, but we are continuing to work with Sendgrid to fully resolve the issue. We will provide another update by 10am CST tomorrow.

4. 2026년 2월 26일 오후 3:37 UTCresolved

   Sendgrid has resolved the issue that is causing delayed email deliveries to some recipients with Microsoft associated inboxes, and pending emails have been delivered. Please contact Snapsheet Support with any further questions or concerns.

1. 2026년 2월 23일 오후 10:37 UTCinvestigating

   There is currently a delay in search indexing that is causing a delay in claims or policies becoming searchable. We are aware of the issue and working to address it as a high priority.

2. 2026년 2월 24일 오전 12:13 UTCresolved

   We have resolved the delay in search indexing and confirmed searches are performing normally.

1. 2026년 2월 2일 오후 11:02 UTCidentified

   We have confirmed that users may experience intermittent issues accessing claims in UAT. We have identified that the issues are related to an interruption with the UAT deployment caused by a Github incident (https://www.githubstatus.com/). We will continue to monitor and work to complete the deployment as soon as possible.

2. 2026년 2월 3일 오전 12:56 UTCmonitoring

   We have successfully deployed the latest UAT release, and we are monitoring to confirm no further issues.

3. 2026년 2월 3일 오전 2:11 UTCresolved

   This incident has been resolved, and the latest UAT release has been successfully deployed. Please contact Snapsheet Support if you experience and further issues.

1. 2026년 1월 22일 오후 11:34 UTCidentified

   Sendgrid is currently investigating an issue with Microsoft that is causing some customers to experience degraded performance of Microsoft Outlook. This issue is resulting in failed deliveries of some emails from Snapsheet to the impacted Microsoft accounts. Updates from Sendgrid are available at https://status.sendgrid.com/.

2. 2026년 1월 23일 오후 2:12 UTCidentified

   Sendgrid is continuing to investigate the issue. Updates from Sendgrid are available at https://status.sendgrid.com/.

3. 2026년 1월 27일 오후 7:59 UTCidentified

   We are seeing a some recovery in email deliverability following the disruption with our email delivery partner Sendgrid. While we are still awaiting official confirmation of a final resolution. We will continue to monitor the situation closely.

4. 2026년 1월 28일 오후 4:35 UTCresolved

   We have received confirmation from SendGrid that the increased Microsoft inbox provider blocks are due to an issue with Microsoft, and that the issue is not isolated to SendGrid’s environment nor specific to their sending configuration. While we are seeing improvement (reduction) of deferrals, Microsoft customers who are continuing to observe excessive deferrals and/or blocks should fill out the OLC Support request form at https://olcsupport.office.com/. Thank you for your patience and understanding regarding this issue. If you have any further questions or concerns, please contact Snapsheet Support for assistance.

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

   We are currently investigating an issue with API calls receiving errors. We are treating the issue as Urgent and will provide an update within one hour.

2. 2025년 12월 1일 오후 4:11 UTCidentified

   We have identified the issue and fix. We are working to implement the fix and continuing to monitor.

3. 2025년 12월 1일 오후 4:38 UTCmonitoring

   We have deployed a fix and continuing to monitor to confirm that there are no ongoing issues.

4. 2025년 12월 1일 오후 5:34 UTCresolved

   The incident is confirmed to be resolved.

1. 2025년 11월 18일 오후 3:12 UTCmonitoring

   There is a Cloudflare outage that is impacting Smartcomms and causing letters to fail. Updates are provided by Cloudflare on their status page at https://www.cloudflarestatus.com/. We will continue to monitor and update our own status page accordingly.

2. 2025년 11월 18일 오후 3:12 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 2025년 11월 18일 오후 4:19 UTCresolved

   The Cloudflare outage has been updated to resolved, and we've confirmed Smartcomm letters are sending successfully.

1. 2025년 10월 30일 오후 3:53 UTCinvestigating

   We are seeing a delay in data replication and are investigating it as a high priority. We will provide updates as they become available.

2. 2025년 10월 30일 오후 4:11 UTCmonitoring

   We are seeing improved performance and continuing to monitor. We will provide additional updates as they become available.

3. 2025년 10월 30일 오후 5:53 UTCresolved

   This incident has been resolved. If you experience any further issues, please reach out to Snapsheet Support.

1. 2025년 10월 20일 오후 2:59 UTCinvestigating

   We are aware of an ongoing outage within Amazon Web Services (AWS). Our team is actively monitoring for any potential impact to our systems and will provide updates as more information becomes available from AWS.

2. 2025년 10월 20일 오후 5:03 UTCinvestigating

   We are continuing to monitor the ongoing AWS outage. As a result of this incident, we are experiencing delays in data warehouse replication. We'll share updates as more information becomes available.

3. 2025년 10월 21일 오전 2:31 UTCinvestigating

   The AWS outage has been confirmed to be resolved. Please reach out to Snapsheet Support with any questions or concerns.

4. 2025년 10월 21일 오전 2:31 UTCresolved

   This incident has been resolved.

1. 2025년 8월 18일 오후 2:54 UTCidentified

   OFAC is experiencing an outage with the OFAC API from trade.gov. They are experiencing a certificate error on their platform and currently looking into it. Payments created with the feature on will be put in Compliance Hold until a user approves them.

2. 2025년 8월 18일 오후 5:55 UTCidentified

   We are continuing to monitor OFAC's progress and will provide updates here as we receive them.

3. 2025년 8월 18일 오후 7:52 UTCmonitoring

   OFAC has updated their certificate to resolve the error. We are currently transitioning the payments and will provide an update when the transitions are complete.

4. 2025년 8월 18일 오후 10:53 UTCresolved

   All of the pending transactions impacted by the issue have been transitioned, and the incident is considered Resolved. Please contact Snapsheet Support if you continue to experience any further issues.

1. 2024년 12월 18일 오후 9:14 UTCidentified

   OFAC is experiencing an outage with the OFAC API from trade.gov. They are experiencing high latency on their platform and currently looking into it. Payments created with the feature on will be put in Compliance Hold until a user approves them.

2. 2024년 12월 18일 오후 9:14 UTCidentified

   OFAC is continuing to work on a fix for this issue.

3. 2024년 12월 19일 오전 12:51 UTCresolved

   This incident has been resolved. If you experience any further issues, please contact Snapsheet support.

1. 2024년 9월 28일 오후 4:30 UTCidentified

   We are currently seeing delays in replication through the data warehouse. We actively working on addressing the delay and will provide another update as soon as possible.

2. 2024년 9월 28일 오후 6:08 UTCidentified

   We are continuing to work on addressing the replication delays and have engaged AWS support for Amazon's Data Migration Service where the delay is being experienced.

3. 2024년 9월 28일 오후 6:55 UTCidentified

   We are seeing normal throughput for the data pipeline and expect the replication delays to be fully resolved shortly.

4. 2024년 9월 28일 오후 7:39 UTCmonitoring

   The delays in replication have been resolved and we are continuing to monitor.

5. 2024년 9월 28일 오후 7:51 UTCresolved

   This issue has been resolved. Please contact Snapsheet Support if you experience any further issues.

1. 2024년 9월 19일 오후 1:51 UTCinvestigating

   “We are investigating an issue with the navigation bar in US UAT and will provide an update as soon as possible”

2. 2024년 9월 19일 오후 2:57 UTCinvestigating

   We are continuing to investigate the issue and will provide an update as soon as possible.

3. 2024년 9월 19일 오후 3:15 UTCresolved

   This incident has been resolved. Please contact Snapsheet Support if you experience any further issues.

1. 2024년 9월 11일 오후 1:47 UTCidentified

   “We are currently seeing delays in claims being indexed for search. We are investigating and will provide updates as they become available.”

2. 2024년 9월 11일 오후 2:36 UTCresolved

   This incident has been resolved. Please contact Snapsheet Support if you experience any further issues.

1. 2024년 9월 4일 오후 1:55 UTCinvestigating

   We are currently experiencing processing delays with claim details showing up in the work queues.

2. 2024년 9월 4일 오후 2:22 UTCinvestigating

   The processing delays have been resolved. We will continue to monitor performance and provide a post-mortem as soon as it becomes available.

3. 2024년 9월 4일 오후 2:22 UTCresolved

   This incident has been resolved.