Start.ca → [Cable] Slow

We over provision with the 10Mbps upload, otherwise we're bound to the same profile as the incumbent. If you PM me your account # I can look at your account. Thanks.

PM'd, thanks Rocca.

even my brother just complained about high ping in WoT, and he is not on unlimited plan.

We're well below capacity at this time so if still having issues it's probably not this end, ie perhaps their end or the node.

just curious what your daily usage is DT, lol.

depends on the day

backups, netflix, downloads, etc.

i am heavy user, big time, but, i am sure that, i am not the only one, but, possibly, in top 10-20 @ Start.

Hopefully, rocca, won't confirm this

Your secret is safe with me.

lots of TV shows out tonight especially with the fall schedule starting.

Thank you sir !

We are watching that "REVENGE" show on Netflix lately, lol.

My wife started watching that, it looked interesting to me as well, and i started watching with her.

Once we put our son to sleep, we watch couple, or we play games

Same thing yesterday seems to have cleared up today.

I think, we shouldn't have issues like this any time soon, as rocca said, that another 10gb link is being installed today (correct me if i am wrong), so, hopefully, everything will be better

It's not another 10G link, it's more capacity added to the existing link. Keep in mind that still doesn't mean that our $10 unlimited package means dedicated speeds at all times.

sounds good to me

I can't seem to tell the difference here. You mentioned that it was a 10G link that is also being added but now it seems to be more capacity to the existing link.

Is a new link added for DPOI and not needed when APOI ?

CBB is logical capacity that runs on top of physical links. Once you get to the capacity of a physical link that's when you add another physical link and balance your CBB across it. Ie, you can have 2 x 10G physical links each with 6G of CBB. The CBB is the expensive part, the physical links are relatively 'cheap'.

Rocca, why is traffic to bell going via cogent. If i remember properly you peer with bell directly, don't you ?

quote:

---

tracert -w 600 67.69.184.212

Tracing route to toroon63dnsvp1.srvr.bell.ca [67.69.184.212]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms home.router [192.168.0.1]
2 12 ms 9 ms 7 ms 10.106.226.1
3 18 ms 16 ms 15 ms 24.156.137.69
4 31 ms 17 ms 18 ms gw01.etob.phub.net.cable.rogers.com [66.185.83.197]
5 18 ms 15 ms 15 ms te0-0-0-27.ccr22.yyz02.atlas.cogentco.com [38.122.69.129]
6 * 28 ms 30 ms be2119.ccr22.jfk02.atlas.cogentco.com [154.54.0.129]
7 36 ms 29 ms 29 ms be2061.ccr21.jfk05.atlas.cogentco.com [154.54.3.70]
8 29 ms 35 ms 36 ms bellnexxia.jfk05.atlas.cogentco.com [154.54.10.206]
9 43 ms 65 ms 47 ms core1-newyork83_POS10-0-0.net.bell.ca [64.230.187.37]
10 * 45 ms 57 ms tcore4-montreal02_pos0-13-0-0 [64.230.187.233]
11 49 ms 71 ms 50 ms core4-toronto63_15-0-0.net.bell.ca [64.230.147.29]
12 44 ms 42 ms 42 ms core1-toronto63_POS0-2.net.bell.ca [64.230.242.98]
13 39 ms 43 ms * dis29-toronto63_Vlan11.net.bell.ca [64.230.242.78]
14 46 ms 41 ms 39 ms toroon63dnsvp1.srvr.bell.ca [67.69.184.212]

---

