Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > limestonenetworks - Packet loss
limestonenetworks - Packet loss
| Posted by jackpx, 03-31-2010, 09:30 PM |
I have 3 servers with LimeStoneNetworks and I monitor the servers with Pingdom
I am receiving many emails (PingdomAlert) of packet loss:
Tracert of Pingdom
-----------------------------------------
traceroute to 216.245.208.1XX (216.245.208.1XX), 30 hops max, 40 byte packets
1 83.140.19.1 (83.140.19.1) 0.236 ms 0.348 ms 0.400 ms
2 83.140.54.17.cust.port80.se (83.140.54.17) 0.639 ms 0.689 ms 0.735 ms
3 v1306-r73.svv-cr1-r72.cph.dk.p80.net (82.96.1.26) 9.085 ms 9.159 ms 9.199 ms
4 64.213.76.165 (64.213.76.165) 13.287 ms 13.327 ms 13.508 ms
5 xe2-0-0-10G.asr1.DAL1.gblx.net (67.17.66.246) 139.920 ms 139.399 ms 139.490 ms
6 WBS-CONNECT.Te7-2.asr1.DAL1.gblx.net (64.210.21.50) 139.920 ms 139.407 ms 139.477 ms
7 po3.bdr1.core2.dllstx2.dallas-idc.com (74.63.203.14) 139.551 ms po3.bdr1.core1.dllstx2.dallas-idc.com (74.63.203.10) 139.933 ms po3.bdr1.core2.dllstx2.dallas-idc.com (74.63.203.14) 139.992 ms
8 ge0-2.vl212.cr01-39.dllstx2.dallas-idc.com (74.63.209.30) 140.151 ms 141.953 ms ge0-1.vl63.cr01-39.dllstx2.dallas-idc.com (74.63.209.26) 139.685 ms
9 * * *
10 * * *
-----------------------------------------traceroute to 216.245.208.1XX (216.245.208.1XX), 30 hops max, 40 byte packets
1 64.120.14.33.ubiquityservers.com (64.120.14.33) 0.413 ms 0.607 ms 0.845 ms
2 ip65-47-180-113.z180-47-65.customer.algx.net (65.47.180.113) 0.940 ms 1.007 ms 1.055 ms
3 ge11-1-4d0.mcr2.chicago-il.us.xo.net (207.88.172.13) 1.179 ms 1.239 ms 1.291 ms
4 ae1d0.mcr1.chicago-il.us.xo.net (216.156.1.81) 19.043 ms 19.125 ms 19.162 ms
5 216.156.0.161.ptr.us.xo.net (216.156.0.161) 2.475 ms 2.561 ms 2.617 ms
6 207.88.13.5.ptr.us.xo.net (207.88.13.5) 55.740 ms 54.292 ms 53.332 ms
7 206.111.2.138.ptr.us.xo.net (206.111.2.138) 1.574 ms 1.654 ms 1.723 ms
8 WBS-CONNECT.Te7-2.asr1.DAL1.gblx.net (64.210.21.50) 26.416 ms 26.612 ms 26.663 ms
9 po3.bdr1.core2.dllstx2.dallas-idc.com (74.63.203.14) 26.521 ms po3.bdr1.core1.dllstx2.dallas-idc.com (74.63.203.10) 33.403 ms 33.462 ms
10 ge0-1.vl63.cr01-39.dllstx2.dallas-idc.com (74.63.209.26) 33.710 ms 33.955 ms 34.456 ms
11 * * *
12 * * *
13 * * *
-----------------------------------------
traceroute to 216.245.208.1XX (216.245.208.1XX), 30 hops max, 40 byte packets
1 hosted.by.pacificrack.com (204.152.200.41) 1.286 ms 1.362 ms 1.428 ms
2 66.63.163.237 (66.63.163.237) 1.167 ms 1.309 ms 1.372 ms
3 208.84.48.249 (208.84.48.249) 2.269 ms 2.299 ms 2.334 ms
4 te-8-2-464.car4.LosAngeles1.Level3.net (4.71.128.169) 1.399 ms 2.137 ms 2.190 ms
5 ae-82-80.ebr2.LosAngeles1.Level3.net (4.69.144.179) 6.104 ms 6.156 ms 6.199 ms
6 ae-3-3.ebr3.Dallas1.Level3.net (4.69.132.78) 33.069 ms 45.859 ms 45.353 ms
7 ae-3-80.edge4.Dallas3.Level3.net (4.69.145.141) 34.294 ms ae-1-60.edge4.Dallas3.Level3.net (4.69.145.13) 34.340 ms ae-3-80.edge4.Dallas3.Level3.net (4.69.145.141) 34.420 ms
8 LIMESTONE-N.edge4.Dallas3.Level3.net (4.59.32.6) 34.171 ms 33.160 ms 33.940 ms
9 po4.bdr2.core2.dllstx2.dallas-idc.com (74.63.203.22) 33.849 ms po4.bdr2.core1.dllstx2.dallas-idc.com (74.63.203.18) 35.638 ms po4.bdr2.core2.dllstx2.dallas-idc.com (74.63.203.22) 34.632 ms
10 ge0-2.vl212.cr01-39.dllstx2.dallas-idc.com (74.63.209.30) 37.499 ms ge0-1.vl63.cr01-39.dllstx2.dallas-idc.com (74.63.209.26) 35.731 ms 35.673 ms
11 * * *
12 * * *
-----------------------------------------
traceroute to 216.245.208.1XX (216.245.208.1XX), 30 hops max, 40 byte packets
1 server52123.uk2net.com (83.170.113.124) 0.357 ms 0.438 ms 0.531 ms
2 inx.uk2.net (83.170.70.137) 0.442 ms 0.512 ms 0.558 ms
3 TenGigabitEthernet4-3.ar8.LON3.gblx.net (208.178.244.181) 0.510 ms 0.527 ms 0.563 ms
4 WBS-CONNECT.Te7-2.asr1.DAL1.gblx.net (64.210.21.50) 120.619 ms 120.665 ms 120.727 ms
5 po3.bdr1.core2.dllstx2.dallas-idc.com (74.63.203.14) 120.696 ms 120.777 ms 120.869 ms
6 ge0-2.vl212.cr01-39.dllstx2.dallas-idc.com (74.63.209.30) 120.990 ms ge0-1.vl63.cr01-39.dllstx2.dallas-idc.com (74.63.209.26) 122.381 ms 122.668 ms
7 * * *
8 * * *
9 * * *
-----------------------------------------
traceroute to 216.245.208.1XX (216.245.208.1XX), 30 hops max, 40 byte packets
1 82.103.143.2 (82.103.143.2) 0.189 ms 0.296 ms 0.325 ms
2 kbn-horsk-i1-link.telia.net (213.248.91.25) 1.593 ms 1.746 ms 1.845 ms
3 kbn-b1-link.telia.net (80.91.249.193) 0.701 ms 0.742 ms 0.770 ms
4 kbn-bb2-link.telia.net (80.91.253.205) 0.947 ms kbn-bb1-link.telia.net (80.91.252.22) 22.173 ms kbn-bb2-link.telia.net (80.91.247.112) 0.892 ms
5 nyk-bb2-link.telia.net (80.91.249.29) 86.355 ms nyk-bb2-link.telia.net (80.91.247.119) 91.886 ms nyk-bb2-link.telia.net (80.91.249.29) 86.407 ms
6 chi-bb1-link.telia.net (80.91.248.196) 106.818 ms 112.267 ms 106.859 ms
7 dls-bb1-link.telia.net (80.91.248.209) 139.010 ms dls-bb1-link.telia.net (213.248.80.149) 131.632 ms dls-bb1-link.telia.net (80.91.248.209) 138.255 ms
8 limestone-ic-135964-dls-bb1.c.telia.net (213.248.74.222) 131.402 ms 131.345 ms 125.879 ms
9 po3.bdr1.core2.dllstx2.dallas-idc.com (74.63.203.14) 125.546 ms * *
10 * * *
11 * * *
12 * * *
Somebody has the same problem?? |
| Posted by Ryan G - Limestone, 03-31-2010, 10:42 PM |
jackpx,
Please open a ticket with us in Rockware so we can get to the bottom of this for you. If you can include these traceroutes along with timestamps for them, it will help our techs troubleshoot the problem. |
| Posted by yyCC, 03-31-2010, 11:34 PM |
Me too, just notice my server is not responding to http/ping etc.
Right before I click submit on the ticket I see some ping coming back but still it timeout half of the time. I'll wait and see. |
| Posted by XFactorServers, 04-01-2010, 02:17 AM |
|
Their site is dead for me. |
| Posted by Ryan G - Limestone, 04-01-2010, 02:32 AM |
|
Our website was down for a few minutes for un-related maintenance. |
| Posted by stablehost, 04-01-2010, 05:14 PM |
|
All of our limestone servers were offline last night, I still have an open ticket and they are currently 'looking into it' |
Add to Favourites 
Print this Article
Also Read
Shared Hosting
Shared Hosting
