Anyone else seeing latency through SJC2.ALTER.NET?

Mon Oct 9 22:12:47 UTC 2006

I've spoke to MCI, which is our hand off... They say things are okay  
now (as of about 15 minutes ago). Problem was caused by "high  
utilization", unknown what device.

Are you still seeing latency? I've got that circuit shut down so I'm  
blind.

-Wil

On Oct 9, 2006, at 2:25 PM, Jonathan Claybaugh wrote:

> Wil,
>
> My traffic enters Alternet in LAX (but not SJC).  I've been seeing  
> a great deal of latency and packet loss through LAX1<->SEA1 for the  
> last few hours.
>
> The problem seemed to spike about 20 minutes ago.
>
> Cheers
> -Jonathan
>
> via Alternet.William Schultz wrote:
>
>>
>>  5  0.so-1-0-0.GW1.SJC2.ALTER.NET (157.130.203.17)  2.173 ms    
>> 2.419  ms   2.228 ms
>> 6  127.ATM4-0.XR1.SJC2.ALTER.NET (152.63.56.202)  287.247 ms     
>> 287.482 ms   287.548 ms
>> 7  0.so-1-0-0.XL1.SJC2.ALTER.NET (152.63.56.137)  287.316 ms     
>> 287.743 ms   288.016 ms
>>
>>  5  0.so-5-1-0.GW6.SJC1.ALTER.NET (152.63.54.169)  1.998 ms    
>> 1.918  ms 0.so-1-0-0.GW1.SJC2.ALTER.NET (157.130.203.17)  1.606 ms
>> 6  0.so-0-3-0.XL1.SJC1.ALTER.NET (152.63.56.174)  289.389 ms     
>> 293.047 ms 127.ATM4-0.XR2.SJC2.ALTER.NET (152.63.56.206)  294.331 ms
>> 7  0.so-1-0-0.XL2.SJC2.ALTER.NET (152.63.56.141)  294.862 ms   
>> 0.so-7-0-0.XL1.SCL2.ALTER.NET (152.63.54.134)  3.410 ms   
>> 0.so-1-0-0.XL2.SJC2.ALTER.NET (152.63.56.141)  295.108 ms
>>
>>  4  63.66.208.1 (63.66.208.1)  2.200 ms   2.143 ms   1.299 ms
>> 5  0.so-1-1-0.GW1.SJC2.ALTER.NET (157.130.203.13)  274.324 ms     
>> 273.923 ms   273.909 ms
>> 6  127.ATM5-0.XR2.SJC2.ALTER.NET (152.63.56.198)  1.973 ms    
>> 2.476  ms   2.431 ms
>> 7  0.so-1-0-0.XL2.SJC2.ALTER.NET (152.63.56.141)  274.125 ms     
>> 274.027 ms   274.190 ms
>>
>> -Wil
>
>
>