Since last week all my customers that ride off the Bell Canada network have been complaining of higher than usual latency. Im trying to figure out if there were any routing changes made and which side of the network the issue is coming from, my colo or Bell ?

Here is a trace

Before:

C:\Documents and Settings\Raza Amir>ping 67.213.68.2

Pinging 67.213.68.2 with 32 bytes of data:

Reply from 67.213.68.2: bytes=32 time=20ms TTL=115
Reply from 67.213.68.2: bytes=32 time=20ms TTL=115
Reply from 67.213.68.2: bytes=32 time=21ms TTL=115
Reply from 67.213.68.2: bytes=32 time=21ms TTL=115

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

C:\Documents and Settings\Raza Amir>tracert 67.213.68.2

Tracing route to 67.213.68.2 over a maximum of 30 hops

1 1 ms <1 ms 1 ms mymodem [192.168.2.1]
2 14 ms 9 ms 9 ms bas2-hull20_lo0_SYMP.net.bell.ca [64.230.197.6]
3 185 ms 228 ms 51 ms dis17-ottawa23_GE7-11.net.bell.ca [64.230.147.1]
4 8 ms 7 ms 7 ms core1-ottawa23_GE6-1.net.bell.ca [64.230.208.249]
5 7 ms 7 ms 7 ms core2-ottawa23_POS0-1.net.bell.ca [64.230.228.178]
6 13 ms 11 ms 11 ms Ncore3-montreal02_POS0-4-0-0.net.bell.ca [64.230.147.133]
7 10 ms 11 ms 9 ms bx4-montreal02_so-0-0-0.net.bell.ca [64.230.170.174]
8 9 ms 11 ms 11 ms peer_Level3_bx4-montreal02.net.bell.ca [67.69.246.126]
9 12 ms 9 ms 11 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
10 18 ms 17 ms 17 ms ae-2-2.car2.Toronto2.Level3.net [4.69.140.253]
11 18 ms 17 ms 17 ms ae-11-11.car1.Toronto2.Level3.net [4.69.140.249]
12 18 ms 18 ms 19 ms INTERNAP-NE.car1.Toronto2.Level3.net [4.59.180.42]
13 18 ms 17 ms 17 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
14 19 ms 21 ms 17 ms 3zcanada-1.border1.tor001.pnap.net [70.42.25.250]
15 18 ms 19 ms 17 ms bb2.yyz01.spdnetwork.net [208.68.88.2]
16 21 ms 19 ms 19 ms 67.213.68.2



C:\Documents and Settings\Raza Amir>ping 67.213.68.2

Pinging 67.213.68.2 with 32 bytes of data:

Reply from 67.213.68.2: bytes=32 time=115ms TTL=113
Reply from 67.213.68.2: bytes=32 time=112ms TTL=113
Reply from 67.213.68.2: bytes=32 time=112ms TTL=113
Reply from 67.213.68.2: bytes=32 time=114ms TTL=113

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

C:\Documents and Settings\Raza Amir>tracert 67.213.68.2

Tracing route to 67.213.68.2 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms mymodem [192.168.2.1]
2 11 ms 9 ms 9 ms bas2-hull20_lo0_SYMP.net.bell.ca [64.230.197.6]
3 8 ms 7 ms 7 ms dis17-ottawa23_GE7-11.net.bell.ca [64.230.147.1]
4 8 ms 7 ms 7 ms core1-ottawa23_GE6-1.net.bell.ca [64.230.208.249]
5 13 ms 11 ms 9 ms Ncore3-montrealak_POS0-4-0-0.net.bell.ca [64.230.147.141]
6 25 ms 21 ms 21 ms newcore1-newyork83_so2-0-0.net.bell.ca [64.230.187.137]
7 25 ms 23 ms 21 ms CORE1-NEWYORK83_POS3-0-0_core.net.bell.ca [64.230.187.82]
8 23 ms 25 ms 23 ms peer-Telia_bx4-newyork83.net.bell.ca [64.230.187.58]
9 21 ms 21 ms 19 ms nyk-bb1-link.telia.net [80.91.252.51]
10 82 ms 80 ms 80 ms sjo-bb1-link.telia.net [80.91.254.177]
11 81 ms 80 ms 80 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
12 81 ms 80 ms 80 ms 10gigabitethernet4-1.core1.sjc2.he.net [72.52.92.70]
13 103 ms 96 ms 94 ms 10gigabitethernet1-3.core1.nyc4.he.net [72.52.92.26]
14 96 ms 98 ms 98 ms 10gigabitethernet1-2.core1.nyc1.he.net [72.52.92.46]
15 96 ms 96 ms 96 ms 10gigabitethernet1-1.core1.nyc5.he.net [72.52.92.154]
16 112 ms 112 ms 137 ms 10gigabitethernet1-1.core1.tor1.he.net [72.52.92.166]
17 * * * Request timed out.
18 110 ms 110 ms 110 ms bb2.yyz01.spdnetwork.net [208.68.88.2]
19 112 ms 112 ms 112 ms 67.213.68.2

Trace complete.