Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Forums › Online streaming services › Netflix streaming issue 2014-05-24
Filter this topic showing only the reply marked as answer View this topic in a long page with up to 500 replies per page Create new topic
1 | ... | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | ... | 53
835 posts

Ultimate Geek

Trusted

  # 1054265 27-May-2014 12:34
Send private message

phantasmNZ: Something has changed.



On Vodafone VDSL I can now get to 50% loading before it fails :-)

1054 posts

Uber Geek


  # 1054266 27-May-2014 12:34
Send private message

No still broken with unotelly and unblock-us .... Always get's to 50% for me and fails since the fault started.

 
 
 
 


8 posts

Wannabe Geek


  # 1054268 27-May-2014 12:36
Send private message

Has anyone else tried messing with caching???

1054 posts

Uber Geek


  # 1054269 27-May-2014 12:37
Send private message

Not something I can try, so would need to be a Slingshot user.

1054 posts

Uber Geek


  # 1054271 27-May-2014 12:40
Send private message

Will stick with acevpn I think, similar price gives you a smart DNS service as well as VPN. VPN is super quick same speed as unblock-us and it works. Will be purchasing a VPN router next week, don't have an old router here that will support DD-WRT :-/

869 posts

Ultimate Geek

Trusted

  # 1054272 27-May-2014 12:42
One person supports this post
Send private message

Can people who are having issues post some pings and trace routes to 198.38.96.176 or 108.175.39.168?

These are both Netflix servers video data is coming from to me. I've tried pinging from a number of connections - only seeing some latency spikes from the Telecom pay phone Wifi (and the mobile data connections, but that's normal) Otherwise streaming perfectly on our Snap VDSL here.

Worth noting Unblockus/Unotelly don't proxy the video, they simply do the websites and related data needed. The videos are streamed directly to you.




 

24 posts

Geek


  # 1054283 27-May-2014 12:55
Send private message

if you are on slingshot, could you try turning caching off (reboot router) - I can't fail mine since I did this - and I've even turned it back on again since) 

 
 
 
 


1054 posts

Uber Geek


  # 1054285 27-May-2014 12:59
Send private message

Tracing route to ipv4_1.lagg0.c082.lax004.ix.nflxvideo.net [198.38.96.176]
over a maximum of 30 hops:

  1    15 ms    14 ms     6 ms  192.168.1.254
  2   132 ms   195 ms   122 ms  be2-100.bras1ftc.akl.vf.net.nz [203.109.129.37]
  3   128 ms   140 ms   141 ms  be5-100.ppnzftc01.akl.vf.net.nz [203.109.129.38]
  4   102 ms   119 ms   166 ms  be7-188.ppnzftc02.akl.vf.net.nz.180.109.203.in-addr.arpa [203.109.180.226]
  5   189 ms   186 ms   184 ms  be8-188.ppnzftc02.akl.vf.net.nz.180.109.203.in-addr.arpa [203.109.180.225]
  6   284 ms   259 ms   298 ms  10.123.80.13
  7   206 ms   253 ms   301 ms  ten-0-2-0.bdr02.sjc01.ca.VOCUS.net [114.31.199.137]
  8   262 ms   220 ms   149 ms  ten-0-0-2-2.cor02.sjc01.ca.VOCUS.net [114.31.199.244]
  9   343 ms   284 ms   281 ms  ten-0-2-0.bdr01.sjc01.ca.VOCUS.net [114.31.199.243]
 10   224 ms   299 ms   242 ms  ip67-92-171-25.z171-92-67.customer.algx.net [67.92.171.25]
 11   186 ms   184 ms   179 ms  207.88.13.237.ptr.us.xo.net [207.88.13.237]
 12   232 ms   190 ms     *     207.88.13.81.ptr.us.xo.net [207.88.13.81]
 13   240 ms   184 ms   241 ms  216.156.65.54.ptr.us.xo.net [216.156.65.54]
 14   231 ms   260 ms   298 ms  ipv4_1.lagg0.c082.lax004.ix.nflxvideo.net [198.38.96.176]

