Hey brackejocke,

No problem at all!

Was this trace done during a period where you were having trouble playing the game (was it a "good" or "bad" period)?

It's still a bit tough to speculate on an hour of data, but it looks like there *may* be some bandwidth constraint between hop #1 and #2 (your pattern at hop #2 looks reminiscent of bandwidth saturation - which seems to carry through your route). You wouldn't be able to say that this is your issue for certain, though, without a bit more information. Ideally, you want your PingPlotter trace to capture a good *and* a bad period. In our experience, letting a trace run continuously for around 24 hours (or longer) is a great way to capture this.

Hopefully you find the guide helpful! If you need any other guidance, please don't hesitate to shoot any additional info/.pp2 files our way!

Best wishes,

-Gary