Unotelly + Hulu tonight

Forums › Online streaming services › Unotelly + Hulu tonight

1 | 2 | 3 | 4

meow
13732 posts

Uber Geek
+1 received by user: 11151

Moderator

ID Verified

Trusted

Lifetime subscriber

#1433624 23-Nov-2015 23:07

Not working with me tonight. Can't go for more than 10 seconds without buffering (browser). Chromecast doesn't like it too and internet is currently idle. Maybe Hulu is cracking down on people out of the US?

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup) | Starlink

NZ Politics 2026 Tracking & Quiz: https://nzpol.nz

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

bash

34 posts

Geek
+1 received by user: 3

#1434106 24-Nov-2015 20:30

Still having issues here with Roku, Hulu and Unotelly - no response other than its been raised to level 2 support...

kingjj

1733 posts

Uber Geek
+1 received by user: 450

ID Verified

Trusted

#1434263 25-Nov-2015 01:36

Is anyone else seeing weird routing to Hulu?

Two trace routes run 10 seconds apart just now:

Tracing route to hulu.com [72.246.190.27]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms fritz.box [192.168.178.1]
2 4 ms 3 ms 3 ms 111-69-1-254.core.snap.net.nz [111.69.1.254]
3 * * * Request timed out.
4 142 ms 142 ms 142 ms xe-0-6-0-6.r01.snjsca04.us.ce.gin.ntt.net [129.250.200.102]
5 143 ms 142 ms 143 ms xe-0-6-0-6.r01.snjsca04.us.bb.gin.ntt.net [129.250.200.101]
6 144 ms 142 ms 142 ms ae-10.r23.snjsca04.us.bb.gin.ntt.net [129.250.3.174]
7 245 ms 248 ms 257 ms ae-4.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.3.7]
8 247 ms 246 ms 246 ms ae-5.r01.tokyjp05.jp.bb.gin.ntt.net [129.250.4.111]
9 247 ms 247 ms 246 ms ae-1.akamai.tokyjp05.jp.bb.gin.ntt.net [61.213.160.42]
10 243 ms 242 ms 243 ms a72-246-190-27.deploy.akamaitechnologies.com [72.246.190.27]

Trace complete.

Tracing route to hulu.com [104.72.70.80]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms fritz.box [192.168.178.1]
2 3 ms 3 ms 3 ms 111-69-1-254.core.snap.net.nz [111.69.1.254]
3 20 ms 17 ms 17 ms 43.243.21.30
4 42 ms 41 ms 41 ms 43.243.21.27
5 42 ms 42 ms 45 ms ten-0-1-0-2.cor01.alb01.akl.VOCUS.net.nz [114.31.202.38]
6 42 ms 41 ms 44 ms ten-0-2-1-0.cor03.syd03.nsw.VOCUS.net.au [114.31.202.36]
7 42 ms 44 ms 43 ms bundle-100.bdr04.syd03.nsw.vocus.net.au [114.31.192.57]
8 43 ms 41 ms 45 ms asn20940.cust.bdr04.syd03.nsw.vocus.net.au [175.45.124.226]
9 41 ms 40 ms 40 ms a104-72-70-80.deploy.static.akamaitechnologies.com [104.72.70.80]

Trace complete.

Each time I run a trace route it switches between the 2 above. Going via the US to Japan would surely causes issues buffering?

steve98

1403 posts

Uber Geek
+1 received by user: 253

Trusted

#1434757 25-Nov-2015 19:26

Unotelly found a change in behaviour from Hulu that was causing them to route requests from the NZ DNS to a different server to normal. Obviously this server gives less than optimal performance. Their support suggested I switch to the Toronto and Montreal DNS servers, and that does seem to have fixed the issue for me. No more buffering.

They acknowledge that this is more of a workaround than a permanent solution but I'm personally happy to just have it working reliably again. Others using Unotelly might want to try the same solution.

howduz1

83 posts

Master Geek
+1 received by user: 2

#1434810 25-Nov-2015 20:45

Awesome work - thanks mate. I'm on getflix but changing to Toronto DNS seems to have fixed it for me. I tried Sydney servers the other day but that seemed to make it worse.

bash

