Snapdocs experienced a major incident on January 31, 2025 affecting Closings, lasting 2d 18h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 31, 2025, 09:04 PM UTC
Snapdocs is currently seeing issues with closings being created from Mortgage Cadence. Mortgage Cadence and Snapdocs are actively investigating the issue. Closings can be created manually within the Snapdocs system while the source of the issue is investigated.
- investigating Jan 31, 2025, 09:37 PM UTC
We are continuing to investigate this issue.
- investigating Jan 31, 2025, 10:07 PM UTC
We are continuing to investigate this issue with the Mortgage Cadence team and will provide another update in 30 minutes
- investigating Jan 31, 2025, 10:37 PM UTC
We are continuing to investigate this issue with the Mortgage Cadence team and will provide another update in 30 minutes.
- investigating Jan 31, 2025, 11:06 PM UTC
We are continuing to investigate this issue with the Mortgage Cadence team and will provide another update in 30 minutes.
- investigating Jan 31, 2025, 11:37 PM UTC
We are continuing to investigate this issue with the Mortgage Cadence team and will provide another update in 30 minutes.
- investigating Feb 01, 2025, 12:07 AM UTC
We are continuing to investigate this issue with the Mortgage Cadence team and will provide another update in 30 minutes.
- investigating Feb 01, 2025, 12:40 AM UTC
We are continuing to investigate this issue with the Mortgage Cadence team and will provide another update in 30 minutes.
- investigating Feb 01, 2025, 01:20 AM UTC
We are continuing to investigate this issue with the Mortgage Cadence team and will provide another update in 30 minutes.
- investigating Feb 01, 2025, 01:57 AM UTC
We are continuing to investigate this issue with the Mortgage Cadence team and will provide another update in 30 minutes.
- monitoring Feb 01, 2025, 02:17 AM UTC
We have implemented a fix and are monitoring the results. Due to the timing of the fix, we will leave this incident in monitoring status until Monday to allow time to confirm.
- resolved Feb 03, 2025, 03:43 PM UTC
This incident has been resolved.