I suddenly have a problem with Netflix. It won't work on any of my devices (2 TV's, 2 computers, one iPad, 2 iPhones). Giving various errors about needing to reset router etc, all of which I have tried. Talked to both Netflix and ISP (Verizon fios), both blaming each other. Netflix wants me to go to fast.com, which shows "0" download speed, even though my internet is otherwise working fine.But here is the kicker. When I log ion to the VPN (GlobalProtect) on my laptop, then I get 37 Mbps from fast.com, and Netflix actually is showing some signs of life (ultimately crashes because they don't support streaming across VPN). Then I log out of VPN and shut down the laptop, and again I get nothing from Netflix. Ultimately I think this is a VPN question so does anyone have any ideas???
Netflix problems even with VPN turned off
- Thread starter duursma
- Start date
Solution
C:\Users\Ron>tracert www.netflix.com
Tracing route to www.us-east-1.prodaa.netflix.com [52.206.171.69]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 17 ms 11 ms 11 ms lo0-100.PITBPA-VFTTP-304.verizon-gni.net [108.39.138.1]
3 9 ms 14 ms 15 ms B3304.PITBPA-LCR-21.verizon-gni.net [100.41.217.26]
4 * * * Request timed out.
5 * * * Request timed out.
6 16 ms 17 ms 16 ms 0.et-9-3-0.GW13.IAD8.ALTER.NET [140.222.235.35]
7 17 ms 17 ms 17 ms neustar-gw.customer.alter.net [152.179.50.58]
8 * * * Request timed out.
9 * * * Request timed out.
10 44 ms 38 ms 24 ms 54.239.110.129
11 18 ms 16 ms 18 ms 54.239.108.63
12 47 ms 25 ms 22 ms 52.93.24.46
13 22 ms 20 ms 17 ms 52.93.24.41
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\Users\Ron>pathping www.netflix.com
Tracing route to www.us-east-1.prodaa.netflix.com [52.207.67.53]
over a maximum of 30 hops:
0 Diablo.fios-router.home [192.168.1.157]
1 192.168.1.1
2 lo0-100.PITBPA-VFTTP-304.verizon-gni.net [108.39.138.1]
3 B3304.PITBPA-LCR-22.verizon-gni.net [100.41.217.30]
4 * * *
Computing statistics for 75 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Diablo.fios-router.home [192.168.1.157]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% lo0-100.PITBPA-VFTTP-304.verizon-gni.net [108.39.138.1]
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% B3304.PITBPA-LCR-22.verizon-gni.net [100.41.217.30]
Trace complete.
Tracing route to www.us-east-1.prodaa.netflix.com [52.206.171.69]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 17 ms 11 ms 11 ms lo0-100.PITBPA-VFTTP-304.verizon-gni.net [108.39.138.1]
3 9 ms 14 ms 15 ms B3304.PITBPA-LCR-21.verizon-gni.net [100.41.217.26]
4 * * * Request timed out.
5 * * * Request timed out.
6 16 ms 17 ms 16 ms 0.et-9-3-0.GW13.IAD8.ALTER.NET [140.222.235.35]
7 17 ms 17 ms 17 ms neustar-gw.customer.alter.net [152.179.50.58]
8 * * * Request timed out.
9 * * * Request timed out.
10 44 ms 38 ms 24 ms 54.239.110.129
11 18 ms 16 ms 18 ms 54.239.108.63
12 47 ms 25 ms 22 ms 52.93.24.46
13 22 ms 20 ms 17 ms 52.93.24.41
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\Users\Ron>pathping www.netflix.com
Tracing route to www.us-east-1.prodaa.netflix.com [52.207.67.53]
over a maximum of 30 hops:
0 Diablo.fios-router.home [192.168.1.157]
1 192.168.1.1
2 lo0-100.PITBPA-VFTTP-304.verizon-gni.net [108.39.138.1]
3 B3304.PITBPA-LCR-22.verizon-gni.net [100.41.217.30]
4 * * *
Computing statistics for 75 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Diablo.fios-router.home [192.168.1.157]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% lo0-100.PITBPA-VFTTP-304.verizon-gni.net [108.39.138.1]
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% B3304.PITBPA-LCR-22.verizon-gni.net [100.41.217.30]
Trace complete.
- Oct 11, 2014
- 34,884
- 3,323
- 146,290
Not seeing anything there per se. However, we also do not know what past results may have been.
Try again but target some other websites: E.g., Google, Microsoft, Amazon.
The intent is to see how much those times vary from the Netflix times.
Overall not sure of what to suggest.
Did come across the following link:
https://www.engadget.com/2017/11/29/netflix-speed-test/
May be some Netflix vs Verizon battle with each trying to blame the other.
Try again but target some other websites: E.g., Google, Microsoft, Amazon.
The intent is to see how much those times vary from the Netflix times.
Overall not sure of what to suggest.
Did come across the following link:
https://www.engadget.com/2017/11/29/netflix-speed-test/
May be some Netflix vs Verizon battle with each trying to blame the other.
Thanks. I still think the big mystery is why fast.com gives 0, except when I'm on the VPN. That zero sounds more like a refused/blocked connection rather than just lack of throughput.
Here is amazon:
C:\>tracert www.amazon.com
Tracing route to e15316.ci.akamaiedge.net [104.100.154.48]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 7 ms 8 ms lo0-100.PITBPA-VFTTP-304.verizon-gni.net [108.39.138.1]
3 13 ms 15 ms 6 ms B3304.PITBPA-LCR-22.verizon-gni.net [100.41.217.30]
4 * * * Request timed out.
5 * * * Request timed out.
6 20 ms 17 ms 17 ms 0.ae4.GW1.EWR19.ALTER.NET [140.222.231.91]
7 20 ms 17 ms 17 ms a104-100-154-48.deploy.static.akamaitechnologies.com [104.100.154.48]
Trace complete.
C:\>pathping www.amazon.com
Tracing route to e15316.ci.akamaiedge.net [104.100.154.48]
over a maximum of 30 hops:
0 Diablo.fios-router.home [192.168.1.157]
1 192.168.1.1
2 lo0-100.PITBPA-VFTTP-304.verizon-gni.net [108.39.138.1]
3 B3304.PITBPA-LCR-22.verizon-gni.net [100.41.217.30]
4 * * *
Computing statistics for 75 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Diablo.fios-router.home [192.168.1.157]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% lo0-100.PITBPA-VFTTP-304.verizon-gni.net [108.39.138.1]
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% B3304.PITBPA-LCR-22.verizon-gni.net [100.41.217.30]
Trace complete.
Here is amazon:
C:\>tracert www.amazon.com
Tracing route to e15316.ci.akamaiedge.net [104.100.154.48]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 7 ms 8 ms lo0-100.PITBPA-VFTTP-304.verizon-gni.net [108.39.138.1]
3 13 ms 15 ms 6 ms B3304.PITBPA-LCR-22.verizon-gni.net [100.41.217.30]
4 * * * Request timed out.
5 * * * Request timed out.
6 20 ms 17 ms 17 ms 0.ae4.GW1.EWR19.ALTER.NET [140.222.231.91]
7 20 ms 17 ms 17 ms a104-100-154-48.deploy.static.akamaitechnologies.com [104.100.154.48]
Trace complete.
C:\>pathping www.amazon.com
Tracing route to e15316.ci.akamaiedge.net [104.100.154.48]
over a maximum of 30 hops:
0 Diablo.fios-router.home [192.168.1.157]
1 192.168.1.1
2 lo0-100.PITBPA-VFTTP-304.verizon-gni.net [108.39.138.1]
3 B3304.PITBPA-LCR-22.verizon-gni.net [100.41.217.30]
4 * * *
Computing statistics for 75 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Diablo.fios-router.home [192.168.1.157]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% lo0-100.PITBPA-VFTTP-304.verizon-gni.net [108.39.138.1]
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% B3304.PITBPA-LCR-22.verizon-gni.net [100.41.217.30]
Trace complete.
- Oct 11, 2014
- 34,884
- 3,323
- 146,290
Well, the cynic in me would suspect that fast.com is not being permitted/allowed via Verizon.
ISP's want tools that show them to be "fast".
Netflix's tool or any third party tool may not do that.....
Must be a fair, objective, and transparent test tool.
Makes it difficult for providers if the performance results are poor or "vary" with the content source.
In any case, what ever is happening is likely outside of your home network...
Not sure (full disclosure) what else to suggest.
Perhaps some other forum member will spot something I have missed or overlooked.
ISP's want tools that show them to be "fast".
Netflix's tool or any third party tool may not do that.....
Must be a fair, objective, and transparent test tool.
Makes it difficult for providers if the performance results are poor or "vary" with the content source.
In any case, what ever is happening is likely outside of your home network...
Not sure (full disclosure) what else to suggest.
Perhaps some other forum member will spot something I have missed or overlooked.
TRENDING THREADS
-
[SOLVED] Is it safe to use a recapped PSU for a long time ?- Started by zwtch_17
- Replies: 5
-
-
Discussion What's your favourite video game you've been playing?- Started by amdfangirl
- Replies: 3K
-
-
News Microsoft updates Windows 11 24H2 requirements, CPU must support SSE4.2 or the OS will not boot- Started by Admin
- Replies: 19
Latest posts
-
Question New Build, Fans Running, RGB working, no mouse, no keyboard, no display- Latest: drivinfast247
-
-
-
Facebook
Twitter
Instagram