Trace complete.


Tracing route to ipv4_1.lagg0.c105.ord001.ix.nflxvideo.net [108.175.39.168]
over a maximum of 30 hops:

  1    68 ms    48 ms    24 ms  192.168.1.254
  2   115 ms   177 ms   157 ms  be2-100.bras1ftc.akl.vf.net.nz [203.109.129.37]
  3   170 ms   174 ms   168 ms  be5-100.ppnzftc01.akl.vf.net.nz [203.109.129.38]
  4   220 ms   180 ms   109 ms  be7-188.ppnzftc02.akl.vf.net.nz.180.109.203.in-addr.arpa [203.109.180.226]
  5   138 ms   145 ms   150 ms  be8-188.ppnzftc02.akl.vf.net.nz.180.109.203.in-addr.arpa [203.109.180.225]
  6   241 ms   260 ms   272 ms  vodafone-gw.customer.alter.net [152.179.103.58]
  7   279 ms   276 ms   251 ms  0.xe-2-2-0.GW2.LAX1.ALTER.NET [152.179.103.57]
  8   350 ms   295 ms   307 ms  0.ae6.BR1.LAX15.ALTER.NET [140.222.225.137]
  9   305 ms   225 ms   327 ms  ae-7.r05.lsanca03.us.bb.gin.ntt.net [129.250.8.85]
 10   221 ms   192 ms   221 ms  ae-2.r20.lsanca03.us.bb.gin.ntt.net [129.250.2.229]
 11   268 ms   203 ms     *     ae-4.r20.dllstx09.us.bb.gin.ntt.net [129.250.2.169]
 12   305 ms     *      258 ms  ae-0.r21.dllstx09.us.bb.gin.ntt.net [129.250.2.59]
 13   341 ms   372 ms   388 ms  ae-4.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.201]
 14   357 ms   322 ms   321 ms  ae-2.r05.chcgil09.us.bb.gin.ntt.net [129.250.2.27]
 15   336 ms   297 ms   343 ms  ae-0.netflix.chcgil09.us.bb.gin.ntt.net [129.250.198.134]
 16   353 ms   336 ms   337 ms  ipv4_1.lagg0.c105.ord001.ix.nflxvideo.net [108.175.39.168]

Trace complete.

