SabreWolfy
Expert Member
- Joined
- Sep 7, 2009
- Messages
- 2,229
- Reaction score
- 1
Seems more widespread.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is the ultimate French toast topping?
Gordon_R
Honorary Master
Chevron
Serial breaker of phones
Yeah, only got home after 5, but I can say that everything is now flying again. Compared speeds and pings to my mtn business account and performs the same.
Thanks to mweb operations who got techs to call me exactly when he said they would. Two thumbs up.
Thanks to mweb operations who got techs to call me exactly when he said they would. Two thumbs up.
Gordon_R
Honorary Master
My latency (CT-Jhb) has just shot up to 500ms this morning (Wed 28th). Anyone else in Cape Town suffering?
Code:
Tracing route to www.dstv.com [196.28.65.142]
over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms home.gateway [192.168.1.254]
2 8 ms 8 ms 8 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
3 651 ms 665 ms 660 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218]
4 710 ms 711 ms 711 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 628 ms 643 ms 655 ms tengig-3-2.vic-core-sw2.mweb.co.za [196.22.169.70]
6 717 ms 729 ms 727 ms 135.75.28.196.netactive.net [196.28.75.135]
7 665 ms 671 ms 661 ms 192.168.196.17
8 656 ms 652 ms 643 ms www.dstv.com [196.28.65.142]
Trace complete.7th day adventist church
Well-Known Member
- Joined
- Nov 4, 2009
- Messages
- 185
- Reaction score
- 0
Yup - local latency is extremely high.
MyWorld
Executive Member
Since Mweb switched over to Seacom the quality and performance has been extremely terrible. This is the worst DSL experience I have ever had.
Most of the international sites time out or do not load completely, very, very disappointed so far.
Code:
PING google.com (64.233.179.104) 56(84) bytes of data.
64 bytes from cpt01s01-in-f104.1e100.net (64.233.179.104): icmp_seq=2 ttl=51 time=1154 ms
64 bytes from cpt01s01-in-f104.1e100.net (64.233.179.104): icmp_seq=3 ttl=51 time=1174 ms
64 bytes from cpt01s01-in-f104.1e100.net (64.233.179.104): icmp_seq=4 ttl=51 time=1188 ms
64 bytes from cpt01s01-in-f104.1e100.net (64.233.179.104): icmp_seq=5 ttl=51 time=1221 ms
64 bytes from cpt01s01-in-f104.1e100.net (64.233.179.104): icmp_seq=6 ttl=51 time=1225 ms
64 bytes from cpt01s01-in-f104.1e100.net (64.233.179.104): icmp_seq=7 ttl=51 time=1247 ms
64 bytes from cpt01s01-in-f104.1e100.net (64.233.179.104): icmp_seq=8 ttl=51 time=1253 ms
64 bytes from cpt01s01-in-f104.1e100.net (64.233.179.104): icmp_seq=9 ttl=51 time=1256 msMost of the international sites time out or do not load completely, very, very disappointed so far.
Gordon_R
Honorary Master
Since Mweb switched over to Seacom the quality and performance has been extremely terrible. This is the worst DSL experience I have ever had.
Most of the international sites time out or do not load completely, very, very disappointed so far.
Trying pinging a local site, such as www.dstv.com. The problem is not SEACOM, but Telkom AFAIK.
killadoob
Honorary Master
Naaa when seacom was busted my local ping was 11-16ms, now it jumps from 74 to 220 back to 140 back up to 250.
Since they turned seacom back on.
Since they turned seacom back on.
MyWorld
Executive Member
Here is some local, and you will hit the floor when reading this!
I'm in Potchefstroom and crying my eyes out!
Code:
ping mybroadband.co.za
PING mybroadband.co.za (41.203.21.136) 56(84) bytes of data.
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=1 ttl=50 time=692 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=2 ttl=50 time=709 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=3 ttl=50 time=670 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=4 ttl=50 time=646 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=5 ttl=50 time=664 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=6 ttl=50 time=678 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=7 ttl=50 time=668 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=8 ttl=50 time=545 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=9 ttl=50 time=549 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=10 ttl=50 time=577 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=11 ttl=50 time=626 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=12 ttl=50 time=682 ms
^C
--- mybroadband.co.za ping statistics ---
13 packets transmitted, 12 received, 7% packet loss, time 14965ms
rtt min/avg/max/mdev = 545.628/642.528/709.916/53.491 msI'm in Potchefstroom and crying my eyes out!
The problem is that Telkom cannot supply Mweb with enough IPC bandwidth. See the reply from Mweb Guy on Free the Web's Facebook page on Monday:
Code:
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=1 ttl=51 time=808 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=2 ttl=51 time=822 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=3 ttl=51 time=841 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=4 ttl=51 time=845 ms
64 bytes from mybroadband.co.za (41.203.21.136): icmp_seq=5 ttl=51 time=838 msMal1ce
Well-Known Member
Same 600ms to local from Durbs, had to switch over to Afrihost capped account, MWEB is un-usable this morning, slow everywhere, pages timing out, etc.
Gordon_R
Honorary Master
When SEACOM was down some MWeb users were switched over to the SAIX backbone. That has now ended, but has nothing to do with the SEACOM international cable itself.
That explanation doesn't make sense, why would local latency jump from 100ms on Tuesday to 500ms to Wednesday?
More likely a broken link somewhere in Gauteng, near MWeb's Victory Park data center.
Edit: At 9h50 my latency suddenly dropped into the 'normal' range. Weird. Not for long though...
Last edited:
killadoob
Honorary Master
When SEACOM was down some MWeb users were switched over to the SAIX backbone. That has now ended, but has nothing to do with the SEACOM international cable itself.
Explain what you mean? It must be the cable, where is mweb routing the local traffic? Do you have such thing as local traffic on a seacom cable i wonder?
What is mweb using for local? I enjoy when seacom is down, i can finally game at 13ms and not 200 average. All axxess seacom accounts suffer the same fate. I am not forking out 90 bucks for saix either. Rather annoying problem grrrrrrrrrrrr
Explain what you mean? It must be the cable, where is mweb routing the local traffic? Do you have such thing as local traffic on a seacom cable i wonder?
What is mweb using for local? I enjoy when seacom is down, i can finally game at 13ms and not 200 average. All axxess seacom accounts suffer the same fate. I am not forking out 90 bucks for saix either. Rather annoying problem grrrrrrrrrrrr
This morning I was getting about 800ms to Hetzner, but during the course of the morning it stabilized for me.
I didn't bother to stop utorrent, so these may not be 100% accurate.
Code:
PING mybroadband.co.za (41.203.21.136) 56(84) bytes of data.
--- mybroadband.co.za ping statistics ---
100 packets transmitted, 100 received, 0% packet loss, time 99039ms
rtt min/avg/max/mdev = 10.849/49.308/162.957/31.528 msI didn't bother to stop utorrent, so these may not be 100% accurate.
Gordon_R
Honorary Master
Belated status update from MWeb:
http://www.mweb.co.za/helpcentre/NetworkStatusNotices/tabid/1765/Default.aspx
Last edited:
Bona Botse
A little insight goes a long way
Code:
Pinging www.mybroadband.co.za [41.203.21.136] with 32 bytes of data:
Reply from 41.203.21.136: bytes=32 time=1021ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1071ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1123ms TTL=50
Reply from 41.203.21.136: bytes=32 time=909ms TTL=50
Reply from 41.203.21.136: bytes=32 time=826ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1078ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1126ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1055ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1036ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1123ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1178ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1133ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1105ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1329ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1424ms TTL=50
Reply from 41.203.21.136: bytes=32 time=1426ms TTL=50
Ping statistics for 41.203.21.136:
Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 826ms, Maximum = 1426ms, Average = 1122ms
Code:
Tracing route to www.mybroadband.co.za [41.203.21.136]
over a maximum of 30 hops:
1 3 ms 2 ms 5 ms 192.168.1.1
2 842 ms 1038 ms 1036 ms 41-133-82-1.dsl.mweb.co.za [41.133.82.1]
3 1298 ms 1125 ms 958 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
4 1057 ms 1085 ms 1002 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 877 ms 834 ms 708 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 726 ms 675 ms 649 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
7 949 ms 960 ms 849 ms rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.
43.8.198]
8 723 ms 767 ms 802 ms 196.43.25.138
9 969 ms 833 ms 734 ms ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181
]
10 919 ms 1056 ms 997 ms 196.30.1.21
11 975 ms 915 ms 920 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.13
6]
12 810 ms 899 ms 938 ms 196.30.213.108
13 925 ms 1019 ms 1145 ms firewall1.jnb2.host-h.net [196.7.216.173]
14 1436 ms 1770 ms 1941 ms mybroadband.co.za [41.203.21.136]
Trace complete.
Last edited:
MWEB... you make no sense
this makes no sense... me and my friend both have 4mb uncapped accounts with MWEB. here is his ping test to mybroadband.co.za
here is HIS tracert
here is my ping test
and here is my tracert
Right off the bat their second hop is ridiclous... and it is exactly the same ip that my tracert hops to...
That is odd enough, then i go to their house, put my details in their router and they get super low latency which rules out the possibility of it being telkom (i think). They phoned mweb, they are not being shaped for excessive downloads and they did line tests with tech support and everything seems fine.
Can anyone out there help with this? Because to me this makes absolutely no sense unless MWEB fluffed up and is routing them to pakistan and then to argentina and back...
this makes no sense... me and my friend both have 4mb uncapped accounts with MWEB. here is his ping test to mybroadband.co.za
Code:
Pinging mybroadband.co.za [41.203.21.136] with 32 bytes of data:
Reply from 41.203.21.136: bytes=32 time=471ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 41.203.21.136:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 471ms, Maximum = 471ms, Average = 471mshere is HIS tracert
Code:
Tracing route to mybroadband.co.za [41.203.21.136]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 564 ms 459 ms 417 ms 41-132-40-1.dsl.mweb.co.za [41.132.40.1]
3 511 ms 586 ms 323 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
4 * 531 ms 578 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 507 ms 531 ms 448 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 525 ms 408 ms 560 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 621 ms 535 ms * rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.43.8.198]
8 319 ms 541 ms 310 ms 196.43.25.138
9 561 ms 465 ms 589 ms ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181]
10 * 507 ms 527 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
11 326 ms 273 ms 122 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
12 34 ms 51 ms 43 ms 196.30.213.108
13 860 ms 419 ms 239 ms firewall1.jnb2.host-h.net [196.7.216.173]
14 787 ms 396 ms 149 ms mybroadband.co.za [41.203.21.136]
Trace complete.here is my ping test
Code:
Pinging mybroadband.co.za [41.203.21.136] with 32 bytes of data:
Reply from 41.203.21.136: bytes=32 time=33ms TTL=50
Reply from 41.203.21.136: bytes=32 time=32ms TTL=50
Reply from 41.203.21.136: bytes=32 time=32ms TTL=50
Reply from 41.203.21.136: bytes=32 time=33ms TTL=50
Ping statistics for 41.203.21.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 33ms, Average = 32msand here is my tracert
Code:
Tracing route to mybroadband.co.za [41.203.21.136]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.254
2 9 ms 8 ms 8 ms 41-132-40-1.dsl.mweb.co.za [41.132.40.1]
3 32 ms 31 ms 33 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218]
4 31 ms 31 ms 31 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 34 ms 33 ms 33 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 31 ms 31 ms 31 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 61 ms 61 ms 61 ms rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.43.8.198]
8 31 ms 31 ms 30 ms 196.43.25.138
9 33 ms 33 ms 32 ms ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181]
10 32 ms 32 ms 34 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
11 34 ms 34 ms 33 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
12 33 ms 33 ms 32 ms 196.30.213.108
13 32 ms 33 ms 33 ms firewall1.jnb2.host-h.net [196.7.216.173]
14 33 ms 33 ms 33 ms mybroadband.co.za [41.203.21.136]
Trace complete.Right off the bat their second hop is ridiclous... and it is exactly the same ip that my tracert hops to...
That is odd enough, then i go to their house, put my details in their router and they get super low latency which rules out the possibility of it being telkom (i think). They phoned mweb, they are not being shaped for excessive downloads and they did line tests with tech support and everything seems fine.
Can anyone out there help with this? Because to me this makes absolutely no sense unless MWEB fluffed up and is routing them to pakistan and then to argentina and back...
Gordon_R
Honorary Master
It's probably a bad line to the DSLAM (or the exchange is being worked on). When you entered your details, you probably rebooted the modem, which reset the line, and improved the latency.
The first 2 hops of any tracert are completely outside of MWeb's control (AFAIK). The 2nd hop (41-133-82-1.dsl.mweb.co.za) is at the exchange itself, and only the 3rd hop is under MWeb's control (tengig-0-0-0-104.vic-ipc-2.mweb.co.za).