Step 1: turn off Corel Cache, and let the bandwidth recover
Step 2: patch the BOINC problem which allows the endless repeat requests
Step 3: look again at the downhill bottleneck, because it's going to staurate with real data sooner or later (what with CUDA, Astropulse, Corei7, ATI/OpenGL, etc. etc.)

Step 4: Only deploy new apps and/or make significant system changes early on Wednesdays so you are around to fix the darn things when they so frequently blow up in your face.

I agree with #4. I work in IT (applications). We don't put anything in Production or make changes past Wednesday. This is to allow to find out problems in the real world during the weekdays when staff and production are around to see issues and fix them (we try our best to QA changes, but sometimes just can't see it until a production load is running). Long time ago, we used to make changes up through Friday, but (a) production was not happy if/when they found a problem late Friday or on Sat/Sun, and (b) IT/Production/Engineering were not happy if they had to come in over on a weekend to fix issues - that is assuming you could find the appropriate people. In a 24x7 worldwide operation, you just can't take the risk (or lose the money).

Yes I'm sure we will hear from Matt in good time. However as some people are now accusing the project team of "staging these outages to get more money" and saying that the problems are down to incompetence, if I was Matt I believe I would be very upset.

Calm down people.

Bernie"Sometimes it is the people no one imagines anything of who do the things that no one can imagine."