MTN Uncapped Lite for R299

1823660949.png


i have downloaded 17 gbs so far this is what i get and im being throttled
 
And the best part is I was able to play black ops and modern warfare 3 on local servers with no lag or spikes
 
i think this speed is bad that you are getting. I did a signal test yesterday at home because im also thinking of getting the mtn uncapped lite. I got 4 bars on HSDPA. Speedtest i get 1Mbit/s. Is your setup set to RAS(Modem) or NDIS?

Hi,not really sure as I am not very clued up on these, but I connect through the router with the sim inside, via wireless connection to pc.
WOW is playable, even PVP was ok, will test tonight in raid to see how it goes (10-man raid, myself and girlfriend gaming same time through the router on WOW, with Raidcall to chat).


Most of the time when I go to the router main page is shows HSPA+,signel between 2 and full usually. But storm outside brought it very slow last night I must admit.

Noob question: Can you please tell me what the difference is in RAS and NDIS?

Thanks:)
 
Hi,

Can someone with this package (preferably someone with FULL signal) please do ping tests to:

quake.isgaming.co.za
 
Hi,

Can someone with this package (preferably someone with FULL signal) please do ping tests to:

quake.isgaming.co.za

I quickly tested. This was tested in Bonaero Park and I think the signal might be full.
Things to note:
1. I am already throttled (So I don't know if you will get the same ping or not)
2. While I did the ping I was streaming radio. Don't want to stop it at the moment, because I am restreaming it to everyone in the office.

ping quake.isgaming.co.za -t

Pinging quake.isgaming.co.za [196.38.180.28] with 32 bytes of
data:
Reply from 196.38.180.28: bytes=32 time=155ms TTL=50
Reply from 196.38.180.28: bytes=32 time=104ms TTL=50
Reply from 196.38.180.28: bytes=32 time=93ms TTL=50
Reply from 196.38.180.28: bytes=32 time=143ms TTL=50
Reply from 196.38.180.28: bytes=32 time=132ms TTL=50
Reply from 196.38.180.28: bytes=32 time=281ms TTL=50
Reply from 196.38.180.28: bytes=32 time=79ms TTL=50
Reply from 196.38.180.28: bytes=32 time=138ms TTL=50
Reply from 196.38.180.28: bytes=32 time=198ms TTL=50
Reply from 196.38.180.28: bytes=32 time=286ms TTL=50
Reply from 196.38.180.28: bytes=32 time=191ms TTL=50
Reply from 196.38.180.28: bytes=32 time=261ms TTL=50
Reply from 196.38.180.28: bytes=32 time=159ms TTL=50
Reply from 196.38.180.28: bytes=32 time=318ms TTL=50
Reply from 196.38.180.28: bytes=32 time=67ms TTL=50
Reply from 196.38.180.28: bytes=32 time=147ms TTL=50
Reply from 196.38.180.28: bytes=32 time=286ms TTL=50
Reply from 196.38.180.28: bytes=32 time=184ms TTL=50
Reply from 196.38.180.28: bytes=32 time=192ms TTL=50
Reply from 196.38.180.28: bytes=32 time=152ms TTL=50
Reply from 196.38.180.28: bytes=32 time=100ms TTL=50
Reply from 196.38.180.28: bytes=32 time=99ms TTL=50
Reply from 196.38.180.28: bytes=32 time=198ms TTL=50
Reply from 196.38.180.28: bytes=32 time=245ms TTL=50
Reply from 196.38.180.28: bytes=32 time=216ms TTL=50
Reply from 196.38.180.28: bytes=32 time=93ms TTL=50
Reply from 196.38.180.28: bytes=32 time=102ms TTL=50
Reply from 196.38.180.28: bytes=32 time=322ms TTL=50
Reply from 196.38.180.28: bytes=32 time=80ms TTL=50
Reply from 196.38.180.28: bytes=32 time=129ms TTL=50
Reply from 196.38.180.28: bytes=32 time=178ms TTL=50
Reply from 196.38.180.28: bytes=32 time=117ms TTL=50
Reply from 196.38.180.28: bytes=32 time=145ms TTL=50
Reply from 196.38.180.28: bytes=32 time=291ms TTL=50
Reply from 196.38.180.28: bytes=32 time=90ms TTL=50
Reply from 196.38.180.28: bytes=32 time=109ms TTL=50
Reply from 196.38.180.28: bytes=32 time=237ms TTL=50
Reply from 196.38.180.28: bytes=32 time=237ms TTL=50
Reply from 196.38.180.28: bytes=32 time=145ms TTL=50
Reply from 196.38.180.28: bytes=32 time=95ms TTL=50

Ping statistics for 196.38.180.28:
Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 67ms, Maximum = 322ms, Average = 169ms
 
Last edited:
Strange,

Pings are better while streaming radio in the background:
C:\Users\Leon>ping quake.isgaming.co.za -t

Pinging quake.isgaming.co.za [196.38.180.28] with 32 bytes of data:
Reply from 196.38.180.28: bytes=32 time=229ms TTL=49
Reply from 196.38.180.28: bytes=32 time=315ms TTL=49
Reply from 196.38.180.28: bytes=32 time=225ms TTL=49
Reply from 196.38.180.28: bytes=32 time=225ms TTL=49
Reply from 196.38.180.28: bytes=32 time=338ms TTL=49
Reply from 196.38.180.28: bytes=32 time=151ms TTL=49
Reply from 196.38.180.28: bytes=32 time=71ms TTL=49
Reply from 196.38.180.28: bytes=32 time=250ms TTL=49
Reply from 196.38.180.28: bytes=32 time=330ms TTL=49
Reply from 196.38.180.28: bytes=32 time=209ms TTL=49
Reply from 196.38.180.28: bytes=32 time=93ms TTL=49
Reply from 196.38.180.28: bytes=32 time=99ms TTL=49
Reply from 196.38.180.28: bytes=32 time=258ms TTL=49
Reply from 196.38.180.28: bytes=32 time=229ms TTL=49
Reply from 196.38.180.28: bytes=32 time=139ms TTL=49
Reply from 196.38.180.28: bytes=32 time=229ms TTL=49
Reply from 196.38.180.28: bytes=32 time=217ms TTL=49
Reply from 196.38.180.28: bytes=32 time=76ms TTL=49
Reply from 196.38.180.28: bytes=32 time=106ms TTL=49
Reply from 196.38.180.28: bytes=32 time=145ms TTL=49
Reply from 196.38.180.28: bytes=32 time=105ms TTL=49
Reply from 196.38.180.28: bytes=32 time=95ms TTL=49
Reply from 196.38.180.28: bytes=32 time=285ms TTL=49
Reply from 196.38.180.28: bytes=32 time=243ms TTL=49
Reply from 196.38.180.28: bytes=32 time=141ms TTL=49
Reply from 196.38.180.28: bytes=32 time=120ms TTL=49
Reply from 196.38.180.28: bytes=32 time=109ms TTL=49
Reply from 196.38.180.28: bytes=32 time=119ms TTL=49
Reply from 196.38.180.28: bytes=32 time=108ms TTL=49
Reply from 196.38.180.28: bytes=32 time=118ms TTL=49
Reply from 196.38.180.28: bytes=32 time=137ms TTL=49
Reply from 196.38.180.28: bytes=32 time=226ms TTL=49
Reply from 196.38.180.28: bytes=32 time=186ms TTL=49
Reply from 196.38.180.28: bytes=32 time=203ms TTL=49
Reply from 196.38.180.28: bytes=32 time=203ms TTL=49
Reply from 196.38.180.28: bytes=32 time=101ms TTL=49
Reply from 196.38.180.28: bytes=32 time=202ms TTL=49
Reply from 196.38.180.28: bytes=32 time=100ms TTL=49
Reply from 196.38.180.28: bytes=32 time=89ms TTL=49
Reply from 196.38.180.28: bytes=32 time=97ms TTL=49
Reply from 196.38.180.28: bytes=32 time=127ms TTL=49
Reply from 196.38.180.28: bytes=32 time=176ms TTL=49
Reply from 196.38.180.28: bytes=32 time=176ms TTL=49
Reply from 196.38.180.28: bytes=32 time=155ms TTL=49
Reply from 196.38.180.28: bytes=32 time=95ms TTL=49
Reply from 196.38.180.28: bytes=32 time=65ms TTL=49
Reply from 196.38.180.28: bytes=32 time=356ms TTL=49
Reply from 196.38.180.28: bytes=32 time=366ms TTL=49
Reply from 196.38.180.28: bytes=32 time=202ms TTL=49

Ping statistics for 196.38.180.28:
Packets: Sent = 49, Received = 49, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 65ms, Maximum = 366ms, Average = 176ms



Without streaming:
C:\Users\Leon>ping quake.isgaming.co.za -t

Pinging quake.isgaming.co.za [196.38.180.28] with 32 bytes of data:
Reply from 196.38.180.28: bytes=32 time=419ms TTL=49
Reply from 196.38.180.28: bytes=32 time=1238ms TTL=49
Reply from 196.38.180.28: bytes=32 time=500ms TTL=49
Reply from 196.38.180.28: bytes=32 time=499ms TTL=49
Reply from 196.38.180.28: bytes=32 time=398ms TTL=49
Reply from 196.38.180.28: bytes=32 time=518ms TTL=49
Reply from 196.38.180.28: bytes=32 time=497ms TTL=49
Reply from 196.38.180.28: bytes=32 time=507ms TTL=49
Reply from 196.38.180.28: bytes=32 time=474ms TTL=49
Reply from 196.38.180.28: bytes=32 time=483ms TTL=49
Reply from 196.38.180.28: bytes=32 time=492ms TTL=49
Reply from 196.38.180.28: bytes=32 time=902ms TTL=49
Reply from 196.38.180.28: bytes=32 time=242ms TTL=49
Reply from 196.38.180.28: bytes=32 time=204ms TTL=49
Reply from 196.38.180.28: bytes=32 time=214ms TTL=49
Reply from 196.38.180.28: bytes=32 time=224ms TTL=49
Reply from 196.38.180.28: bytes=32 time=1429ms TTL=49
Reply from 196.38.180.28: bytes=32 time=909ms TTL=49
Reply from 196.38.180.28: bytes=32 time=408ms TTL=49

Ping statistics for 196.38.180.28:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 204ms, Maximum = 1429ms, Average = 555ms
 
This is what I get, with full signal

Pinging quake.isgaming.co.za [196.38.180.28] with 32 bytes of data:
Reply from 196.38.180.28: bytes=32 time=734ms TTL=49
Reply from 196.38.180.28: bytes=32 time=648ms TTL=49
Reply from 196.38.180.28: bytes=32 time=657ms TTL=49
Reply from 196.38.180.28: bytes=32 time=437ms TTL=49
Reply from 196.38.180.28: bytes=32 time=337ms TTL=49
Reply from 196.38.180.28: bytes=32 time=218ms TTL=49
Reply from 196.38.180.28: bytes=32 time=268ms TTL=49
Reply from 196.38.180.28: bytes=32 time=268ms TTL=49
Reply from 196.38.180.28: bytes=32 time=258ms TTL=49
Reply from 196.38.180.28: bytes=32 time=550ms TTL=49
Reply from 196.38.180.28: bytes=32 time=158ms TTL=49
Reply from 196.38.180.28: bytes=32 time=228ms TTL=49
Reply from 196.38.180.28: bytes=32 time=258ms TTL=49
Reply from 196.38.180.28: bytes=32 time=168ms TTL=49
Reply from 196.38.180.28: bytes=32 time=378ms TTL=49
Reply from 196.38.180.28: bytes=32 time=188ms TTL=49
Reply from 196.38.180.28: bytes=32 time=168ms TTL=49
Reply from 196.38.180.28: bytes=32 time=228ms TTL=49
Reply from 196.38.180.28: bytes=32 time=248ms TTL=49
Reply from 196.38.180.28: bytes=32 time=289ms TTL=49
Reply from 196.38.180.28: bytes=32 time=118ms TTL=49
Reply from 196.38.180.28: bytes=32 time=159ms TTL=49
Reply from 196.38.180.28: bytes=32 time=238ms TTL=49
Reply from 196.38.180.28: bytes=32 time=269ms TTL=49
Reply from 196.38.180.28: bytes=32 time=299ms TTL=49
Reply from 196.38.180.28: bytes=32 time=249ms TTL=49
Reply from 196.38.180.28: bytes=32 time=349ms TTL=49
Reply from 196.38.180.28: bytes=32 time=319ms TTL=49
Reply from 196.38.180.28: bytes=32 time=179ms TTL=49
Reply from 196.38.180.28: bytes=32 time=299ms TTL=49
Reply from 196.38.180.28: bytes=32 time=229ms TTL=49
Reply from 196.38.180.28: bytes=32 time=189ms TTL=49
Reply from 196.38.180.28: bytes=32 time=219ms TTL=49
Reply from 196.38.180.28: bytes=32 time=319ms TTL=49
Reply from 196.38.180.28: bytes=32 time=289ms TTL=49
Reply from 196.38.180.28: bytes=32 time=219ms TTL=49
 
I have pretty bad signal (~100dBm). So for other people that have bad reception: I get around 100KBps while not throttled. Currently my throttled speed is at around 15KBps, with bursts up to around 30KBps.

Pings around 180ms to local and 300ms+ to EU, very jittery but some MMORPGs are playable.

Pinging kat.ph [109.163.227.73] with 32 bytes of data:
Reply from 109.163.227.73: bytes=32 time=305ms TTL=50
Reply from 109.163.227.73: bytes=32 time=323ms TTL=50
Reply from 109.163.227.73: bytes=32 time=461ms TTL=50
Reply from 109.163.227.73: bytes=32 time=399ms TTL=50

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


Pinging mtn.co.za [196.11.240.17] with 32 bytes of data:
Reply from 196.11.240.17: bytes=32 time=303ms TTL=50
Reply from 196.11.240.17: bytes=32 time=181ms TTL=50
Reply from 196.11.240.17: bytes=32 time=168ms TTL=50
Reply from 196.11.240.17: bytes=32 time=195ms TTL=50

Ping statistics for 196.11.240.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 303ms, Average = 211ms
 
Hey guys... so...do they throttle you now, or not.... what's the official answer?

And if they throttle you, to what speeds?
 
Hey guys... so...do they throttle you now, or not.... what's the official answer?

And if they throttle you, to what speeds?

Yes, once you receive an sms from them that says you have been throttled then you know.

The throttled speed is a bit varaible:
Test I did now: http://www.speedtest.net/result/1839139341.png
And another test I did a few days ago:
I have been throttled since 5 days ago. Still going good
Here is my throttled speed: http://www.speedtest.net/result/1833102037.png
 
Is this package still available? Went to MTN and they have the uncapped lite with router only for R 329 per month.
 
Is this package still available? Went to MTN and they have the uncapped lite with router only for R 329 per month.

Should still be available.

As far as I know there are 3 Uncapped Lite packages:
- R289p/m then you get the E367 USB modem
- R299p/m then you get the B660 router
- R329p/m then you get the B683 router
 
Any of you guys use this with newsgroups?
Guess it would be the paid option if being used.
 
Should still be available.

As far as I know there are 3 Uncapped Lite packages:
- R289p/m then you get the E367 USB modem
- R299p/m then you get the B660 router
- R329p/m then you get the B683 router

Thanks for that. The lady at mtn told me they had those options you mentioned but that they were over and only the R 329 option was available...will contact mtn sales on Monday and recheck
 
1844653783.png

1844653783.png
[/URL][/IMG]

beat that mtn and vodacom and even you telkom !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

888888888888888888888888888tttttttttttttttttttttttaaaaaaaaaaaaaaaaaaaaaaaaa !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 
Top
Sign up to the MyBroadband newsletter
X