Inside the Attack that Crippled Revision3

The popular Internet television network Revision3 suffered from a severe DDoS attack, launched by the infamous anti-piracy organization MediaDefender. After targeting The Pirate Bay’s trackers, MediaDefender apparently thought it was a good idea to spread their fake torrents through Revision3.


revision 3The CEO of Revision3 - Jim Louderback - was quite surprised when he found out that MediaDefender was the source of the attack that took down their entire network this weekend. He found out that MediaDefender used the Revision3 BitTorrent tracker for the fake torrents they upload to various BitTorrent sites.

In a lengthy blog post Louderback explains what happened, as he writes: “Media Defender was abusing one of Revision3’s servers for their own purposes – quite without our approval. When we closed off their backdoor access, MediaDefender’s servers freaked out, and went into attack mode – much like how a petulant toddler will throw an epic tantrum if you take away an ill-gotten Oreo.”

MediaDefender’s attack effectively took down the Revision3 BitTorrent tracker this weekend, and people were unable to grab the latest episodes. That was not all, the flood of SYN packets also took out their webserver and their email. These kind of attacks are illegal according to US law, and if Revision3 decides to pursue this case in court, it would not be the first time MediaDefender gets caught.

Only a few months ago, The Pirate Bay sued several media companies that hired MediaDefender, for exactly the same behavior. Pirate Bay founder Peter Sunde said at the time: “They are going around accusing the pirate community for doing immoral stuff, when they do illegal stuff. We need to make a statement that just because something might be hard to fight it doesn’t mean that laws do not imply in the case.”

Louderback has no idea whether the attack on their network was intentional or not, but said he involved the FBI. “Was it malicious? Intentional? Negligent? Spoofed? I can’t say. But what I do know is that the FBI is looking into the matter – and it’s far more serious than toddlers squabbling over broken toys and lost cookies.”

This is yet another epic fail in MediaDefender’s history, and this might very well be the the final punch to knock the company out. Most of you probably remember the leaked emails and confidential information, which cost the company hundreds of thousands of dollars, and brought them on the verge of bankruptcy.

To quote MediaDefender’s CEO Randy Saaf: “This is really fucked.”

Jim Louderback's Blogpost is contained below, in full:



Inside the Attack that Crippled Revision3


on May 29th, 2008 at 07:49 am by Jim Louderback in Polemics


As many of you know, Revision3’s servers were brought down over the Memorial Day weekend by a denial of service attack. It’s an all too common occurrence these days. But this one wasn’t your normal cybercrime – there’s a chilling twist at the end. Here’s what happened, and why we’re even more concerned today, after it’s over, than we were on Saturday when it started.

It all started with just a simple “hi”. Now “hi” can be the sweetest word in the world, breathlessly whispered into your ear by a long-lost lover, or squealed out by your bouncy toddler at the end of the day. But taken to excess – like by a cranky 3-year old–it gets downright annoying. Now imagine a room full of hyperactive toddlers, hot off of a three hour Juicy-Juice bender, incessantly shrieking “hi” over and over again, and you begin to understand what our poor servers went through this past weekend.

On the internet, computers say hi with a special type of packet, called “SYN”. A conversation between devices typically requires just one short SYN packet exchange, before moving on to larger messages containing real data. And most of the traffic cops on the internet – routers, firewalls and load balancers – are designed to mostly handle those larger messages. So a flood of SYN packets, just like a room full of hyperactive screaming toddlers, can cause all sorts of problems.

For adults, it’s typically an inability to cope, followed either by quickly fleeing the room, or orchestrating a massive Teletubbies intervention. Since they lack both legs and a ready supply of plushies, internet devices usually just shut down.

revision3_f5_dos.jpg
That’s what happened to us. Another device on the internet flooded one of our servers with an overdose of SYN packets, and it shut down – bringing the rest of Revision3 with it. In webspeak it’s called a Denial of Service attack – aka DoS – and it happens when one machine overwhelms another with too many packets, or messages, too quickly. The receiving machine attempts to deal with all that traffic, but in the end just gives up.
(Note the photo of our server equipment responding to the DoS Attack)

