[outages] Internap/XO/Savvis problems? > Worst

[a. rahman isnaini r.sutan]

I'm still having problem with one of my client AS24523 while tracing via 
Savvis.
The problem between Savvis & Reach am I right ?

rgs
a. rahman isnaini r.sutan

Todd Lyons wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Thu, Jul 03, 2008 at 11:02:48AM +0700, a. rahman isnaini r.sutan wrote:
> 
>> route-server.savvis.net>traceroute 203.84.155.21
>>
>> Type escape sequence to abort.
>> Tracing the route to peer21-noc-gw.orion.net.id (203.84.155.21)
>>
>>   1 bhr2-pos-11-1.santaclarasc8.savvis.net (209.1.169.178) 0 msec 0 msec 
>> 0 msec
>>   2 204.70.200.25 4 msec 4 msec 0 msec
>>   3 pr1-ge-4-0-0.SanJoseEquinix.savvis.net (204.70.200.221) 0 msec 0  
>> msec 0 msec
>>   4  *  *  *
>>   5  *  *  *
>>   6 pr1-so-6-1-0.PaloAltoPaix.savvis.net (204.70.199.113) 0 msec 4 msec
>>     pr1-so-1-1-0.PaloAltoPaix.savvis.net (204.70.199.105) 0 msec
>>   7  *  *  *
>>   8 pr1-so-6-1-0.PaloAltoPaix.savvis.net (204.70.199.113) 0 msec 0 msec  
>>> Savvis case number is 1336683, no ETA yet, but engineers are on it.
>>> Savvis confirmed that it is a connectivity issue to Asia/Pac region.
> 
> About 20 minutes after I posted the above info, it was back up.  From
> the outside, it looks like they routed around it:
> 
> Router: Ivenue bgp1
> Command: traceroute 58.175.246.90
> 
> 
> Tracing the route to 58.175.246.90
> 
>   1 64.70.17.121 [AS 3561] 0 msec 4 msec 0 msec
>   2 204.70.203.90 [AS 3561] 0 msec 0 msec 4 msec
>   3 ber1-tenge-2-1.losangeles.savvis.net (204.70.193.106) [AS 3561] 0
> msec 0 msec 4 msec
>   4 208.174.194.58 [AS 3561] 0 msec 0 msec 0 msec
>   5 i-6-1.wil-core03.net.reach.com (202.84.251.229) [AS 4637] 0 msec
>     i-1-2.wil-core03.net.reach.com (202.84.251.213) [AS 4637] 0 msec
>     i-2-0.wil-core03.net.reach.com (202.84.251.193) [AS 4637] 4 msec
>   6 i-4-1.sydp-core01.net.reach.com (202.84.140.30) [AS 4637] 148 msec
> 148 msec 148 msec
>   7 10GigabitEthernet5-0.pad-gw1.Sydney.telstra.net (203.50.13.25) [AS
> 1221] 152 msec 152 msec 148 msec
>   8 Bundle-Ether3.chw-core2.Sydney.telstra.net (203.50.6.26) [AS 1221]
> 152 msec 148 msec 152 msec
>   9 Bundle-Ether4.ken-core4.Sydney.telstra.net (203.50.6.41) [AS 1221]
> 148 msec 148 msec 152 msec
>  10 Bundle-POS1.win-core1.Melbourne.telstra.net (203.50.6.22) [AS 1221]
> 164 msec 164 msec 164 msec
>  11 TenGigabitEthernet7-2.win16.Melbourne.telstra.net (203.50.80.156)
> [AS 1221] 164 msec 160 msec 164 msec
>  12 telstr460.lnk.telstra.net (165.228.108.98) [AS 1221] 164 msec 164
> msec 164 msec
>  13 CPE-61-9-133-5.vic.bigpond.net.au (61.9.133.5) [AS 1221] 164 msec
> 164 msec 164 msec
>  14 58.160.7.253 [AS 1221] 164 msec 160 msec 160 msec
>  15 58.160.4.9 [AS 1221] 168 msec 172 msec 164 msec
> <snip>
> - -- 
> Regards...		Todd
> I've visited conferences where the wireless LAN was deemed "secure" by
> the organisation because they had outlawed sniffers.    --Neils Bakker
> Linux kernel 2.6.24-18-generic   3 users,  load average: 0.04, 0.03, 0.00
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> 
> iD8DBQFIbFKXY2VBGxIDMLwRAu1UAJ9QcKdhhYwvX4mktmLcYEAFYhauvwCfSRMk
> 7V+m/2QbMUaBmgjHpwY4ZWI=
> =Mpfw
> -----END PGP SIGNATURE-----
> _______________________________________________
> outages mailing list
> outages at isotf.org
> https://puck.nether.net/mailman/listinfo/outages
> 
> 
>