34 posts

Geek
+1 received by user: 3

#1434812 25-Nov-2015 20:48

Thanks Steve98, just changed to Unotelly Seattle Servers, and back to proper streaming again..still haven't had a reply from their Level 2 support team on the initial issue with NZ DNS.

Lenovo

Shop now for Lenovo laptops and other devices (affiliate link).

UnoTellyService

62 posts

Master Geek
+1 received by user: 40

Trusted

Unotelly

#1434906 26-Nov-2015 05:59

Hello GeekZone users

I'm here from UnoTelly to give you all an update on this Hulu performance issue. We have found the cause of the matter and we would like to solicit some tests from you to help assist us in finding the best solution.

Explanation of the issue:
We do not actually proxy the Hulu video streams on Apple TV 4 - you are getting the video directly from Hulu's servers.

Hulu appears to be using 3 different servers for the video and it detects your DNS server's location to assign you one of these three.

I have tested all of our DNS servers and found they are breaking them up into very neat regions:
1. Americas (Including Canada, Costa Rica and Brazil)
2. Europe, Middle East and Africa (Includes Turkey, Israel, Egypt and South Africa)
3. East Asia (Includes Japan, India, Hong Kong, Australia and New Zealand)

Since you are all in NZ you will be getting assigned their #3 server. Some of you who have tested this out with our servers in North America have said that they are significantly better in performance.

The Tests:

We would like for you to run some tests on your computer to determine which servers are fastest for you all in NZ. We could then potentially have our DNS servers in NZ point out to whichever the tests say is best for you.

For Windows please open up a command prompt and run these commands one at a time, saving the results and posting them here:
tracert 93.184.215.248
tracert 68.232.34.133
tracert 68.232.45.253

For Mac OS X please open up the Terminal.app and run these commands one at a time, saving the results and posting them here:
traceroute 93.184.215.248
traceroute 68.232.34.133
traceroute 68.232.45.253

Please also indicate your Internet Service Provider and the City where you performed the test from.

Possible Solution:

Obviously we want this to be as fast as possible for all of our users. Since this is just Hulu's own servers we can safely point you to another one but first we need good test results. Ones that display the actual routing information and latency of each hop so we can see exactly where it is slowing down precisely.

Please understand that we do take such issues very seriously and will work to resolve them.

steve98

1403 posts

Uber Geek
+1 received by user: 253

Trusted

#1434908 26-Nov-2015 06:16

UnoTellyService:

Explanation of the issue:
We do not actually proxy the Hulu video streams on Apple TV 4 - you are getting the video directly from Hulu's servers.

Just to be clear, this affects more than just the Apple TV 4, right? For example, the device I am using is the Apple TV 3 and PS4 and both were impacted.

BuzzLightyear

422 posts

Ultimate Geek
+1 received by user: 109

#1434913 26-Nov-2015 07:17

FYI I have Spark ADSL with Hulu and unotelly and use it all the time and have never experienced any problems. I have Voda VDSL and getflix at my Bach and over the weekend no issues either. I use Apple TV app only. Are we sure this problem is not limited to 2d/Snap?

bash

34 posts

Geek
+1 received by user: 3

#1434949 26-Nov-2015 08:43

Hi Team

Am based in Auckland using 2 Degrees Broadband. Using Hulu via Webbrowser as well as a Roku.

From Steattle Unotelly DNS (50.22.147.234) results below

Tracing route to 93.184.215.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 20 ms 20 ms 20 ms 57.35.69.111.static.snap.net.nz [111.69.35.57]
3 * * * Request timed out.
4 144 ms 143 ms 144 ms TWO-DEGREES.bar1.SanFrancisco1.Level3.net [4.16.192.146]
5 145 ms 145 ms 145 ms xe-4-2-0.bar1.SanFrancisco1.Level3.net [4.16.192.145]
6 * * 150 ms ae-4-90.ear1.SanJose3.Level3.net [4.69.152.216]
7 * * 150 ms ae-4-90.ear1.SanJose3.Level3.net [4.69.152.216]
8 149 ms 149 ms 150 ms 192.229.129.238
9 149 ms 149 ms 149 ms 93.184.215.248

Trace complete.

