MWEB gaming SUCKS!!(Latency Spikes)

S

Some Guy

New member
Latency Issues with MWeb uncapped. any pro's that can help me?

Ive been having issues from Jan where my latency will spike at night and weekends.

My 3rd ticket is now logged for more than 60 days with mweb technical.

This is what i have done from my side thus far:
Replaced my router with a brand new Trendnet
Replaced my ADSL port filter
Replaced Telkom wall socket
Scanned PC with Combo Fix and CCleaner
After that i formatted my PC

Still no victory...

What mweb has done from there side:
Gave me a telkom account to test
Gave me an unshaped account to test
Upgraded my line to 10mb
Escalated my problem 10 million times to telkom

The only thing that had an effect was when they upped my line to 10mb the line spiked at max of 350ms where as on the 4mb line it spiked at +-1000ms.

Currently its spikes for 15 minutes then return top normal then spikes again. After i was informed that telkom did something from their side again i tested again. This only happens at night and during the weekend.

Below is some tracert i did last night to an mweb and a IS gaming CSS server:

C:\Users\Moonlord>tracert 196.38.180.25

Tracing route to strike.isgaming.co.za [196.38.180.25]
over a maximum of 30 hops:

1 410 ms 913 ms 949 ms 41-132-14-1.dsl.mweb.co.za [41.132.14.1]
2 463 ms 803 ms 920 ms 197-80-4-70.jhb.mweb.co.za [197.80.4.70]
3 850 ms 701 ms 711 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
4 617 ms 779 ms 670 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
5 694 ms 479 ms 464 ms tengig0-0-0-0.vic-up-2.mweb.co.za [197.80.4.127]

6 455 ms 606 ms 154 ms jx2621-1-S1-AP.mweb.net [196.22.163.5]
7 7 ms 44 ms 144 ms is.jinx.net.za [196.223.14.10]
8 509 ms 232 ms 14 ms 168.209.1.140
9 443 ms 433 ms 539 ms 168.209.100.206
10 736 ms 653 ms 493 ms 168.209.218.22
11 645 ms 655 ms 700 ms strike.isgaming.co.za [196.38.180.25]

Trace complete.

C:\Users\Moonlord>tracert 196.38.180.25

Tracing route to strike.isgaming.co.za [196.38.180.25]
over a maximum of 30 hops:

1 254 ms 568 ms 675 ms 41-132-14-1.dsl.mweb.co.za [41.132.14.1]
2 271 ms 150 ms 19 ms 197-80-4-70.jhb.mweb.co.za [197.80.4.70]
3 381 ms 31 ms 13 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
4 191 ms 436 ms 596 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
5 592 ms 356 ms 554 ms tengig0-0-0-0.vic-up-2.mweb.co.za [197.80.4.127]

6 24 ms 8 ms 14 ms jx2621-1-S1-AP.mweb.net [196.22.163.5]
7 494 ms 8 ms 6 ms is.jinx.net.za [196.223.14.10]
8 134 ms 136 ms 257 ms 168.209.1.140
9 445 ms 34 ms 10 ms 168.209.100.206
10 904 ms 751 ms 372 ms 168.209.218.22
11 313 ms 465 ms 508 ms strike.isgaming.co.za [196.38.180.25]

Trace complete.

C:\Users\Moonlord>tracert 196.38.180.25

Tracing route to strike.isgaming.co.za [196.38.180.25]
over a maximum of 30 hops:

1 386 ms 659 ms 495 ms 41-132-14-1.dsl.mweb.co.za [41.132.14.1]
2 609 ms 644 ms 746 ms 197-80-4-70.jhb.mweb.co.za [197.80.4.70]
3 644 ms 548 ms 566 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
4 810 ms 675 ms 718 ms tengig0-7-0-2.12.vic-p-2.mweb.co.za [196.22.169.
242]
5 643 ms 510 ms 586 ms tengig0-0-0-0.vic-up-2.mweb.co.za [197.80.4.127]

6 650 ms 595 ms 572 ms jx2621-1-S1-AP.mweb.net [196.22.163.5]
7 572 ms 506 ms 498 ms is.jinx.net.za [196.223.14.10]
8 569 ms 473 ms 493 ms 168.209.1.140
9 914 ms 509 ms 584 ms 168.209.100.206
10 655 ms 709 ms 536 ms 168.209.218.22
11 504 ms 599 ms 599 ms strike.isgaming.co.za [196.38.180.25]

