Hi Harinder,

Thanks for getting in touch - and thank you for using PingPlotter!

The packet loss that you're seeing at hop #7 doesn't look like it may be the root cause of any issues here. Although you've got a bit of packet loss at your final destination (around .8%), the pattern of packet loss at hop #7 (the 43% or so) isn't all carrying through your route.

Some devices aren't fond of timed out ICMP requests (ICMP requests where the TTL = 0 after reaching them), and may down prioritize them (or not respond to them at all) to make way for other network traffic. When this happens, it can show up as packet loss at that hop in PingPlotter - but as long as the packet loss or latency isn't carrying through to the next hop (or to the final destination in your route), then it's usually nothing you need to factor into your troubleshooting efforts. We cover this idea in a bit more detail here:

http://www.pingman.com/kb/5

It's tough to speculate on what may be causing your issue with the limited amount of information we have here. If you'd like, feel free to send over a pp2 file of any PingPlotter results you may have (via the "File" -> "Export sample set" or "File" -> "Share" option in program), along with a description of the problem you're troubleshooting - and we'd be happy to review that information and offer any guidance we can!

In the meantime, we've got a great guide that goes over some best practices and strategies for using PingPlotter to troubleshoot network issues - which also provides some tips on how to communicate your findings to a provider. Have a look here:

http://www.pingplotter.com/fix-your-network

If you should find yourself with any questions, or needing any other assistance - please let us know!

Best wishes,

-Gary