daft 3 #1 Posted January 28, 2014 First I want to say how much fun I have had playing on the Lotus servers and everyone involved does a great job. My problem seems to be one of ping. Over the past week or so any Lotus server with Texas in the name has been reporting a ping in the 80 - 100 range (live in Texas and enjoy playing on those servers). Usually I ping in the high teens to low twenties. At first I thought it was my internet connection but other servers that are owned by Lotus located in Chicago give me a ping of about 50. The weird thing is that yesterday(Sunday) the Texas servers seemed to be back to normal, but when I recently checked tonight they are back to showing up in the 80-100 range. And, as the night goes on, the ping seems to decrease. It's really weird. I tried taking a screenshot of the server list but the F5 button just refreshes it so if there is any other proof I need to supply I am more than happy to do that. Thanks for your time. Quote Share this post Link to post Share on other sites
fever 9,884 #2 Posted January 28, 2014 Thanks for reporting this. We'll look into it. Quote Share this post Link to post Share on other sites
Mana 3,867 #3 Posted January 28, 2014 Can you post a traceroute when this starts happening? If you don't know how this should help: http://www.wikihow.com/Traceroute Quote Share this post Link to post Share on other sites
daft 3 #4 Posted January 29, 2014 (edited) Just to be clear about the traceroute; I should put in "tracert [server IP]"? I'll do this when I get home, thanks for the responses. EDIT: Here are the tracerts from about 8:30 pm CST: 24/7 Hightower Microsoft Windows [Version 6.1.7601]Copyright © 2009 Microsoft Corporation. All rights reserved.C:\Users\Chris>tracert 208.115.218.37Tracing route to 37-218-115-208.static.reverse.lstn.net [208.115.218.37]over a maximum of 30 hops: 1 9 ms 6 ms 33 ms Chris-PC [0.0.0.0] 2 7 ms 46 ms 49 ms 173-219-229-64-link.sta.suddenlink.net [173.219.229.64] 3 56 ms 24 ms 71 ms 173-219-230-206-link.sta.suddenlink.net [173.219.230.206] 4 * 23 ms 92 ms xe-2-3-0.er2.dfw2.us.above.net [64.124.200.181] 5 23 ms 54 ms 16 ms ae2.cr2.dfw2.us.above.net [64.125.27.81] 6 86 ms 99 ms 79 ms xe-0-2-0.mpr1.dfw1.us.above.net [64.125.27.213] 7 100 ms 128 ms 113 ms 64.125.188.182.t00822-03.above.net [64.125.188.182] 8 138 ms 104 ms 121 ms te6-1.bdr2.core2.dllstx3.dallas-idc.com [208.115.192.62] 9 102 ms 116 ms 134 ms ge0-2.vl123.cr03-73.dllstx3.dallas-idc.com [208.115.251.86] 10 154 ms 101 ms 117 ms 37-218-115-208.static.reverse.lstn.net [208.115.218.37]Trace complete. Payload Race Microsoft Windows [Version 6.1.7601]Copyright © 2009 Microsoft Corporation. All rights reserved.C:\Users\Chris>tracert 208.115.218.37Tracing route to 37-218-115-208.static.reverse.lstn.net [208.115.218.37]over a maximum of 30 hops: 1 9 ms 6 ms 33 ms Chris-PC [0.0.0.0] 2 7 ms 46 ms 49 ms 173-219-229-64-link.sta.suddenlink.net [173.219.229.64] 3 56 ms 24 ms 71 ms 173-219-230-206-link.sta.suddenlink.net [173.219.230.206] 4 * 23 ms 92 ms xe-2-3-0.er2.dfw2.us.above.net [64.124.200.181] 5 23 ms 54 ms 16 ms ae2.cr2.dfw2.us.above.net [64.125.27.81] 6 86 ms 99 ms 79 ms xe-0-2-0.mpr1.dfw1.us.above.net [64.125.27.213] 7 100 ms 128 ms 113 ms 64.125.188.182.t00822-03.above.net [64.125.188.182] 8 138 ms 104 ms 121 ms te6-1.bdr2.core2.dllstx3.dallas-idc.com [208.115.192.62] 9 102 ms 116 ms 134 ms ge0-2.vl123.cr03-73.dllstx3.dallas-idc.com [208.115.251.86] 10 154 ms 101 ms 117 ms 37-218-115-208.static.reverse.lstn.net [208.115.218.37]Trace complete. 24/7 2Fort Microsoft Windows [Version 6.1.7601]Copyright © 2009 Microsoft Corporation. All rights reserved.C:\Users\Chris>tracert 208.115.218.37Tracing route to 37-218-115-208.static.reverse.lstn.net [208.115.218.37]over a maximum of 30 hops: 1 9 ms 6 ms 33 ms Chris-PC [0.0.0.0] 2 7 ms 46 ms 49 ms 173-219-229-64-link.sta.suddenlink.net [173.219.229.64] 3 56 ms 24 ms 71 ms 173-219-230-206-link.sta.suddenlink.net [173.219.230.206] 4 * 23 ms 92 ms xe-2-3-0.er2.dfw2.us.above.net [64.124.200.181] 5 23 ms 54 ms 16 ms ae2.cr2.dfw2.us.above.net [64.125.27.81] 6 86 ms 99 ms 79 ms xe-0-2-0.mpr1.dfw1.us.above.net [64.125.27.213] 7 100 ms 128 ms 113 ms 64.125.188.182.t00822-03.above.net [64.125.188.182] 8 138 ms 104 ms 121 ms te6-1.bdr2.core2.dllstx3.dallas-idc.com [208.115.192.62] 9 102 ms 116 ms 134 ms ge0-2.vl123.cr03-73.dllstx3.dallas-idc.com [208.115.251.86] 10 154 ms 101 ms 117 ms 37-218-115-208.static.reverse.lstn.net [208.115.218.37]Trace complete. 24/7 2Fort #2 Microsoft Windows [Version 6.1.7601]Copyright © 2009 Microsoft Corporation. All rights reserved.C:\Users\Chris>tracert 208.115.218.37Tracing route to 37-218-115-208.static.reverse.lstn.net [208.115.218.37]over a maximum of 30 hops: 1 9 ms 6 ms 33 ms Chris-PC [0.0.0.0] 2 7 ms 46 ms 49 ms 173-219-229-64-link.sta.suddenlink.net [173.219.229.64] 3 56 ms 24 ms 71 ms 173-219-230-206-link.sta.suddenlink.net [173.219.230.206] 4 * 23 ms 92 ms xe-2-3-0.er2.dfw2.us.above.net [64.124.200.181] 5 23 ms 54 ms 16 ms ae2.cr2.dfw2.us.above.net [64.125.27.81] 6 86 ms 99 ms 79 ms xe-0-2-0.mpr1.dfw1.us.above.net [64.125.27.213] 7 100 ms 128 ms 113 ms 64.125.188.182.t00822-03.above.net [64.125.188.182] 8 138 ms 104 ms 121 ms te6-1.bdr2.core2.dllstx3.dallas-idc.com [208.115.192.62] 9 102 ms 116 ms 134 ms ge0-2.vl123.cr03-73.dllstx3.dallas-idc.com [208.115.251.86] 10 154 ms 101 ms 117 ms 37-218-115-208.static.reverse.lstn.net [208.115.218.37]Trace complete. At around 6 pm or so my time the servers seemed to be fine and would return tracerts in the 40's when pinging the Dallas servers. I'll try to get some tomorrow in the early afternoon if needed. Edited January 29, 2014 by daft 3 Quote Share this post Link to post Share on other sites
Mana 3,867 #5 Posted February 7, 2014 A normal traceroute would be helpful to compare if you can get that. Should of asked for one initially as well. Quote Share this post Link to post Share on other sites
