Hi!
The PingPlotter data capture here implies a complete loss of connectivity to google.ca. Hops 4-7 all have the exact same pattern, which implies that the problem originates at hop 4 or before. Hop 3 isn't normally a good responder (in the data you sent at least). This means we can't say *too* much about hop 3, but the pattern at hop 3 is different during the period of outage. This implies (but does not prove) that hop 3 was involved.
Hop 2 is non-responsive, and hop 1 is inside your network. Hop 1 looks like maybe you're connected via WiFi with your computer, but that connection is pretty good. Hop 2 is non-responsive, but that's not any indication of problems (discussion / examples here:
http://www.pingman.com/kb/24).
Based on this short time period (20 minutes) and no description of the symptoms you were seeing during this period, I would *guess* that there's something a bit unreliable about your DSL connection to your provider (you're on DSL, right?).
Things to ask, though:
* What problem are you trying to solve, with which application(s)? What symptoms are you seeing?
* Were the symptoms you were seeing similar to the data you posted in PingPlotter? Did you have a total loss of connectivity for a couple of minutes? It's important to correlate the PingPlotter data to the actual symptoms so you know you're chasing the right thing.
* Does PingPlotter normally show this type of packet loss pattern when you're experiencing symptoms?
We cover those questions, and walk through some best practices of building a case here:
https://www.pingplotter.com/netnirvanaI would recommend using the worksheet there to help isolate and document the problem. You might call your ISP next and see if they seen anything wrong from their end (signal strength, noise, etc) - it helps if you can clearly describe the problem and how it affects you (see the worksheet for that), and then you can document the call with them so if there's any followup needed you have a trail to help expedite conversation.
Hope that helps.
Best wishes,
Pete