Pinging 198.38.96.176 with 32 bytes of data:
Reply from 198.38.96.176: bytes=32 time=275ms TTL=50
Reply from 198.38.96.176: bytes=32 time=238ms TTL=50
Reply from 198.38.96.176: bytes=32 time=322ms TTL=50
Reply from 198.38.96.176: bytes=32 time=172ms TTL=50
Reply from 198.38.96.176: bytes=32 time=237ms TTL=50
Reply from 198.38.96.176: bytes=32 time=163ms TTL=50
Reply from 198.38.96.176: bytes=32 time=280ms TTL=50
Reply from 198.38.96.176: bytes=32 time=245ms TTL=50
Reply from 198.38.96.176: bytes=32 time=153ms TTL=50
Reply from 198.38.96.176: bytes=32 time=250ms TTL=50
Reply from 198.38.96.176: bytes=32 time=255ms TTL=50
Reply from 198.38.96.176: bytes=32 time=278ms TTL=50
Reply from 198.38.96.176: bytes=32 time=242ms TTL=50
Reply from 198.38.96.176: bytes=32 time=224ms TTL=50
Reply from 198.38.96.176: bytes=32 time=268ms TTL=50
Reply from 198.38.96.176: bytes=32 time=263ms TTL=50
Reply from 198.38.96.176: bytes=32 time=197ms TTL=50
Reply from 198.38.96.176: bytes=32 time=190ms TTL=50
Reply from 198.38.96.176: bytes=32 time=174ms TTL=50
Reply from 198.38.96.176: bytes=32 time=219ms TTL=50
Reply from 198.38.96.176: bytes=32 time=260ms TTL=50
Reply from 198.38.96.176: bytes=32 time=188ms TTL=50
Reply from 198.38.96.176: bytes=32 time=206ms TTL=50
Reply from 198.38.96.176: bytes=32 time=206ms TTL=50
Reply from 198.38.96.176: bytes=32 time=317ms TTL=50
Reply from 198.38.96.176: bytes=32 time=230ms TTL=50
Reply from 198.38.96.176: bytes=32 time=208ms TTL=50
Reply from 198.38.96.176: bytes=32 time=204ms TTL=50
Reply from 198.38.96.176: bytes=32 time=226ms TTL=50
Reply from 198.38.96.176: bytes=32 time=238ms TTL=50
Reply from 198.38.96.176: bytes=32 time=239ms TTL=50
Reply from 198.38.96.176: bytes=32 time=306ms TTL=50
Reply from 198.38.96.176: bytes=32 time=263ms TTL=50
Reply from 198.38.96.176: bytes=32 time=250ms TTL=50
Reply from 198.38.96.176: bytes=32 time=318ms TTL=50
Reply from 198.38.96.176: bytes=32 time=312ms TTL=50
Reply from 198.38.96.176: bytes=32 time=271ms TTL=50
Reply from 198.38.96.176: bytes=32 time=318ms TTL=50
Reply from 198.38.96.176: bytes=32 time=324ms TTL=50
Reply from 198.38.96.176: bytes=32 time=227ms TTL=50
Reply from 198.38.96.176: bytes=32 time=263ms TTL=50
Reply from 198.38.96.176: bytes=32 time=309ms TTL=50
Reply from 198.38.96.176: bytes=32 time=215ms TTL=50
Reply from 198.38.96.176: bytes=32 time=294ms TTL=50
Reply from 198.38.96.176: bytes=32 time=255ms TTL=50
Reply from 198.38.96.176: bytes=32 time=296ms TTL=50
Reply from 198.38.96.176: bytes=32 time=332ms TTL=50
Reply from 198.38.96.176: bytes=32 time=313ms TTL=50
Reply from 198.38.96.176: bytes=32 time=273ms TTL=50
Reply from 198.38.96.176: bytes=32 time=195ms TTL=50
Reply from 198.38.96.176: bytes=32 time=191ms TTL=50
Reply from 198.38.96.176: bytes=32 time=301ms TTL=50
Reply from 198.38.96.176: bytes=32 time=288ms TTL=50
Reply from 198.38.96.176: bytes=32 time=240ms TTL=50
Reply from 198.38.96.176: bytes=32 time=210ms TTL=50
Reply from 198.38.96.176: bytes=32 time=214ms TTL=50
Reply from 198.38.96.176: bytes=32 time=241ms TTL=50
Reply from 198.38.96.176: bytes=32 time=231ms TTL=50
Reply from 198.38.96.176: bytes=32 time=194ms TTL=50
Reply from 198.38.96.176: bytes=32 time=259ms TTL=50
Reply from 198.38.96.176: bytes=32 time=214ms TTL=50
Reply from 198.38.96.176: bytes=32 time=309ms TTL=50
Reply from 198.38.96.176: bytes=32 time=191ms TTL=50
Reply from 198.38.96.176: bytes=32 time=245ms TTL=50
Reply from 198.38.96.176: bytes=32 time=282ms TTL=50
Reply from 198.38.96.176: bytes=32 time=255ms TTL=50
Reply from 198.38.96.176: bytes=32 time=263ms TTL=50
Reply from 198.38.96.176: bytes=32 time=239ms TTL=50
Reply from 198.38.96.176: bytes=32 time=278ms TTL=50
Reply from 198.38.96.176: bytes=32 time=309ms TTL=50
Reply from 198.38.96.176: bytes=32 time=246ms TTL=50
Reply from 198.38.96.176: bytes=32 time=313ms TTL=50
Reply from 198.38.96.176: bytes=32 time=365ms TTL=50
Reply from 198.38.96.176: bytes=32 time=272ms TTL=50
Reply from 198.38.96.176: bytes=32 time=405ms TTL=50
Reply from 198.38.96.176: bytes=32 time=273ms TTL=50
Reply from 198.38.96.176: bytes=32 time=242ms TTL=50
Reply from 198.38.96.176: bytes=32 time=323ms TTL=50
Reply from 198.38.96.176: bytes=32 time=295ms TTL=50
Reply from 198.38.96.176: bytes=32 time=212ms TTL=50
Reply from 198.38.96.176: bytes=32 time=163ms TTL=50
Reply from 198.38.96.176: bytes=32 time=224ms TTL=50
Reply from 198.38.96.176: bytes=32 time=144ms TTL=50
Reply from 198.38.96.176: bytes=32 time=190ms TTL=50
Reply from 198.38.96.176: bytes=32 time=283ms TTL=50
Reply from 198.38.96.176: bytes=32 time=171ms TTL=50
Reply from 198.38.96.176: bytes=32 time=224ms TTL=50
Reply from 198.38.96.176: bytes=32 time=162ms TTL=50
Reply from 198.38.96.176: bytes=32 time=281ms TTL=50
Reply from 198.38.96.176: bytes=32 time=186ms TTL=50
Reply from 198.38.96.176: bytes=32 time=210ms TTL=50
Reply from 198.38.96.176: bytes=32 time=241ms TTL=50
Reply from 198.38.96.176: bytes=32 time=257ms TTL=50
Reply from 198.38.96.176: bytes=32 time=312ms TTL=50
Reply from 198.38.96.176: bytes=32 time=314ms TTL=50
Reply from 198.38.96.176: bytes=32 time=181ms TTL=50
Reply from 198.38.96.176: bytes=32 time=305ms TTL=50
Reply from 198.38.96.176: bytes=32 time=262ms TTL=50
Reply from 198.38.96.176: bytes=32 time=278ms TTL=50
Reply from 198.38.96.176: bytes=32 time=306ms TTL=50
Reply from 198.38.96.176: bytes=32 time=274ms TTL=50
Reply from 198.38.96.176: bytes=32 time=264ms TTL=50
Reply from 198.38.96.176: bytes=32 time=235ms TTL=50
Reply from 198.38.96.176: bytes=32 time=194ms TTL=50
Reply from 198.38.96.176: bytes=32 time=211ms TTL=50
Reply from 198.38.96.176: bytes=32 time=145ms TTL=50
Reply from 198.38.96.176: bytes=32 time=227ms TTL=50
Reply from 198.38.96.176: bytes=32 time=201ms TTL=50
Reply from 198.38.96.176: bytes=32 time=284ms TTL=50
Reply from 198.38.96.176: bytes=32 time=261ms TTL=50
Reply from 198.38.96.176: bytes=32 time=206ms TTL=50
Reply from 198.38.96.176: bytes=32 time=268ms TTL=50
Reply from 198.38.96.176: bytes=32 time=251ms TTL=50
Reply from 198.38.96.176: bytes=32 time=263ms TTL=50
Reply from 198.38.96.176: bytes=32 time=309ms TTL=50
Reply from 198.38.96.176: bytes=32 time=151ms TTL=50
Request timed out.
Reply from 198.38.96.176: bytes=32 time=270ms TTL=50
Reply from 198.38.96.176: bytes=32 time=252ms TTL=50
Reply from 198.38.96.176: bytes=32 time=233ms TTL=50
Reply from 198.38.96.176: bytes=32 time=267ms TTL=50
Reply from 198.38.96.176: bytes=32 time=253ms TTL=50
Reply from 198.38.96.176: bytes=32 time=193ms TTL=50
Reply from 198.38.96.176: bytes=32 time=301ms TTL=50
Reply from 198.38.96.176: bytes=32 time=190ms TTL=50
Reply from 198.38.96.176: bytes=32 time=268ms TTL=50
Reply from 198.38.96.176: bytes=32 time=226ms TTL=50
Reply from 198.38.96.176: bytes=32 time=294ms TTL=50
Reply from 198.38.96.176: bytes=32 time=290ms TTL=50
Reply from 198.38.96.176: bytes=32 time=301ms TTL=50
Reply from 198.38.96.176: bytes=32 time=284ms TTL=50
Reply from 198.38.96.176: bytes=32 time=207ms TTL=50
Reply from 198.38.96.176: bytes=32 time=259ms TTL=50
Reply from 198.38.96.176: bytes=32 time=260ms TTL=50
Reply from 198.38.96.176: bytes=32 time=321ms TTL=50
Reply from 198.38.96.176: bytes=32 time=316ms TTL=50
Reply from 198.38.96.176: bytes=32 time=253ms TTL=50
Reply from 198.38.96.176: bytes=32 time=217ms TTL=50
Reply from 198.38.96.176: bytes=32 time=274ms TTL=50
Reply from 198.38.96.176: bytes=32 time=242ms TTL=50
Reply from 198.38.96.176: bytes=32 time=206ms TTL=50
Reply from 198.38.96.176: bytes=32 time=272ms TTL=50
Reply from 198.38.96.176: bytes=32 time=223ms TTL=50
Reply from 198.38.96.176: bytes=32 time=310ms TTL=50
Reply from 198.38.96.176: bytes=32 time=359ms TTL=50
Reply from 198.38.96.176: bytes=32 time=219ms TTL=50
Reply from 198.38.96.176: bytes=32 time=245ms TTL=50
Reply from 198.38.96.176: bytes=32 time=255ms TTL=50
Reply from 198.38.96.176: bytes=32 time=272ms TTL=50
Reply from 198.38.96.176: bytes=32 time=227ms TTL=50
Reply from 198.38.96.176: bytes=32 time=175ms TTL=50
Reply from 198.38.96.176: bytes=32 time=319ms TTL=50
Reply from 198.38.96.176: bytes=32 time=321ms TTL=50
Reply from 198.38.96.176: bytes=32 time=234ms TTL=50
Reply from 198.38.96.176: bytes=32 time=188ms TTL=50
Reply from 198.38.96.176: bytes=32 time=427ms TTL=50
Reply from 198.38.96.176: bytes=32 time=193ms TTL=50
Reply from 198.38.96.176: bytes=32 time=188ms TTL=50
Reply from 198.38.96.176: bytes=32 time=221ms TTL=50
Reply from 198.38.96.176: bytes=32 time=180ms TTL=50
Reply from 198.38.96.176: bytes=32 time=240ms TTL=50
Reply from 198.38.96.176: bytes=32 time=260ms TTL=50
Reply from 198.38.96.176: bytes=32 time=226ms TTL=50
Reply from 198.38.96.176: bytes=32 time=273ms TTL=50
Reply from 198.38.96.176: bytes=32 time=265ms TTL=50
Reply from 198.38.96.176: bytes=32 time=249ms TTL=50
Reply from 198.38.96.176: bytes=32 time=286ms TTL=50
Reply from 198.38.96.176: bytes=32 time=312ms TTL=50
Reply from 198.38.96.176: bytes=32 time=290ms TTL=50
Reply from 198.38.96.176: bytes=32 time=298ms TTL=50
Reply from 198.38.96.176: bytes=32 time=336ms TTL=50
Reply from 198.38.96.176: bytes=32 time=320ms TTL=50
Reply from 198.38.96.176: bytes=32 time=318ms TTL=50
Reply from 198.38.96.176: bytes=32 time=324ms TTL=50
Reply from 198.38.96.176: bytes=32 time=346ms TTL=50
Reply from 198.38.96.176: bytes=32 time=300ms TTL=50
Reply from 198.38.96.176: bytes=32 time=279ms TTL=50
Reply from 198.38.96.176: bytes=32 time=164ms TTL=50
Reply from 198.38.96.176: bytes=32 time=301ms TTL=50
Reply from 198.38.96.176: bytes=32 time=243ms TTL=50
Reply from 198.38.96.176: bytes=32 time=228ms TTL=50
Reply from 198.38.96.176: bytes=32 time=239ms TTL=50
Reply from 198.38.96.176: bytes=32 time=182ms TTL=50
Reply from 198.38.96.176: bytes=32 time=187ms TTL=50
Reply from 198.38.96.176: bytes=32 time=223ms TTL=50
Reply from 198.38.96.176: bytes=32 time=210ms TTL=50
Reply from 198.38.96.176: bytes=32 time=252ms TTL=50
Reply from 198.38.96.176: bytes=32 time=242ms TTL=50
Reply from 198.38.96.176: bytes=32 time=248ms TTL=50
Reply from 198.38.96.176: bytes=32 time=258ms TTL=50
Reply from 198.38.96.176: bytes=32 time=252ms TTL=50
Reply from 198.38.96.176: bytes=32 time=294ms TTL=50
Reply from 198.38.96.176: bytes=32 time=300ms TTL=50
Reply from 198.38.96.176: bytes=32 time=265ms TTL=50