Trace complete.

C:\Users\Moonlord>tracert 41.86.98.15

Tracing route to 41-86-98-15.mweb.co.za [41.86.98.15]
over a maximum of 30 hops:

1 537 ms 585 ms 255 ms 41-132-14-1.dsl.mweb.co.za [41.132.14.1]
2 6 ms 6 ms 6 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
3 312 ms 495 ms 764 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
4 707 ms 645 ms 139 ms tengig-3-2.vic-core-sw2.mweb.co.za [196.22.169.7
0]
5 430 ms 727 ms 38 ms 85.75.28.196.netactive.net [196.28.75.85]
6 58 ms 86 ms 137 ms 41-86-98-15.mweb.co.za [41.86.98.15]

Trace complete.

C:\Users\Moonlord>tracert 41.86.98.15

Tracing route to 41-86-98-15.mweb.co.za [41.86.98.15]
over a maximum of 30 hops:

1 5 ms 5 ms 5 ms 41-132-14-1.dsl.mweb.co.za [41.132.14.1]
2 16 ms 12 ms 6 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
3 7 ms 6 ms 11 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
4 7 ms 8 ms 7 ms tengig-3-2.vic-core-sw2.mweb.co.za [196.22.169.7
0]
5 7 ms 7 ms 6 ms 85.75.28.196.netactive.net [196.28.75.85]
6 7 ms 7 ms 7 ms 41-86-98-15.mweb.co.za [41.86.98.15]

Trace complete.

C:\Users\Moonlord>tracert 41.86.98.15

Tracing route to 41-86-98-15.mweb.co.za [41.86.98.15]
over a maximum of 30 hops:

1 8 ms 28 ms 78 ms 41-132-14-1.dsl.mweb.co.za [41.132.14.1]
2 25 ms 79 ms 54 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
3 14 ms 33 ms 127 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
4 114 ms 24 ms 34 ms tengig-3-2.vic-core-sw2.mweb.co.za [196.22.169.7
0]
5 62 ms 153 ms 9 ms 85.75.28.196.netactive.net [196.28.75.85]
6 18 ms 30 ms 7 ms 41-86-98-15.mweb.co.za [41.86.98.15]

Trace complete.

C:\Users\Moonlord>tracert 41.86.98.15

Tracing route to 41-86-98-15.mweb.co.za [41.86.98.15]
over a maximum of 30 hops:

1 14 ms 13 ms 9 ms 41-132-14-1.dsl.mweb.co.za [41.132.14.1]
2 17 ms 10 ms 32 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.16
9.170]
3 43 ms 8 ms 27 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
4 19 ms 10 ms 18 ms tengig-3-2.vic-core-sw2.mweb.co.za [196.22.169.7
0]
5 75 ms 51 ms 30 ms 85.75.28.196.netactive.net [196.28.75.85]
6 34 ms 114 ms 65 ms 41-86-98-15.mweb.co.za [41.86.98.15]

Trace complete.

These traces was done right after each after. I have then noticed that my ping was 500+ when i was ingame and did a trace route. The low tracert was done when i closed the game. I then deleted steam reinstalled it and redownloaded and installed CSS.

Today i spoke to the admin of the intoxicated gungame server(hosted by mweb) he he says my ping still spikes... there is no choke on the line but my ping still spikes but not high yet here is the findings:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Moonlord>ping intoxicated.co.za -t

Pinging intoxicated.co.za [197.85.190.43] with 32 bytes of data:
Reply from 197.85.190.43: bytes=32 time=46ms TTL=55
Reply from 197.85.190.43: bytes=32 time=34ms TTL=55
Reply from 197.85.190.43: bytes=32 time=27ms TTL=55
Reply from 197.85.190.43: bytes=32 time=28ms TTL=55
Reply from 197.85.190.43: bytes=32 time=33ms TTL=55
Reply from 197.85.190.43: bytes=32 time=68ms TTL=55
Reply from 197.85.190.43: bytes=32 time=65ms TTL=55
Reply from 197.85.190.43: bytes=32 time=37ms TTL=55
Reply from 197.85.190.43: bytes=32 time=27ms TTL=55
Reply from 197.85.190.43: bytes=32 time=32ms TTL=55
Reply from 197.85.190.43: bytes=32 time=27ms TTL=55
Reply from 197.85.190.43: bytes=32 time=32ms TTL=55
Reply from 197.85.190.43: bytes=32 time=28ms TTL=55