Tracing route to 68.232.34.133 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 20 ms 20 ms 20 ms 57.35.69.111.static.snap.net.nz [111.69.35.57]
3 * * * Request timed out.
4 144 ms 143 ms 143 ms xe-0-6-0-6.r01.snjsca04.us.ce.gin.ntt.net [129.250.200.102]
5 144 ms 144 ms 145 ms xe-0-6-0-6.r01.snjsca04.us.bb.gin.ntt.net [129.250.200.101]
6 144 ms 144 ms 145 ms ae-1.r22.snjsca04.us.bb.gin.ntt.net [129.250.3.26]
7 207 ms 207 ms 208 ms ae-7.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.238]
8 * 294 ms * ae-2.r23.amstnl02.nl.bb.gin.ntt.net [129.250.6.163]
9 298 ms 298 ms 298 ms ae-2.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.159]
10 292 ms 292 ms 292 ms 83.231.213.90
11 293 ms 292 ms 292 ms 68.232.34.133

Trace complete.

Tracing route to 68.232.45.253 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 20 ms 20 ms 21 ms 57.35.69.111.static.snap.net.nz [111.69.35.57]
3 * * * Request timed out.
4 44 ms 43 ms 44 ms as23655.sydney.megaport.com [103.26.68.14]
5 43 ms 43 ms 44 ms as15133.sydney.megaport.com [103.26.68.60]
6 44 ms 43 ms 43 ms 68.232.45.253

Trace complete.

Using NZ Unotelly DNS Server (103.6.212.24) results below

Tracing route to 93.184.215.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 20 ms 20 ms 20 ms 57.35.69.111.static.snap.net.nz [111.69.35.57]
3 * * * Request timed out.
4 144 ms 144 ms 144 ms TWO-DEGREES.bar1.SanFrancisco1.Level3.net [4.16.192.146]
5 145 ms 145 ms 146 ms xe-4-2-0.bar1.SanFrancisco1.Level3.net [4.16.192.145]
6 * * 150 ms ae-4-90.ear1.SanJose3.Level3.net [4.69.152.216]
7 * * 150 ms ae-4-90.ear1.SanJose3.Level3.net [4.69.152.216]
8 149 ms 150 ms 150 ms 192.229.129.238
9 150 ms 149 ms 149 ms 93.184.215.248

Trace complete.

Tracing route to 68.232.34.133 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 20 ms 20 ms 20 ms 57.35.69.111.static.snap.net.nz [111.69.35.57]
3 * * * Request timed out.
4 144 ms 144 ms 144 ms xe-0-6-0-6.r01.snjsca04.us.ce.gin.ntt.net [129.250.200.102]
5 145 ms 144 ms 145 ms xe-0-6-0-6.r01.snjsca04.us.bb.gin.ntt.net [129.250.200.101]
6 146 ms 144 ms 144 ms ae-1.r22.snjsca04.us.bb.gin.ntt.net [129.250.3.26]
7 207 ms 207 ms 207 ms ae-7.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.238]
8 294 ms 297 ms * ae-2.r23.amstnl02.nl.bb.gin.ntt.net [129.250.6.163]
9 298 ms 298 ms 298 ms ae-2.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.159]
10 292 ms 292 ms 292 ms 83.231.213.90
11 298 ms 297 ms 293 ms 68.232.34.133

Tracing route to 68.232.45.253 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 22 ms 20 ms 20 ms 57.35.69.111.static.snap.net.nz [111.69.35.57]
3 * * * Request timed out.
4 43 ms 44 ms 43 ms as23655.sydney.megaport.com [103.26.68.14]
5 44 ms 43 ms 44 ms as15133.sydney.megaport.com [103.26.68.60]
6 44 ms 44 ms 44 ms 68.232.45.253

Trace complete.

UnoTellyService

62 posts

Master Geek
+1 received by user: 40

Trusted

Unotelly

#1434978 26-Nov-2015 09:40

bash: Hi Team

Am based in Auckland using 2 Degrees Broadband. Using Hulu via Webbrowser as well as a Roku.

From Steattle Unotelly DNS (50.22.147.234) results below
.....
Using NZ Unotelly DNS Server (103.6.212.24) results below
.....

