Savvis outage

Mon Jun 9 17:29:40 UTC 2008

Same old story.. Savvis points finger at XO, XO points finger at 
Savvis.. Neither side actually finds out and tells me who/what fixed the 
issue, but at least its fixed.

--Justin

Justin Sharp wrote:
> Anyone know what might be up w/ XO to Savvis peering?
>
> This is a trace to netsuite.com, notice 80% packet loss at bpr2 in Los 
> Angeles
>
> Host                                Loss%   Snt   Last   Avg  Best  
> Wrst StDev
> 1. 10.0.0.1      0.0%    21    0.3   0.4   0.3   1.6   0.3
> 2. ip65-44-114-97.z114-44-65.custom  0.0%    21    1.2   1.2   1.1   
> 1.8   0.2
> 3. ip65-46-48-29.z48-46-65.customer  0.0%    20    2.8   3.1   2.7   
> 5.6   0.6
> 4. p6-0-0d0.mar2.saltlake-ut.us.xo. 10.0%    20    3.0   7.0   3.0  
> 68.5  15.4
> 5. p3-1-0d0.rar2.la-ca.us.xo.net     0.0%    20   90.2  31.3  16.8 
> 114.1  32.1
> 6. p0-0-0d0.rar1.la-ca.us.xo.net     5.0%    20   17.9  18.8  17.7  
> 26.2   2.6
> 7. te-4-1-0.rar3.la-ca.us.xo.net     0.0%    20   19.5  20.0  18.6  
> 27.9   1.9
> 8. 207.88.12.154.ptr.us.xo.net       0.0%    20   16.9  17.4  16.8  
> 22.4   1.3
> 9. bpr2-so-6-1-0.losangeles.savvis. 57.9%    20   85.9  85.9  84.9  
> 90.4   1.8
> 10. cr1-gig-0-7-5-3.LosAngeles.savvi 78.9%    20  1040. 349.8 105.6 
> 1040. 460.6
>    cr2-gig-0-7-5-3.losangeles.savvis.net
> 11. cr2-pos-0-0-5-0.sanfrancisco.sav 84.2%    20  133.0 406.4  94.7 
> 991.5 507.1
>    cr1-loopback.sfo.savvis.net
> 12. er1-te-1-0-1.sanjose3equinix.sav 68.4%    20   94.2  94.8  94.2  
> 95.7   0.5
>    er1-te-2-0-1.SanJose3Equinix.savvis.net
> 13. hr1-te-2-0-0.santaclarasc5.savvi 78.9%    20   94.3  95.2  94.3  
> 95.8   0.7
> 14. hr1-te-2-0-0.santaclarasc8.savvi 70.0%    20   94.3  94.7  94.0  
> 95.7   0.6
> 15. 66.35.192.2                      75.0%    20   96.2  95.4  94.5  
> 96.2   0.8
> 16. 167.216.129.12                   78.9%    20   95.0  95.4  94.4  
> 96.9   1.1
>
>
> Thanks,
> --Justin
>