![]() ![]() ![]() |
|
Me and the other half have been having trouble with World of Warcraft off the American Servers, been some significant lag in the past few days which is very unusual. Even at the worst of the cable congestion it would never lag out.
seems to be back to normal for me now
After you said that I was hoping something may have been fixed as our internet/tv has constantly been DCing tonight. But after checking on overwatch and a couple other things I still get this unstable connection.
Time to spend hours on the phone tomorrow :/
(if the video didnt work https://www.youtube.com/watch?v=yTaHP7fk5QI)
In my case, I can get a better download speed from using a free wifi in Wellington as compared to my cable at home.
Home Donwload rate to SFDC is between 120kbps to 240 kbps.
Free CBDfree wifi I get almost 1.6Mbps to same site. Difference is cbdfree uses Spark GlobalGateway.
traceroute na27-chi.force.com using Free CBD Wifi
traceroute to na27-chi.force.com (136.146.208.104), 64 hops max, 52 byte packets
1 10.102.64.1 (10.102.64.1) 9.655 ms 1.557 ms 2.024 ms
2 eth2.wn014-rt3.citylink.co.nz (198.48.2.254) 1.851 ms 1.623 ms 1.587 ms
3 g0-2-4061.wn014-rt1.corp.clnz.net (202.8.44.236) 1.923 ms 2.277 ms 1.888 ms
4 124.157.65.14 (124.157.65.14) 9.596 ms 9.779 ms 10.187 ms
5 ae9-121.akbr6.global-gateway.net.nz (202.50.233.197) 34.749 ms 36.900 ms 34.082 ms
6 ae5-2.akbr7.global-gateway.net.nz (210.55.202.213) 34.112 ms 33.760 ms 34.322 ms
7 ae1-10.tkbr12.global-gateway.net.nz (202.50.232.37) 33.701 ms 33.780 ms 33.667 ms
8 xe2-3-1.lebr7.global-gateway.net.nz (122.56.127.22) 158.519 ms
xe8-0-2-0.lebr7.global-gateway.net.nz (210.55.202.194) 158.301 ms 161.391 ms
9 ae3-10.sjbr3.global-gateway.net.nz (122.56.127.25) 165.861 ms
ae0.pabr5.global-gateway.net.nz (203.96.120.74) 162.615 ms
ae3-10.sjbr3.global-gateway.net.nz (122.56.127.25) 166.854 ms
10 ae0.pabr5.global-gateway.net.nz (203.96.120.74) 166.614 ms 166.705 ms 166.576 ms
11 palo-b1-link.telia.net (62.115.145.204) 166.606 ms
las-b3-link.telia.net (62.115.119.101) 177.022 ms
palo-b1-link.telia.net (62.115.145.204) 167.352 ms
12 sjo-b21-link.telia.net (62.115.143.121) 169.735 ms
las-b21-link.telia.net (62.115.116.41) 174.463 ms
sjo-b21-link.telia.net (62.115.118.205) 168.203 ms
13 las-b21-link.telia.net (62.115.116.41) 177.555 ms 178.215 ms
las-b21-link.telia.net (62.115.116.191) 182.959 ms
14 phx-b1-link.telia.net (80.91.245.76) 193.548 ms
phx-b1-link.telia.net (62.115.138.199) 192.557 ms
phx-b1-link.telia.net (80.91.245.76) 187.859 ms
15 salesforce-ic-311998-phx-b1.c.telia.net (62.115.44.14) 188.528 ms 187.927 ms 188.500 ms
16 xe-3-0-0--dcr2-chi.net.sfdc.net (136.146.192.13) 222.933 ms
xe-4-0-0.edge2-chi.net.salesforce.com (13.108.1.50) 339.336 ms 298.457 ms
17 na27-chi.force.com (136.146.208.104) 227.203 ms
xe-3-0-0--dcr2-chi.net.sfdc.net (136.146.192.13) 231.745 ms
xe-3-0-0--dcr1-chi.net.sfdc.net (136.146.192.9) 227.144 ms
traceroute na27-chi.force.com Johnsonville Cable
traceroute to na27-chi.force.com (136.146.208.104), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 2.712 ms 20.966 ms 4.615 ms
2 * * *
3 lo0.internet.ivpn.pe15.telstraclear.net (218.101.61.30) 23.384 ms * 94.514 ms
4 * ie2-g-0-0-0.telstraclear.net (203.98.50.2) 23.102 ms 19.302 ms
5 ge-0-2-0-1.xcore1.acld.telstraclear.net (203.98.50.251) 20.322 ms 20.573 ms 26.073 ms
6 unknown.telstraglobal.net (134.159.174.38) 20.396 ms
be10-2.bgnzftc02.akl.vf.net.nz (203.109.130.41) 19.429 ms
unknown.telstraglobal.net (134.159.174.42) 22.866 ms
7 unknown.telstraglobal.net (134.159.174.41) 24.472 ms
unknown.telstraglobal.net (134.159.174.37) 25.766 ms 22.780 ms
8 * * i-0-5-1-1.1wlt-core01.bx.telstraglobal.net (202.84.142.114) 152.353 ms
9 i-0-5-2-0.1wlt-core01.bi.telstraglobal.net (202.84.251.146) 165.516 ms
i-0-4-0-4.1wlt-core01.bi.telstraglobal.net (202.40.149.221) 147.528 ms *
10 i-0-1-0-11.siko-core04.bx.telstraglobal.net (202.84.249.10) 213.855 ms
i-0-1-0-4.siko-core04.bx.telstraglobal.net (202.84.143.162) 230.058 ms 203.978 ms
11 i-0-0-1-0.siko08.bi.telstraglobal.net (202.84.148.134) 204.650 ms *
i-0-0-2-2.siko08.bi.telstraglobal.net (202.84.148.229) 286.036 ms
12 pacnet-peer.siko08.pr.telstraglobal.net (134.159.98.58) 210.773 ms 288.245 ms 307.479 ms
13 ip-202-147-0-108.asianetcom.net (202.147.0.108) 409.154 ms 409.429 ms 260.576 ms
14 kbs-0001.10026.telstraglobal.net (203.192.150.54) 279.123 ms 305.946 ms 409.672 ms
15 xe-1-3-0.edge1-sfm.net.salesforce.com (13.108.1.25) 614.430 ms 302.556 ms 307.716 ms
16 xe-3-0-2.edge1-chi.net.salesforce.com (13.108.1.8) 613.746 ms 416.543 ms 384.805 ms
17 xe-2-0-1--dcr2-chi.net.sfdc.net (136.146.192.7) 314.487 ms
xe-2-0-1--dcr1-chi.net.sfdc.net (136.146.192.3) 313.744 ms 443.395 ms
18 na27-chi.force.com (136.146.208.104) 512.110 ms * 314.048 ms
I also notice my facebook is sluggish some times as well.
Hopefully, VFNZ can sort their international capacity/peering soonish.
We've been having lots of issues watching many videos on YouTube as of late. It can take 3+ minutes for videos to finally start playing, and even then they generally only start playing at 360p or some other silly low resolution. Every single time it seems to get caught up on something at *.pppoe.ihug.co.nz.
One stream in particular was at r6.sn-8vq54voxo1-53az.googlevideo.com. I couldn't ping that server for minutes on end; however, as soon as I was able to start pinging it, video playback also started. It seems like things are keeling over entirely for minutes on end. Incredibly frustrating.
trib:
In my case, I can get a better download speed from using a free wifi in Wellington as compared to my cable at home.
I hear you there. I often get better performance with a spotty 3G connection than I do on cable. :(
Still continuing to have issues on YouTube. Yet again, it seems to connect to connect to something cached on Vodafone's servers, but the server is completely inaccessible for an extended period of time. Here's an example showing what happens when I try to ping it, until it eventually and seemingly randomly starts "working":
C:\Users\Colton>ping r5---sn-8vq54voxo1-53az.googlevideo.com
Pinging r5.sn-8vq54voxo1-53az.googlevideo.com [203.118.143.208] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 203.118.143.208: bytes=32 time=28ms TTL=58
Reply from 203.118.143.208: bytes=32 time=18ms TTL=58
Ping statistics for 203.118.143.208:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 28ms, Average = 23ms
I'm very fortunate that it started working when it did, because I forgot the -t flag and could have simply had everything time out. :P
Either way, this prolonged issue is beyond frustrating. Please, Vodafone, get this caching sorted out. :(
|
![]() ![]() ![]() |