In its coverage Tuesday CNet asked the question, “Now who would want to attack Revision3?” Who indeed? So we set out to find out.

Internet attacks leave lots of evidence. In this case it was pretty easy to see exactly what our shadowy attacker was so upset about. It turns out that those zillions of SYN packets were addressed to one particular port, or doorway, on one of our web servers: 20000. Interestingly enough, that’s the port we use for our Bittorrent tracking server. It seems that someone was trying to destroy our bittorrent distribution network.

Let me take a step back and describe how Revision3 uses Bittorrent, aka BT. The BT protocol is a peer to peer scheme for sharing large files like music, programs and video. By harnessing the peer power of many computers, we can easily and cheaply distribute our huge HD-quality video shows for a lot less money. To get started, the person sharing that large file first creates a small file called a “torrent”, which contains metadata, along with which server will act as the conductor, coordinating the sharing. That server is called the tracking server, or “tracker”. You can read much more about Bittorrent at Wikipedia, if you really want to understand how it works.

Revision3 runs a tracker expressly designed to coordinate the sharing and downloading of our shows. It’s a completely legitimate business practice, similar to how ESPN puts out a guide that tells viewers how to tune into its network on DirecTV, Dish, Comcast and Time Warner, or a mall might publish a map of its stores.

But someone, or some company, apparently took offense to Revision3 using Bittorrent to distribute its own slate of shows. Who could that be?

Along with where it’s bound, every internet packet has a return address. Often, particularly in cases like this, it’s forged – or spoofed. But interestingly enough, whoever was sending these SYN packets wasn’t shy. Far from it: it’s as if they wanted us to know who they were.

A bit of address translation, and we’d discovered our nemesis. But instead of some shadowy underground criminal syndicate, the packets were coming from right in our home state of California. In fact, we traced the vast majority of those packets to a public company called Artistdirect (ARTD.OB). Once we were able to get their internet provider on the line, they verified that yes, indeed, that internet address belonged to a subsidiary of Artist Direct, called MediaDefender.

Now why would MediaDefender be trying to put Revision3 out of business? Heck, we’re one of the biggest defenders of media around. So I stopped by their website and found that MediaDefender provides “anti-piracy solutions in the emerging Internet-Piracy-Prevention industry.” The company aims to “stop the spread of illegally traded copyrighted material over the internet and peer-to-peer networks.” Hmm. We use the internet and peer-to-peer networks to accelerate the spread of legally traded materials that we own. That’s sort of directly opposite to what Media Defender is supposed to be doing.

Who pays MediaDefender to disrupt peer to peer networks? I don’t know who’s ponying up today, but in the past their clients have included Sony, Universal Music, and the central industry groups for both music and movies – the RIAA and MPAA. According to an article by Ars Technica, the company uses “its array of 2,000 servers and a 9GBps dedicated connection to propagate fake files and launch denial of service attacks against distributors.” Another Ars Technica story claims that MediaDefender used a similar denial of service attack to bring down a group critical of its actions.

Hmm. Now this could have been just a huge misunderstanding. Someone could have incorrectly configured a server on Friday, and left it to flood us mercilessly with SYN packets over the long Memorial Day weekend. If so, luckily it was pointed at us, and not, say, at the intensive care unit at Northwest Hospital and Medical Center But Occam’s razor leads to an entirely different conclusion.

So I picked up the phone and tried to get in touch with ArtistDirect interim CEO Dimitri Villard. I eventually had a fascinating phone call with both Dimitri Villard and Ben Grodsky, Vice President of Operations at Media Defender.

First, they willingly admitted to abusing Revision3’s network, over a period of months, by injecting a broad array of torrents into our tracking server. They were able to do this because we configured the server to track hashes only – to improve performance and stability. That, in turn, opened up a back door which allowed their networking experts to exploit its capabilities for their own personal profit.

