Pro-Tips on Diagnosing Lag and Rubberbanding
Background:
For those unfamiliar with latency (or lag), this is how quickly your computer transfers files to a distant end. In our case, we're looking at how your computer interacts with Cryptic's servers.
Latency is measured in milliseconds (ms). This is directly measuring how long it takes to send/receive data. You want any tests below to have lower values. Think of it like waiting in line at the bank; you don't want to be there all day.
Bandwidth is measured in kilobites per second (KB/sec). You want these values to be high. Think of this as how much stuff you can mail at once.
Your computer is connected through many other computers to reach Cryptic's servers. Think of it like the Postal Service. Packets of information (just like mail) need to pass through several places (like your local and regional sorting centers). Sometimes a problem can be with a user, sometimes it can be with Cryptic. Before either party blames each other, sometimes the problem is one of these connections between Cryptic's Servers and you.
What the Devs Need from You to Fix the Issue:
- Tracert test results (see below)
- Nettest results (see below)
- Your Internet Service Provider (ISP) or who your purchase internet access from.
Test Summary:
We'll run two tests. The first is a called
tracert and measures how quickly various connections between Cryptic and you respond. The second is called
nettest and gauges how much data can be passed at once on various ports.
Test 1: tracert
- For Windows, hit the start button
- Where it says Search All Files and Programs, type CMD and press ENTER
- The first result should be cmd.exe
- Right-click on cmd.exe and select Run as Administrator
- A black, command-prompt window should appear
- From here type the following command:
- tracert patchserver.crypticstudios.com
Good Results:
- Values lower than 180 are ideal for playing MMOs (and anything under 100 is outstanding). Higher values usually cause lag and rubber-banding in-game. Report any values above 180ms. Right-click in the Command Prompt Window and select all. Save as a text file (txt).
.
Test 2: nettest
You'll see several columns. The ones we're focusing on have KB/sec to the right of a number value.
Good results:
- Column 1: ~300-500 KB/sec
- Column 2: ~20kb/sec
- Column 3: ~300- 500kb/sec
Report the Port Number and which columns are
below the average ranges.
Nettest can be copied by:
- right clicking on the window title bar
- select Edit then Mark
- highlight the text by holding the left mouse button
- hit enter to copy to the windows clipboard.
- paste into notepad or word and save as TXT
(thanks PegasusMD for nettest copying instructions)
Final Words:
When posting a problem, be sure to include the tracert text file and also the nettest results.
Let us know with which ISP you are trying to contact us from where.
The combination of this information can help if we are trying to find out if a problem may hail from a specific local area or provider.
Sporadic ISP Issue Fix:
The below is
not guaranteed to work but might help solve some issues with your ISP. Using the Post Office analogy, this is like getting a new address and having mail delivered there.
Renew IP Address
- Go to Start Menu
- Search for cmd
- Right-click and "Run as Administrator"
- Type the following: ipconfig /release
- Hit Enter
- Now, type ipconfig /renew
- Hit Enter
Comments
select edit then mark.
highlight the text by left mouse hold drag then hit enter to copy to the windows clipboard.
you can then paste the information .
Thanks.
These questions come up a lot and I figured I'd write up a thread on how to diagnose lag/rubberbanding issues. I've credit you for the nettest copying steps.
Hopefully, I can just link to this post whenever anyone asks about server issues.
Providing this information can help--though everyone wishes problems were fixed overnight. However, some things are beyond Cryptic's control.
For example, dstahl mentioned that the recent connection issues had to do with a particular hub trying to connect to Cryptic's servers in MA--something they contacted the ISP over. This explains why only some users experienced the issues and why Cryptic's servers had no problem communicating with most players.
Live long and prosper.
Let us know with which ISP you are trying to contact us from where.
The combination of this information can help if we are trying to find out if a problem may hail from a specific local area or provider.
Updated original post to reflect this.
But... I have no idea what this means....???
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Rac>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 = <1 ms <1 ms <1 ms ***.***.***.**
2 = 30 ms 19 ms 29 ms cable-mac1.schnny52-ar4003.nyroc.rr.com [72.226.112.1]
3 = 12 ms 12 ms 12 ms gig3-1-3.albynywav-rtr02.nyroc.rr.com [24.29.34.145]
4 = 17 ms 18 ms 38 ms ge-7-1-0.syrcnycsr-rtr03.nyroc.rr.com [24.29.39.25]
5 = 21 ms 21 ms 22 ms ae10-0.rochnyei-rtr000.nyroc.rr.com [24.24.21.221]
6 = 34 ms 34 ms 37 ms 107.14.19.28
7 = 35 ms 34 ms 34 ms ae-0-0.pr0.chi10.tbone.rr.com [66.109.6.153]
8 = 34 ms 53 ms 34 ms te0-2-0-7.ccr22.ord03.atlas.cogentco.com [154.54.11.145]
9 = 37 ms 34 ms 34 ms te0-3-0-0.ccr21.ord01.atlas.cogentco.com [154.54.5.25]
10 = 58 ms 60 ms 60 ms te0-1-0-1.ccr22.bos01.atlas.cogentco.com [154.54.6.21]
11 = 59 ms 60 ms 57 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.130]
12 = 65 ms 53 ms 53 ms 38.111.40.114
13 = 53 ms 50 ms 50 ms 208.95.185.41
Trace complete.
I get some of it... cause I'm using Time Warner Roadrunner out of the Capital District of NY...
schnny = Schenectady... alby = Albany... syrc = Syracuse... roch = Rochester.. these are all cities in NY.
Do the numbers really mean that I'm running 50 to 60-ish ms ???
Is that possible... is it even good???
(I wasn't sure if I should post my starting number... the stars are my doing)
...2nd test...
contacting nettest server..
Local IP: **.***.***.***
Ping: 50.9 msec
Port: 80: 893 KB/sec 31 KB/sec 943 KB/sec 500
Port: 80: 834 KB/sec 28 KB/sec 880 KB/sec 500
Port: 443: 877 KB/sec 31 KB/sec 926 KB/sec 500
Port: 443: 872 KB/sec 29 KB/sec 920 KB/sec 500
Port: 7255: 739 KB/sec 24 KB/sec 779 KB/sec 500
Port: 7255: 851 KB/sec 28 KB/sec 896 KB/sec 500
Port: 7003: 960 KB/sec 32 KB/sec 1013 KB/sec 500
Port: 7003: 853 KB/sec 30 KB/sec 901 KB/sec 500
Port: 7202: 847 KB/sec 30 KB/sec 894 KB/sec 500
Port: 7202: 916 KB/sec 33 KB/sec 968 KB/sec 500
Port: 7499: 846 KB/sec 29 KB/sec 893 KB/sec 500
Port: 7499: 823 KB/sec 26 KB/sec 867 KB/sec 500
Port: 80: 823 KB/sec 27 KB/sec 868 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
Is this any good???
(...again, the stars are my doing.)
I´ve tried this setting, but it is getting worse with that. With the eu-proxy I´m stuck in the Charakter retrieving screen and get disconnected from the login server. Without (no proxy set) I can log in and play, but after each loading screen (and there are a lot in this game) I´m getting the "server is not responding"-message (maybe for 10 seconds). After that I can go on, but sometimes the game freezes (I can move, but without my toon and I cannot interact); I can´t even log out, only quit the game entirely.
1. I do not have Win 7 (it´s Vista)
2. My Anti Virus scanner is blocking the web-address because it believes it is a dangerous url
3. My provider is Telekom Austria
Do you have that new feature of Thiers OFF?
The one that Delay Loads the game as we play...
If it is on.., Perhaps that is whats is causing the problem...?
I was noticing a bit of a problem when I first started paying after the start of Season 4...
Shutting that Off, cleared it up.
You can run tracert from Vista too--just do a search for cmd.exe and make sure to run it as an administrator.
Also, if the address for the server is blocked, I think there's an explanation for rubberbanding.
Your results are outstanding: low latency (meaning things don't take long to go back and forth between you and Cryptic) and you have great bandwidth (more than enough for the game).
That said, it can be confusing reading tracerts because some regions have monopolies over DSL or cable lines but sell access to it to smaller ISPs. You can have one ISP but connect through another ISP's switches.
In short, pay attention to the numerical values instead of the name. The devs can do a WHOIS look-up for an IP address to contact the ISP and ask them what's wrong.
What does "Thier" mean?
And which feature is it that delays the loads?
In the options of the laucher if have nothing checked, only Language is set to "english" and proxy to "none".
First, just because you (and several others you might know) are having lag, does not mean almost everyone has it. You can't possibly have surveyed enough people to get anywhere close to determining what "almost everyone" is experiencing.
Second, if there's an issue with a tier 1 or 2 Internet provider somewhere, it could be affecting SOME paths to the server but not others. A traceroute helps spot such issues.
Third, I have had no problems for the past several days, so be careful when you assume it's affecting everyone.
Fourth, what if the problem isn't the server(s) but the network connection that Cryptic is using? Again, traceroutes and such things can help identify this.
But hey, if you think yelling will be more helpful than providing info, knock yourself out.
What doe these numbers show?
It means something interesting is going on. Most likely a reverse traceroute done by Cryptic to your IP will point to the cause. What's interesting to me is between hops 11 and 12:
There's a significant jump in latency from one boston hop to the other within the same ISP. What this does not tell you is if the problem is actually on the return path back to you (causing this bogus result). Cryptic will need to do a reverse traceroute and verify that it is that point which is causing the problem or if a return path is taking a different route back to you. (This, in networking terms, is called asymmetric routing. The path from A to Z is one way, but Z to A goes a completely different route. Only comparing the two will yield viable data.)
This coming from someone who is a dual specialty (and 10 years of ISP experience) of Network Engineering and Systems Administration.
Here are the results for my tracert:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Windows\system32>tracert patchserver.crypticstudios.com
Routenverfolgung zu patchserver.crypticstudios.com [208.95.185.41]
Well...
First off... the most obvious thing it means...,
...is at 3 in the morning, I can't spell worth a damn... (Their)
What I meant was...
After clicking on the OPTIONS tab...
Put an 'X' in the box labeled... Disable On-Demand Paching
This forces the game to Pre-Load ALL of any new patch They put out, instead of letting it patch piecemeal while you are playing the game.
I found the game lag a lot more noticeable, when this feature was allowed to run.
I´ve downloaded all patch-data a few days ago. Even if i´m disabling On-Demand Patching now, it isn´t getting better.
As you can see, most users have 10-14 hops between them and Cryptic and some of these have proven problematic. Although a large part of Cryptic's userbase might get routed through these connections, it doesn't mean it's Cryptic's server.
That said, it can always be Cryptic's Servers but one must realize that there statistically more connections that are beyond either Cryptic or the user's control.
I've run the usual tracert and nettest for today and here are my results coming from Virginmedia (Telewest) in the UK.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 17 ms 25 ms 7 ms 10.89.168.1
3 9 ms 8 ms 11 ms nmal-geam-1a-ge94.network.virginmedia.net [81.96
.225.45]
4 11 ms 30 ms 30 ms croy-core-1a-pc111.network.virginmedia.net [62.3
0.242.37]
5 8 ms 43 ms 30 ms brnt-bb-1a-ae2-0.network.virginmedia.net [195.18
2.178.82]
6 43 ms 10 ms 35 ms brnt-bb-1b-ae0-0.network.virginmedia.net [213.10
5.174.226]
7 9 ms 9 ms 20 ms brnt-tmr-1-ae5-0.network.virginmedia.net [213.10
5.159.50]
8 24 ms 23 ms 28 ms telc-ic-1-as0-0.network.virginmedia.net [62.253.
185.74]
9 9 ms 10 ms 41 ms te1-3.ccr01.lon04.atlas.cogentco.com [130.117.15
.69]
10 10 ms 21 ms 11 ms te2-8.mpd01.lon01.atlas.cogentco.com [130.117.3.
189]
11 11 ms 9 ms 41 ms te3-1.mpd02.lon01.atlas.cogentco.com [130.117.2.
26]
12 113 ms 83 ms 82 ms te0-2-0-4.mpd22.lon13.atlas.cogentco.com [154.54
.57.165]
13 94 ms 84 ms 83 ms te0-3-0-4.ccr22.bos01.atlas.cogentco.com [154.54
.5.122]
14 90 ms 112 ms 104 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
15 97 ms 125 ms 89 ms 38.111.40.114
16 82 ms 95 ms 84 ms 208.95.185.41
Trace complete.
contacting nettest server..
Local IP: 82.44.22.123
Ping: 100.2 msec
Port: 80: 261 KB/sec 8 KB/sec 275 KB/sec 500
Port: 80: 259 KB/sec 8 KB/sec 273 KB/sec 500
Port: 443: 261 KB/sec 8 KB/sec 275 KB/sec 500
Port: 443: 263 KB/sec 9 KB/sec 278 KB/sec 500
Port: 7255: 171 KB/sec 5 KB/sec 181 KB/sec 500
Port: 7255: 262 KB/sec 7 KB/sec 276 KB/sec 500
Port: 7003: 262 KB/sec 7 KB/sec 276 KB/sec 500
Port: 7003: 262 KB/sec 8 KB/sec 276 KB/sec 500
Port: 7202: 261 KB/sec 9 KB/sec 274 KB/sec 500
Port: 7202: 261 KB/sec 7 KB/sec 275 KB/sec 500
Port: 7499: 256 KB/sec 7 KB/sec 270 KB/sec 500
Port: 7499: 262 KB/sec 9 KB/sec 277 KB/sec 500
Port: 80: 265 KB/sec 9 KB/sec 279 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
I would like to know if it is possible to have the address for the proxy servers to run a traceroute, this would help to see if the connection goes via the servers another route completely.
Ah, of course!
Anyway, the results of the traceroute to the proxy server as follows.
Tracing route to eu2.proxy.crypticstudios.com [79.125.26.110]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 17 ms 29 ms 10.89.168.1
3 11 ms 45 ms 10 ms nmal-geam-1b-ge133.network.virginmedia.net [81.9
6.225.181]
4 16 ms 41 ms 12 ms croy-core-1b-pc112.network.virginmedia.net [62.3
0.242.53]
5 8 ms 29 ms 27 ms popl-bb-1b-ae2-0.network.virginmedia.net [195.18
2.178.86]
6 78 ms 14 ms 36 ms manc-bb-1a-as3-0.network.virginmedia.net [62.252
.192.157]
7 16 ms 26 ms 15 ms manc-bb-1b-ae0-0.network.virginmedia.net [62.253
.187.178]
8 22 ms 18 ms 17 ms dubl-bb-1b-as0-0.network.virginmedia.net [213.10
5.159.125]
9 36 ms 27 ms 51 ms dubl-bb-1b-ge-300-0.network.virginmedia.net [62.
253.187.90]
10 * * * Request timed out.
11 31 ms 19 ms 39 ms 178.236.0.130
12 19 ms 19 ms 60 ms 178.236.0.125
13 52 ms 31 ms 27 ms ec2-79-125-0-132.eu-west-1.compute.amazonaws.com
[79.125.0.132]
14 20 ms 19 ms 22 ms ec2-79-125-0-229.eu-west-1.compute.amazonaws.com
[79.125.0.229]
15 19 ms 19 ms 19 ms ec2-79-125-0-139.eu-west-1.compute.amazonaws.com
[79.125.0.139]
16 28 ms 19 ms 29 ms ec2-79-125-0-79.eu-west-1.compute.amazonaws.com
[79.125.0.79]
17 18 ms 19 ms 58 ms ec2-79-125-26-110.eu-west-1.compute.amazonaws.co
m [79.125.26.110]
Trace complete.
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 * * * Request timed out.
2 18 ms 25 ms 19 ms nexthop.nsw.iinet.net.au [203.215.17.248]
3 19 ms 17 ms 19 ms te1-1.syd-ult-bdr2.iinet.net.au [203.215.16.24]
4 17 ms 17 ms 17 ms te1-2.syd-ult-bdr1.iinet.net.au [203.215.20.146]
5 19 ms 20 ms 16 ms xe-1-1-0-0.syd-ult-core1.iinet.net.au [203.215.2
0.30]
6 16 ms 17 ms 61 ms ae0.syd-mas-core1.iinet.net.au [203.215.20.111]
7 210 ms 211 ms 210 ms 34023.sydp06.cu.reach.com [134.159.160.57]
8 167 ms 165 ms 165 ms i-0-0-2-0.paix-core01.bx.reach.com [202.84.140.1
06]
9 169 ms 167 ms 169 ms g3_0-pax04.net.reach.com [202.84.251.38]
10 * 190 ms * te4-5.mpd01.sjc04.atlas.cogentco.com [154.54.11.
157]
11 190 ms 189 ms 192 ms te0-0-0-6.mpd21.sfo01.atlas.cogentco.com [154.54
.2.165]
12 189 ms 188 ms 190 ms te0-1-0-0.ccr21.sfo01.atlas.cogentco.com [154.54
.30.49]
13 238 ms 240 ms 237 ms te0-4-0-1.ccr21.mci01.atlas.cogentco.com [154.54
.45.61]
14 251 ms 250 ms 280 ms te0-0-0-3.ccr21.ord01.atlas.cogentco.com [154.54
.2.218]
15 269 ms 268 ms 266 ms te0-0-0-5.ccr22.bos01.atlas.cogentco.com [154.54
.42.254]
16 264 ms 263 ms 263 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.25
4]
17 268 ms 269 ms 284 ms 38.111.40.114
18 244 ms 244 ms 243 ms patchserver.crypticstudios.com [208.95.185.41]
Trace complete.
contacting nettest server..
Local IP: 114.198.32.98
Ping: 231.4 msec
Port: 80: 114 KB/sec 5 KB/sec 121 KB/sec 500
Port: 80: 108 KB/sec 5 KB/sec 114 KB/sec 500
Port: 443: 29 KB/sec 1 KB/sec 31 KB/sec 500
Port: 443: 110 KB/sec 5 KB/sec 127 KB/sec 500
Port: 7255: 52 KB/sec 3 KB/sec 55 KB/sec 500
Port: 7255: 57 KB/sec 3 KB/sec 60 KB/sec 500
Port: 7003: 122 KB/sec 7 KB/sec 129 KB/sec 500
Port: 7003: 120 KB/sec 5 KB/sec 127 KB/sec 500
Port: 7202: 54 KB/sec 3 KB/sec 62 KB/sec 500
Port: 7202: 62 KB/sec 3 KB/sec 66 KB/sec 500
Port: 7499: 120 KB/sec 5 KB/sec 127 KB/sec 500
Port: 7499: 118 KB/sec 5 KB/sec 126 KB/sec 500
Port: 80: 115 KB/sec 8 KB/sec 133 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\HP_Administrator>tracert patchserver.crypticstudios.co
m
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 6 ms 6 ms 74-131-48-1.dhcp.insightbb.com [74.131.48.1]
3 8 ms 6 ms 7 ms 74-131-0-193.dhcp.insightbb.com [74.131.0.193]
4 7 ms 6 ms 7 ms 74.128.9.245
5 19 ms 18 ms 17 ms sl-crs2-akr-.sprintlink.net [144.228.22.21]
6 31 ms 30 ms 30 ms sl-crs2-spr-0-4-5-0.sprintlink.net [144.232.18.1
09]
7 33 ms 33 ms 32 ms sl-st20-bos-0-0-0.sprintlink.net [144.232.8.48]
8 32 ms 32 ms 42 ms sl-internap-190725-0.sprintlink.net [144.223.45.
50]
9 33 ms 34 ms 31 ms border11.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
04]
10 * 40 ms 35 ms cryptic-3.border11.bsn.pnap.net [216.52.61.78]
11 32 ms 32 ms 31 ms 208.95.185.41
Trace complete.
contacting nettest server..
Local IP: 74.131.50.156
Ping: 65.2 msec
Port: 80: 24 KB/sec 1 KB/sec 26 KB/sec 500
Port: 80: 57 KB/sec 2 KB/sec 60 KB/sec 500
Port: 443: 56 KB/sec 2 KB/sec 59 KB/sec 500
Port: 443: 111 KB/sec 6 KB/sec 118 KB/sec 500
Port: 7255: 100 KB/sec 4 KB/sec 108 KB/sec 500
Port: 7255: 43 KB/sec 2 KB/sec 47 KB/sec 500
Port: 7003: 229 KB/sec 8 KB/sec 244 KB/sec 500
Port: 7003: 27 KB/sec 1 KB/sec 29 KB/sec 500
Port: 7202: 58 KB/sec 3 KB/sec 62 KB/sec 500
Port: 7202: 13 KB/sec 1 KB/sec 20 KB/sec 500
Port: 7499: 107 KB/sec 4 KB/sec 114 KB/sec 500
Port: 7499: 85 KB/sec 6 KB/sec 104 KB/sec 500
Port: 80: 53 KB/sec 3 KB/sec 58 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
hit return to exit
tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 <1 ms 5 ms <1 ms home [10.0.0.138]
2 25 ms 25 ms 24 ms loop0.lns20.hba1.internode.on.net [203.33.255.118]
3 25 ms 29 ms 27 ms gi0-2-3.cor1.hba1.internode.on.net [203.33.255.9]
4 41 ms 41 ms 38 ms gi0-2-805.bdr1.mel6.internode.on.net [203.33.255.169]
5 213 ms 219 ms 209 ms te2-0-0.bdr1.cbr1.internode.on.net [150.101.160.173]
6 214 ms 208 ms 216 ms te6-0-0.bdr1.syd4.internode.on.net [150.101.160.170]
7 215 ms 227 ms 203 ms te0-0-0.bdr1.syd6.internode.on.net [150.101.197.1]
8 217 ms 239 ms 222 ms pos0-0-0.bdr1.lax1.internode.on.net [203.16.213.186]
9 214 ms 237 ms 222 ms sl-st30-la-.sprintlink.net [144.223.30.1]
10 220 ms 211 ms 209 ms sl-st31-la-0-4-2-0.sprintlink.net [144.232.5.102]
11 231 ms 224 ms 215 ms sl-crs2-ria-0-2-0-0.sprintlink.net [144.232.24.66]
12 239 ms 237 ms 235 ms sl-crs2-fw-0-13-3-0.sprintlink.net [144.232.19.197]
13 268 ms 267 ms 264 ms sl-crs2-nsh-0-9-2-0.sprintlink.net [144.232.25.123]
14 294 ms 302 ms 292 ms sl-crs2-dc-0-12-3-0.sprintlink.net [144.232.19.201]
15 284 ms 276 ms 282 ms sl-crs2-rly-0-0-3-0.sprintlink.net [144.232.8.165]
16 288 ms 288 ms 348 ms sl-crs2-pen-0-5-0-0.sprintlink.net [144.232.19.3]
17 279 ms 282 ms 279 ms sl-crs2-nyc-0-14-0-0.sprintlink.net [144.232.20.94]
18 295 ms 295 ms 297 ms sl-crs2-spr-0-0-2-0.sprintlink.net [144.232.25.23]
19 291 ms 282 ms 290 ms sl-st20-bos-0-0-0.sprintlink.net [144.232.8.48]
20 299 ms 303 ms 297 ms sl-internap-190725-0.sprintlink.net [144.223.45.50]
21 302 ms 300 ms 295 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
22 289 ms 285 ms 285 ms cryptic-3.border11.bsn.pnap.net [216.52.61.78]
23 289 ms 295 ms 289 ms 208.95.185.41
Trace complete.
---
tracert eu2.proxy.crypticstudios.com
Tracing route to eu2.proxy.crypticstudios.com [79.125.26.110]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home [10.0.0.138]
2 25 ms 25 ms 56 ms loop0.lns20.hba1.internode.on.net [203.33.255.118]
3 36 ms 34 ms 31 ms gi0-2-3.cor1.hba1.internode.on.net [203.33.255.9]
4 42 ms 43 ms 47 ms gi0-2-805.bdr1.mel6.internode.on.net [203.33.255.169]
5 204 ms 203 ms 205 ms te2-0-0.bdr1.cbr1.internode.on.net [150.101.160.173]
6 215 ms 207 ms 204 ms te6-0-0.bdr1.syd4.internode.on.net [150.101.160.170]
7 196 ms 196 ms 196 ms te0-0-0.bdr1.syd6.internode.on.net [150.101.197.1]
8 200 ms 198 ms 199 ms pos5-0.bdr1.lax1.internode.on.net [203.16.213.158]
9 198 ms 196 ms 197 ms xe-7-0-3.edge2.LosAngeles9.Level3.net [4.53.230.45]
10 217 ms 206 ms 206 ms vlan90.csw4.LosAngeles1.Level3.net [4.69.144.254]
11 209 ms 204 ms 205 ms ae-93-93.ebr3.LosAngeles1.Level3.net [4.69.137.45]
12 276 ms 283 ms 281 ms ae-4-4.ebr4.Washington1.Level3.net [4.69.132.82]
13 297 ms 272 ms 281 ms ae-84-84.csw3.Washington1.Level3.net [4.69.134.186]
14 275 ms 270 ms 272 ms ae-82-82.ebr2.Washington1.Level3.net [4.69.134.153]
15 341 ms 347 ms 343 ms ae-43-43.ebr2.Paris1.Level3.net [4.69.137.57]
16 364 ms 369 ms 367 ms ae-6-6.car1.Dublin3.Level3.net [4.69.148.53]
17 377 ms 380 ms 379 ms ae-7-7.car2.Dublin1.Level3.net [4.69.148.58]
18 358 ms 360 ms 368 ms 213.242.106.150
19 367 ms 366 ms 368 ms 178.236.0.112
20 359 ms 357 ms 357 ms 178.236.0.58
21 372 ms 376 ms 369 ms ec2-79-125-0-4.eu-west-1.compute.amazonaws.com [79.125.0.4]
22 363 ms 364 ms 366 ms ec2-79-125-0-79.eu-west-1.compute.amazonaws.com [79.125.0.79]
23 367 ms 365 ms 371 ms ec2-79-125-26-110.eu-west-1.compute.amazonaws.com [79.125.26.110]
Trace complete.
---
contacting nettest server..
Local IP: 118.208.203.TRIBBLE
Ping: 300.1 msec
Port: 80: 144 KB/sec 6 KB/sec 152 KB/sec 500
Port: 80: 40 KB/sec 2 KB/sec 43 KB/sec 500
Port: 443: 279 KB/sec 7 KB/sec 286 KB/sec 500
Port: 443: 124 KB/sec 6 KB/sec 131 KB/sec 500
Port: 7255: 39 KB/sec 2 KB/sec 42 KB/sec 500
Port: 7255: 66 KB/sec 3 KB/sec 71 KB/sec 500
Port: 7003: 218 KB/sec 18 KB/sec 238 KB/sec 500
Port: 7003: 143 KB/sec 6 KB/sec 152 KB/sec 500
Port: 7202: 82 KB/sec 5 KB/sec 89 KB/sec 500
Port: 7202: 224 KB/sec 9 KB/sec 238 KB/sec 500
Port: 7499: 184 KB/sec 11 KB/sec 197 KB/sec 500
Port: 7499: 38 KB/sec 2 KB/sec 41 KB/sec 500
Port: 80: 201 KB/sec 8 KB/sec 212 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 0 KB/sec
fact is the server lag is so high that disconection happens in 2-3 minute basis and no one in the staff can fix that