Resolved -
This incident has been resolved.
Jul 24, 22:04 CDT
Update -
We are continuing to work on a fix for this issue.
Jul 24, 21:45 CDT
Update -
We are continuing to work on a fix for this issue.
Jul 24, 21:21 CDT
Update -
We are continuing to work on a fix for this issue.
Jul 24, 21:08 CDT
Update -
We are continuing to work on a fix for this issue.
Jul 24, 20:56 CDT
Update -
We are continuing to work on a fix for this issue.
Jul 24, 20:38 CDT
Update -
We are continuing to work on a fix for this issue.
Jul 24, 20:24 CDT
Identified -
The issue has been identified and a fix is being implemented.
Jul 24, 20:02 CDT
Update -
We are continuing to monitor for any further issues.
Jul 24, 19:44 CDT
Update -
We are continuing to monitor for any further issues.
Jul 24, 18:50 CDT
Update -
We are continuing to monitor for any further issues.
Jul 24, 18:28 CDT
Update -
We are continuing to monitor for any further issues.
Jul 24, 17:42 CDT
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 24, 17:27 CDT
Update -
We are continuing to work on a fix for this issue.
Jul 24, 17:07 CDT
Update -
We are continuing to work on a fix for this issue.
Jul 24, 16:46 CDT
Update -
We are continuing to work on a fix for this issue.
Jul 24, 16:28 CDT
Identified -
The issue has been identified and a fix is being implemented.
Jul 24, 16:11 CDT
Update -
We are continuing to monitor for any further issues.
Jul 24, 15:55 CDT
Update -
We are continuing to monitor for any further issues.
Jul 24, 15:23 CDT
Update -
We are continuing to monitor for any further issues.
Jul 24, 14:51 CDT
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 24, 14:38 CDT
Identified -
The issue has been identified and a fix is being implemented.
Jul 24, 14:37 CDT
Update -
We are continuing to investigate this issue.
Jul 24, 14:22 CDT
Update -
We are continuing to investigate this issue.
Jul 24, 14:02 CDT
Investigating -
We are currently investigating this issue.
Jul 24, 13:44 CDT