Second, and here’s where the chain of events come into focus, although not the motive. We’d noticed some unauthorized use of our tracking server, and took steps to de-authorize torrents pointing to non-Revision3 files. That, as it turns out, was exactly the wrong thing to do. MediaDefender’s servers, at that point, initiated a flood of SYN packets attempting to reconnect to the files stored on our server. And that torrential cascade of “Hi”s brought down our network.

Grodsky admits that his computers sent those SYN packets to Revision3, but claims that their servers were each only trying to contact us every three hours. Our own logs show upwards of 8,000 packets a second.

“Media Defender did not do anything specific, targeted at Revision3″, claims Grodsky. “We didn’t do anything to increase the traffic” – beyond what they’d normally be sending us due to the fact that Revision3 was hosting thousands of MediaDefender torrents improperly injected into our corporate server. His claim: that once we turned off MediaDefender’s back-door access to the server, “traffic piled up (to Revision3 from MediaDefender servers because) it didn’t get any acknowledgment back.”

Putting aside the company’s outrageous use of our servers for their own profit, and the large difference between one connection every three hours and 8,000 packets a second, I’m still left to wonder why they didn’t just tell us our basement window was unlocked. A quick call or email and we’d have locked it up tighter than a drum.

It’s as if McGruff the Crime Dog snuck into our basement, enlisted an army of cellar rats to eat up all of our cheese, and then burned the house down when we finally locked him out – instead of just knocking on the front door to tell us the window was open.

In the end, here’s what I know:


  • A torrential flood of SYN packets rained down on Revision3’s network over Memorial Day weekend.

  • Those packets – up to 8,000 a second – came primarily from computers controlled by MediaDefender, who is in the business of shutting down illegal torrent sites.

  • Revision3 suffered measurable harm to its business due to that flood of packets, as the attacks on our legitimate and legal Torrent Tracking server spilled over into our entire internet infrastructure. Thus we were unable to serve videos and advertising through much of the weekend, and into Tuesday – and even our internal email servers were brought down.

  • Denial of service attacks are illegal in the US under 12 different statutes, including the Economic Espionage Act and the Computer Fraud and Abuse Act.


Although I can only guess, here’s what I think really happened. Media Defender was abusing one of Revision3’s servers for their own purposes – quite without our approval. When we closed off their backdoor access, MediaDefender’s servers freaked out, and went into attack mode – much like how a petulant toddler will throw an epic tantrum if you take away an ill-gotten Oreo.

That tantrum threw upwards of 8,000 SYN packets a second at our servers. And that was enough to bring down both our public facing site, our RSS server, and even our internal corporate email – basically the entire Revision3 business. Smashing the cookie jar, as it were, so that no one else could have any Oreos either.

Was it malicious? Intentional? Negligent? Spoofed? I can’t say. But what I do know is that the FBI is looking into the matter – and it’s far more serious than toddlers squabbling over broken toys and lost cookies.

MediaDefender claims that they have taken steps to ensure this won’t happen again. “We’ve added a policy that will investigate open public trackers to see if they are associated with other companies”, promised Grodsky, “and first will make a communication that says, hey are you aware of this.”

In the end, I don’t think Media Defender deliberately targeted Revision3 specifically. However, the company has a history of using their servers to, as Ars Technica said, “launch denial of service attacks against distributors.” They saw us as a “distributor” – even though we were using Bittorrent for legitimate reasons. Once we shut them out, their vast network of servers were automatically programmed to implement a scorched earth policy, and shut us down in turn. The long Memorial Day weekend holiday made it impossible for us to contact either Media Defender or their ISP, which only exacerbated the problem.

All I want, for Revision3, is to get our weekend back – both the countless hours spent by our heroic tech staff attempting to unravel the mess, and the revenue, traffic and entertainment that we didn’t deliver.

