TekSavvy → Re: [Cable] Customer Service Review

Teksavvy ticket has been in limbo due to support staff being off and apparently my computer is not reachable via ICMP ping.

I'm able to reach the computer via site's with external testing tools. I'll put it out there, 24.212.219.113. Anyone not able to reach it?

Not working from TSI cCable.

Pinging 24.212.219.113 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 24.212.219.113:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Weird how it works for others.

Pinging 24.212.219.113 with 32 bytes of data:
Reply from 24.212.219.113: bytes=32 time=10ms TTL=54
Reply from 24.212.219.113: bytes=32 time=10ms TTL=54
Reply from 24.212.219.113: bytes=32 time=10ms TTL=54
Reply from 24.212.219.113: bytes=32 time=10ms TTL=54

Ping statistics for 24.212.219.113:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 10ms, Average = 10ms

Pings fine from here at work on Bell FTTH.

But for kicks, I remoted into my home computer which is on TSI DSL, and I cannot ping it. This is pretty weird.

Pinging 24.212.219.113 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 24.212.219.113:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Tracing route to 24-212-219-113.cable.teksavvy.com [24.212.219.113]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.253
2 4 ms 4 ms 4 ms lo0-0-lns02-tor2.teksavvy.com [206.248.155.244]
3 5 ms 5 ms 5 ms ae1-2140-bdr01-tor2.teksavvy.com [69.196.136.138]
4 6 ms 5 ms 6 ms ae12-0-bdr01-tor.teksavvy.com [206.248.155.10]
5 5 ms 5 ms 4 ms ae0-2160-agg01-tor.teksavvy.com [192.171.59.67]
6 5 ms 6 ms 10 ms 104-195-128-70.cpe.teksavvy.com [104.195.128.70]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.

This is the tracert from Bell to your IP. There's a hop that times out, but it reaches.

Tracing route to 24-212-219-113.cable.teksavvy.com [24.212.219.113]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms router.asus.com [192.168.1.1]
2 1 ms 1 ms 1 ms 10.11.6.177
3 1 ms 1 ms 1 ms 10.178.206.66
4 1 ms 1 ms 1 ms 10.178.206.67
5 9 ms 7 ms 7 ms tcore3-toronto63_2-4-0-1.net.bell.ca [64.230.101.120]
6 3 ms 7 ms 7 ms tcore3-torontoxn_hundredgige0-8-0-0.net.bell.ca [64.230.50.7]
7 2 ms 1 ms 1 ms dis6-torontoxn_2-0-0.net.bell.ca [64.230.97.149]
8 1 ms 1 ms 1 ms 204.101.5.250
9 1 ms 1 ms 1 ms ae1-0-agg01-tor2.teksavvy.com [206.248.155.14]
10 2 ms 3 ms 2 ms 104-195-128-214.cpe.teksavvy.com [104.195.128.214]
11 * * * Request timed out.
12 10 ms 10 ms 10 ms 24-212-219-113.cable.teksavvy.com [24.212.219.113]

I'm seeing the same thing as HiVolt, from Teksavvy VDSL:

--- 24.212.219.113 ping statistics ---
50 packets transmitted, 0 packets received, 100% packet loss
 

From OVH Montreal:

--- 24.212.219.113 ping statistics ---
50 packets transmitted, 50 received, 0% packet loss, time 49075ms
rtt min/avg/max/mdev = 16.168/16.590/17.373/0.263 ms
 

I wonder if TSI customers are not allowed to ping other TSI customers, or any TSI IP can't ping another... something like that...

Thank you. I've reset the modem, picked up new IP 23.233.2.212. Is it still unreachable via a Teksavvy Cable connection?

That IP seems to work from Teksavvy VDSL now:

--- 23.233.2.212 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 23.631/43.672/107.194 ms
 

Thank you.

Works from here, too, even though the jitter is crazy:

Pinging 23.233.2.212 with 32 bytes of data:
Reply from 23.233.2.212: bytes=32 time=47ms TTL=57
Reply from 23.233.2.212: bytes=32 time=32ms TTL=57
Reply from 23.233.2.212: bytes=32 time=132ms TTL=57
Reply from 23.233.2.212: bytes=32 time=42ms TTL=57

Ping statistics for 23.233.2.212:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 132ms, Average = 63ms

It's reachable from my TSI VDSL now as well.