Cybersmart's Poor Pings

NomNom

NomNom

Executive Member
Joined
Oct 23, 2009
Messages
5,018
Reaction score
9
Location
Auckland, New Zealand
I am starting to get really ticked off now about the poor pings during the day with Cybersmart, please tell me that I'm not the only one :cry:

This is local at 11:57am today.

Pinging mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=497ms TTL=50
Reply from 41.203.21.137: bytes=32 time=461ms TTL=50
Reply from 41.203.21.137: bytes=32 time=480ms TTL=50
Reply from 41.203.21.137: bytes=32 time=481ms TTL=50

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


Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 31 ms 27 ms 30 ms 1.1.177.41-discover.co.za [41.177.1.1]
3 446 ms 446 ms 449 ms 196.6.121.50-backbone.cybersmart.co.za [196.6.121.50]
4 485 ms 484 ms 487 ms 196.6.121.114-backbone.cybersmart.co.za [196.6.121.114]
5 493 ms 476 ms 491 ms gw-ctn-servers.cybersmart.co.za [196.41.124.1]
6 494 ms 496 ms 495 ms wbs-ip-esr-1-wan.telkom-ipnet.co.za [196.25.247.97]
7 484 ms 476 ms 462 ms 196.43.11.234
8 436 ms 441 ms 454 ms 196.43.25.206
9 504 ms 502 ms 483 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
10 445 ms 443 ms 462 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
11 461 ms 473 ms 473 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
12 462 ms 464 ms 451 ms 196.30.213.108
13 458 ms 460 ms 451 ms firewall1.jnb2.host-h.net [196.7.216.173]
14 482 ms 486 ms 480 ms mybroadband.co.za [41.203.21.137]

Trace complete.


This is international at 12:00pm today


Pinging facebook.com [69.63.189.11] with 32 bytes of data:
Reply from 69.63.189.11: bytes=32 time=834ms TTL=240
Reply from 69.63.189.11: bytes=32 time=828ms TTL=240
Reply from 69.63.189.11: bytes=32 time=831ms TTL=240
Reply from 69.63.189.11: bytes=32 time=827ms TTL=240

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


Tracing route to facebook.com [69.63.189.11]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 28 ms 30 ms 27 ms 1.1.177.41-discover.co.za [41.177.1.1]
3 471 ms 488 ms 497 ms 196.6.121.50-backbone.cybersmart.co.za [196.6.121.50]
4 505 ms 491 ms 471 ms 196.6.121.114-backbone.cybersmart.co.za [196.6.121.114]
5 708 ms 716 ms 718 ms 217.78.88.17 testament
6 718 ms 728 ms 722 ms if-2-0-6.core4.LDN-London.as6453.net [195.219.195.225]
7 755 ms 748 ms * Vlan52.icore1.LDN-London.as6453.net [80.231.76.2]
8 704 ms 705 ms 699 ms xe-10-2-2.edge3.London1.level3.net [4.68.63.105]
9 713 ms * 749 ms ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
10 * 818 ms * ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]
11 796 ms 791 ms 813 ms ae-10-10.ebr2.Washington12.Level3.net [4.69.148.50]
12 803 ms 764 ms 763 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
13 776 ms 794 ms 812 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.158]
14 807 ms 857 ms 865 ms ae-4-99.edge3.Washington4.Level3.net [4.68.17.213]
15 804 ms 752 ms 749 ms FACEBOOK-IN.edge2.Washington4.Level3.net [4.53.114.74]
16 771 ms 781 ms 814 ms ae1.bb01.iad2.tfbnw.net [204.15.20.54]
17 804 ms * 804 ms ae1.dr02.ash2.tfbnw.net [74.119.76.79]
18 805 ms 805 ms 815 ms po1014.csw01a.ash2.tfbnw.net [74.119.76.129]
19 834 ms 792 ms 792 ms www-10-01-ash2.facebook.com [69.63.189.11]

Trace complete.
 
Last edited:
Tried with a different ISP? If you haven't, it could be your exchange having issues, happened this side a while ago.
 
NomNom said:
I am starting to get really ticked off now about the poor pings during the day with Cybersmart, please tell me that I'm not the only one :cry:

