MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
Nobody's forcing you to read it. If comments about Mweb irritate you then stop coming back for more. Nobody says they force you (Necuno skool of reading?) , but they do encourage customers to give them the line.

Sigh. Yes, the "Necuno skool of reading". You are very perceptive. How did you guess.

I look forward to a post from you sometime that does not have a single negative, barbed comment or snide remark in it. Maybe one day.

Actually, forget that. I don't look forward to any of your posts. Anyone with me in making an agreement not to feed this troll any more? I've decided I certainly have better things to do with my time than wasting it on replies.

/ignore Tanya35 :) Ah. Peace.
 
Last edited:
I would suggest we stop feeding it guys :D.

The less attention you give it the less it will post :D.

LOLs

----------------------

@Everyone, the reason that 'most' of us get slow speeds using the Mweb Uncapped is due to the fact the majority of the exchange is allocated to Telkom's own customers and a tiny portion of the exchange is allocated to the 'third-party' ISPs (i.e. Mweb, Afrihost, Screamer etc.)
Due to this you may or may not experience slow speeds with other 'third-party' ISPs. Although with Mweb Uncapped, in my case is that there are a lot of Mweb clients connected through the small portion of the exchange that Telkom has allocated to Mweb and therefore the exchange becomes congested. This means that Mweb has to shape some of what you do online (i.e. P2P downloads) and give priority to the 'larger' users of the exchange such as businesses. We all get shaped and that is why we experience slow speeds although what adds to my problem is that the exchange is 'majorly-congested' and 'old', yes the exchange is old, and that is why my speeds are incredibly slow.
 
The problem with trolling (of any kind) is that if you let it keep going on and and on there will be some negative fallout for whoever the target of the trolling is. If you're technically minded and can refute trollness then hopefully random others reading will be able to make an informed decision one way or another. The number of people feeding a troll always exceeds the number of people choosing to use the ignore function.

In this case it probably is the DSLAM or some part of Telkom's network. The rational approach to figuring this out is fairly simple however, posts like "This sort of problem has little or nothing to do with a DSLAM dude." (implication, MWEB is lying for its own nefarious reasons) do little to help the user (Bluink) come to a satisfactory explanation.

It's well known that Telkom and ISPs like to play customers off on one another. It's often the easiest solution.
However, since Bluink lives far away from the exchange, it is perfectly reasonable to assume that the DSLAM may be part of the problem.
Take into account the recent surge in ISP subscriptions due to cheap uncapped and you have a reason for Bluink's problems after 15 years of things potentially being fine.

If we accept that there is no gain for MWEB in lying about the DSLAM (really, what is the gain?) then their assertion that there is little else they can do besides ask for a transfer is proven correct. MWEB have no control over Telkom infrastructure and it is readily apparent that Telkom are not in the habit of keeping a gleeming and problem free network - that can be verified anywhere on these forums.

QED.
 
LOLs

----------------------

@Everyone, the reason that 'most' of us get slow speeds using the Mweb Uncapped is due to the fact the majority of the exchange is allocated to Telkom's own customers and a tiny portion of the exchange is allocated to the 'third-party' ISPs (i.e. Mweb, Afrihost, Screamer etc.)
Due to this you may or may not experience slow speeds with other 'third-party' ISPs. Although with Mweb Uncapped, in my case is that there are a lot of Mweb clients connected through the small portion of the exchange that Telkom has allocated to Mweb and therefore the exchange becomes congested. This means that Mweb has to shape some of what you do online (i.e. P2P downloads) and give priority to the 'larger' users of the exchange such as businesses. We all get shaped and that is why we experience slow speeds although what adds to my problem is that the exchange is 'majorly-congested' and 'old', yes the exchange is old, and that is why my speeds are incredibly slow.

I don't think so. Mweb is given the same allocation. What each ISP does with it gives it a character. If Mweb decides to load it with a contention of 1:100 instead of, say 1:20, then the latency will be higher. Consequently, they will implement measures to keep all these people browsing happily. They do this by de-prioritising games, P2P, RS. This is no secret. They allege that the need to shape so aggressively diminishes after hours, but we've seen that this is not often the case. The more people they cram into a reduced bandwidth, the cheaper the service is to run. Less support (appointments to speak to a techie) from a limited number of under-qualified people (not even a Btech) is a cost saving.

As you see, this is their model. Other ISP's do it differently.
 
The problem with trolling (of any kind) is that if you let it keep going on and and on there will be some negative fallout for whoever the target of the trolling is. If you're technically minded and can refute trollness then hopefully random others reading will be able to make an informed decision one way or another. The number of people feeding a troll always exceeds the number of people choosing to use the ignore function.

In this case it probably is the DSLAM or some part of Telkom's network. The rational approach to figuring this out is fairly simple however, posts like "This sort of problem has little or nothing to do with a DSLAM dude." (implication, MWEB is lying for its own nefarious reasons) do little to help the user (Bluink) come to a satisfactory explanation.