Hi Bash,

Thank you for those test results. I just wanted to let other users know that there is no need to do this with different DNS servers. You do not even need to use our DNS servers.

steve98: Just to be clear, this affects more than just the Apple TV 4, right? For example, the device I am using is the Apple TV 3 and PS4 and both were impacted.

My apologies steve98 - this is focused on just Apple TV 4 at this moment. I was given a ticket earlier this week and the user sent me along to this thread. I will look into expanding the scope of devices to ATV3 and PS4 for you.

BuzzLightyear: FYI I have Spark ADSL with Hulu and unotelly and use it all the time and have never experienced any problems. I have Voda VDSL and getflix at my Bach and over the weekend no issues either. I use Apple TV app only. Are we sure this problem is not limited to 2d/Snap?

This is the purpose of these tests. We need to gather them all from users in this thread who are reporting issues with Hulu and UnoTelly :) I will have to look at expanding the number of devices this test's scope is concerned with. The reason is things like the ATV3 and Roku may be using totally different Hulu servers.

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

kingjj

1733 posts

Uber Geek
+1 received by user: 450

ID Verified

Trusted

#1434999 26-Nov-2015 10:03

Not using UnoTelly but having similar issue with another provider. Tracert's done on 2D Fibre:

tracert 93.184.215.248

Tracing route to 93.184.215.248 over a maximum of 30 hops

1 1 ms 1 ms 1 ms fritz.box [192.168.178.1]
2 3 ms 3 ms 3 ms 111-69-1-254.core.snap.net.nz [111.69.1.254]
3 * * * Request timed out.
4 144 ms 142 ms 141 ms TWO-DEGREES.bar1.SanFrancisco1.Level3.net [4.16.192.146]
5 143 ms 143 ms 157 ms xe-4-2-0.bar1.SanFrancisco1.Level3.net [4.16.192.145]
6 * * * Request timed out.
7 * 150 ms 151 ms ae-2-70.ear1.SanJose3.Level3.net [4.69.152.88]
8 150 ms 149 ms 149 ms 192.229.129.238
9 149 ms 149 ms 151 ms 93.184.215.248

Trace complete.

tracert 68.232.34.133

Tracing route to 68.232.34.133 over a maximum of 30 hops

1 1 ms 1 ms 1 ms fritz.box [192.168.178.1]
2 3 ms 3 ms 33 ms 111-69-1-254.core.snap.net.nz [111.69.1.254]
3 * * * Request timed out.
4 142 ms 142 ms 142 ms xe-0-6-0-6.r01.snjsca04.us.ce.gin.ntt.net [129.250.200.102]
5 144 ms 142 ms 142 ms xe-0-6-0-6.r01.snjsca04.us.bb.gin.ntt.net [129.250.200.101]
6 142 ms 143 ms 142 ms ae-1.r22.snjsca04.us.bb.gin.ntt.net [129.250.3.26]
7 209 ms 209 ms 208 ms ae-7.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.238]
8 * * * Request timed out.
9 303 ms 304 ms 304 ms ae-2.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.159]
10 300 ms 300 ms 299 ms 83.231.213.86
11 305 ms 305 ms 305 ms 68.232.34.133

Trace complete.

tracert 68.232.45.253

Tracing route to 68.232.45.253 over a maximum of 30 hops

1 1 ms 2 ms 2 ms fritz.box [192.168.178.1]
2 5 ms 3 ms 3 ms 111-69-1-254.core.snap.net.nz [111.69.1.254]
3 * * * Request timed out.
4 43 ms 41 ms 41 ms as23655.sydney.megaport.com [103.26.68.14]
5 41 ms 42 ms 44 ms as15133.sydney.megaport.com [103.26.68.60]
6 41 ms 42 ms 41 ms 68.232.45.253

Trace complete.

steve98

1403 posts

Uber Geek
+1 received by user: 253

Trusted

#1435054 26-Nov-2015 11:00

UnoTellyService:
steve98: Just to be clear, this affects more than just the Apple TV 4, right? For example, the device I am using is the Apple TV 3 and PS4 and both were impacted.

