The tubes must be clogged

[g5:~] dluke% ping geeklair.net
PING geeklair.net (129.250.34.2): 56 data bytes
64 bytes from 129.250.34.2: icmp_seq=0 ttl=51 time=36.435 ms
64 bytes from 129.250.34.2: icmp_seq=1 ttl=51 time=34.689 ms
64 bytes from 129.250.34.2: icmp_seq=2 ttl=51 time=34.465 ms
64 bytes from 129.250.34.2: icmp_seq=3 ttl=51 time=35.686 ms
64 bytes from 129.250.34.2: icmp_seq=4 ttl=51 time=35.032 ms
64 bytes from 129.250.34.2: icmp_seq=10 ttl=51 time=35.661 ms
^C
--- geeklair.net ping statistics ---
11 packets transmitted, 6 packets received, 45% packet loss
round-trip min/avg/max/stddev = 34.465/35.328/36.435/0.671 ms

Of course, when I called and let them know about the problem on Saturday, the earliest they could send someone out was this Friday.

I suspect it may have something to do with the snow+ice we recently got. Or the comcast trucks that were roaming the neighborhood (or the one that stopped outside my house with the tech. who did something to the cable up on the pole at about midnight Sunday morning).

It's CRAPcastic.

Oh well.

| 4 Comments

4 Comments

Residential internet sucks.

Good luck!

You said it:

--- geeklair.net ping statistics ---
94 packets transmitted, 3 packets received, 96% packet loss
round-trip min/avg/max/stddev = 34.924/35.160/35.479/0.234 ms

Hey bud,
How's life, the wife, etc etc?

Work continues, although there are several times a day when I wish I could ask you some questions. :)

Things are good (and the tubes are working again).

Questions are good, as is the search for the answers to those questions (I find I often learn new useful things that aren't directly related to the problem when trying to figure out some solution).

Powered by Movable Type 4.34-en
Creative Commons License
This blog is licensed under a Creative Commons License.