Andy Insano

My net access keeps going through phases where I get 65-85% packet loss, it’ll do it for a big chunk of time. Being almost connected to the internet is driving me up the wall. I can browse to pages after a few reloads, during the little spurts of packets that get through, then it will die completely for 20 seconds, then be back for 10. Conversations on any form of instant messaging system go horribly awry instantly, I stop receiving messages, they stop receiving messages, everything happens sporadically.

There has got to be some kind of interference on my line, like somebody’s phone line is hooked up to this or something. They laid a new wire but I don’t really have many tools to check this stuff out. Grrr. Will need to research once I can get net access that appears vaguely stable. Kill kill kill.

PING an9.org (64.62.161.97): 56 data bytes
64 bytes from 64.62.161.97: icmp_seq=0 ttl=58 time=107.179 ms
64 bytes from 64.62.161.97: icmp_seq=1 ttl=58 time=28.385 ms
64 bytes from 64.62.161.97: icmp_seq=2 ttl=58 time=13.81 ms
64 bytes from 64.62.161.97: icmp_seq=3 ttl=58 time=13.702 ms
64 bytes from 64.62.161.97: icmp_seq=4 ttl=58 time=13.579 ms
64 bytes from 64.62.161.97: icmp_seq=5 ttl=58 time=37.773 ms
64 bytes from 64.62.161.97: icmp_seq=6 ttl=58 time=13.601 ms
64 bytes from 64.62.161.97: icmp_seq=7 ttl=58 time=62.906 ms
64 bytes from 64.62.161.97: icmp_seq=8 ttl=58 time=13.416 ms
64 bytes from 64.62.161.97: icmp_seq=9 ttl=58 time=17.475 ms
64 bytes from 64.62.161.97: icmp_seq=28 ttl=58 time=21.223 ms
64 bytes from 64.62.161.97: icmp_seq=29 ttl=58 time=13.972 ms
64 bytes from 64.62.161.97: icmp_seq=30 ttl=58 time=13.449 ms
64 bytes from 64.62.161.97: icmp_seq=31 ttl=58 time=13.855 ms
64 bytes from 64.62.161.97: icmp_seq=32 ttl=58 time=14.073 ms
64 bytes from 64.62.161.97: icmp_seq=33 ttl=58 time=14.013 ms
64 bytes from 64.62.161.97: icmp_seq=34 ttl=58 time=13.184 ms
64 bytes from 64.62.161.97: icmp_seq=35 ttl=58 time=35.621 ms
64 bytes from 64.62.161.97: icmp_seq=36 ttl=58 time=75.736 ms
64 bytes from 64.62.161.97: icmp_seq=37 ttl=58 time=12.536 ms
64 bytes from 64.62.161.97: icmp_seq=60 ttl=58 time=12.79 ms
64 bytes from 64.62.161.97: icmp_seq=61 ttl=58 time=14.603 ms
64 bytes from 64.62.161.97: icmp_seq=62 ttl=58 time=83.986 ms
64 bytes from 64.62.161.97: icmp_seq=63 ttl=58 time=32.197 ms
64 bytes from 64.62.161.97: icmp_seq=64 ttl=58 time=63.014 ms
64 bytes from 64.62.161.97: icmp_seq=65 ttl=58 time=14.894 ms
64 bytes from 64.62.161.97: icmp_seq=66 ttl=58 time=13.061 ms
64 bytes from 64.62.161.97: icmp_seq=67 ttl=58 time=13.754 ms
64 bytes from 64.62.161.97: icmp_seq=68 ttl=58 time=13.452 ms
64 bytes from 64.62.161.97: icmp_seq=69 ttl=58 time=13.734 ms
64 bytes from 64.62.161.97: icmp_seq=70 ttl=58 time=53.987 ms
64 bytes from 64.62.161.97: icmp_seq=94 ttl=58 time=13.22 ms
64 bytes from 64.62.161.97: icmp_seq=96 ttl=58 time=12.925 ms
^C
--- an9.org ping statistics ---
97 packets transmitted, 33 packets received, 65% packet loss  

7 thoughts on “Andy Insano

  1. whip out the knife, and stab that packet loss right in the damn face!

  2. I’m sorry, but WHY does anyone care that your internet connection is broken?

    I can’t even believe I’m reading this. This is why blogs are retarded. Please, get a life.

  3. actually, his, ya know, friends might care. “Hey, why isn’t andy responding? Oh! Ok, his internet is broken!”

    And we won’t even begin to go into the second comment… bah to you!

  4. prolly… but really… sometimes you just wanna look at someone and say “Does… does it hurt to be retarded?”

Leave a Reply

Your email address will not be published. Required fields are marked *