Ping statistics for 197.85.190.43:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 68ms, Average = 37ms
Control-C
^C
C:\Users\Moonlord>tracert intoxicated.co.za

Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:

1 11 ms 25 ms 20 ms 41-132-14-1.dsl.mweb.co.za [41.132.14.1]
2 23 ms 19 ms 14 ms tengig-0-0-0-107.vic-ipc-1.mweb.co.za [196.22.16
9.158]
3 27 ms 14 ms 15 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
4 73 ms 31 ms 74 ms tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.
226]
5 43 ms 35 ms 69 ms tengig0-1-0-0.cpt-up-1.mweb.co.za [197.84.4.34]

6 74 ms 67 ms 52 ms 196.28.178.115
7 96 ms 38 ms 63 ms 196.28.178.70
8 58 ms 33 ms 81 ms cte-access2.vwol.net [196.41.144.31]
9 60 ms 56 ms 55 ms 197-85-190-43.cpt.mweb.co.za [197.85.190.43]

Trace complete.

C:\Users\Moonlord>

Noticed the inconsistent latency

Is there anyone out there that can tell me whats wrong coz no one at Mweb can:cry:
 
Last edited:
Experiencing high latency again did a ping test to the server:

Marked with italic/bold is when im ingame and do the ping and normal is when im not ingame

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Moonlord>ping 196.38.180.25 -t

Pinging 196.38.180.25 with 32 bytes of data:
Reply from 196.38.180.25: bytes=32 time=74ms TTL=53
Reply from 196.38.180.25: bytes=32 time=157ms TTL=53
Reply from 196.38.180.25: bytes=32 time=81ms TTL=53
Reply from 196.38.180.25: bytes=32 time=48ms TTL=53
Reply from 196.38.180.25: bytes=32 time=50ms TTL=53
Reply from 196.38.180.25: bytes=32 time=222ms TTL=53
Reply from 196.38.180.25: bytes=32 time=298ms TTL=53
Reply from 196.38.180.25: bytes=32 time=29ms TTL=53
Reply from 196.38.180.25: bytes=32 time=231ms TTL=53
Reply from 196.38.180.25: bytes=32 time=393ms TTL=53
Reply from 196.38.180.25: bytes=32 time=89ms TTL=53
Reply from 196.38.180.25: bytes=32 time=445ms TTL=53
Reply from 196.38.180.25: bytes=32 time=280ms TTL=53
Reply from 196.38.180.25: bytes=32 time=10ms TTL=53
Reply from 196.38.180.25: bytes=32 time=347ms TTL=53
Reply from 196.38.180.25: bytes=32 time=646ms TTL=53

Ping statistics for 196.38.180.25:
Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 646ms, Average = 212ms
Control-C
^C
C:\Users\Moonlord>ping 196.38.180.25 -t

Pinging 196.38.180.25 with 32 bytes of data:
Reply from 196.38.180.25: bytes=32 time=37ms TTL=53
Reply from 196.38.180.25: bytes=32 time=27ms TTL=53
Reply from 196.38.180.25: bytes=32 time=37ms TTL=53
Reply from 196.38.180.25: bytes=32 time=32ms TTL=53
Reply from 196.38.180.25: bytes=32 time=15ms TTL=53
Reply from 196.38.180.25: bytes=32 time=20ms TTL=53
Reply from 196.38.180.25: bytes=32 time=25ms TTL=53
Reply from 196.38.180.25: bytes=32 time=50ms TTL=53
Reply from 196.38.180.25: bytes=32 time=82ms TTL=53
Reply from 196.38.180.25: bytes=32 time=12ms TTL=53
Reply from 196.38.180.25: bytes=32 time=32ms TTL=53
Reply from 196.38.180.25: bytes=32 time=10ms TTL=53
Reply from 196.38.180.25: bytes=32 time=11ms TTL=53
Reply from 196.38.180.25: bytes=32 time=47ms TTL=53
Reply from 196.38.180.25: bytes=32 time=11ms TTL=53
Reply from 196.38.180.25: bytes=32 time=13ms TTL=53

