Monday, May 14, 2012
Server Maintenance
There will be a scheduled server maintenance May 22nd through May 24, 2012. Our WeBWorK server webwork.uwstout.edu might not be available during that time.
Saturday, March 31, 2012
webwork.uwstout.edu unavailable for the moment
Update: at 6:58pm CDT, server webwork.uwstout.edu seems to be available.
At 5:44pm CDT, server webwork.uwstout.edu seems to be unavailable, as well as most of UW-Stout websites. Most likely, there is something wrong with campus networking.
At 5:44pm CDT, server webwork.uwstout.edu seems to be unavailable, as well as most of UW-Stout websites. Most likely, there is something wrong with campus networking.
Friday, January 20, 2012
Planned Outage: Saturday, January 21st, 3pm-4pm
WeBWorK server will be offline for updates this Saturday, January 21st, 3pm-4pm
Wednesday, November 23, 2011
UW-Stout campus network maintenance: Fri, Nov. 25th, 4am-10am
Due to UW-Stout campus network maintenance, webwork.uwstout.edu server might not be available Friday, November 25th, from approximately 4am-10am.
Friday, November 11, 2011
webwork.uwstout.edu will be offline 1pm-3pm this Sunday
Our webwork server, webwork.uwstout.edu will be offline from 1pm-3pm this Sunday, November 13th.
Thursday, March 10, 2011
Planned outage: 4am Monday, March 14th through 9am Tuesday, March 15th
There will be a power outage in Jarvis Hall at UW-Stout starting at 5am Monday, March 14th due to some construction-related activities. WeBWorK server will go offline at 4am and most likely stay offline until about 9am Tuesday, March 15th
Wednesday, March 9, 2011
Intermittent network issues
There seem to be intermittent network issues in Jarvis Hall Science Wing at UW-Stout, where webwork.uwstout.edu server is located. The network connectivity was unreliable since 7am this morning and the issue (if there is an issue) still appears to be unresolved.
Update (March 10th, 5:20pm): it looks like a defective switch was causing the connection issues. That should be fixed by now.
Update (March 10th, 5:20pm): it looks like a defective switch was causing the connection issues. That should be fixed by now.
Subscribe to:
Posts (Atom)