This is local at 11:57am today.

Pinging mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=497ms TTL=50
Reply from 41.203.21.137: bytes=32 time=461ms TTL=50
Reply from 41.203.21.137: bytes=32 time=480ms TTL=50
Reply from 41.203.21.137: bytes=32 time=481ms TTL=50

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


Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 31 ms 27 ms 30 ms 1.1.177.41-discover.co.za [41.177.1.1]
3 446 ms 446 ms 449 ms 196.6.121.50-backbone.cybersmart.co.za [196.6.121.50]
4 485 ms 484 ms 487 ms 196.6.121.114-backbone.cybersmart.co.za [196.6.121.114]
5 493 ms 476 ms 491 ms gw-ctn-servers.cybersmart.co.za [196.41.124.1]
6 494 ms 496 ms 495 ms wbs-ip-esr-1-wan.telkom-ipnet.co.za [196.25.247.97]
7 484 ms 476 ms 462 ms 196.43.11.234
8 436 ms 441 ms 454 ms 196.43.25.206
9 504 ms 502 ms 483 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
10 445 ms 443 ms 462 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
11 461 ms 473 ms 473 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
12 462 ms 464 ms 451 ms 196.30.213.108
13 458 ms 460 ms 451 ms firewall1.jnb2.host-h.net [196.7.216.173]
14 482 ms 486 ms 480 ms mybroadband.co.za [41.203.21.137]

Trace complete.


This is international at 12:00pm today


Pinging facebook.com [69.63.189.11] with 32 bytes of data:
Reply from 69.63.189.11: bytes=32 time=834ms TTL=240
Reply from 69.63.189.11: bytes=32 time=828ms TTL=240
Reply from 69.63.189.11: bytes=32 time=831ms TTL=240
Reply from 69.63.189.11: bytes=32 time=827ms TTL=240

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


Tracing route to facebook.com [69.63.189.11]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 28 ms 30 ms 27 ms 1.1.177.41-discover.co.za [41.177.1.1]
3 471 ms 488 ms 497 ms 196.6.121.50-backbone.cybersmart.co.za [196.6.121.50]
4 505 ms 491 ms 471 ms 196.6.121.114-backbone.cybersmart.co.za [196.6.121.114]
5 708 ms 716 ms 718 ms 217.78.88.17
6 718 ms 728 ms 722 ms if-2-0-6.core4.LDN-London.as6453.net [195.219.195.225]
7 755 ms 748 ms * Vlan52.icore1.LDN-London.as6453.net [80.231.76.2]
8 704 ms 705 ms 699 ms xe-10-2-2.edge3.London1.level3.net [4.68.63.105]
9 713 ms * 749 ms ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
10 * 818 ms * ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]
11 796 ms 791 ms 813 ms ae-10-10.ebr2.Washington12.Level3.net [4.69.148.50]
12 803 ms 764 ms 763 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
13 776 ms 794 ms 812 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.158]
14 807 ms 857 ms 865 ms ae-4-99.edge3.Washington4.Level3.net [4.68.17.213]
15 804 ms 752 ms 749 ms FACEBOOK-IN.edge2.Washington4.Level3.net [4.53.114.74]
16 771 ms 781 ms 814 ms ae1.bb01.iad2.tfbnw.net [204.15.20.54]
17 804 ms * 804 ms ae1.dr02.ash2.tfbnw.net [74.119.76.79]
18 805 ms 805 ms 815 ms po1014.csw01a.ash2.tfbnw.net [74.119.76.129]
19 834 ms 792 ms 792 ms www-10-01-ash2.facebook.com [69.63.189.11]

Trace complete.
Click to expand...

You using capped or "fixed priced" account?
 
NomNom said:
I am starting to get really ticked off now about the poor pings during the day with Cybersmart, please tell me that I'm not the only one :cry:

This is local at 11:57am today.