My apologies steve98 - this is focused on just Apple TV 4 at this moment. I was given a ticket earlier this week and the user sent me along to this thread. I will look into expanding the scope of devices to ATV3 and PS4 for you.
.

That was my ticket I believe! It wasn't about Apple TV 4 though. And the solution worked.

UnoTellyService

62 posts

Master Geek
+1 received by user: 40

Trusted

Unotelly

#1435846 27-Nov-2015 10:19

kingjj: Not using UnoTelly but having similar issue with another provider. Tracert's done on 2D Fibre:

Thanks kingjj

Dynamike

167 posts

Master Geek
+1 received by user: 52

#1435865 27-Nov-2015 10:40

Here are my Tracert's

ISP: Spark ADSL
Location: Wanganui
Unotelly Auckland Servers

Tracing route to 93.184.215.248 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms TP-LINK.Home [192.168.1.1]
2 132 ms 119 ms 127 ms 122-58-236-1.jetstream.xtra.co.nz [122.58.236.1]
3 * * * Request timed out.
4 131 ms 127 ms 123 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 134 ms 130 ms 131 ms 210.55.202.213
6 131 ms 134 ms 127 ms ae1-10.tkbr12.global-gateway.net.nz [202.50.232.37]
7 251 ms 258 ms 255 ms xe-0-0-7-3.sjbr3.global-gateway.net.nz [202.50.232.18]
8 255 ms 247 ms 262 ms ae0.pabr5.global-gateway.net.nz [203.96.120.74]
9 285 ms 288 ms 287 ms ae60.edge1.SanJose2.Level3.net [4.28.172.109]
10 261 ms 211 ms 262 ms ae-3-80.ear1.SanJose3.Level3.net [4.69.152.151]
11 257 ms 266 ms 259 ms 192.229.129.238
12 268 ms 262 ms 262 ms 93.184.215.248

Trace complete.

Tracing route to 68.232.34.133 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms TP-LINK.Home [192.168.1.1]
2 122 ms 115 ms 120 ms 122-58-236-1.jetstream.xtra.co.nz [122.58.236.1]
3 * * * Request timed out.
4 135 ms 135 ms 128 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 134 ms 131 ms 130 ms 210.55.202.213
6 129 ms 135 ms 131 ms ae1-10.tkbr12.global-gateway.net.nz [202.50.232.37]
7 254 ms 285 ms 281 ms xe-0-0-7-3.sjbr3.global-gateway.net.nz [202.50.232.18]
8 201 ms 248 ms 258 ms ae0.pabr5.global-gateway.net.nz [203.96.120.74]
9 293 ms 291 ms 291 ms ae-8.r06.plalca01.us.bb.gin.ntt.net [129.250.203.41]
10 440 ms 438 ms 438 ms ae-15.r02.snjsca04.us.bb.gin.ntt.net [129.250.4.119]
11 285 ms 268 ms 264 ms ae-11.r22.snjsca04.us.bb.gin.ntt.net [129.250.3.120]
12 317 ms 313 ms 335 ms ae-7.r23.asbnva02.us.bb.gin.ntt.net [129.250.6.238]
13 * 441 ms * ae-2.r23.amstnl02.nl.bb.gin.ntt.net [129.250.6.163]
14 446 ms 438 ms 437 ms ae-2.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.159]
15 413 ms 422 ms 412 ms 83.231.213.82
16 414 ms 415 ms 415 ms 68.232.34.133

Trace complete.

Tracing route to 68.232.45.253 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms TP-LINK.Home [192.168.1.1]
2 118 ms 130 ms 134 ms 122-58-236-1.jetstream.xtra.co.nz [122.58.236.1]
3 * * * Request timed out.
4 124 ms 130 ms 134 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 128 ms 130 ms 127 ms 210.55.202.213
6 157 ms 156 ms 148 ms xe0-0-4.sgbr3.global-gateway.net.nz [122.56.127.94]
7 149 ms 134 ms 156 ms ae7-10.sebr4.global-gateway.net.nz [122.56.127.214]
8 157 ms 152 ms 149 ms 110.232.179.21
9 158 ms 152 ms 149 ms 68.232.45.253

Trace complete.

1 | 2 | 3 | 4