Need Ping and traces from Bell

[Plastikman]

I have been receiving some complaints from Bell customers.

If you are can you please send me a trace and ping so i can see where the issue is

thanks

[[AP|N] .Strider]

yeah, starts off good, then jumps to 130+

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.


ping 67.213.68.2

Pinging 67.213.68.2 with 32 bytes of data:

Reply from 67.213.68.2: bytes=32 time=136ms TTL=113
Reply from 67.213.68.2: bytes=32 time=136ms TTL=113
Reply from 67.213.68.2: bytes=32 time=136ms TTL=113
Reply from 67.213.68.2: bytes=32 time=136ms 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 = 136ms, Maximum = 136ms, Average = 136ms



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 192.168.1.1
2 44 ms 47 ms 44 ms bas1-toronto09_lo0_SYMP.net.bell.ca [64.230.197.215]
3 41 ms 41 ms 42 ms core1-toronto12_13-0-5_148.net.bell.ca [64.230.139.193]
4 41 ms 41 ms 42 ms core4-toronto12_POS0-1.net.bell.ca [64.230.242.197]
5 52 ms 52 ms 51 ms core2-chicago23_pos3-0-0.net.bell.ca [64.230.147.22]
6 52 ms 53 ms 52 ms bx3-chicagodt_so-1-0-0-0.net.bell.ca [64.230.203.42]
7 51 ms 51 ms 51 ms chi-bb1-link.telia.net [213.248.85.25]
8 97 ms 99 ms 97 ms sjo-bb1-link.telia.net [213.248.80.25]
9 98 ms 99 ms 99 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
10 100 ms 99 ms 99 ms 10gigabitethernet4-1.core1.sjc2.he.net [72.52.92.70]
11 121 ms 124 ms 124 ms 10gigabitethernet1-3.core1.nyc4.he.net [72.52.92.26]
12 119 ms 120 ms 124 ms 10gigabitethernet1-2.core1.nyc1.he.net [72.52.92.46]
13 120 ms 120 ms 120 ms 10gigabitethernet1-1.core1.nyc5.he.net [72.52.92.154]
14 141 ms 135 ms 135 ms 10gigabitethernet1-1.core1.tor1.he.net [72.52.92.166]
15 137 ms 136 ms 137 ms gw-spdnetwork.torontointernetxchange.net [198.32.245.81]
16 136 ms 135 ms 135 ms bb2.yyz01.spdnetwork.net [208.68.88.2]
17 136 ms 135 ms 138 ms 67.213.68.2

Trace complete.

[Plastikman]

wow looks like some issues on the bell network

can i get some more traces. How long as it been like this ? what was your ping before

[[AP|N] .Strider]

ping was 40-60 b4 for me.

Others have had 15-30 b4

[[AP|N] Thegreat1 Halo2]

I've noticed I've been having huge pings too since i came back. I use to average 30-40 in the servers, now the cod4 one I'm getting 130-160 ping. One thing I just noticed when tracing is that I keep getting a time out on the run, i never use to have that before.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

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.

C:\Documents and Settings\Raza Amir>

[Masskiller]

i would glady give you my ifno if i knew how to do a trace. Can someone tell me how please?

[[AP|N] Thegreat1 Halo2]

Go to : Start > Run > type "cmd" then press enter
In this new section you type in:
ping 67.213.68.2

After the ping thing completes type this:
tracert 67.213.68.2

When the trace is complete it should clearly indicate : Trace complete

Then copy by right clicking and choosing the : select all
Paste here

[Masskiller]

Thanks halo, well here you go bossman.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\joey>ping 67.213.68.2

Pinging 67.213.68.2 with 32 bytes of data:
Reply from 67.213.68.2: bytes=32 time=105ms TTL=115
Reply from 67.213.68.2: bytes=32 time=103ms TTL=115
Reply from 67.213.68.2: bytes=32 time=104ms TTL=115
Reply from 67.213.68.2: bytes=32 time=104ms 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 = 103ms, Maximum = 105ms, Average = 104ms