Ping statistics for 198.38.96.176:
    Packets: Sent = 194, Received = 193, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 144ms, Maximum = 427ms, Average = 253ms


Pinging 108.175.39.168 with 32 bytes of data:
Reply from 108.175.39.168: bytes=32 time=294ms TTL=47
Reply from 108.175.39.168: bytes=32 time=241ms TTL=47
Reply from 108.175.39.168: bytes=32 time=366ms TTL=47
Reply from 108.175.39.168: bytes=32 time=342ms TTL=47
Reply from 108.175.39.168: bytes=32 time=203ms TTL=47
Reply from 108.175.39.168: bytes=32 time=276ms TTL=47
Reply from 108.175.39.168: bytes=32 time=240ms TTL=47
Reply from 108.175.39.168: bytes=32 time=286ms TTL=47
Reply from 108.175.39.168: bytes=32 time=300ms TTL=47
Reply from 108.175.39.168: bytes=32 time=231ms TTL=47
Reply from 108.175.39.168: bytes=32 time=490ms TTL=47
Reply from 108.175.39.168: bytes=32 time=325ms TTL=47
Reply from 108.175.39.168: bytes=32 time=296ms TTL=47
Reply from 108.175.39.168: bytes=32 time=331ms TTL=47
Reply from 108.175.39.168: bytes=32 time=260ms TTL=47
Reply from 108.175.39.168: bytes=32 time=292ms TTL=47
Reply from 108.175.39.168: bytes=32 time=271ms TTL=47
Reply from 108.175.39.168: bytes=32 time=203ms TTL=47
Reply from 108.175.39.168: bytes=32 time=231ms TTL=47
Reply from 108.175.39.168: bytes=32 time=276ms TTL=47
Reply from 108.175.39.168: bytes=32 time=349ms TTL=47
Reply from 108.175.39.168: bytes=32 time=336ms TTL=47
Reply from 108.175.39.168: bytes=32 time=243ms TTL=47
Reply from 108.175.39.168: bytes=32 time=388ms TTL=47
Reply from 108.175.39.168: bytes=32 time=283ms TTL=47
Reply from 108.175.39.168: bytes=32 time=377ms TTL=47
Reply from 108.175.39.168: bytes=32 time=323ms TTL=47
Reply from 108.175.39.168: bytes=32 time=216ms TTL=47
Reply from 108.175.39.168: bytes=32 time=322ms TTL=47
Reply from 108.175.39.168: bytes=32 time=362ms TTL=47
Reply from 108.175.39.168: bytes=32 time=336ms TTL=47
Reply from 108.175.39.168: bytes=32 time=322ms TTL=47
Reply from 108.175.39.168: bytes=32 time=369ms TTL=47
Reply from 108.175.39.168: bytes=32 time=368ms TTL=47
Reply from 108.175.39.168: bytes=32 time=341ms TTL=47
Reply from 108.175.39.168: bytes=32 time=261ms TTL=47
Reply from 108.175.39.168: bytes=32 time=301ms TTL=47
Reply from 108.175.39.168: bytes=32 time=372ms TTL=47
Reply from 108.175.39.168: bytes=32 time=276ms TTL=47
Reply from 108.175.39.168: bytes=32 time=369ms TTL=47
Reply from 108.175.39.168: bytes=32 time=400ms TTL=47
Reply from 108.175.39.168: bytes=32 time=333ms TTL=47
Reply from 108.175.39.168: bytes=32 time=288ms TTL=47
Reply from 108.175.39.168: bytes=32 time=293ms TTL=47
Reply from 108.175.39.168: bytes=32 time=302ms TTL=47
Reply from 108.175.39.168: bytes=32 time=311ms TTL=47
Reply from 108.175.39.168: bytes=32 time=292ms TTL=47
Reply from 108.175.39.168: bytes=32 time=310ms TTL=47
Reply from 108.175.39.168: bytes=32 time=312ms TTL=47
Reply from 108.175.39.168: bytes=32 time=226ms TTL=47
Reply from 108.175.39.168: bytes=32 time=323ms TTL=47
Reply from 108.175.39.168: bytes=32 time=373ms TTL=47
Reply from 108.175.39.168: bytes=32 time=286ms TTL=47
Reply from 108.175.39.168: bytes=32 time=273ms TTL=47
Reply from 108.175.39.168: bytes=32 time=303ms TTL=47
Reply from 108.175.39.168: bytes=32 time=210ms TTL=47
Reply from 108.175.39.168: bytes=32 time=259ms TTL=47
Reply from 108.175.39.168: bytes=32 time=271ms TTL=47
Reply from 108.175.39.168: bytes=32 time=254ms TTL=47
Reply from 108.175.39.168: bytes=32 time=311ms TTL=47
Reply from 108.175.39.168: bytes=32 time=272ms TTL=47
Reply from 108.175.39.168: bytes=32 time=289ms TTL=47
Reply from 108.175.39.168: bytes=32 time=300ms TTL=47
Reply from 108.175.39.168: bytes=32 time=293ms TTL=47
Reply from 108.175.39.168: bytes=32 time=277ms TTL=47
Reply from 108.175.39.168: bytes=32 time=280ms TTL=47
Reply from 108.175.39.168: bytes=32 time=306ms TTL=47
Reply from 108.175.39.168: bytes=32 time=340ms TTL=47
Reply from 108.175.39.168: bytes=32 time=324ms TTL=47
Reply from 108.175.39.168: bytes=32 time=322ms TTL=47
Reply from 108.175.39.168: bytes=32 time=342ms TTL=47
Reply from 108.175.39.168: bytes=32 time=331ms TTL=47
Reply from 108.175.39.168: bytes=32 time=273ms TTL=47
Reply from 108.175.39.168: bytes=32 time=276ms TTL=47
Reply from 108.175.39.168: bytes=32 time=264ms TTL=47
Reply from 108.175.39.168: bytes=32 time=320ms TTL=47
Reply from 108.175.39.168: bytes=32 time=321ms TTL=47
Reply from 108.175.39.168: bytes=32 time=280ms TTL=47
Reply from 108.175.39.168: bytes=32 time=246ms TTL=47
Reply from 108.175.39.168: bytes=32 time=254ms TTL=47
Reply from 108.175.39.168: bytes=32 time=272ms TTL=47
Reply from 108.175.39.168: bytes=32 time=292ms TTL=47
Reply from 108.175.39.168: bytes=32 time=325ms TTL=47
Reply from 108.175.39.168: bytes=32 time=286ms TTL=47
Reply from 108.175.39.168: bytes=32 time=362ms TTL=47

