
Originally Posted by
Kuo
6 12 ms 1778 ms 1787 ms 208.74.223.62
That is not a good sign right there. Not familiar with Dunklin Communications, but it looks like things are not going well in the Arkansas area. Two responses took over 1.75 seconds to respond right after taking 0.012 seconds. That's enough jitter to combine with latency in Canada to cause a timeout and retransmit request. If it happens enough, you could get flagged by the TCP/IP congestion control to slow your transmission down, and then it's downhill from there until the congestion subsides.
Might want to run a few more traces, possibly some rounds of extended pings to submit to your ISP for review. Will help your case if you can get snapshots also during off-peak times that are clean so there is a baseline and a fouled up state to compare. If you also run a few tests against some normal sites like Google/YouTube or Yahoo as well and see some funkiness there as well, submitting those reports with the XIV data can be a motivator for them to get involved. Hopefully it will peak someone's interest at Tier3 or higher to escalate the issue for further investigation.
Won't lie... your mileage may vary on just how responsive they will be to your request for assistance, but if you are persistent enough you can get them to take action. After all, you are their paying customer... sometimes you may have to remind them of that fact (try to do it nicely though). I finally got someone committed to my issues with my gateway this weekend... third ticket I filed against that one issue (said something about it may be time to look at AT&T's 6Mb special offer if they can't figure this thing out). A lead tech in Tier3 actually called me back after he ran some tests himself and confirmed my findings on his end. They think they've finally pinned down the issue in the upstream and are sending a bucket truck Tuesday to work at the pole to hopefully fix that problem. It's the last link in the chain to a more perfect line to SE.
This can and does work if you are properly prepared and are persistent about getting through to Tier3 or higher support... those guys you call at the help desk are powerless to do anything past your modem. You need to get past them... ask for a supervisor if they can't take you to Tier3. You need someone who can at least escalate you to a higher department. Last fall when I called about these same issues I found with Cogentco, I had to be pretty stern in pushing for them to connect me to Tier3...they wanted me to reboot and have a tech come on-site first. Once I finally got sent to T3 and I told them where to trace to (my server's IP at the time) and they were able to see it themselves, they gave me an email to forward all my trace/ping data showing the good, bad, and the ugly. Took them a few months of moving my route all over the place, but they finally nailed that end down pretty tight. Now I just have my first hop left for them to address:
Code:
22:05:25.49 Sat 03/08/14
Tracing route to 199.91.189.25 over a maximum of 30 hops
1 2 ms <1 ms 1 ms LPTSRV [10.10.100.1]
2 1805 ms * * cpe-098-025-064-001.sc.res.rr.com [98.25.64.1]
3 10 ms 12 ms 13 ms cpe-024-031-198-005.sc.res.rr.com [24.31.198.5]
4 25 ms 23 ms 25 ms xe-7-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.40]
5 31 ms 31 ms 33 ms 107.14.19.44
6 29 ms 31 ms 38 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 32 ms 31 ms 31 ms te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209]
8 38 ms 34 ms 41 ms be2177.ccr22.dca01.atlas.cogentco.com [154.54.41.206]
9 41 ms 40 ms 41 ms be2149.ccr22.jfk02.atlas.cogentco.com [154.54.31.126]
10 44 ms 44 ms 45 ms be2106.ccr21.alb02.atlas.cogentco.com [154.54.3.50]
11 65 ms 65 ms 66 ms be2088.ccr21.ymq02.atlas.cogentco.com [154.54.43.17]
12 60 ms 60 ms 64 ms 38.122.42.34
13 46 ms 43 ms 49 ms 192.34.76.10
14 44 ms 45 ms 45 ms 199.91.189.242
15 43 ms 45 ms 44 ms 199.91.189.25
That is from Florence, SC... and yes, when things are good I can consistently have less then a 70ms (0.07 seconds) response time to my Midgard server in Montreal Canada--without using BattlePing or something similar. My problem now is isolated to getting through that gateway at 98.25.64.1--when it goes south, everything I do online gets knackered up. It is a major one that handles traffic for a TON of people in multiple regions, so who knows just how many are affected (the Ralegh/Charlotte circuits we go through have been having problems for some time now, could be related). If they manage to fix this weirdness here in Florence, hopefully it will set a model for them to follow elsewhere for other regions as well, ultimately clearing up a lot of problems in the long run. <crossing fingers>
Never know just how far you may get until you try.