LATENCY ISSUES - SOFTLAYER
|
Ok... so the hop you listed is not actually a problem... It's what they call "traffic mitigation" and it is common on congested nodes. If you notice however, that there is 0 packet loss and 420 hops. That means all hops were sent and received without issue. The latency there looks good as well.
There's still something up with your first hop, which as you said you'll have to take up with your ISP. Perhaps the hardware is failing or something and clearing that up will clear up your issues.... but I see early issues in all of your traces. |
|
|
hmm ok maybe its just my understand of how this works that wrong, but looking at this line in particular:
------------------- Host --------------- % | Sent | Recv | Best | Avrg | Wrst | Last | | po1.fcr01.sr03.sng01.networklayer.com - 94 | 45 | 3 | 7 | 23 | 46 | 7 | Isnt there some issue where with 45 packages sent and only 3 received? IGN: Buhh_XXXXXXXX
| |
|
You can't really look at a single hop. You have to look at the whole trace to understand what is going on.
If it were real packet loss, or a real problem, all the nodes after that node would show similar signs of packet loss or latency, etc. Because it is only that node and none after, it is just that node dropping the lower priority packets addressed to it. Think of it like this.... I get you and 10 of your friends together and have you all stand in a line.. You next to me, someone next to you, someone else next to them, etc... all the way down the line. Now, I hand you an envelope. The instructions are, if the envelope has your name on it, you are to open it, respond to it, then hand it back up the line to me. If the envelope does NOT have your name on it, you pass it to the person next to you. This is basically how the packets work, and how the trace works. They hand packets from one to the other only opening the ones addressed to them. In the case of the hop you posted, it is a busy node. It doesn't have time to directly respond to packets that are low priority, instead favoring other things (like passing packets on). In this case, if it gets one of those envelopes addressed to it, it just drops it on the ground unless it has time to respond. If there are packets waiting to go through, they instead favor passing those on. That is what "traffic mitigation" is. They favor some packets more than others, and generally only drop packets that are specifically addressed to themselves, never packets addressed to someone else. |
|
|
nice thorough reply, much appreciated it. makes sense.
Ill bring up the issue with the ISP in general, give some of these data sets and see if they come up with a solution to the issues of general package loss. your help much appreciated. IGN: Buhh_XXXXXXXX
| |
|
Hopefully this tread is not dead yet
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 182.55.225.2 - 0 | 400 | 400 | 3 | 20 | 549 | 26 | | an-ts-br05.starhub.net.sg - 0 | 400 | 400 | 3 | 21 | 1281 | 5 | | 183.90.44.177 - 0 | 400 | 400 | 2 | 17 | 1311 | 3 | | ip-202-147-32-138.asianetcom.net - 0 | 400 | 400 | 2 | 19 | 1280 | 3 | | ae2-0.gw2.sin0.asianetcom.net - 0 | 400 | 400 | 3 | 20 | 1304 | 5 | | SFL-0022.asianetcom.net - 1 | 393 | 391 | 4 | 14 | 710 | 6 | | ae6.dar01.sr03.sng01.networklayer.com - 1 | 397 | 396 | 4 | 14 | 708 | 6 | | po1.fcr01.sr03.sng01.networklayer.com - 32 | 177 | 121 | 0 | 11 | 56 | 11 | | 5b.cb.0cd8.ip4.static.sl-reverse.com - 1 | 396 | 395 | 4 | 18 | 656 | 95 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider here's my. Constant Dc evry 5-6 mins, 12.47am, 09th Jan. I have also sent 3 traces to Starhub , yet to reply me. Thanks Last edited by Kopiooo#3851 on Jan 8, 2016, 11:48:58 AM
|
|
