Ping statistics for 108.175.39.168:
    Packets: Sent = 85, Received = 85, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 203ms, Maximum = 490ms, Average = 301ms

5 posts

Wannabe Geek


  # 1054293 27-May-2014 13:08
Send private message

Hi phantasmNZ, great news it is working for you.

Which provider are you with?

569 posts

Ultimate Geek

Subscriber

  # 1054303 27-May-2014 13:23
Send private message

@dlmurray
phantasmNZ said in an earlier post here was with UnoTelly.

phantasmNZ: Something has changed.

NF US is working for me every time now. - UnoTelly and Slingshot Global Mode. Since about 40 minutes ago.... 

Banana?
4904 posts

Uber Geek

Subscriber

  # 1054310 27-May-2014 13:35
Send private message

I am hoping the issue is actually a Netflix one, and my internal panic about them doing away with GeoBlockers is unfounded.

Fingers crossed.

Oh, and, thanks to the Telco reps that have responded in this thread - especially the one from Telecom - good to have that feedback.

3 posts

Wannabe Geek


  # 1054333 27-May-2014 14:09
Send private message

Slingshot VDSL with Global mode - just watched a complete show for the first time since problems started, previously I only got the first few seconds via web browsers and nothing via Apple TV.

Made no changes. My Caching option is currently turned on, which I guess is how it's always been as I've never checked this before.

