Hey Jim,

Thank you for the additional details - this helps out quite a bit.

If you were experiencing buffering during the period that these results were taken from - I think we can pretty much rule out anything in your network being the cause of this issue at this point. Both traces you've submitted here look good, and neither show indication of any problems. The packet loss you're seeing in your trace to Netflix isn't anything that would cause you trouble here - the "Destination Unreachable" message you're getting there is a result of the last hop not responding to ICMP echo requests (something we discuss more in depth here - http://www.nessoft.com/kb/8). The hop right before it (#19), looks great.

That being said, this is something you'd now probably need to get in touch with your ISP, or Netflix (or both) about. The issue doesn't appear to be anything on your end - so it's something that they would need to investigate further. If you provide them the same data that you've provided here for us, it should allow them to start troubleshooting and begin narrowing down what could be causing this.

If you're looking for some best practices to employ when contacting them - please keep our Network Nirvana guide in mind (http://www.pingplotter.com/netnirvana) - as it goes over some of the best methods for making the process of navigating a customer service structure a bit faster, and more efficient.

Best wishes,

-Gary