Skip to main content

Performance: Elist service is heavily backlogged

Last Updated:
2013-02-22 05:00:00
Event:
2013-02-22 05:00:00
Status:
Closed
Brief Description:
User Impact:
N/A
Workaround:
There is no workaround for this issue
Current Status:
N/A
Services Affected:
Full Description:
The elist service is heavily back logged following this morning's fishing attack.
CIT TDX ID:



Timeline of Changes

Description Current Status Date Time
Currently we expect it will take at least four(4) hours for the back log to clear out. So messages posted to elists will suffer lengthy delays through out the day. Currently we expect it will take at least four(4) hours for the back log to clear out. So messages posted to elists will suffer lengthy delays through out the day. 2013-02-22 05:00:00
We have managed to clear much of the fishing attack from the incoming queue on the elist server. There is still a back log of legitimate mail, however it is much smaller. We expect it will still take some time for the back log to clear out ... perhaps 1.5 hours. We are monitoring the situation. We have managed to clear much of the fishing attack from the incoming queue on the elist server. There is still a back log of legitimate mail, however it is much smaller. We expect it will still take some time for the back log to clear out ... perhaps 1.5 hours. We are monitoring the situation. 2013-02-22 05:00:00
The elist server is all caught up with the backlog and is running normally now. The elist server is all caught up with the backlog and is running normally now. 2013-02-22 05:00:00