Is Snapsheet down?

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.

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

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.

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.

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.

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.

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

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

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

### **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.

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.

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.

This incident has been resolved.