Doing so now but backing up the current 4.0.10 build we have as we've not had any issues with it Hopefully Dan from EZPZ will report this has resolved his issues - any insight as to what was causing the 503s (if you can post it)?
This does seem to have fixed the problem - clients have reported that they've not seen the error since we upgraded. Still no idea what caused it though.