Ping statistics for 196.38.180.25:
Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 82ms, Average = 28ms
Control-C
^C
C:\Users\Moonlord>ping 196.38.180.25 -t

Pinging 196.38.180.25 with 32 bytes of data:
Reply from 196.38.180.25: bytes=32 time=12ms TTL=53
Reply from 196.38.180.25: bytes=32 time=13ms TTL=53
Reply from 196.38.180.25: bytes=32 time=9ms TTL=53
Reply from 196.38.180.25: bytes=32 time=16ms TTL=53
Reply from 196.38.180.25: bytes=32 time=41ms TTL=53
Reply from 196.38.180.25: bytes=32 time=29ms TTL=53
Reply from 196.38.180.25: bytes=32 time=17ms TTL=53
Reply from 196.38.180.25: bytes=32 time=28ms TTL=53
Reply from 196.38.180.25: bytes=32 time=17ms TTL=53
Reply from 196.38.180.25: bytes=32 time=74ms TTL=53
Reply from 196.38.180.25: bytes=32 time=13ms TTL=53
Reply from 196.38.180.25: bytes=32 time=55ms TTL=53
Reply from 196.38.180.25: bytes=32 time=32ms TTL=53
Reply from 196.38.180.25: bytes=32 time=39ms TTL=53
Reply from 196.38.180.25: bytes=32 time=15ms TTL=53

Ping statistics for 196.38.180.25:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 74ms, Average = 27ms
Control-C
^C
C:\Users\Moonlord>ping 196.38.180.25 -t

Pinging 196.38.180.25 with 32 bytes of data:
Reply from 196.38.180.25: bytes=32 time=457ms TTL=53
Reply from 196.38.180.25: bytes=32 time=523ms TTL=53
Reply from 196.38.180.25: bytes=32 time=503ms TTL=53
Reply from 196.38.180.25: bytes=32 time=355ms TTL=53
Reply from 196.38.180.25: bytes=32 time=252ms TTL=53
Reply from 196.38.180.25: bytes=32 time=141ms TTL=53
Reply from 196.38.180.25: bytes=32 time=151ms TTL=53
Reply from 196.38.180.25: bytes=32 time=338ms TTL=53
Reply from 196.38.180.25: bytes=32 time=625ms TTL=53
Reply from 196.38.180.25: bytes=32 time=735ms TTL=53
Reply from 196.38.180.25: bytes=32 time=774ms TTL=53
Reply from 196.38.180.25: bytes=32 time=817ms TTL=53
Reply from 196.38.180.25: bytes=32 time=850ms TTL=53
Reply from 196.38.180.25: bytes=32 time=940ms TTL=53
Reply from 196.38.180.25: bytes=32 time=827ms TTL=53
Reply from 196.38.180.25: bytes=32 time=835ms TTL=53
Reply from 196.38.180.25: bytes=32 time=895ms TTL=53

Ping statistics for 196.38.180.25:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 141ms, Maximum = 940ms, Average = 589ms
Control-C
^C
C:\Users\Moonlord>

Anyone knows what the hell is going on? I have been able to play 2 days ago with a ping of 20ms while someone was downloading.
 
Which area do you live in?

Telkom might be having exchange congestion or line faults in your area.
 
No Offence James it been like this for 3 months now and MWEB will know about this...

I am in the dowerglen area.

Which i dont understand is why is my oing fine when im not connected to a game but as soon as i connect it jumps
 
You shouldn't really start off a thread by saying how something sucks in the topic, it makes you look like a whiner and people would be less inclined to bother reading what you wrote. Rather pose a question or ask for help, more productive.

Looking over your stuff I see they gave you a Telkom account to test, did this improve things or did you still get these spikes. If it was stilling happening then it has nothing to do with mweb and judging from the time periods you say it happens I would guess that your exchange is over saturated so when everyone is using their connections at the same time your latency goes to poo. Maybe try see if any of your neighbours play games and see if they also get spikes at those same times.
 
