Any UK users had problems with high latency using Sky as ISP? Just getting our 6 member band on the go, five of us are up & running very well with a variety of Windows PCs & Macs and internet providers, including one using Sky. Together we get 20 - 25 msec total latency. Our 6th member uses an iMac & has Sky as ISP, her audio system is great but internet latency is horrible, wanders a lot but overall latency sits between 90 and 120 msec. has anybody found this and fixed it? Unfortunately she uses her Mac for home working and I can't risk digging into the router admin setup to ensure port forwarding etc. as that risks her not being able to do her job. Sorry it's vague, kind of hoping for a user who's found a very simple fix. If not it's probably a change of broadband provider that we'll go for.
5ms latency is almost magically fast for a WAN link! but yes, DSL is not the best transport for this purpose.
This could be useful:
ping your router - this will measure your LAN latency (I'm on Wifi now, BTW)
mine: --- 192.168.1.250 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 2.166/2.207/2.242/0.025 ms
ping your ISP gateway
mine: --- 73.11.51.1 ping statistics ---
9 packets transmitted, 9 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 18.794/23.561/34.716/4.579 ms
ping a remote server
--- jamkazam.com ping statistics ---
16 packets transmitted, 16 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 69.639/71.565/78.726/2.194 ms
more fun - trace your route: (tracert for Windows)
traceroute to 45.79.61.39 (45.79.61.39), 64 hops max, 52 byte packets
1 192.168.1.250 (192.168.1.250) 2.792 ms 1.476 ms 1.403 ms
2 96.120.60.105 (96.120.60.105) 16.904 ms 10.060 ms 36.291 ms
3 ae-255-1227-rur101.salem.or.bverton.comcast.net (162.151.125.45) 12.957 ms 14.711 ms 11.931 ms
4 ae-2-rur02.salem.or.bverton.comcast.net (68.85.146.170) 12.232 ms 85.302 ms 11.177 ms
5 96.108.80.73 (96.108.80.73) 22.551 ms 65.125 ms 49.995 ms
6 be-33490-cr01.seattle.wa.ibone.comcast.net (68.86.92.217) 92.748 ms 34.693 ms 33.677 ms
7 be-10846-pe01.seattle.wa.ibone.comcast.net (68.86.86.90) 19.035 ms 20.382 ms 18.691 ms
8 be3014.ccr21.sea02.atlas.cogentco.com (154.54.11.229) 18.642 ms 20.616 ms 19.284 ms
9 be2085.ccr21.slc01.atlas.cogentco.com (154.54.2.198) 49.747 ms
154.54.89.102 (154.54.89.102) 69.606 ms 55.683 ms
10 be3037.ccr21.den01.atlas.cogentco.com (154.54.41.146) 46.928 ms 71.336 ms 64.157 ms
11 be3035.ccr21.mci01.atlas.cogentco.com (154.54.5.90) 62.118 ms
be3036.ccr22.mci01.atlas.cogentco.com (154.54.31.90) 63.252 ms 66.939 ms
12 be2433.ccr32.dfw01.atlas.cogentco.com (154.54.3.213) 70.876 ms
be2432.ccr31.dfw01.atlas.cogentco.com (154.54.3.133) 72.110 ms
be2433.ccr32.dfw01.atlas.cogentco.com (154.54.3.213) 72.102 ms
13 be2763.ccr41.dfw03.atlas.cogentco.com (154.54.28.74) 71.448 ms 97.110 ms 69.902 ms
14 * * *
15 45.79.12.3 (45.79.12.3) 94.768 ms
45.79.12.1 (45.79.12.1) 74.075 ms
45.79.12.3 (45.79.12.3) 76.207 ms
16 nb-45-79-61-39.dallas.nodebalancer.linode.com (45.79.61.39) 75.566 ms 127.246 ms 114.102 ms
look at that - my LAN has less than 3ms latency but getting from here to Jamkazam.com is about 120 ms!
These ping times will vary at different times of the day, and the routes also change, so your latency will also change.
Of course the point here is that it matters what kind of internet service you use, and there are some bumpy lanes out there....
Thanks guys. Both replies very helpful, blandis your research was quite correct, turns out she's on Sky's Essential ADSL service not their Superfast Fibre product. I got her to do a broadband speed check, download 10.7Mb/s, upload only 1.8, ping 25ms, no wonder she's having trouble! Product change is on the way asap, then we'll see if we can hold a 6 member session. First proper 5 man session takes place this evening, we've had one short session together with just a few issues getting everybody to hear each other but once we got going it was fantastic. The issues were that sometimes one of us would drop out, other times one of us couldn't alter the gain of another member in their personal mix, seemed to fix each by leaving & re-entering the session. Really hoping the app keeps getting better, developers are doing lots of updates it seems. If there are any developers seeing this well done you guys!!
Glad to hear you're persevering, Mark. One bit of good news: the JamKazam sessions are "peer-to-peer" with no central server connection required. You only connect to JamKazam in Texas for login and prep/setup; once your session starts it is just amongst your players locally.
