Traceroute fun?
Links: home · search · speed test · login · more ·

---

 
Links: Reply New Topic
Forums » Canadian » Cogeco » Traceroute fun?

alamarco @ 26th Oct 11:42PM:
Traceroute fun?

In light of Fireblade's comment, I'm wondering if maybe this problem of mine is fixable.

A ping to crunchyroll.com:
PING crunchyroll.com (65.49.43.41): 56 data bytes64 bytes from 65.49.43.41: icmp_seq=0 ttl=54 time=138.527 ms64 bytes from 65.49.43.41: icmp_seq=1 ttl=54 time=124.864 ms64 bytes from 65.49.43.41: icmp_seq=2 ttl=54 time=114.618 ms64 bytes from 65.49.43.41: icmp_seq=3 ttl=54 time=116.933 ms64 bytes from 65.49.43.41: icmp_seq=4 ttl=54 time=113.651 ms --- crunchyroll.com ping statistics ---5 packets transmitted, 5 packets received, 0.0% packet lossround-trip min/avg/max/stddev = 113.651/121.719/138.527/9.282 ms
An average ping of 121ms.

A traceroute of crunchyroll.com:
traceroute to crunchyroll.com (65.49.43.41), 64 hops max, 52 byte packets 1 unknown (192.168.1.1) 1.315 ms 1.056 ms 0.960 ms 2 * * * 3 d226-4-209.home.cgocable.net (24.226.4.209) 15.719 ms 13.853 ms 12.994 ms 4 113-0-226-24.cgocable.net (24.226.0.113) 15.616 ms 23.519 ms 14.720 ms 5 gw-he.torontointernetxchange.net (198.32.245.112) 26.264 ms 14.821 ms 15.964 ms 6 10gigabitethernet1-2.core1.nyc5.he.net (72.52.92.165) 43.617 ms 30.631 ms 29.536 ms 7 10gigabitethernet1-4.core1.nyc1.he.net (72.52.92.153) 44.218 ms 45.310 ms 42.599 ms 8 10gigabitethernet1-1.core1.nyc4.he.net (72.52.92.45) 32.812 ms 31.084 ms 42.493 ms 9 10gigabitethernet3-1.core1.sjc2.he.net (72.52.92.25) 111.554 ms 112.580 ms 110.034 ms10 * * *
After 9, it's *'s all the way until it times out.

ping to cp71915.edgefcs.net:
PING a116.vi5g5.akafms.net (72.246.43.111): 56 data bytes64 bytes from 72.246.43.111: icmp_seq=0 ttl=123 time=16.005 ms64 bytes from 72.246.43.111: icmp_seq=1 ttl=123 time=18.521 ms64 bytes from 72.246.43.111: icmp_seq=2 ttl=123 time=18.131 ms64 bytes from 72.246.43.111: icmp_seq=3 ttl=123 time=16.291 ms64 bytes from 72.246.43.111: icmp_seq=4 ttl=123 time=15.849 ms --- a116.vi5g5.akafms.net ping statistics ---5 packets transmitted, 5 packets received, 0.0% packet lossround-trip min/avg/max/stddev = 15.849/16.959/18.521/1.132 ms
An average ping of 16 ms.

A traceroute to cp71915.edgefcs.net:
traceroute to a116.vi5g5.akafms.net (72.246.43.111), 64 hops max, 52 byte packets 1 unknown (192.168.1.1) 1.166 ms 1.055 ms 1.000 ms 2 * * * 3 d226-4-209.home.cgocable.net (24.226.4.209) 14.359 ms 14.052 ms 12.798 ms 4 102-0-226-24.cgocable.net (24.226.0.102) 14.138 ms 16.120 ms 14.380 ms 5 gw-akamai.torontointernetxchange.net (198.32.245.24) 14.177 ms 17.671 ms 15.131 ms 6 * * *
Same thing happens, after 5 it's all *'s.

Is anyone else on Cogeco experiencing this with these sites? I'm pretty sure cp71915.edgefcs.net is the video server I was told about it while asking about video issues, but the support there is so bad that I thought I'd inquire here.

The two weird spots for me are the blip at the very beginning and the end where I can't even reach the destination. To me, it seems like that end is causing a bad connection. When watching videos I find myself repeatidly pausing the video to allow buffering and a bandwidth monitor shows ~30 KB/s, sometimes even 0 KB/s.

I figure I'll find out here if this is an issue with me, the ISP, or their servers. This way I can use their lousy support as a last ditch.

Just now had a friend traceroute cp71915.edgefcs.net and his was able to complete, though still had the same blip at the beginning.

tracert cp71915.edgefcs.net Tracing route to a116.vi5g5.akafms.net [72.246.43.111]over a maximum of 30 hops:  1 * * * Request timed out. 2 42 ms 26 ms 59 ms d226-4-145.home.cgocable.net [24.226.4.145] 3 35 ms 24 ms 28 ms 26-0-226-24.cgocable.net [24.226.0.26] 4 55 ms 20 ms 71 ms gw-akamai.torontointernetxchange.net [198.32.245.24] 5 30 ms 37 ms 53 ms a72-246-43-111.deploy.akamaitechnologies.com [72.246.43.111] Trace complete.
From my buddies traceroute it seems I'm failing at the final destination. Any troubleshooting tips, possibly something Cogeco can look into?

Thanks. :)

Oh, and another piece of information that would help. This issue is a little old and I had my router setup for QOS, etc. with Tomato firmware. I've since restored the router to Tomato defaults, and QOS turned off. All the provided information is on default Tomato configuration (except for static DHCP and port forwards).

reply

---

exseven @ 27th Oct 06:29AM:
Re: Traceroute fun?

if you ping the final destination fine and the pingtime isnt out of this world i wouldnt worry about it. Some routers (read the entire thread from gixxers post) dont respond to pings, or QOS ICMP destined to itself so pass actual data a little faster
reply

---

alamarco @ 27th Oct 10:13AM:
Re: Traceroute fun?

Ah, dumb mistake by me. I knew routers would drop PING requests, but assumed this was ICMP only. The traceroute defaults to UDP, and I didn't even try ICMP since I figured it was more prone to drops. By going ICMP I was able to reach the destination.

Boy do I feel dumb. Thanks for the response, now I know it's not me.
reply

---

Thank you for using lo-fi dslreports.com - report bugs
© 99-2009 silver matrix LLC