Resolved -
We have completed the data restoration and synchronization. Team members have confirmed the fix has produced the proper results. Incident resolved.
Feb 4, 08:40 EST
Update -
The team will conduct functional testing to ensure the system is fully restored and operating as expected. We will send an update on the next hour.
Feb 4, 07:12 EST
Update -
We are continuing to work on a fix for this issue.
Feb 4, 07:12 EST
Update -
The team is still working in the recovery process. We will provide an update within the next hour once the system is fully restored.
Feb 4, 06:14 EST
Update -
Recovery efforts are actively underway. We will continue to monitor progress and provide updates once services have been fully restored.
Feb 4, 05:15 EST
Update -
Recovery efforts are currently ongoing and we will share updates once restoration is completed.
Feb 4, 04:16 EST
Update -
We are continuing to work on a fix for this issue.
Feb 4, 03:10 EST
Update -
Recovery are still in progress. Our technical teams are restoring affected system components, and we are closely monitoring progress. A detailed update will follow once restoration is complete.
Feb 4, 02:03 EST
Update -
Recovery efforts are ongoing. Our technical teams are actively restoring affected system objects to ensure a stable return to service. We are monitoring progress closely and will share a more detailed update once the restoration phase is complete.
Feb 4, 01:04 EST
Update -
Recovery efforts are ongoing. Our technical teams are actively restoring affected system objects to ensure a stable return to service. We are monitoring progress closely and will share a more detailed update once the restoration phase is complete.
Feb 4, 01:04 EST
Update -
IT is still working on restoration of affected objects.
Feb 4, 00:03 EST
Update -
We are continuing to work on a fix for this issue.
Feb 3, 23:04 EST
Identified -
We’re currently experiencing an issue where some forms are not successfully attaching to transactions. Instead of being added, an error message appears.
Our team is actively working to identify the cause and resolve the issue as quickly as possible. We’ll share updates as soon as we have more information or a fix in place.
Feb 3, 23:03 EST