Mailing List Archive: Internap/XO/Savvis problems?

Internap/XO/Savvis problems? > Worst

Jul 2, 2008, 9:02 PM

Post #1 of 3 (187 views)

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
4 msec
9 * * *
10 pr1-so-6-1-0.PaloAltoPaix.savvis.net (204.70.199.113) 0 msec
pr1-so-1-1-0.PaloAltoPaix.savvis.net (204.70.199.105) 0 msec 0 msec
11 * * *
12 pr1-so-6-1-0.PaloAltoPaix.savvis.net (204.70.199.113) 0 msec 0 msec
0 msec
13 * * *
14 pr1-so-1-1-0.PaloAltoPaix.savvis.net (204.70.199.105) 0 msec 0 msec
0 msec
15 * * *
16 pr1-so-6-1-0.PaloAltoPaix.savvis.net (204.70.199.113) 0 msec
pr1-so-1-1-0.PaloAltoPaix.savvis.net (204.70.199.105) 0 msec 0 msec
17 * * *
18 pr1-so-1-1-0.PaloAltoPaix.savvis.net (204.70.199.105) 0 msec 0 msec
0 msec
19 * * *
20 pr1-so-1-1-0.PaloAltoPaix.savvis.net (204.70.199.105) 0 msec 0 msec
pr1-so-6-1-0.PaloAltoPaix.savvis.net (204.70.199.113) 0 msec
21 * * *
22 pr1-so-1-1-0.PaloAltoPaix.savvis.net (204.70.199.105) 0 msec 4 msec
pr1-so-6-1-0.PaloAltoPaix.savvis.net (204.70.199.113) 0 msec
23 * * *
24 pr1-so-1-1-0.PaloAltoPaix.savvis.net (204.70.199.105) 200 msec
pr1-so-6-1-0.PaloAltoPaix.savvis.net (204.70.199.113) 200 msec
pr1-so-1-1-0.PaloAltoPaix.savvis.net (204.70.199.105) 232 msec
25 * * *
26 pr1-so-1-1-0.PaloAltoPaix.savvis.net (204.70.199.105) 0 msec 4 msec
pr1-so-6-1-0.PaloAltoPaix.savvis.net (204.70.199.113) 0 msec
27 *
pr3-so-0-0-0.PaloAltoPaix.savvis.net (204.70.199.106) 4 msec *
28 pr1-so-6-1-0.PaloAltoPaix.savvis.net (204.70.199.113) 0 msec
pr1-so-1-1-0.PaloAltoPaix.savvis.net (204.70.199.105) 4 msec
pr1-so-6-1-0.PaloAltoPaix.savvis.net (204.70.199.113) 0 msec
29 * * *
30 pr1-so-1-1-0.PaloAltoPaix.savvis.net (204.70.199.105) 0 msec 4 msec
0 msec
route-server.savvis.net>

a. rahman isnaini r.sutan
Netsoft, PT
Jakarta Indonesia

Todd Lyons wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, Jul 03, 2008 at 10:56:21AM +1000, Matt Palmer wrote:
>
>> traceroute to 165.228.176.49 (165.228.176.49), 30 hops max, 40 byte packets
>> 1 33.254.201.74.static.ey03.engineyard.com (74.201.254.33) 0.907 ms 0.908 ms 0.928 ms
>> 2 76.254.201.74.static.ey03.engineyard.com (74.201.254.76) 0.210 ms 0.241 ms 0.273 ms
>> 3 core1.te6-1-bbnet1.nym007.pnap.net (216.52.95.24) 1.559 ms core1.te6-2-bbnet2.nym007.pnap.net (216.52.95.88) 1.338 ms core1.te6-1-bbnet1.nym007.pnap.net (216.52.95.24) 1.369 ms
>> 4 208.173.129.61 (208.173.129.61) 1.441 ms 1.525 ms 1.658 ms
>> 5 * * *
>> 6 cr2-loopback.sfo.savvis.net (206.24.210.71) 98.457 ms 94.617 ms 101.634 ms
>> 7 pr1-so-0-0-0.PaloAltoPaix.savvis.net (204.70.200.193) 89.389 ms 89.397 ms 89.478 ms
>> (constellations from here on)
>
> Same here, with a Savvis peering:
>
> Router: Ivenue bgp1
> Command: traceroute 165.228.176.49
>
> Tracing the route to ATM1-0-60.win17.Melbourne.telstra.net (165.228.176.49)
>
> 1 64.70.17.121 [AS 3561] 4 msec 4 msec 0 msec
> 2 204.70.203.90 [AS 3561] 0 msec 8 msec 0 msec
> 3 * *
> cr2-loopback.sfo.savvis.net (206.24.210.71) [AS 3561] 12 msec
> 4 pr1-so-0-0-0.PaloAltoPaix.savvis.net (204.70.200.193) [AS 3561] 12
> msec 12 msec 12 msec
> 5 * * * repeated ad nauseum
>
>> Wondering if anyone else is seeing similar problems, or if anyone knows of
>> any widespread problems with Internap/XO/Savvis that I can pass on to my
>> customer to let them know what's going on.
>
> Don't know what the issues are, but the gist from tech support is
> "Eastern Australia can't connect".
>
> 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.
> - --
> Regards... Todd
> They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety. --Benjamin Franklin
> Linux kernel 2.6.24-18-generic 3 users, load average: 0.00, 0.00, 0.00
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFIbEDuY2VBGxIDMLwRAkyJAJsHqeeMg4PmQ0NwgoZnnlum5ewgywCfdjhP
> 1Xhg7q00y5/+TG0GuWC/8C8=
> =Okzj
> -----END PGP SIGNATURE-----
> _______________________________________________
> outages mailing list
> outages at isotf.org
> https://puck.nether.net/mailman/listinfo/outages
>
>
>

Internap/XO/Savvis problems? > Worst [ In reply to ]

tlyons at ivenue

Jul 2, 2008, 9:16 PM

Post #2 of 3 (185 views)

Permalink

-----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-----

Internap/XO/Savvis problems? > Worst [ In reply to ]

risnaini at indo

Jul 2, 2008, 9:26 PM

Post #3 of 3 (181 views)

Permalink

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
>
>
>