That looks suspiciously like you are being routed out as if you were a Rogers customer. What is your IP address (you can omit the last part for privacy and just put it as .*

I got curious as well so I thought I'd take a look too.

My source IP is 108.168.42.*

traceroute to 184.150.172.189 (184.150.172.189), 64 hops max, 52 byte packets
1 buddynet (10.255.0.1) 0.582 ms 0.353 ms 0.237 ms
2 10.104.207.129 (10.104.207.129) 7.247 ms 6.845 ms 7.772 ms
3 24.156.150.249 (24.156.150.249) 16.181 ms 9.532 ms 11.847 ms
4 69.63.252.222 (69.63.252.222) 10.973 ms 10.158 ms 8.201 ms
5 te0-0-0-27.ccr22.yyz02.atlas.cogentco.com (38.122.69.129) 8.206 ms 9.309 ms 8.212 ms
6 be2119.ccr22.jfk02.atlas.cogentco.com (154.54.0.129) 19.723 ms 20.728 ms
be2121.mpd22.jfk02.atlas.cogentco.com (154.54.24.69) 20.205 ms
7 be2061.ccr21.jfk05.atlas.cogentco.com (154.54.3.70) 21.329 ms 21.305 ms 19.718 ms
8 bellnexxia.jfk05.atlas.cogentco.com (154.54.10.206) 20.962 ms
bellnexxia.jfk05.atlas.cogentco.com (154.54.9.46) 21.103 ms
bellnexxia.jfk05.atlas.cogentco.com (154.54.10.206) 20.840 ms
9 newcore2-newyork83_so0-1-0.net.bell.ca (64.230.187.21) 37.722 ms 33.565 ms 33.726 ms
10 tcore3-montreal02_pos0-13-0-0 (64.230.187.237) 37.489 ms 41.341 ms
tcore4-montreal02_po0-6-0-0.net.bell.ca (64.230.187.134) 37.461 ms
11 core3-toronto63_15-0-0-0.net.bell.ca (64.230.147.25) 41.262 ms 40.062 ms
core4-toronto63_15-0-0.net.bell.ca (64.230.147.29) 38.712 ms
12 agg2-toronto63_ge11-0-6 (184.150.172.189) 53.602 ms 32.559 ms 37.964 ms


From Bell's Looking Glass (Toronto Router):
traceroute to 108.168.42.x (108.168.42.x), 30 hops max, 38 byte packets
1 agg2-toronto63_ge11-0-6 (184.150.172.189) 0.246 ms 0.146 ms 0.121 ms
2 bx5-chicagodt_xe6-1-2_0 (64.230.186.253) 30.017 ms bx5-chicagodt_xe5-0-2.net.bell.ca (64.230.186.78) 14.814 ms bx5-chicagodt_xe6-0-0.net.bell.ca (64.230.186.86) 84.719 ms
3 * xe-1-0-6.ar2.ord1.us.nlayer.net (69.31.111.97) 13.842 ms 15.265 ms
4 ae2-40g.cr2.ord1.us.nlayer.net (69.31.111.149) 10.326 ms 14.850 ms 12.588 ms
5 xe-3-0-3.cr1.tor1.ca.nlayer.net (69.22.142.78) 14.983 ms 14.943 ms 12.701 ms
MPLS Label=569743 CoS=5 TTL=1 S=0
6 ae0-30g.cr1.tor2.ca.nlayer.net (69.31.143.25) 14.513 ms 14.507 ms 14.648 ms
7 * * *
8 198.2.121.22 (198.2.121.22) 29.946 ms 36.616 ms 30.304 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


From Bell's Looking Glass (Montreal Router):
traceroute to 108.168.42.x (108.168.42.x), 30 hops max, 38 byte packets
1 agg2-montreal02_ge11-1-7 (184.150.172.61) 0.261 ms 0.146 ms 0.122 ms
2 bx6-newyork83_xe3-0-0.net.bell.ca (64.230.187.158) 9.777 ms 12.116 ms bx6-newyork83_xe2-0-0.net.bell.ca (64.230.187.162) 9.811 ms
3 core1.nyc4.he.net (198.32.118.57) 24.048 ms 9.851 ms 12.292 ms
4 10gigabitethernet1-2.core1.tor1.he.net (184.105.222.18) 27.090 ms 26.722 ms 25.295 ms
5 * * *
6 198.2.121.22 (198.2.121.22) 29.079 ms 24.015 ms 23.779 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


Strange that my router never responds in the traceroute. Does Start.ca filter traces to its customers?

From Bell's Looking Glass:
PING 108.168.42.x (108.168.42.x) 56(84) bytes of data.
64 bytes from 108.168.42.231: icmp_seq=0 ttl=53 time=37.8 ms
64 bytes from 108.168.42.231: icmp_seq=1 ttl=53 time=33.2 ms
64 bytes from 108.168.42.231: icmp_seq=2 ttl=53 time=34.4 ms
64 bytes from 108.168.42.231: icmp_seq=3 ttl=53 time=34.4 ms
64 bytes from 108.168.42.231: icmp_seq=4 ttl=53 time=34.5 ms

--- 108.168.42.x ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 33.273/34.931/37.862/1.550 ms, pipe 2


From Rogers' Looking Glass:
Type escape sequence to abort.
Tracing the route to dhcp-108-168-42-x.cable.user.start.ca (108.168.42.x)

1 64.71.255.62 0 msec 0 msec 0 msec
2 ge-4-3-1.gw02.ym.phub.net.cable.ROGERS.com (66.185.82.241) 4 msec 4 msec 4 msec
3 69.63.250.97 4 msec 4 msec 0 msec
4 24.153.3.114 0 msec
te0-7-0-16.ccr22.yyz02.atlas.cogentco.com (154.54.10.201) [AS 174] 0 msec
24.153.3.114 4 msec
5 * * *
6 198.2.121.22 [AS 40788] 4 msec 4 msec 0 msec
7 * * *
8 * * *
9 * * *


TTL also expired here.

I also thought Start had Bell has a transit provider. Perhaps we're mistaken?

Also, curious about the traceroutes back to my public IP.

EDIT: updated my traceroute

Consumer routers have their SPI Firewalls turned on by default and block incoming pings by default. It's why testing without a router connected is recommended when troubleshooting internet connection issue (amongst other things as well).

i seem to go directly through BellNexxia transit to reach it on Start DSL:

HOST: Zapp.local                         Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 192.168.1.1                         0.0%     5    0.3   0.3   0.2   0.4   0.0
  2.|-- lns1-london1-lo0.net.start.ca       0.0%     5   15.7  21.3  15.5  44.1  12.7
  3.|-- core2-london1-ge1-120.net.start.ca  0.0%     5   15.7  15.7  15.5  15.9   0.2
  4.|-- 204.101.4.193                       0.0%     5   57.3  24.0  15.5  57.3  18.6
  5.|-- dis29-toronto63_vlan11.net.bell.ca  0.0%     5   19.0  19.1  19.0  19.3   0.1
  6.|-- toroon63dnsvp1.srvr.bell.ca         0.0%     5   19.3  19.1  19.0  19.3   0.1
 

also while your IP seems to belong to Start, your route is going entirely through Rogers's network it seems and not hitting Start. 24.156.150.249 and 69.63.252.222 (the next 2 hops after 10/8 and before going into Cogent are Rogers IPs).

Yes we do, but not all traffic is advertised over it due to a pending upgrade in London. It's still active for our other services (DSL, wireless, colo, etc) and should be in the mix for cable in a few weeks after the upgrade is completed.

that explains it. thanks rocca!

So, I did a speed test today to see if anything has changed, and in the middle of my speedtest, my speed dipped all the way to 10 mbps, and slowly rose back up.

Uhh... what happened?

Ping dropped from 9ms to 6ms though.

Did you try factory reset? Did you check modem stats?

Resetted, happens once in every 5 - 10 times, stats are fine. Forward Path:
Channel Frequency Power SNR BER Modulation
1 663.0 MHz -7.3 dBmV 39.9 dB 0.000 % 256 QAM
2 615.0 MHz -6.9 dBmV 39.8 dB 0.000 % 256 QAM
3 621.0 MHz -6.5 dBmV 39.8 dB 0.000 % 256 QAM
4 633.0 MHz -7.6 dBmV 39.3 dB 0.000 % 256 QAM
5 639.0 MHz -6.5 dBmV 40.3 dB 0.000 % 256 QAM
6 645.0 MHz -6.1 dBmV 40.8 dB 0.000 % 256 QAM
7 651.0 MHz -6.9 dBmV 40.3 dB 0.000 % 256 QAM
8 657.0 MHz -7.6 dBmV 39.4 dB 0.000 % 256 QAM
Return Path:
Channel ID Frequency Power Modulation
2 30.6 MHz 43.5 dBmV 64 QAM
1 38.6 MHz 43.5 dBmV 64 QAM
3 23.7 MHz 43.5 dBmV 64 QAM
0 0.0 MHz 0.0 dBmV QPSK

Weird, might be something on local node.

Is it direct connection or ur using router?

I would give support a call (or e-mail)

Don't think its an issue really, basically a direct connection. (Modem - 4 port switch - my PC) Probably a node issue, yeah.

Oh... crap.

Reset's been done, been like this starting from around 8:30PM Eastern.

»www.speedtest.net/result ··· 0426.png

C:\Users\owner>ping google.com

Pinging google.com [173.194.43.65] with 32 bytes of data:
Reply from 173.194.43.65: bytes=32 time=351ms TTL=58
Reply from 173.194.43.65: bytes=32 time=360ms TTL=58
Reply from 173.194.43.65: bytes=32 time=209ms TTL=58
Reply from 173.194.43.65: bytes=32 time=210ms TTL=58

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

Yeah.

Cable Signal Details
Forward Path:
Channel Frequency Power SNR BER Modulation
1 663.0 MHz -7.4 dBmV 39.8 dB 0.000 % 256 QAM
2 615.0 MHz -6.9 dBmV 39.7 dB 0.000 % 256 QAM
3 621.0 MHz -6.7 dBmV 39.9 dB 0.000 % 256 QAM
4 633.0 MHz -7.7 dBmV 39.4 dB 0.000 % 256 QAM
5 639.0 MHz -6.5 dBmV 40.3 dB 0.000 % 256 QAM
6 645.0 MHz -6.3 dBmV 40.8 dB 0.000 % 256 QAM
7 651.0 MHz -7.1 dBmV 40.0 dB 0.000 % 256 QAM
8 657.0 MHz -7.6 dBmV 39.4 dB 0.000 % 256 QAM
Return Path:
Channel ID Frequency Power Modulation
2 30.6 MHz 43.5 dBmV 64 QAM
1 38.6 MHz 43.5 dBmV 64 QAM
3 23.7 MHz 43.5 dBmV 64 QAM
0 0.0 MHz 0.0 dBmV QPSK