If it can happen to Revision3, it could happen to your business too. We’re simply in the business of delivering entertainment and information – that’s not life or death stuff. But what if MediaDefender discovers a tracker inside a hospital, fire department or 911 center? If it happened to us, it could happen to them too. In my opinion, Media Defender practices risky business, and needs to overhaul how it operates. Because in this country, as far as I know, we’re still innocent until proven guilty – not drawn, quartered and executed simply because someone thinks you’re an outlaw.

- Jim Louderback
CEO - Revision3

How Twitter's ComcastCares Turned My Stress Filled Week Into One That Wasn't

Edit: This post was previously two posts but to make it easier to follow the whole story, I've edited them into a single post that was better formatted. I apologize for my long winded, and probably, poor written explanation. I'm a Web Designer/Content Manager - not an English Major (and I never liked Shakespeare anyway).

Original Post - May 12th, 2008

Let me walk you back to April 15th, 2008. I had just started a new job & just gotten my application approved to my new apartment that I would be moving into on May 15th, 2008. Trying to make sure that I took care of scheduling all of my new utilities well in advance, I called the Comcast building representative for my new complex (as my leasing agent told me to do). I told him which services I wanted and explained to him that I would not be moving into my new apartment until April 15th and that, if possible, I wanted to have them come on May 17th, a Saturday, and schedule a hookup of my new television & internet service. I also told him how I would need two single stream or one multi-stream CableCard for my HD Tivo. Having heard horror stories from fellow Tivo owners, online, about getting Comcast to successfully install Cable Cards or much less admit to you being able to get them (or spending an hour on the phone with a rep who doesn't know what they are) I was pleasantly surprised when, without batting an eye, the rep told me it would be no problem to have CableCard(s) sent out.

Very pleased, I hung up the phone, opened my Google Calendar & scheduled the appointment for that day.

Fast forward to this morning, May 12th, 2008.

I receive a call on my cell phone, while sitting at my desk at work that was marked restricted via caller ID. I answer the phone and a person, whom I can barely hear, tells me he is a Comcast service tech and wants to verify that I was at my apartment because he is on his way to install my new Comcast service. Exasperated I tell him that...no....this is not ok, as I don't live there yet. I explained that I called a month ago to schedule a hookup on the 17th and that my time window was from 9:00 am until noon. He said...oh ok and was about to hang up when I stopped him. "Wait Wait," I said. "Are you going to come Saturday still to connect my new service." He answers, "I dunno." Pause. I ask, "Well - I was told, a month ago, that it would be May 17th between 9 and 12. Should I call customer service to verify this?" He said, "Oh yes yes. Goodbye" and hung up.

I immediately dug through my email to get the contact number for the Comcast building rep for our complex and I called him.

The conversation went as such:

"Hello"

"Uh, Hi. I'm calling to verify that my scheduled hookup appointment is still Saturday May 17th between 9:00 and 12:00. I just received a call from a tech who was on his way to my apartment to hookup my service except this isn't correct. I scheduled it for the 17th."

"Ummm....can I call you back at this number in several minutes?"

I then explain to him that the number he is seeing on his caller ID isn't my actual desk number - but the main number for my employer. I then try to give him my desk line and he says "One moment sir, I need to pull over so I can take down your information." Uh - since when do Comcast reps drive around????

I give him my information and he says he will call me back later once he can look up my info. I tell him, worried, "I called a month ago to schedule this hookup." He sounds doubtful, "I don't know if we have any times available still on Sautrday." Grrrrrrrr

THATS WHY I CALLED A MONTH AGO TO SCHEDULE IT YOU IMBECILE!!!!!

COMCAST CUSTOMER SERVICE SUCKS

(Edit from May 21st: Can't you tell how frustrated/pissed off I was? Keep in mind we had planned to move the following weekend (16th & 17th) and this date had been approaching for several weeks, with the stress building. This news wasn't helping. )

Update - May 14th, 2008

Wow - a lot has happened since Monday. Let me bring you up to date. Immediately after the posting below, I twittered my displeasure as well. I then remembered that Comcast has a Twitter account called Comcastcares. I sent an @ message to the account, linking to this post and giving them a brief summary of the issue. About an hour later, the person behind the account (Frank), replied to me requesting that I email them (he supplied an email address) explaining this issue in detail. I linked them to this blog post and re-explained the issue in the body of the email.

About an hour after this I received a call from Comcast Corporate in Philadelphia PA asking me to explain the issue. He said that he wanted to see that this is resolved and promised to call the local Comcast office here and then give me a call back Monday evening or Tuesday morning. Monday evening passes and I hear nothing.

Tuesday, I am out to lunch and I receive an email on my blackberry. It is from a different person at the local Comcast office, but someone at their local headquarters office in Manassas. The gentleman said he was informed about my problem and had cleared it up with the local office, ensuring me that my original scheduled install would happen on Saturday, May 17th, 2008. Once I arrived back at my office, I realized he had left me a voicemail as well, saying the same thing. I called him back, leaving a voicemail saying that I appreciate his call and that I was out to lunch, which is why he missed me. I replied to his email as well, just to make sure he got my message. I stepped out of my office to meet with a co-worker and upon my return, found that he had called once more. I emailed once again letting him know I had gotten his message and that I appreciate his prompt reply. I then replied to Comcastcares on twitter, letting Frank know that someone had gotten in touch with me (well, two someones actually) and that I was surprised and pleased with their response. He thanked me. I told him I would follow up, post Saturday, to let him know how it went. Thinking this was the end of it, I went home

This morning I arrived in my office to find out a THIRD person from Comcast HQ had contacted me at 5:20 pm yesterday from a 215 area code. According to google, 215 is PA so this must be their Corporate HQ once more. I just left the gentleman a voicemail assuring him that I had been contacted and that I was aware my appointment had been correctly rescheduled for Saturday.

Let me just say that Comcast is a huge ISP that has many strikes against them. Their local & regional customer service leaves something to be desired. Their shady means of monitoring and capping network traffic is anti-net neutrality and I think they leave something to be desired in that department. That being said, I am THOROUGHLY IMPRESSED by their response to my issue. Their use of social networks via Twitter to seek out customers with problem and respond to them is a breath of fresh air amongst the common means of corporate customer service. Having received 2 follow-up calls from their Corporate HQ in PA and 1 from their Regional HQ in Manassas has left me with the feeling that they really wanted to fix my issue and make sure I knew that they had taken the steps to do so. If only all of their customer service was like this. What happens to all of the users who AREN'T on Twitter like I am? No doubt, they are left at the mercy of the seemingly under trained local CS reps. It does seem, though, that people at Comcast Corporate HQ with some authority have recognized this is a problem and are taking means to fix it. I know that once companies grow, there are detrimental silos created within a company where the left hand doesn't know what the right hand is doing. Clearly the Right Hand, in this case, is trying to fix this issue via innovative means. Cheers guys - you're doing a good job.

Friday, May 16th
Let me first take you back to Friday afternoon. Steffanie and I are packing the moving trucks, the both of us having took the day off to do so. I got a call from Comcast; It was an automated message confirming my installation appointment for the following morning between 9:00 am and noon. I hung up and told Steff that it was just the automated Comcast reminder. We go back to work.

Saturday, May 17th

Steff and I get up bright and early, despite our exhausted state from the day before - having went to bed around 1:00 am the night before from a very long day of moving. Marlo was due sometime between 8:00 am and 11:00 am to deliver our new couch. I got up at 7:00 to be ready for them to get here, and sure enough, around 8:15 they called. Went downstairs and helped them get it inside the loading dock, up the service elevator and into our apartment. They left around 8:40 and I began preparing for the Comcast technician to arrive. I setup the TV on the TV stand and hooked up my TivoHD to it. I setup the TV in the bedroom (which was due to receive an analog connection - not digital) and prepared our router in the "Office" (2nd bedroom) for the modem. It took me until 9:30 to finish all of this, and I was hoping that during this time the tech wouldn't arrive yet, as I hadn't had time to get all of this done until then.

Having finished all this, we resumed unpacking the other 30-40 other boxes packed in every bit of free-space around the apartment. I kept checking the clock every little bit, and as the morning wore on, it was fast approaching noon. The time window for the tech to get there was 9-12 so I was beginning to get worried that he wouldn't show. Alas, me fears were unfounded as he arrived at around 11:45 - having called me about 20 minutes before and letting me know he was on his way.

At 11:45 he walks in with his equipment to immediately tell me that he was unable to locate any Cable Cards that morning before leaving for his service calls. He asked me if an HDTV digital converter box would be sufficient. I told him that I was pretty sure that it wouldn't be, as the TivoHD specifically says it needs CableCards. Thinking about it more, I asked him what he meant by HDTV digital converter box and he held up the very very infamous Craptastic™ Scientific Atlantic box that Comcast is notorious for pushing off on their customers, something that is very well known in the tech enthusiast world as one of the most horribly designed devices to ever exist. I then explained to him that, no, this would not work as the whole point of a Tivo was for the CableCards to be able to change the channel on their own for the Tivo so as to be able to record different programs when Steff or I weren't there. He then nods in understanding and begins to work on the other tasks.

Because our apartment complex is new, having only just opened earlier this year, no one has ever lived in our unit before. The technician took about 15 minutes walking in every room of our apartment looking for a main routing station panel for all of the cables in our walls. After he and I were unable to locate one, he guessed (and was correct) that it was located behind the main panel in the living room - the supposed location one would put their main TV. He removed the faceplate from the outlet, found the junction, and began putting ends on the coax.

Once he finished with this, he asked where I wanted to put the cable modem. I showed him the office and explained that I had my own router/network, and that he only needed to setup the router on a certain table & provision it, and I would then hook it into the router & get the network setup. He began to work on this issue, which took a while as the first 2 cable modems he had with him would not acquire a signal. He had to go down to his truck to retrieve another, coming back a bit later with it.

All of these tasks had taken about 2 hours time. During this time, and I cannot remember exactly when, I emailed Frank at Comcastcares, of whom I corresponded with earlier in the week due to the scheduling issues. I had meant to email him very shortly after I found out that the tech did not have our CableCards, but I got caught up in helping the tech out that I had forgot. It wasn't until the tech headed down to his truck that I remembered. so I drafted an email to Frank. At this point, due to not being able to setup the CableCards, I expected the tech to come back shortly with a working router, set up our internet, and then leave - probably well before I received a message back from Frank. To my surprise, this was not to be.

Within a few minutes, I had an email on my blackberry:

Is the technician still there? Can you ask him to have his supervisor call my cell?

xxx-xxx-xxxx

Frank Eliason
NCO Customer Service Manager


"Wow!" I thought. Not wanting to talk about the technician within hearing distance, I silently mouthed a word to Steffanie and handed her my blackberry so she could read the message. She saw it and smiled. I took the blackberry back from her, and turned to walk into the other room.

"Excuse me sir. I know this is going to sound unusual, but I have been in communication with one of your colleagues who works in Pennsylvania for your corporate office and he just emailed me telling me to have you have your supervisor call his cell. The Technician, stared back at me, I guess a little surprised. I handed him my blackberry so he could see the message myself...signed, Frank Eliason, NCO Customer Service Manager. The tech, without saying a word, removes his company cell & places a call to his dispatcher, kind of unsure of himself, but explaining to his supervisor what just happened and gave him the number. I smiled, thanking him once he got off the phone, and took my blackberry back. I immediately emailed Frank to let him know that I did as instructed, not really believing the local supervisor would call Frank. I get an email message back from Frank:

I spoke to him already and I have called a few other people. I will let you know. We will get one to you ASAP and I am trying for today.

Frank Eliason
NCO Customer Service Manager


Once again, I was shocked. Really - at this point I should cease to be surprised due to the way Frank had helped my earlier issue with the scheduling snafu. I had actually found a person with the authority to do something about people's problems who actually gave a care to customer's issues at Comcast. Something I didn't think was possible.

I wrote him back:

Ok Frank - I appreciate it.

Joel


The tech continues to work, and 9 minutes later, I get this:
I just got off the phone with some local people. They are working to locate one and get it to you.

I will keep you updated.

Frank Eliason
NCO Customer Service Manager


Not 2 minutes after receiving this, the tech gets a call from his dispatcher. The dispatcher says something inaudible about CableCards. The Tech responds to the dispatcher with something I didn't hear. I email Frank:
Tech is still here working on my inet connection now. Heard some correspondance between someone in local office and him talking about cablecards.

Forty minutes later, the tech finishes working on the internet. He then packs up his things and just as he is getting ready to leave, he gets another call. The dispatcher asks him where he is and if he can come to xxx location. The tech responds, saying he is only 10 minutes from there. After getting off the phone, he turns to me and tells me he is off to get the CableCard (multistream) and then will be right back. I smile and thank him, offering him some more sweet tea that I had given him earlier while he was working. He heads out the door w/ a to-go cup in hand just as I receive this:
They will be bringing one over today.

Frank Eliason
NCO Customer Service Manager


Smiling I resume unpacking things from boxes, until the technician returns. About 30 minutes later, he arrives back w/ a CableCard in hand. I offer him a seat on the couch and we go to work. We insert it into the #1 slot. He reads off the serial number, model number, and some other things from the card to someone at the local office over the phone. We wait for channels to start "coming in" or appearing in the channel test mode in the tivo menu. It takes about 15 minutes before the first one's start to appear. The tech explains to me that this will somtimes take a long time, he estimated 45 minutes to 24 hours, which I was skeptical about. The tech stood up and we shook hands. I asked him his last name so I could write Frank back & tell him his name & ID number so I could tell them how polite, and patient he was with me that day - knowing that my particular problem must be a pain in the ass.

At this point Steffanie really needed to head out to go shopping for some things we needed for the new place. We departed. At this point it was 4:03pm when I wrote Frank. The tech had spent from 11:50ish until 4:00 dealing with us.

We arrived home that night very late - around 11 pm. I checked the Tivo - no dice - the same lack of channels as before. I decided to wait a bit longer, until around 1:00 am. At this point it had been 9 hours since the CableCard was provisioned. I decided that if it was still getting in channels, as the tech said, I should have been seeing a small amount start to appear after every few hours. Given that there had been no change, in 9 hours, I spent about 20 minutes researching on the Tivo Community forums until I found this post from someone in Arlington from back in January who was having a problem very very similar to mine. I wrote Frank, letting him know that new issues had arisen. I detailed the issue, linked to the above forum post, and then proceeded to thank him profusely for all the help so far. I told him not to bother getting back to me until it was convenient for him because of the account that it was so late, and that it was the weekend.

Sunday, May 19, 2008

I received a reply the next day:

For some reason I am not able to access your information to reset the card. I will have someone do it in the morning.

XXXXX,
Can you follow up with this? Follow the trail below; we need to send a hit to the cable card.


He had handed me off to someone on his team who, apparently, had some sort of technical expertise/experience in dealing with CableCards.

Monday- Wednesday, May 20-22, 2008

I begun a new email thread with this new person over the next 2 days (Monday and Tuesday). We eventually figured out that the technician hadn't provisioned my card correctly. As of Monday he called me at work to tell me this and told me to check it that night. I did so but it still wasn't working. I emailed him back and also twittered to Frank. The next day I got another email from the new person and he told me he was handing me off to someone locally who could trouble shoot directly with me once I arrived home. I got a call a short time later from this new local person. I thanked her and we setup a time (Wednesday at 6) when they would call me back at home to help me. I arrived home that night (Tuesday) to find that I HAD ALL OF MY CHANNELS! I immediately wrote an email to Frank/new person & twittered to Frank. Apparently, on a hunch, Frank told the other person to "hit" my card with a "setup" signal again and this worked to solve my issue. I told them that the phone call on Wednesday at 6 wouldn't be necessary (although I still got it, but it wasn't a big deal as I just thanked the man and told him to have a good night). After 10 days of email/twitter/phone tag, my issues were resolved and everything worked as it should.

