Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > Softlayer.com packet loss
Softlayer.com packet loss
| Posted by 123finder.com, 05-06-2010, 04:33 PM |
I just started having a hard time accessing my server and also softlayer.com (hence cannot use ticket) from multiple locations. Anyone else?
[root@d2 ~]# ping softlayer.com
PING softlayer.com (66.228.118.53) 56(84) bytes of data.
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=1 ttl=245 time=141 ms
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=3 ttl=245 time=141 ms
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=4 ttl=245 time=141 ms
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=5 ttl=245 time=141 ms
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=9 ttl=245 time=142 ms
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=10 ttl=245 time=141 ms
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=11 ttl=245 time=141 ms
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=12 ttl=245 time=141 ms
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=13 ttl=245 time=141 ms
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=15 ttl=245 time=141 ms
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=16 ttl=245 time=141 ms
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=18 ttl=245 time=142 ms
64 bytes from www.softlayer.com (66.228.118.53): icmp_seq=19 ttl=245 time=141 ms
--- softlayer.com ping statistics ---
20 packets transmitted, 13 received, 35% packet loss, time 19011ms
rtt min/avg/max/mdev = 141.249/141.651/142.139/0.494 ms
============================================================
macbook hells x$ traceroute softlayer.com
traceroute to softlayer.com (66.228.118.53), 64 hops max, 52 byte packets
....
5 pos-1-8-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.91.229) 14.892 ms 13.316 ms 16.454 ms
6 pos-0-7-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.86.206) 21.152 ms 25.086 ms 23.947 ms
7 pos-0-13-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.146) 56.449 ms 58.301 ms 79.754 ms
8 pos-0-0-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.86.90) 59.323 ms 56.866 ms 57.293 ms
9 softlayer-cr01.dallas.tx.ibone.comcast.net (75.149.228.34) 63.666 ms 63.494 ms 65.101 ms
10 * * po4.bbr01.sr01.dal01.networklayer.com (173.192.18.193) 445.154 ms
11 173.192.18.179-static.reverse.networklayer.com (173.192.18.179) 113.426 ms 112.794 ms 112.568 ms
12 po1.slr01.dal01.networklayer.com (66.228.118.138) 62.446 ms 64.567 ms 63.718 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
============================================================
[root@d2 ~]# traceroute softlayer.com
traceroute to softlayer.com (66.228.118.53), 30 hops max, 40 byte packets
...
3 po42.dsr02.dllstx3.theplanet.com (70.87.253.77) 0.630 ms 0.542 ms 0.567 ms
4 2d.ff.5746.static.theplanet.com (70.87.255.45) 0.349 ms 0.298 ms 0.543 ms
5 * * *
6 po3.bbr01.sr01.dal01.networklayer.com (173.192.18.191) 140.940 ms po4.bbr01.sr01.dal01.networklayer.com (173.192.18.193) 141.082 ms 141.031 ms
7 173.192.18.181-static.reverse.networklayer.com (173.192.18.181) 141.125 ms 141.067 ms 141.143 ms
8 po2.slr01.dal01.softlayer.com (66.228.118.142) 91.335 ms 91.338 ms 91.204 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * * |
| Posted by sirius, 05-06-2010, 04:34 PM |
Seeing the same thing here - seems they have something funky going on in the network. Tracing from a server in Washington, DC takes me all over the united states.
From Washington, DC....
PHP Code:
2 fcr01.wdc01.softlayer.com (208.43.96.165) 0.372 ms 0.391 ms 0.420 ms
3 po101.cer02.wdc01.networklayer.com (208.43.118.137) 0.387 ms 0.355 ms 0.357 ms
4 po7.bbr01.eq01.wdc01.networklayer.com (173.192.18.196) 0.788 ms 0.825 ms 0.762 ms
5 po3.bbr02.eq01.chi01.networklayer.com (173.192.18.155) 18.897 ms 18.929 ms 19.012 ms
6 po4.bbr02.cf01.den01.networklayer.com (173.192.18.131) 43.986 ms 44.005 ms 44.075 ms
7 po4.bbr01.wb01.sea01.networklayer.com (173.192.18.144) 95.359 ms * *
8 * * po3.bbr01.sr01.sea01.networklayer.com (173.192.18.199) 95.518 ms
9 po1.cer02.sr01.sea01.networklayer.com (173.192.18.185) 95.591 ms * po1.cer02.sr01.sea01.networklayer.com (173.192.18.185) 95.503 ms
10 tuk-edge-09.inet.qwest.net (65.112.24.21) 99.708 ms * *
11 * sjp-brdr-01.inet.qwest.net (205.171.233.30) 124.261 ms 124.320 ms
12 63.146.26.202 (63.146.26.202) 105.173 ms * 63.146.26.202 (63.146.26.202) 105.198 ms
13 * * 0.so-0-1-0.XT2.SCL2.ALTER.NET (152.63.57.102) 108.111 ms
14 0.ge-4-1-0.SJC01-BB-RTR1.verizon-gni.net (152.63.1.178) 108.630 ms 108.700 ms *
15 so-3-0-0-0.LAX01-BB-RTR2.verizon-gni.net (130.81.19.115) 112.667 ms 113.839 ms 113.813 ms
16 so-4-0-0-0.DFW01-BB-RTR2.verizon-gni.net (130.81.17.27) 116.566 ms * *
17 * ge-5-3-0-0.TPA01-BB-RTR2.verizon-gni.net (130.81.17.47) 129.814 ms *
|
| Posted by MIRhosting.com, 05-06-2010, 04:37 PM |
|
The same here, losses about 50%. Last 2 days also detect issues with concurrent connections. |
| Posted by sirius, 05-06-2010, 04:39 PM |
|
Just talked to the NOC - they are having "a network abnormality" and are working to fix it. |
| Posted by nkaiser, 05-06-2010, 04:40 PM |
|
We have about 40 servers down because of this. If anyone hears an update please advise. NOC didn't have any etas yet. |
| Posted by 123finder.com, 05-06-2010, 04:43 PM |
|
Just called the support toll-free number and they confirmed a networking issue. I hope they get it fixed quickly. |
| Posted by nyjimbo, 05-06-2010, 04:44 PM |
Same problems here. If anybody can fix it, Softlayer can. I will just kick back and wait.  |
| Posted by raidz, 05-06-2010, 04:46 PM |
|
I am totally disappointed in them. They don't even have failover setup for their website??!? Their Seattle location seems to be going strong, we have multiple servers at all of their locations, we failed-over to our Seattle Webserver. Weeeeeeee |
| Posted by chiratsu, 05-06-2010, 04:46 PM |
This has been happening way too often, We are seriously considering a host change.
Totally unacceptable! |
| Posted by raidz, 05-06-2010, 04:48 PM |
|
Looks like they just updated their control panel, why would they do this during the day?!? |
| Posted by nonparity, 05-06-2010, 04:48 PM |
|
It looks like the network has gotten a little better but is still pretty bad. |
Add to Favourites 
Print this Article
Also Read
Shared Hosting
Shared Hosting