It's well known that Telkom and ISPs like to play customers off on one another. It's often the easiest solution.
However, since Bluink lives far away from the exchange, it is perfectly reasonable to assume that the DSLAM may be part of the problem.
Take into account the recent surge in ISP subscriptions due to cheap uncapped and you have a reason for Bluink's problems after 15 years of things potentially being fine.

If we accept that there is no gain for MWEB in lying about the DSLAM (really, what is the gain?) then their assertion that there is little else they can do besides ask for a transfer is proven correct. MWEB have no control over Telkom infrastructure and it is readily apparent that Telkom are not in the habit of keeping a gleeming and problem free network - that can be verified anywhere on these forums.

QED.
You are assuming that the Mweb person who made the assertions about the DSLAM knows what he's talking about. In my experience, Mweb techies are not much of a step above your typical Telkom van jockey. As we've seen from Telkom's pamphlets, they are not very impressed with Mweb offering uncapped and taking away some of their ISP business. One can expect rivalry or even sabotage (though I'm not entirely convinced of that).
 
Rubbish tanya mweb went out of their to show me that the problem lies with telkom.

They let me connect through saix via my username which revealed my ping and slow internet is caused by my exchanged which i pretty much thought it must be after doing my own tests on various accounts.
This was on a sunday nogal :D.

Anyways that is your last meal :D.
 
@Tanya35 Actually you think wrong as Mweb told me that they do receive a smaller allocation of the exchange and that is why we experience slower speeds and yes their contention ratios are much higher than Telkom.

@killadoob Agreed, Mweb allowed me to do the same thing and the problem persists.

------------------
ADD
It's now 23:25 and I'm downloading at 49KB/s on a 384 line, so how can the problem be that the exchange is old (Does he get young at night?!?) 0_o
 
Last edited:
Rubbish tanya mweb went out of their to show me that the problem lies with telkom.

They let me connect through saix via my username which revealed my ping and slow internet is caused by my exchanged which i pretty much thought it must be after doing my own tests on various accounts.
This was on a sunday nogal :D.

Anyways that is your last meal :D.

I guess when you connected through the SAIX proxy you also saw your ping drop?
 
@Tanya35 Actually you think wrong as Mweb told me that they do receive a smaller allocation of the exchange and that is why we experience slower speeds and yes their contention ratios are much higher than Telkom.

@killadoob Agreed, Mweb allowed me to do the same thing and the problem persists.

------------------
ADD
It's now 23:25 and I'm downloading at 49KB/s on a 384 line, so how can the problem be that the exchange is old (Does he get young at night?!?) 0_o

You are doing what now?
 
I guess when you connected through the SAIX proxy you also saw your ping drop?

Nope

Saix IS and mweb uncapped all have average local pings of of between 120-200 :(. Saix was actually the worse with 50% packet loss.

My ping this morning on mweb uncapped.

Pinging games.saix.net [196.43.22.222] with 32 bytes o
Reply from 196.43.22.222: bytes=32 time=25ms TTL=245
Reply from 196.43.22.222: bytes=32 time=23ms TTL=245
Reply from 196.43.22.222: bytes=32 time=14ms TTL=245
Reply from 196.43.22.222: bytes=32 time=32ms TTL=245

I will update it today and you will check this will last maybe an hour and it will be back over 150ms.

I have a few friends with mweb uncapped and their pings are normal and they game happily on it. I cannot get consistent pings on any account IS SAIX or MWEB
 
Last edited:
Nope

Saix IS and mweb uncapped all have average local pings of of between 120-200 :(. Saix was actually the worse with 50% packet loss.

My ping this morning on mweb uncapped.

Pinging games.saix.net [196.43.22.222] with 32 bytes o
Reply from 196.43.22.222: bytes=32 time=25ms TTL=245
Reply from 196.43.22.222: bytes=32 time=23ms TTL=245
Reply from 196.43.22.222: bytes=32 time=14ms TTL=245
Reply from 196.43.22.222: bytes=32 time=32ms TTL=245

I will update it today and you will check this will last maybe an hour and it will be back over 150ms.

I have a few friends with mweb uncapped and their pings are normal and they game happily on it. I cannot get consistent pings on any account IS SAIX or MWEB

We had the SAIX link for a few weeks to test. The pings on SAIX were consistently around 1/2 of Mweb's. Speeds were not much better though. Then Mweb said we're using too much cap on the SAIX link and kicked us back to Mweb. So much for uncapped. It was better for gaming on SAIX and torrents were nearly always full speed in the very early evening.
 
I am currently having an annoying high latency to my server in the Netherlands. Pingtest.com reveals a 500ms ping to NL. Ping in Suid-Afrika is 100ms. Anyone else having issues with latency internationally at the moment? Download speeds normal. Im having a 384 line in Kaapstad.
 
I am currently having an annoying high latency to my server in the Netherlands. Pingtest.com reveals a 500ms ping to NL. Ping in Suid-Afrika is 100ms. Anyone else having issues with latency internationally at the moment? Download speeds normal. Im having a 384 line in Kaapstad.

Hi Schavuit, I did the test on pingtest.net also on a 384k line and I got a 305ms ping
 
Redid it again and again got 500ms ping, and some packet loss. Also to USA servers.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X