Brie Gordon
I'm Brie, a 22 year-old graduate of Slippery Rock University's Computer Science department. My interests include Linux (generally and Ubuntu), networking, BSD-style operating systems including my own, BrieSD, translating English-Spanish-English for open source projects and LAMP configuration. Aside from that, I enjoy photography, making short films and soccer.
Posterous is one of my favorite new(ish) web sites!
brie@briegordon.com
Search
Tags
- comcast (3)
- advanced (2)
- custom (2)
- customization (2)
- google (2)
- ISP (2)
- linux (2)
- network (2)
- network latency (2)
- posterous (2)
- View all 92 tags
- programming (2)
- python (2)
- Apache (1)
- auth (1)
- backbone (1)
- backgrounds (1)
- backup (1)
- bash (1)
- bash script (1)
- bin (1)
- brainstorm (1)
- calculator (1)
- capacity (1)
- client (1)
- collatz (1)
- collatz conjecture (1)
- compliant (1)
- contract (1)
- core (1)
- crawl (1)
- crawler (1)
- cron (1)
- css (1)
- customer service (1)
- default (1)
- dropbox (1)
- email (1)
- favicon (1)
- fios (1)
- folder (1)
- friends (1)
- gmail (1)
- googlebot (1)
- google wave (1)
- grep (1)
- host (1)
- hosting (1)
- image (1)
- imgur (1)
- interview (1)
- invites (1)
- IP (1)
- latency (1)
- logs (1)
- lonely (1)
- mailing lists (1)
- math (1)
- mathematics (1)
- newbie (1)
- NIX (1)
- open source (1)
- packet (1)
- packet loss (1)
- php (1)
- ping (1)
- provider (1)
- python development (1)
- reality (1)
- reddit (1)
- RFC (1)
- rfc822 (1)
- robots (1)
- robots.txt (1)
- routing (1)
- rsync (1)
- sales tax (1)
- script (1)
- security (1)
- SEO (1)
- server (1)
- ssh (1)
- technician (1)
- throttling (1)
- tweet (1)
- twitter (1)
- ubuntu (1)
- unix (1)
- verizon (1)
- virtue (1)
- wave (1)
- web (1)
- windows7 (1)
November 21st, 3:50pm
0 comments
Getting Through to Comcast @ComcastCares
Today I was experiencing extreme fluctuating network latency between here and everywhere via Comcast. I started up some endless pings to monitor the situation and called up Comcast. Once I got through Shaq and Ben Stein's irritating greeting this is what I had to go through to get to a real person:
Push 1
Push 2
Push 0
Push 1
Push 2
Push 2
Push 1
Listen to a sappy message about how unusually high the call volume is and how long the wait time is
Listen to a sappy message about how unusually high the call volume is and how long the wait time is
Sit on hold briefly
Push 1
Listen to another different message about how unusually high the call volume is and how long the wait time is
Push 2 to continue the call (or Push 1 to hang up and call back later; umm, I meant to call you, not a mistake.)
Push 2
Wait a while
"Thank you for calling Comcast; I'm a real person. How can I help?"
Fortunately the tech was very helpful. He saw some high numbers (2054 ms to a server about 15 mins from me) and some extreme fluctuation. He is sending a tech out ASAP (which is Monday afternoon, lol). I asked him why the routing seemed so crazy and he acknowledged that it was weird but had no clue why. Traceroutes to a server in the same city go through Chicago, New York, Philly or Virginia before leaving Comcast's network. I don't know enough about ISP routing methodology to comment further but that seems inefficient to me.
I asked the tech why I had to push all those buttons and if there was a more direct way to get through and he said he'd leave it at no comment. Smart man.
Posted 8 months ago
Comments (0)
Leave a comment...