Comcast needs to give Frank a promotion and hire about 30 people to work for him. He gets things done. Last week about this time I was DREADING being a Comcast Customer, as I have no choice for my area. This week, I still don't think that Comcast is the ISP I would like to have (I want FIOS) but I feel a LOT better about it knowing that Frank is there, should I ever need him.

Lesson of the week? If you're a Comcast customer and are having issues getting the service you ordered/were promised, just send a little note to Frank. He's got your back.

Almost Arrested for Taking Photos at Union Station

A fellow DC Twitterer and social media guru who works for National Public Radio (NPR) by the name of Andy Carvin took a new gigapan camera to Union Station here in Washington DC yesterday to test if out. NPR is thinking of using it for a story soon and they need to test it more in order to become familiar with it. He was erroneously hassled by the rent-a-cops while attempting this.

read more | digg story

How To Fix Your Twitter

Courtesy of Mashable:

Have you, like so many other users, experienced problems with Twitter in the last couple of days? Not getting updates from all the people you’re following, but only a handful? The problem seems to be lying with Twitter cache.

Here’s a quick fix for the problem. Simply find some person you’re not already following, follow them and then unfollow them. Refresh your Twitter page and voila, your Twitter cache should now be restored, and you should be getting updates from everyone.

Thanks to engtech for the tip on Twitter. Check his blog, too, it’s cool.