According to mweb this is not the problem my exchange is 15% under, no one else in this area has this problem.

The telkom account nothing changed, my line and ADSL is with mweb so its there problem to sort out telkom, which they have been unsuccessful till today!

Ive noticed this:

Reply from 196.38.180.25: bytes=32 time=8ms TTL=53
Reply from 196.38.180.25: bytes=32 time=8ms TTL=53
Reply from 196.38.180.25: bytes=32 time=8ms TTL=53
Reply from 196.38.180.25: bytes=32 time=9ms TTL=53
Reply from 196.38.180.25: bytes=32 time=11ms TTL=53
Reply from 196.38.180.25: bytes=32 time=135ms TTL=53
Reply from 196.38.180.25: bytes=32 time=467ms TTL=53
Reply from 196.38.180.25: bytes=32 time=9ms TTL=53
Reply from 196.38.180.25: bytes=32 time=365ms TTL=53
Reply from 196.38.180.25: bytes=32 time=755ms TTL=53
Reply from 196.38.180.25: bytes=32 time=870ms TTL=53
Reply from 196.38.180.25: bytes=32 time=796ms TTL=53
Reply from 196.38.180.25: bytes=32 time=809ms TTL=53
Reply from 196.38.180.25: bytes=32 time=842ms TTL=53
Reply from 196.38.180.25: bytes=32 time=802ms TTL=53
Reply from 196.38.180.25: bytes=32 time=965ms TTL=53
Reply from 196.38.180.25: bytes=32 time=810ms TTL=53
Reply from 196.38.180.25: bytes=32 time=686ms TTL=53
Reply from 196.38.180.25: bytes=32 time=1323ms TTL=53
Reply from 196.38.180.25: bytes=32 time=288ms TTL=53
Reply from 196.38.180.25: bytes=32 time=22ms TTL=53
Reply from 196.38.180.25: bytes=32 time=25ms TTL=53
Reply from 196.38.180.25: bytes=32 time=11ms TTL=53
Reply from 196.38.180.25: bytes=32 time=32ms TTL=53
Reply from 196.38.180.25: bytes=32 time=31ms TTL=53
Reply from 196.38.180.25: bytes=32 time=30ms TTL=53
Reply from 196.38.180.25: bytes=32 time=29ms TTL=53
Reply from 196.38.180.25: bytes=32 time=18ms TTL=53
Reply from 196.38.180.25: bytes=32 time=37ms TTL=53
Reply from 196.38.180.25: bytes=32 time=13ms TTL=53
Reply from 196.38.180.25: bytes=32 time=10ms TTL=53
Reply from 196.38.180.25: bytes=32 time=11ms TTL=53
Reply from 196.38.180.25: bytes=32 time=24ms TTL=53
Reply from 196.38.180.25: bytes=32 time=8ms TTL=53
Reply from 196.38.180.25: bytes=32 time=8ms TTL=53
Reply from 196.38.180.25: bytes=32 time=8ms TTL=53
Reply from 196.38.180.25: bytes=32 time=8ms TTL=53
Reply from 196.38.180.25: bytes=32 time=53ms TTL=53
Reply from 196.38.180.25: bytes=32 time=19ms TTL=53

Notice the latency jump, thats when i connect to a server and want to play.
Bearing in mind my pc has been formatted, im playing the game at 300fps i reinstalled steam and redownloaded and installed a fresh copy of the game.

According to the above it would be the game... but no the game run at 20ms during working hours while downloading torrents. Its only specific times the latency spike. It just started in the middle of January and has not stopped since.

Any ideas? My line speed is still perfect at these "spike" times.
 
It looks like an exchange issue to me.
See how the first jump from your computer to the exchange goes all high and stuff?

Normal said:
1 5 ms 5 ms 5 ms 41-132-14-1.dsl.mweb.co.za [41.132.14.1]
Click to expand...
Not Normal said:
1 254 ms 568 ms 675 ms 41-132-14-1.dsl.mweb.co.za [41.132.14.1]
Click to expand...

Anything up to 50ms is fine.
 
ok network setup:

only my pc wired to router tried PPPOE and BRIDGED dailup with no difference.
All cables to router and everything has been replaced.
Router is a Trendnet TEW - 658BRM
Wireless disabled
PC running Windows 7 Ulti
PC spec not important running 300 fps so its not the spec, all drivers are up to date and windows.
Wireless on router disabled

According to mweb telkom has made several changes on the exchange and has several times found no fault with my line.

I did borrow iburts one night from a friend and when my css started to lag i switched over to iburst and got a ping of between 80-120ms.

Also the time i spike is random at night and weekends, during the day my ping is perfect with no issues.

So my conclusion is:
It cannot be my PC - been formatted
Not my network - its random times
Not my mweb account - Tried a Telkom Account
Not the game - Tried Several other games still high latency spikes
Not the server - everyone else is fine

SO what i think it is:
My line to the exchange
The exchange itself

Till date not one telkom technician came out to my house to test anything here...

I really do not know what to do, i think i have tried everything from my side. Im willing to try any recommendations

I would like if someone from MWEB can comment on whats been going on, on their side and give some technical details
 
I would get another isp account, even if its R10/R15 something and test. If that account is without problems then clearly you have solved the testing problem:

1) your pc is fine
2) your network is fine
3) router is fine
4) telkom line to exchange is fine
5) exchange itself is fine
6) from exchange to where ever is fine.

Problem with the iBurst comparison is that it is not over the same line and exchange.
 
I wish it was so simple...

I tried with the following accounts:
Mweb (shaped)
Telkom
Tiscali
Mweb (Unshaped)

With no victory...

I got a FNB connect account now and these were the results:

tracert with FNB connect

Tracing route to strike.isgaming.co.za [196.38.180.25]
over a maximum of 30 hops:

1 2121 ms 1909 ms 744 ms 41.183.11.1
2 922 ms 301 ms 74 ms 41.183.132.6
3 391 ms 188 ms 462 ms 41.183.132.68
4 130 ms 111 ms 61 ms 41.183.132.82
5 216 ms 220 ms 132 ms 192.168.251.18
6 * 1731 ms * mi-za-rba-gsrpe1-gi1-0-4-100.ip.isnet.net [168.2
09.18.5]
7 2414 ms 143 ms 154 ms ar1-rba-gi0-1.ip.isnet.net [168.209.86.121]
8 93 ms 231 ms 1144 ms core1a-pkl-te-1-1.ip.isnet.net [196.26.0.60]
9 305 ms 122 ms 137 ms core1a-bry-te0-0-0-1.ip.isnet.net [168.209.100.7
8]
10 875 ms 1647 ms 165 ms 168.209.217.22
11 198 ms 63 ms 339 ms strike.isgaming.co.za [196.38.180.25]

did the same with mweb:

Tracing route to strike.isgaming.co.za [196.38.180.25]
over a maximum of 30 hops:

1 319 ms 481 ms 431 ms 41-132-14-1.dsl.mweb.co.za [41.132.14.1]
2 79 ms 28 ms 37 ms tengig-0-0-0-100.vic-ipc-2.mweb.co.za [196.22.16
3.206]
3 442 ms 532 ms 675 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
4 402 ms 204 ms 215 ms tengig0-0-0-2.11.vic-p-2.mweb.co.za [196.22.169.
226]
5 20 ms 28 ms 39 ms tengig0-0-0-0.vic-up-1.mweb.co.za [197.80.4.131]

6 74 ms 18 ms 164 ms g-0-3-vic-jinx-2.mweb.co.za [196.22.163.1]
7 1001 ms 1010 ms 653 ms is.jinx.net.za [196.223.14.10]
8 616 ms 226 ms 331 ms 196.26.0.61
9 128 ms 266 ms 230 ms 168.209.100.206
10 163 ms 439 ms 736 ms 168.209.218.22

Any other ideas guys? I also now have a 2gig FNB account that i will not use if someone wants it.
 
Clearly if multiple isps gives you more or less the same result VS iburst being smooth. Then from your pc to exchange and onwards there is an issue.

More questions
Tried different router?
What is your up/down attenuations?
This recently started?
Asked for a port reset?
Sync good?