Pinging mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=497ms TTL=50
Reply from 41.203.21.137: bytes=32 time=461ms TTL=50
Reply from 41.203.21.137: bytes=32 time=480ms TTL=50
Reply from 41.203.21.137: bytes=32 time=481ms TTL=50

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


Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 31 ms 27 ms 30 ms 1.1.177.41-discover.co.za [41.177.1.1]
3 446 ms 446 ms 449 ms 196.6.121.50-backbone.cybersmart.co.za [196.6.121.50]
4 485 ms 484 ms 487 ms 196.6.121.114-backbone.cybersmart.co.za [196.6.121.114]
5 493 ms 476 ms 491 ms gw-ctn-servers.cybersmart.co.za [196.41.124.1]
6 494 ms 496 ms 495 ms wbs-ip-esr-1-wan.telkom-ipnet.co.za [196.25.247.97]
7 484 ms 476 ms 462 ms 196.43.11.234
8 436 ms 441 ms 454 ms 196.43.25.206
9 504 ms 502 ms 483 ms ge0-3.br2.cpt1.za.mtnbusiness.net [196.7.8.206]
10 445 ms 443 ms 462 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
11 461 ms 473 ms 473 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
12 462 ms 464 ms 451 ms 196.30.213.108
13 458 ms 460 ms 451 ms firewall1.jnb2.host-h.net [196.7.216.173]
14 482 ms 486 ms 480 ms mybroadband.co.za [41.203.21.137]

Trace complete.


This is international at 12:00pm today


Pinging facebook.com [69.63.189.11] with 32 bytes of data:
Reply from 69.63.189.11: bytes=32 time=834ms TTL=240
Reply from 69.63.189.11: bytes=32 time=828ms TTL=240
Reply from 69.63.189.11: bytes=32 time=831ms TTL=240
Reply from 69.63.189.11: bytes=32 time=827ms TTL=240

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


Tracing route to facebook.com [69.63.189.11]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 28 ms 30 ms 27 ms 1.1.177.41-discover.co.za [41.177.1.1]
3 471 ms 488 ms 497 ms 196.6.121.50-backbone.cybersmart.co.za [196.6.121.50]
4 505 ms 491 ms 471 ms 196.6.121.114-backbone.cybersmart.co.za [196.6.121.114]
5 708 ms 716 ms 718 ms 217.78.88.17
6 718 ms 728 ms 722 ms if-2-0-6.core4.LDN-London.as6453.net [195.219.195.225]
7 755 ms 748 ms * Vlan52.icore1.LDN-London.as6453.net [80.231.76.2]
8 704 ms 705 ms 699 ms xe-10-2-2.edge3.London1.level3.net [4.68.63.105]
9 713 ms * 749 ms ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
10 * 818 ms * ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]
11 796 ms 791 ms 813 ms ae-10-10.ebr2.Washington12.Level3.net [4.69.148.50]
12 803 ms 764 ms 763 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
13 776 ms 794 ms 812 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.158]
14 807 ms 857 ms 865 ms ae-4-99.edge3.Washington4.Level3.net [4.68.17.213]
15 804 ms 752 ms 749 ms FACEBOOK-IN.edge2.Washington4.Level3.net [4.53.114.74]
16 771 ms 781 ms 814 ms ae1.bb01.iad2.tfbnw.net [204.15.20.54]
17 804 ms * 804 ms ae1.dr02.ash2.tfbnw.net [74.119.76.79]
18 805 ms 805 ms 815 ms po1014.csw01a.ash2.tfbnw.net [74.119.76.129]
19 834 ms 792 ms 792 ms www-10-01-ash2.facebook.com [69.63.189.11]

Trace complete.
Click to expand...


The problem is on our side. If you go through the route 196.6.121.50, if you go through the other route there won't be a problem. We are working on fixing it, it may be one or two days though.

Regards

Laurie
 
clickme said:
You using capped or "fixed priced" account?
Click to expand...

capped

laurie said:
The problem is on our side. If you go through the route 196.6.121.50, if you go through the other route there won't be a problem. We are working on fixing it, it may be one or two days though.

Regards

Laurie
Click to expand...

Thank you Laurie, just wanted to make sure I wasn't the only one with the problem.

On another note, I would also like to know if you will be fixing the connection problems with the call of Duty Black Ops servers or is that related the the above problem?
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X