I've discovered a fairly substantial pattern to the ongoing packet loss currently exhibited.
First, some statements of fact, all based on rigorous and methodical testing:
- While the particular Netflix video server will vary from session to session, with 100% consistency, the destination Netflix IP is always Los Angeles-based (as indicated by the following naming convention: laxZZZ.ix.nflxvideo.net—"ZZZ" being a numeric-based variable).
- Most, but not all, of the time, I specifically receive lax008.ix.nflxvideo.net.
- Within lax008.ix.nflxvideo.net, there are 100 separate possibilities, each with their own IP (C001 through C100). Consider these two examples: c001.lax008.ix.nflxvideo.net [23.246.24.130]; c051.lax008.ix.nflxvideo.net [23.246.25.130]
- C001 through C050 all map to an IP in the range of 23.246.24.XXX, first passing through a penultimate hop of 23.246.24.10. (Feel free to test this.)
- C051 through C100 all map to an IP in the range of 23.246.25.XXX, first passing through a penultimate hop of 23.246.25.10. (Again, try it.)
With that long string of findings out of the way, here were my main observations:
- All 23.246.25.XXX IPs consistently lead to packet loss, and always during the final hops.
- All 23.246.24.XXX IPs consistently lead to 0% packet loss.
I am hopeful that my findings will prove to be consistent by others who currently are encountering this issue.