I'm thinking that either the card in the exchange is going or your socket where the line goes in is miff. I had the latter once where I rented a house and a techie needed to reinsert my line into another socket and it was fine.
 
Thank you Prophet,

Firstly im not bad mouthing iburst, i used it as a test to see if my pc is maybe downloading something in the background or something like that. The latency i got from iburst was between 80-120ms bearing in mind i didnt test the signal strength or anything it was merely for the purpose of testing to see if the line spike which it didn't. Meaning nothing from my network is causing the spike.

Router - Used to have the Telkom Marconi router when the issue happened then borrowed friend's cisco router with same result then decided to buy a brand new one and still the same issue so its def not the router

What is your up/down attenuations? is this that ATUC rates and stuff? if yes where do i find it as this was what they noticed in the beginning that was wrong, i had no max rates set to my line

Started : 21 January 2012

Port has been resetting and stabilized so many times....

Sync meaning? My internet is up 24/7 and my download speeds dont get effected. When i start to spike, i stop playing and start downloading.

The spikes normally occurs from 5pm till i dont know what time. and it differs its not always the same times but its normally around 5 o clock when it starts and the whole weekend!

According to mweb it was with my DSLAM that was the fault and i dont know what else has been done as they always tell me telkom has done something but they never tell me what has been done.

I now went and posted a complaint on hellopeter and asked a mweb tech to come and give input here.
 
Some Guy said:
Thank you Prophet,

Firstly im not bad mouthing iburst, i used it as a test to see if my pc is maybe downloading something in the background or something like that. The latency i got from iburst was between 80-120ms bearing in mind i didnt test the signal strength or anything it was merely for the purpose of testing to see if the line spike which it didn't. Meaning nothing from my network is causing the spike.

Router - Used to have the Telkom Marconi router when the issue happened then borrowed friend's cisco router with same result then decided to buy a brand new one and still the same issue so its def not the router

What is your up/down attenuations? is this that ATUC rates and stuff? if yes where do i find it as this was what they noticed in the beginning that was wrong, i had no max rates set to my line

Started : 21 January 2012

Port has been resetting and stabilized so many times....

Sync meaning? My internet is up 24/7 and my download speeds dont get effected. When i start to spike, i stop playing and start downloading.

The spikes normally occurs from 5pm till i dont know what time. and it differs its not always the same times but its normally around 5 o clock when it starts and the whole weekend!

According to mweb it was with my DSLAM that was the fault and i dont know what else has been done as they always tell me telkom has done something but they never tell me what has been done.

I now went and posted a complaint on hellopeter and asked a mweb tech to come and give input here.
Click to expand...

I hate to say it but that sounds like congestion. Best is to get a tech out as you did. Ugh dsl is such a bitch :mad:, I hope you get it fixed.
 
Did you ask anyone in your street with dsl if they having the same problem

If yes then its congestion, if no then it's the card in dslam or something else wrong on the line somewhere.
 
According to Mweb:

Not congestion still 15% then only will the exchange be full
No one else in this area reported anything
DSLAM problem reported by mweb 2 months ago
 
I have a similar issue on my line. Generally not as severe, but it's still a real hassle. Normally only strikes after about 7pm at night, so I suspect exchange congestion has something to do with it. Telkom hasn't been able to resolve it, in spite of logging three or four tickets with them regarding it. It is ISP independent though, as I get the same latency on a Telkom account. Next time I run into the issue, I'm going to give Telkom a call and see what the line latency and exchange congestion are like then and there.
 
Please post your snr and attenuation stats, if they fine then it could only be congestion at the dslam/exchange. The 15% that Mweb and telkom are talking about is not free capacity on the dslam/exchange, but rather the amount of ports free.
 
Only 2 things can be wrong here. Either something is eating bandwidth on your line (forgotten about a torrent seeding, someone downloading without your knowledge at home etc.), or your exchange is congested.

Because the problem is at its worst at peak times and the exchange is only 15% under, I would bet my whole years salary on it being your exchange that's congested. 15% under is not sufficient because at peak times when everyone gets home from work they fire up their torrents and downloads, then that 15% unused capacity vanishes.

In this case there is basically nothing Mweb can do, they sit and plead with Telkom to get it fixed just like the rest of us.
 
You must log in or register to reply here.
Back
Top