Resolved -
This incident has been resolved.
Nov 28, 06:08 CST
Update -
We are continuing to monitor for any further issues.
Nov 28, 03:11 CST
Update -
We have resolved the issue causing this incident, and our monitoring has confirmed that performance has returned to acceptable levels.
We are continuing to process any data impacted or delayed during the incident.
Thank you for your patience while we worked through this issue. We sincerely apologize for the inconvenience.
Nov 28, 00:31 CST
Update -
We are continuing to monitor for any further issues.
Nov 27, 22:19 CST
Monitoring -
We have corrected the issue that caused this incident and we're actively monitoring the situation to ensure performance returns to acceptable levels. Thank you for your patience.
Nov 27, 21:13 CST
Update -
We are still working to correct the issue identified earlier. We appreciate your patience while we work to resolve this issue.
Nov 27, 20:38 CST
Update -
We are still working to correct the issue identified earlier. We appreciate your patience while we work to resolve this issue.
Nov 27, 19:39 CST
Update -
We are still working to correct the issue identified earlier. We appreciate your patience while we work to resolve this issue.
Nov 27, 18:04 CST
Update -
We are still working to correct the issue identified earlier. We appreciate your patience while we work to resolve this issue.
Nov 27, 16:59 CST
Identified -
We have identified the cause of this incident and our Technology team is working diligently to correct it. Thanks for your continued patience.
Nov 27, 16:02 CST
Investigating -
We are investigating an open incident with our document processing infrastructure which is potentially causing delays or failures for transactions processing through the system. No data has been lost and the system should be caught up shortly. We will reconcile all data after we have recovered from the incident to ensure all transactions are processed as expected.
Nov 27, 15:36 CST