Hey Jim,

A few things here:

When tracing to your Roku, you want to make sure that it's during a period that you're using the Roku to watch Netflix. The goal is to catch any issues as they happen - so you can see what patterns develop when issues arise (which can help out tremendously in your troubleshooting process).

The information you've submitted thus far doesn't explicitly point to any sort of obvious problem. This may be because it's a Roku-only problem (rather than your computer's problem).

This is a scenario where the timeline graphs from PingPlotter Standard (or Pro) really shine. The erratic / occasional nature of your problem makes the timeline graph a necessity for continued review of this problem. It's not a valuable use of our time (yours or mine), to attempt to troubleshoot without them.

Our "Common Network Problems" article demonstrates just how important the timeline graphs are in diagnosing and troubleshooting network issues. Have a look here:

http://www.pingplotter.com/commonnetworkproblems

The Roadmap to Network Nirvana also may prove beneficial at this stage in your troubleshooting process:

http://www.pingplotter.com/netnirvana

The information you've provided so far has been enough to make me curious about your problem, so I've asked for more information to clarify. I've also offered some advice based on my experience (via looking at thousands of PingPlotter graphs and looking at thousands of network problems). That's all I'm doing, though - exploring the problem with you - so if you don't want to follow this advice, that's fine too. Sometimes the best way to isolate problems like this is to get advice and then apply it to your situation, which is why I've been giving you ideas on how to isolate the possible problems.

Hopefully this helps get you pointed in the right direction!

-Gary