Twitter Having Problems? Say It Ain't So!

It has been a good while since twitter has had serious uptime issues. The last time it happened was...well....since this. Well - Twitter is up to its old tricks again. It isn't offline per say, but it might as well be. As others have pointed out Twitter has been having serious issues since Saturday, April 19th. The service has been online but has not been displaying tweets from some users on their followers' timelines.

I first noticed this about midday Saturday as I was at PodcampDC with my beautiful girlfriend, Steffanie, watchin Andy Carvin and Jim Long, of NPR & NBC respectivley, do a presentation on the power of twitter as a news gathering and conveying mechanism. I would estimate that PodcampDC has about 100 people in attendance. I would say about 30 of us were Twitter users. At various times during the day I would make tweets about PodcampDC happenings or see Andy or Jim use Twitter theirselves but their updates wouldn't hit my feed. I has a feeling in the back of my head that something was going on but was so preoccupied with the day's events that I didn't pay much attention to it. After the event was over with, Steff and I ran some errands & preoccupied ourselves for the rest of the day. It wasn't until the next day, Sunday, that I started seeing a few posts on Techmeme about it. This type of error we're seeing reminded me of the problems Twitter had several months back when people like Merlin Mann, Leo Laporte, Robert Scoble, or Jason Calacanis couldn't add people as friends OR have people see their updates. It seems that a lot of the people having messaging problems now are people with lots of followers. It seems like a potential database issue tied to accounts with large sql fields? Just guessing.

Anywho - I'm writing about this to help get the word out to my followers. As I make this post it will go out to Twitter. Hopefully those that are blissfully unaware of Twitter issues at the moment will see the title/link & read it and help spread the message. (Hi followers :)) In the meantime Twitter, the company, has remained mostly silent on this issue preferring to take the old corporate methodology to dealing with the problem - pretending it doesn't exist until they fix it. They did acknowledge the problem at their twitter status account but you only got the message if you follow them (which I didn't - as I didn't know the account existed until i saw another blogger write about it) and I doubt a lot of people got it even if they DID follow it, as that is the problem in the first place.

Consider yourself informed.