Discussion
Tinterweb said:
root@Mook:~> ping xsession.com
PING xsession.com (80.71.2.156): 56 data bytes
64 bytes from 80.71.2.156: icmp_seq=0 ttl=125 time=1088.324 ms
64 bytes from 80.71.2.156: icmp_seq=1 ttl=125 time=941.187 ms
64 bytes from 80.71.2.156: icmp_seq=2 ttl=125 time=974.183 ms
64 bytes from 80.71.2.156: icmp_seq=3 ttl=125 time=972.963 ms
64 bytes from 80.71.2.156: icmp_seq=4 ttl=125 time=866.099 ms
64 bytes from 80.71.2.156: icmp_seq=5 ttl=125 time=1073.010 ms
64 bytes from 80.71.2.156: icmp_seq=6 ttl=125 time=1006.215 ms
64 bytes from 80.71.2.156: icmp_seq=7 ttl=125 time=1004.924 ms
64 bytes from 80.71.2.156: icmp_seq=8 ttl=125 time=924.703 ms
64 bytes from 80.71.2.156: icmp_seq=9 ttl=125 time=986.694 ms
64 bytes from 80.71.2.156: icmp_seq=11 ttl=125 time=117.436 ms
^C
--- xsession.com ping statistics ---
12 packets transmitted, 11 packets received, 8% packet loss
round-trip min/avg/max/stddev = 117.436/905.067/1088.324/256.127 ms
root@Mook:~> traceroute xsession.com
traceroute to xsession.com (80.71.2.156), 64 hops max, 40 byte packets
1 gigfx10-0.ipcolo1.London1.Level3.Serverstream.net (80.253.108.1) 0.593 ms 0.459 ms 0.517 ms
2 ae-15-51.car5.London1.Level3.net (4.68.116.19) 0.792 ms 0.727 ms 0.789 ms
3 ge1.br-thn-01.caladan.net.uk (195.50.112.50) 1.422 ms 0.956 ms 1.248 ms
4 * 80.71.2.156 (80.71.2.156) 830.396 ms *
Ouch
at those ping times. Looks like they're either under attack or have saturated their line naturally, either way not fun for their clients ;(
J
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff



. Was the lady helpful?
just as well you dont offer hosting from it