Comcast: Why Must I Count the Ways in Which you Suck

Posted by: on Apr 15, 2007 | One Comment

A typical night lately with Comcast’s Cable Internet:

> ping comcast.net
PING comcast.net (204.127.228.15): 56 data bytes
64 bytes from 204.127.228.15: icmp_seq=2 ttl=45 time=45.688 ms
64 bytes from 204.127.228.15: icmp_seq=7 ttl=45 time=44.837 ms
64 bytes from 204.127.228.15: icmp_seq=17 ttl=45 time=45.918 ms
64 bytes from 204.127.228.15: icmp_seq=44 ttl=45 time=44.433 ms
^C
--- comcast.net ping statistics ---
79 packets transmitted, 4 packets received, 94% packet loss
round-trip min/avg/max/stddev = 44.433/45.219/45.918/0.607 ms

That’s right — 94% packet loss.

All my queries to Comcast result in lame form responses, all ripe with denials about how it’s not their issue. So fuck ’em, I’m gonna start my own personal jihad against Comcast until I can publicly shame them into admitting they’ve got issues and engage in egregious amounts of false advertising. I’m keeping a detailed XLS of outages. And I’m not even complaining about “slowdowns,” I’m talking a total lack of availability.

As Colbert would say, Comcast: you’re on notice.

1 Comment

  1. da_berzerker
    April 17, 2007

    OMG, I think I got you beat!
    ping verizon.com
    Pinging verizon.com [192.76.85.245] with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Ping statistics for 192.76.85.245:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),