dslreports logo
spacer Home Reviews Speed Test Tools News Forums Info About Join  
 
    All Forums Hot Topics Gallery
spc

Search similar:
Forums → O Canada! → Canadian →

Bell Canada → My Ping Time Increased Sevenfold - Why?

 uniqs
1336
Share
« [Internet] FTTH and power outage • Lol why the hell would bell merge services with no notice »
prev · 1 · 2

sbrook
Mod
join:2001-12-14
Ottawa

sbrook to pstewart

Mod

2013-Dec-25 6:41 pm

to pstewart

Re: My Ping Time Increased Sevenfold - Why?

Of couse when I want to go to show you a sample, it goes straight there via xe4! Murphy is alive and well.

On the other hand going to a Bell address gives me this

Tracing route to www.bell.ca [184.150.211.7]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms TARDIS [192.168.0.1]
2 8 ms 9 ms 7 ms 10.124.146.1
3 20 ms 22 ms 15 ms 24.156.158.89
4 17 ms 15 ms 15 ms so-4-0-0.gw02.ym.phub.net.cable.rogers.com [66.185
.82.125]
5 15 ms 17 ms 19 ms 69.196.136.68
6 17 ms 17 ms 16 ms te0-7-0-22.ccr21.yyz02.atlas.cogentco.com [38.122.
69.201]
7 26 ms 27 ms 29 ms be2120.mpd21.jfk02.atlas.cogentco.com [154.54.24.2
9]
8 29 ms 29 ms 27 ms be2060.ccr21.jfk05.atlas.cogentco.com [154.54.31.1
0]
9 36 ms 30 ms 27 ms bellnexxia.jfk05.atlas.cogentco.com [154.54.10.206
]
10 * * ^C
actions · 2013-Dec-25 6:41 pm ·

pstewart
Premium Member
join:2005-10-12
Peterborough, ON

pstewart

Premium Member

2013-Dec-25 9:46 pm

Weird... for some reason Bell will not pick up certain transit providers within Canada (Cogent in this example). If they picked up the transit within Canada then the path would remain right within Toronto as both Rogers and Bell have Cogent connectivity. At one time, it used to be more cost effective to haul traffic out to NYC or CHI and purchase transit there but those days are long gone - maybe someone at Bell missed the memo?

Regarding towards Nexicom, I have seen certain IP blocks in the past with Rogers (and have heard 2nd hand with Bell) that are being routed via "longer paths" than what would be considered optimal unfortunately...
actions · 2013-Dec-25 9:46 pm ·

DKS
Damn Kidney Stones

join:2001-03-22
Owen Sound, ON

DKS to pstewart

2013-Dec-25 10:15 pm

to pstewart
said by pstewart:

A trace route from an AS577 customer to Nexicom should look like this from Toronto:

traceroute to www.nexicom.net (216.168.96.30), 30 hops max, 38 byte packets
1 agg2-toronto63_ge11-0-6 (184.150.172.189) 1.280 ms 1.223 ms 0.148 ms
2 bx1-torontoxn_et1-0-0.net.bell.ca (64.230.97.157) 1.435 ms bx1-torontoxn_et4-0-0.net.bell.ca (64.230.97.159) 1.443 ms bx1-torontoxn_et1-0-0.net.bell.ca (64.230.97.157) 1.425 ms
3 xe-8-1-0.edge1.Toronto2.Level3.net (4.59.181.1) 0.969 ms level3_bx1-torontoxn.net.bell.ca (67.69.246.158) 0.363 ms xe-8-1-0.edge1.Toronto2.Level3.net (4.59.181.1) 1.523 ms
4 TRIO-NETWOR.edge1.Toronto2.Level3.net (4.59.183.166) 0.416 ms 1.635 ms 0.806 ms
5 xe0-0-3.dis1.cavan1.nexicom.net (98.124.46.162) 1.852 ms 1.816 ms 1.986 ms
MPLS Label=359936 CoS=6 TTL=1 S=0
6 xe0-0-0.dis2.cavan1.nexicom.net (98.124.56.98) 1.850 ms 1.797 ms 1.986 ms
MPLS Label=345072 CoS=6 TTL=1 S=0
7 xe0-0-3.dis2.millbrook1.nexicom.net (98.124.56.89) 2.307 ms 3.348 ms 3.369 ms
8 ge6-0-20.dis3.millbrook1.nexicom.net (98.124.50.2) 3.464 ms 2.401 ms 2.323 ms

Please let me know if I"m missing something here

I am a Bell Sympatico customer out of the Kitchener BAS and my trace route does look like the one you suggest.

1 2 ms 1 ms 1 ms 192.168.1.1
2 2 ms 2 ms 4 ms 192.168.2.1
3 16 ms 15 ms 15 ms 64.230.197.34
4 13 ms 12 ms 12 ms 64.230.239.241
5 18 ms 16 ms 16 ms 64.230.97.157
6 18 ms 17 ms 16 ms 4.59.181.1
7 16 ms 15 ms 17 ms 4.59.183.166
8 17 ms 18 ms 20 ms 98.124.46.162
9 20 ms 18 ms 19 ms 98.124.56.98
10 19 ms 18 ms 18 ms 98.124.56.89
11 19 ms 18 ms 19 ms 98.124.50.2
actions · 2013-Dec-25 10:15 pm ·
Forums → O Canada! → Canadian → Bell Canada
« [Internet] FTTH and power outage • Lol why the hell would bell merge services with no notice »
prev · 1 · 2