Traceroute & times of lag

[GM-Pandora]

My conversation with the host is going nowhere, all they do is ask me for more information each reply they send me, then say there is no problem, yet the lag is clearly there and there are other servers hosted at the same facility that get it too (I've told the host this but it didn't seem to matter to them).

So, if anyone volunteers to help, I need either or both of the following:

- As soon as you start experiencing a lag spike, type @time in game, once the spike is over it will display the time, please copy here the date and time in xx:xx:xx format.

- Open a cmd prompt, type the following without quotation "tracert heroserver.bounceme.net" but don't press enter yet. As soon you start experiencing a lag spike switch to that window and press enter. Copy Paste the info here.

Before adding the info here you could ask on @main if others felt it, to ensure that it's a global lag and not something just on your end.

I've already been doing this myself but I'm not always online and Marivel has been helping with times, but the more info we have the better.

Thanks for your help, please keep this thread factual, comments and such can go in the other existing threads about the lag. Keep in mind we are aware the lag is most inconvenient and believe us we want it solved just as much as you all do, we already checked everything that could possibly be wrong on our end, and the server is fine, it has plenty of memory and cpu resource, the computer could easily handle 10x more.

[proto]

Friday, May 28th 23:59:05

Whole party lagged so I hope this helps

[tan313008]

Saturday, May 29 2010 00:34:48

[Général_Argos]

Doing a traceroute lenght longer than the duration of a lagspike.

[Namine]

Saturday, May 29 2010 07:47:00

[Whispers]

19:56:42 just now.??

And again at 20:07:11

Another at 20:09:46

[Namine]

Saturday, May 29 2010 19:56:41

*note: on main, Pirateman said he has no lag when I tried to verify if it's global.




*note2: by the time I finished the trace, there's 2 more complaints of lagging on main*

[Whispers]

23:17:53

[Namine]

May 30 1:27:30

[Revenant]

Tracing route to heroserver.bounceme.net [67.205.124.138]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 23 ms * 23 ms b-ras2.prp.dublin.eircom.net [159.134.155.6]
3 24 ms 23 ms 23 ms 86.43.246.1
4 31 ms 23 ms 23 ms tenge-3-1-1.core2.prp.core.eircom.net [86.43.252
.69]
5 23 ms 22 ms 23 ms tenge-2-2-1.pe2.crz.crz-crz.eircom.net [86.43.25
2.142]
6 93 ms 93 ms 105 ms 86.43.244.41
7 94 ms 93 ms 93 ms 83.71.113.110
8 94 ms 94 ms 94 ms xe-1-0-0.paix.nyc-telx-dis-1.peer1.net [198.32.1
18.146]
9 * * * Request timed out.
10 106 ms 110 ms 105 ms te6-3.cl-core05.peer1.mtl.iweb.com [216.187.90.1
34]
11 105 ms 106 ms 105 ms te9-7.cl-vcore05.mtl.iweb.com [67.205.127.206]
12 105 ms 106 ms 105 ms te8-2.v0688.cl-vcore08.mtl.iweb.com [67.205.127.
190]
13 107 ms 106 ms 105 ms ip-67-205-124-138.static.privatedns.com [67.205.
124.138]

Trace complete.

Pinging heroserver.bounceme.net [67.205.124.138] with 32 bytes of data:
Reply from 67.205.124.138: bytes=32 time=106ms TTL=50
Reply from 67.205.124.138: bytes=32 time=106ms TTL=50
Reply from 67.205.124.138: bytes=32 time=106ms TTL=50
Reply from 67.205.124.138: bytes=32 time=107ms TTL=50

Ping statistics for 67.205.124.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 106ms, Maximum = 107ms, Average = 106ms

10:50 AM GMT