C:\Users\joey>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 10 ms 11 ms 9 ms 64.230.197.112
3 8 ms 9 ms 9 ms dis15-ottawa23_Vlan101.net.bell.ca [64.230.228.41]
4 8 ms 9 ms 9 ms core1-ottawa23_xe6-0-0.net.bell.ca [64.230.165.69]
5 13 ms 13 ms 13 ms Ncore3-montrealak_POS0-4-0-0.net.bell.ca [64.230.147.141]
6 21 ms 23 ms 21 ms newcore1-newyork83_so2-0-0.net.bell.ca [64.230.187.137]
7 20 ms 21 ms 21 ms bx4-newyork83_pos_2_0_0.net.bell.ca [64.230.187.18]
8 36 ms 36 ms 35 ms Telia-bx3-newyork83.net.bell.ca [64.230.187.2]
9 34 ms 34 ms 35 ms nyk-bb2-link.telia.net [80.91.252.53]
10 81 ms 82 ms 82 ms sjo-bb1-link.telia.net [213.248.80.1]
11 89 ms 82 ms 82 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
12 81 ms 82 ms 82 ms 10gigabitethernet4-1.core1.sjc2.he.net [72.52.92.70]
13 109 ms 115 ms 109 ms 10gigabitethernet1-3.core1.nyc4.he.net [72.52.92.26]
14 108 ms 115 ms 109 ms 10gigabitethernet1-2.core1.nyc1.he.net [72.52.92.46]
15 108 ms 109 ms 110 ms 10gigabitethernet1-1.core1.nyc5.he.net [72.52.92.154]
16 125 ms 127 ms 125 ms 10gigabitethernet1-1.core1.tor1.he.net [72.52.92.166]
17 104 ms 104 ms 104 ms gw-spdnetwork.torontointernetxchange.net [198.32.245.81]
18 103 ms 104 ms 103 ms bb2.yyz01.spdnetwork.net [208.68.88.2]
19 102 ms 106 ms 106 ms 67.213.68.2

Trace complete.

C:\Users\joey>

[UnderPL]

Noticed too I was gonna post about it. Ping was 10-25 and now 100-130(since monday i think).

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

>ping 67.213.68.2

Pinging 67.213.68.2 with 32 bytes of data:
Reply from 67.213.68.2: bytes=32 time=99ms TTL=115
Reply from 67.213.68.2: bytes=32 time=97ms TTL=115
Reply from 67.213.68.2: bytes=32 time=98ms TTL=115
Reply from 67.213.68.2: bytes=32 time=97ms 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 = 97ms, Maximum = 99ms, Average = 97ms

>tracert 67.213.68.2

Tracing route to 67.213.68.2 over a maximum of 30 hops

  1     1 ms     2 ms     1 ms  192.168.2.1
  2     9 ms     9 ms     9 ms  64.230.197.98
  3     7 ms     8 ms     8 ms  dis23-montreal02_Vlan150.net.bell.ca [64.230.225
.153]
  4     8 ms     8 ms     8 ms  core3-montreal02_GE11-0.net.bell.ca [64.230.203.
158]
  5     9 ms     8 ms     8 ms  Ncore4-montreal02_POS0-12-1-0_core.net.bell.ca [
64.230.170.121]
  6    14 ms    15 ms    16 ms  newcore2-newyork83_so1-0-0.net.bell.ca [64.230.1
87.133]
  7    15 ms    15 ms    15 ms  CORE2-NEWYORK83_POS6-0-0_core.net.bell.ca [64.23
0.187.86]
  8    30 ms    31 ms    31 ms  Telia-bx3-newyork83.net.bell.ca [64.230.187.2]
  9    30 ms    31 ms    31 ms  nyk-bb1-link.telia.net [80.91.252.51]
 10    78 ms    78 ms    77 ms  sjo-bb1-link.telia.net [80.91.254.177]
 11    82 ms    78 ms    78 ms  hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
 12    78 ms    78 ms    78 ms  10gigabitethernet4-1.core1.sjc2.he.net [72.52.92
.70]
 13   105 ms   110 ms   104 ms  10gigabitethernet1-3.core1.nyc4.he.net [72.52.92
.26]
 14   105 ms   106 ms   115 ms  10gigabitethernet1-2.core1.nyc1.he.net [72.52.92
.46]
 15   104 ms   105 ms   105 ms  10gigabitethernet1-1.core1.nyc5.he.net [72.52.92
.154]
 16   120 ms   121 ms   125 ms  10gigabitethernet1-1.core1.tor1.he.net [72.52.92
.166]
 17    98 ms    98 ms    98 ms  gw-spdnetwork.torontointernetxchange.net [198.32
.245.81]
 18    97 ms    98 ms    97 ms  bb2.yyz01.spdnetwork.net [208.68.88.2]
 19    99 ms    98 ms   100 ms  67.213.68.2

Trace complete.

[[AP|N] Thegreat1 Halo2]

I think the fact that i traced it twice and it timed out twice would explain why i keep getting those internet connection problems for 2-3 months now.. I just lag out very often where as I use to never lag out. High pings yes, but lag out no not at all, specially when it keeps saying <missing key packetS> which i use to never get :S before