33 posts

Geek


  # 1054341 27-May-2014 14:19
Send private message

Slingshot VDSL user here- will try when I get home from work tonight. Finger crossed.

1194 posts

Uber Geek

Trusted

  # 1054345 27-May-2014 14:27
One person supports this post
Send private message

SaRaCeNz: Slingshot VDSL user here- will try when I get home from work tonight. Finger crossed.


Just the one?

3 posts

Wannabe Geek


  # 1054357 27-May-2014 15:11
Send private message

I've tried a bunch of shows now, seems good.. can't fault it at the moment.

1 | ... | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | ... | 53
Filter this topic showing only the reply marked as answer View this topic in a long page with up to 500 replies per page Create new topic



Twitter and LinkedIn »



Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:





News »

Ring launches indoor-only security camera
Posted 23-Jan-2020 17:26

New report findings will help schools implement the digital technologies curriculum content
Posted 23-Jan-2020 17:25

N4L to upgrade & support wireless internet inside schools
Posted 23-Jan-2020 17:22

Netflix releases 21 Studio Ghibli works
Posted 22-Jan-2020 11:42

Vodafone integrates eSIM into device and wearable roadmap
Posted 17-Jan-2020 09:45

Do you need this camera app? Group investigates privacy implications
Posted 16-Jan-2020 03:30

JBL launches headphones range designed for gaming
Posted 13-Jan-2020 09:59

Withings introduces ScanWatch wearable combining ECG and sleep apnea detection
Posted 9-Jan-2020 18:34

NZ Police releases public app
Posted 8-Jan-2020 11:43

Suunto 7 combine sports and smart features on new smartwatch generation
Posted 7-Jan-2020 16:06

Intel brings innovation with technology spanning the cloud, network, edge and PC
Posted 7-Jan-2020 15:54

AMD announces high performance desktop and ultrathin laptop processors
Posted 7-Jan-2020 15:42

AMD unveils four new desktop and mobile GPUs including AMD Radeon RX 5600
Posted 7-Jan-2020 15:32

Consolidation in video streaming market with Spark selling Lightbox to Sky
Posted 19-Dec-2019 09:09

Intel introduces cryogenic control chip to enable quantum computers
Posted 10-Dec-2019 21:32


Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Support Geekzone »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron


Updates »

Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.