Judging by traceroutes to livejournal.com, which is hosted at Internap,
there are problems with Sprintlink after that hop to Toyko. I'm now hitting
Verio instead.
([EMAIL PROTECTED]/pts/1:~) traceroute shell.wgops.com
traceroute to shell.wgops.com (66.92.192.108), 30 hops max, 38 byte packets
1
According to speakeasy system status page (my DSL provider at the other end
there)... It seems though it's rather more widespread than what this
notice makes it out to be.
09/26/03 02:18:07 PM Seattle POP Packet Loss
Region : Seattle
E.T.A. : (none)
Services Affected : Some broadband services
I'm seeing this on my cable connection too.
([EMAIL PROTECTED]/pts/1:~) traceroute shell.wgops.com
traceroute to shell.wgops.com (66.92.192.108), 30 hops max, 38 byte packets
1 10.65.80.1 (10.65.80.1) 7.106 ms 11.420 ms 40.080 ms
2 srp4-0.chrlncsa-rtr4.carolina.rr.com (24.93.66.110) 6.847
- Original Message -
From: "Michael Loftis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 01, 2003 2:47 PM
Subject: Massive sprintlink problems?
>
> Anyone else seeing this:: (1sec+ delay to my idle DSL line across
> sprintlink..
Anyone else seeing this:: (1sec+ delay to my idle DSL line across
sprintlink...)
traceroute is definitely taking an asymmetric path, since pings and tcp
connections are consistent 1sec plus RTT starting somewhere in seattle or
tacoma.tok? tokyo? Anyway before I start rattling this around
