Netflix no longer streaming

I also have the Nokia gateway and it is on firmware 1.2201.00.0324 which it has been on for some time now. I have been streaming Netflix this evening on a iPad Pro and I had it up on my MacBook Pro earlier. No problems streaming Netflix here in east TN. Since there was work on either the T-Mobile network or Netflix it might be necessary to clear the cache on the Netflix app and try it again. I did not see the disruption to Netflix here during the period where others did. I don't know what is different to account for that but it has continued to work on all the devices I checked here. My gateway has been up  without a reboot for 38 days and 9 hours and change. I run two parallel SSIDs and roughly 24 devices on the network so it does get exercise but just keeps on chugging along. 

Howdy neighbor @iTinkeralot,  I'm in E TN as well and I have been having the same issues. It started 3 days ago with my Roku devices and my Samsung TV. I'm using the Sagemcon gateway with the latest firmware like the others. I have gotten nowhere with Netflix or T-Mobile on a resolve for this. The biggest part that sucks, is I just convinced the wife to kick Spectrum to the curb and go with this. They dont fix this, I maybe kicking T-Mobile to the curb after being with Sprint/Tmobile for over 20 yrs.

Another thing that's interesting is that I cannot see this forum while I'm at home as well. I discovered that after I got to work and here I am seeing it. Starting to question some fishy stuff going on.

That is curious. It may just be due to users with the apps on the smart TVs in part or just because that is what they tend to stream on. So far the problem does not seem to present itself here. I know my wife and daughter have been streaming downstairs either with the Fire Stick or with the Xbox to our TV which is not a "smart" TV. It may not be smart but it works. At any rate I have seen no issue streaming Netflix on my iPad Pro or my M1 MacBook Pro. I run the Netflix app on the iPad Pro but on my MacBook Pro I just open Safari and it pops right up. I just upgraded to the 14" M1 MacBook Pro via the black Friday sale at BestBuy. What a huge difference over my old 2014 MacBook Pro. 

So, it is curious and hard to say what causes that issue. I have had the Nokia gateway since January 2012 at the later part of the BETA period and it just continues to carry on. I am glad I don't have the Arcadyan or Sagemcon as managing the gateway with the mobile app is a pain in the backside. The Nokia still allows the web GUI and it is by far a MUCH more friendly way to do it. More options with the Nokia gateway as well. I only run the T-Mobile gateway and have not added any mesh solution or extenders etc… The wireless on the Nokia gets the job done here over the upstairs in most places even from the basement window. There are a couple of near dead zones but not bad. Simpler and less expensive than going into all the extra when I don't really need it.

The part I suspected yesterday and still do is the authentication with secure HTTP. When I see what you posted for, what I suspect to be working vs not working is the server responding on port 443. The failure takes place or seems to before the user can even get authenticated via the HTTPS connection to the Netflix server. Watch the front end of the session closely. I will have to run a capture later as I don't have the time right now but I know it is working here so I can at least record the initial setup and know what to expect for the initial setup of the session with the server. Without hard data I am just speculating.

That is another factor I have had some suspicions about. Users that use additional routers vs those that do not. I have ONLY the Nokia gateway running. It works. Is the gateway hardware a factor OR additional router or mesh connected to the gateway part of the equation? I don't know as there are not enough data points to draw additional conclusions or a theory that has some substance based upon data. It could still be in the T-Mobile IPv6 network vs at the edge.

From that seeing the 443 time out tells me it appears to be excessive delay on the initial authentication setup. At least that is what I suspected. 

Here are all the requests that I see in order:

android.prod.cloud.netflix.com = Successful connection 

nrdp60-appboot.netflix.com = Successful connection

occ-0-7094-90.1.nflxso.net = Failed SYN packet, no response on T-Mobile IP

api-global.netflix.com = Successful connection

secure.netflix.com = Successful connection

occ-0-7094-90.1.nflxso.net = Failed SYN packet, no response on T-Mobile IP

ichnaea.netflix.com = Successful connection

Testing to occ-0-7094-90.1.nflxso.net from T-Mobile home gateway:

curl -v https://occ-0-7094-90.1.nflxso.net
*   Trying 208.54.15.202:443...
* connect to 208.54.15.202 port 443 failed: Operation timed out

Testing to occ-0-7094-90.1.nflxso.net from Comcast IP:

curl -v https://occ-0-7094-90.1.nflxso.net
*   Trying 208.54.15.203:443...
* Connected to occ-0-7094-90.1.nflxso.net (208.54.15.203) port 443 (#0)

I hope T-Mobile can resolve this ASAP as it has been many days with no progress

That specific information needs to get to the engineers so they can see for themselves. That makes it pretty obvious the HTTPS did not connect.

Thanks so much for taking the packet captures from both sources. I am not sure what gateways were used for those two or if it has any bearing on the problem but clearly the HTTPS session does not complete authentication. I could have taken captures here but mine seems to be working but have the Nokia gateway. We could be in different regions for all I know and that may have a bearing on the problem as well. If it is due to firmware on the gateways then it might take some time for them to push the update out. Who knows how long that will take to complete given you can't go get it.

Agreed, nothing better than seeing packets. I have the Arcadyan KVD21 gateway Firmware 1.00.16 on the East Coast.