Is Snapsheet down?

We are experiencing data replication delays in the US production environment. We have identified the cause and made enhancements to improve performance. The current ETA for resumption of normal replication speed is 18 - 24 hours, and we are continuing to work on further optimizations. We will provide an update within 4 hours.

Please note that the data replication delay is only for history/audits tables in the US production environment. Other tables are replicating normally. We are continuing to investigate possible optimizations and will provide an update within 4 hours.

We are continuing to make updates to enhance system performance and minimize latency on the history/audits tables in the US production environment. The current ETA for resumption of normal replication speed is approximately 10 hours. We will provide an update tomorrow morning to confirm status.

This incident has been resolved.

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.

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

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

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.