The AP follows up on their story from earlier in the week...

Comcast has repeatedly denied blocking any Internet application, including "peer-to-peer" file-sharing programs like BitTorrent, which the AP used in its nationwide tests.

On Tuesday, Mitch Bowling, senior vice president of Comcast Online Services, added a nuance to that statement, saying that while Comcast may block initial connection attempts between two computers, it eventually lets the traffic through if the computers keep trying. ...

However, users also reported Comcast blocking some transfers of e-mails with large attachments through an application that is fully in the legal sphere: Lotus Notes, an IBM Corp. program used in corporate settings.

Kevin Kanarski, a network engineer for a major law firm, noticed the disruption in August and eventually traced the problem to Comcast. But he got the cold shoulder from the company's customer support department.

On Tuesday, Bowling acknowledged the problem, saying it was unintentional and due to a software bug that has been fixed. Kanarski said transfers started working again last week.
I am writing this entry as much to applaud Mitch Bowling as to update on the overall issue.

Based on blog entries, e-mails, and conversations with Lotus support, I've been trying to reach people within Comcast for several days.  A blog reader sent me a note last week with a different name at Comcast, someone that they thought could help.  That e-trail eventually ended up with Mitch Bowling.  Bowling called me on Monday to indicate, as he told the AP, that they have fixed the problem with Notes.  Further, without going into the details of the call, I want you to know that Bowling's tone was very positive and honest about the whole issue.  I sincerely believe that it was unintentional that Lotus Notes got caught up in whatever traffic-related tools Comcast is/was using.  

Most importantly, the Lotus and blogging community was what made the communication between IBM and Comcast successful.  I don't know how I would have ever approached this issue before social networking tools.  I certainly don't know how we would have found the right people and gotten it resolved.  Someone would have known someone would have known someone, but it would have taken time and "telephone" games.  Now, one customer (Kevin Kanarski) spoke, many listened. Lotus support engaged and did the right diagnosing and troubleshooting.  A developer chimed in after reading the blog.  We all worked together -- despite, as I've admitted, my initial slowness in engaging with Kevin when he first contacted me -- and got this issue addressed.  Very, very cool.

Link: Associated Press: Comcast Admits Delaying Some Traffic > (Thanks for the link, Rob)

Post a Comment