[yg-alerts] Site Slowness Friday April 27

[Guest guest]

Groups is being affected by a network connectivity issue that isaffecting a number of properties. This issue is not specific toGroups. We are working with the Network Operations team toresolve the problem, which began Friday April 27, at approximately 8:00 a.m. Pacific (http://www.timeanddate.com/worldclock/).We do not have an estimate of when this will be resolved. We will keepyou updated via the Groups team blog: http://blog.360./y_groups_team

[Guest guest]

This problem actually started yesterday afternoon. I have

seen it in reports from the servers I use for my email Talk Lists. Lots

of delayed email for and Comcast also.

Dick

At 10:56 AM 4/27/2007, you wrote:

Groups is being

affected by a network connectivity issue that is

affecting a number of properties.

This issue is not specific to Groups.

We are working with the Network Operations team to

resolve the problem, which began Friday April 27, at approximately

8:00 a.m. Pacific

(

http://www.timeandd ate.com/worldclo

ck/).

[Guest guest]

For a fun time try http://www.peternoone.com.

For The DC5 fans, please check the updates on Mike at

http://www.mikesmith1964.com

----- Forwarded Message ----From: y_groups_team <y_groups_team@...>yg-alerts Sent: Friday, April 27, 2007 1:27:05 PMSubject: [yg-alerts] Site Slowness Friday April 27

Groups is being affected by a network connectivity issue that isaffecting a number of properties. This issue is not specific toGroups. We are working with the Network Operations team toresolve the problem, which began Friday April 27, at approximately 8:00 a.m. Pacific (http://www.timeandd ate.com/worldclo ck/).We do not have an estimate of when this will be resolved. We will keepyou updated via the Groups team blog: http://blog. 360.. com/y_groups_ team

[Guest guest]

[yg-alerts] Site Slowness Friday April 27

Groups is being affected by a network connectivity issue that is

affecting a number of properties. This issue is not specific to

Groups. We are working with the Network Operations team to

resolve the problem, which began Friday April 27, at approximately

8:00 a.m. Pacific (http://www.timeanddate.com/worldclock/).

We do not have an estimate of when this will be resolved. We will keep

you updated via the Groups team blog:

http://blog.360./y_groups_team