MWEB Uncapped ADSL Feedback

Status
Not open for further replies.
eish. Please can TS stop calling me. I did send the mail, it did went through as headers would reflect from my send items.



rest of

Good evening Prophet, I will request that they stop trying to contact you.
 
As much as I appreciate a phone call because I'm having issues, what I don't appreciate is the condescension. Throwing technical jargon at me and making out I dunno what I'm talking about when I do in fact know a lot, just pisses me off. And if you keep pushing that it's the exchange and you can see the exchange only has so much % available, it's congested, blah blah blah, please do tell me how my other accounts are just peachy when Mweb gives me shyte? I even tried to say as much but no, I'm a stupid consumer obviously.

Not a happy customer at the moment.
 
As much as I appreciate a phone call because I'm having issues, what I don't appreciate is the condescension. Throwing technical jargon at me and making out I dunno what I'm talking about when I do in fact know a lot, just pisses me off. And if you keep pushing that it's the exchange and you can see the exchange only has so much % available, it's congested, blah blah blah, please do tell me how my other accounts are just peachy when Mweb gives me shyte? I even tried to say as much but no, I'm a stupid consumer obviously.

Not a happy customer at the moment.

Good Evening Mephisto_Helix, my apologies for your experience. I will ensure that I provide your feedback to the relevant management.
 
Does anyone else have very slow torrents atm? I am literally getting like 24 K max off 1 Meg connection...
 
Does anyone else have very slow torrents atm? I am literally getting like 24 K max off 1 Meg connection...

Good evening Dames, Torrents speed are not gauranteed.
 
Hi Kitty09,

I have checked your account and ADSL line and could not find anything wrong.

"I want to know how it happened." Could of of just been a glitch as I do not see any dropped connections on your account.

If it happens again, let me know.

MWEB Guy

Ok, thanks :) Will let you know when it happens again :) I think it has something to do with our router. If the router is overheated (caused by downloading 24/7) then it will behave weirdly like disconnecting etc. Right?
 
Last edited:
Good evening Dames, Torrents speed are not gauranteed.

lol I know that. It just seems weird that it's fine for like 3 weeks then randomly it isn't getting full speed. Plus, usually there are a bunch of people complaining when something isn't as usual, so it seems a bit weird to me that I am the only one at the moment. There must be some reason... And I definitely haven't downloaded enough to be over threshold. But I guess there are good and bad days, so hopefully it'll be better tomorrow!

Thanks for the help earlier btw, I'll leave you alone now for a bit lol
 
I have packet lost at my buissnes adsl at work an my home dsl on the same hop 176.67.177.148



-----------------------------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network |
-----------------------------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 192.168.178.26 | - | | | 0 | x | [Local Network] |
| 1 | | 192.168.178.1 | fritz.box | | | 0 | x | [Local Network] |
| 2 | | 41.133.132.1 | 41-133-132-1.dsl.mweb.co.za | (South Africa) | | 7 | x | |
| 3 | | 196.28.178.222 | 196-28-178-222.adsl.mweb.co.za | (Mauritius) | | 24 | x | African Network Information Center |
| 4 | | 197.84.3.2 | 197-84-3-2.cpt.mweb.co.za | (Mauritius) | | 17 | x | African Network Information Center |
| 5 | | 196.28.178.113 | tengige0-3-0-0.12.cpt-up-1.mweb.co.za | (Mauritius) | | 34 | x-- | African Network Information Center |
| 6 | | 197.80.4.136 | tenge0-0-0-3.cpt-p-1.mweb.co.za | (Mauritius) | | 202 | x- | African Network Information Center |
| 7 | | 196.22.164.2 | pos0-0-3-0.lon-up-1.mweb.co.za | (South Africa) | | 170 | x | Early registration addresses |
| 8 | 56 | 176.67.177.148 | - | (United Kingdom) | | 196 | x | MWEB CONNECT (PROPRIETARY) LIMITED |
| 9 | | 195.66.224.168 | linxnap.netarch.akamai.com | London, UK | | 200 | x | London Internet Exchange (LINX) |
| 10 | | 92.122.208.144 | www.heute.de | | | 194 | x | Akamai Technologies |
-----------------------------------------------------------------------------------------------------------------------------------------------------------

 
Last edited:
lol I know that. It just seems weird that it's fine for like 3 weeks then randomly it isn't getting full speed. Plus, usually there are a bunch of people complaining when something isn't as usual, so it seems a bit weird to me that I am the only one at the moment. There must be some reason... And I definitely haven't downloaded enough to be over threshold. But I guess there are good and bad days, so hopefully it'll be better tomorrow!

Thanks for the help earlier btw, I'll leave you alone now for a bit lol

LOL... it could also be the file itself, the speed at which the file is being shared.
 
I have packet lost at my buissnes adsl at work an my home dsl on the same hop


-----------------------------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location | Tzone | ms | Graph | Network |
-----------------------------------------------------------------------------------------------------------------------------------------------------------
| 0 | | 192.168.178.26 | - | | | 0 | x | [Local Network] |
| 1 | | 192.168.178.1 | fritz.box | | | 0 | x | [Local Network] |
| 2 | | 41.133.132.1 | 41-133-132-1.dsl.mweb.co.za | (South Africa) | | 7 | x | |
| 3 | | 196.28.178.222 | 196-28-178-222.adsl.mweb.co.za | (Mauritius) | | 24 | x | African Network Information Center |
| 4 | | 197.84.3.2 | 197-84-3-2.cpt.mweb.co.za | (Mauritius) | | 17 | x | African Network Information Center |
| 5 | | 196.28.178.113 | tengige0-3-0-0.12.cpt-up-1.mweb.co.za | (Mauritius) | | 34 | x-- | African Network Information Center |
| 6 | | 197.80.4.136 | tenge0-0-0-3.cpt-p-1.mweb.co.za | (Mauritius) | | 202 | x- | African Network Information Center |
| 7 | | 196.22.164.2 | pos0-0-3-0.lon-up-1.mweb.co.za | (South Africa) | | 170 | x | Early registration addresses |
| 8 | 56 | 176.67.177.148 | - | (United Kingdom) | | 196 | x | MWEB CONNECT (PROPRIETARY) LIMITED |
| 9 | | 195.66.224.168 | linxnap.netarch.akamai.com | London, UK | | 200 | x | London Internet Exchange (LINX) |
| 10 | | 92.122.208.144 | www.heute.de | | | 194 | x | Akamai Technologies |
-----------------------------------------------------------------------------------------------------------------------------------------------------------



Evening kohlhtor, please provide me tracers to the same site using command prompt.
 
sorry i run a mac i have 56 % packet lost



==========================================================================
VisualRoute trace to www.heute.de
==========================================================================


---------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location | Tzone | ms |
---------------------------------------------------------------------------------------------------------
| 0 | | 192.168.178.26 | - | | | 0 |
| 1 | | 192.168.178.1 | fritz.box | | | 0 |
| 2 | | 41.133.132.1 | 41-133-132-1.dsl.mweb.co.za | (South Africa) | | 6 |
| 3 | | 196.28.178.222 | 196-28-178-222.adsl.mweb.co.za | (Mauritius) | | 25 |
| 4 | | 197.84.3.2 | 197-84-3-2.cpt.mweb.co.za | (Mauritius) | | 17 |
| 5 | | 196.28.178.113 | tengige0-3-0-0.12.cpt-up-1.mweb.co.za | (Mauritius) | | 26 |
| 6 | | 197.80.4.136 | tenge0-0-0-3.cpt-p-1.mweb.co.za | (Mauritius) | | 203 |
| 7 | | 196.22.164.2 | pos0-0-3-0.lon-up-1.mweb.co.za | (South Africa) | | 170 |
| 8 | 50 | 176.67.177.148 | - | (United Kingdom) | | 200 |
| 9 | | 195.66.224.168 | linxnap.netarch.akamai.com | London, UK | | 202 |
| 10 | | 92.122.208.144 | www.heute.de | | | 193 |
--------------------------------------------------------------------------------------------------------
 
macbook:~ kohlt$ traceroute www.heute.de
traceroute: Warning: www.heute.de has multiple addresses; using 92.122.208.144
traceroute to a1684.g.akamai.net (92.122.208.144), 64 hops max, 52 byte packets
1 fritz.box (192.168.178.1) 1.100 ms 0.398 ms 0.410 ms
2 41-133-132-1.dsl.mweb.co.za (41.133.132.1) 6.031 ms 6.291 ms 5.830 ms
3 196-28-178-222.adsl.mweb.co.za (196.28.178.222) 23.332 ms 23.462 ms 23.207 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 16.402 ms 17.168 ms 17.206 ms
5 tengige0-3-0-0.12.cpt-up-1.mweb.co.za (196.28.178.113) 26.712 ms 28.225 ms 25.776 ms
6 tenge0-0-0-3.cpt-p-1.mweb.co.za (197.80.4.136) 203.915 ms 204.067 ms 202.907 ms
7 pos0-0-3-0.lon-up-1.mweb.co.za (196.22.164.2) 170.710 ms 167.827 ms 167.671 ms
8 * * 176.67.177.148 (176.67.177.148) 195.178 ms
9 linxnap.netarch.akamai.com (195.66.224.168) 205.709 ms 200.965 ms 206.310 ms
10 a92-122-208-144.deploy.akamaitechnologies.com (92.122.208.144) 209.866 ms 205.565 ms 200.913 ms
macbook:~ kohlt$
 
Is anything going on in PE? I live in Mill Park and my internet has been down most of today. My router displays "down" on the adsl status page.
 
macbook:~ kohlt$ traceroute www.heute.de
traceroute: Warning: www.heute.de has multiple addresses; using 92.122.208.144
traceroute to a1684.g.akamai.net (92.122.208.144), 64 hops max, 52 byte packets
1 fritz.box (192.168.178.1) 1.100 ms 0.398 ms 0.410 ms
2 41-133-132-1.dsl.mweb.co.za (41.133.132.1) 6.031 ms 6.291 ms 5.830 ms
3 196-28-178-222.adsl.mweb.co.za (196.28.178.222) 23.332 ms 23.462 ms 23.207 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 16.402 ms 17.168 ms 17.206 ms
5 tengige0-3-0-0.12.cpt-up-1.mweb.co.za (196.28.178.113) 26.712 ms 28.225 ms 25.776 ms
6 tenge0-0-0-3.cpt-p-1.mweb.co.za (197.80.4.136) 203.915 ms 204.067 ms 202.907 ms
7 pos0-0-3-0.lon-up-1.mweb.co.za (196.22.164.2) 170.710 ms 167.827 ms 167.671 ms
8 * * 176.67.177.148 (176.67.177.148) 195.178 ms
9 linxnap.netarch.akamai.com (195.66.224.168) 205.709 ms 200.965 ms 206.310 ms
10 a92-122-208-144.deploy.akamaitechnologies.com (92.122.208.144) 209.866 ms 205.565 ms 200.913 ms
macbook:~ kohlt$

Hi kohlhtor

Thank you for the added information, I will escalate this immediately to the relevant department to investigate.

Regards
MWEB Guy
 
Is anything going on in PE? I live in Mill Park and my internet has been down most of today. My router displays "down" on the adsl status page.

Hi Bryn26

We are not experiencing any outages in your area. Send me your MWEB details so that I can investigate.

Regards
MWEB Guy
 
Hi kohlhtor

Thank you for the added information, I will escalate this immediately to the relevant department to investigate.

Regards
MWEB Guy

I have the same problem at Work Buissnes ADSL

==========================================================================
VisualRoute trace to twitter.com
==========================================================================


This trace was started on 21 Feb 2012 8:42:24 AM.
The host 'twitter.com' (known as r-199-59-148-82.twttr.com) has been found, and is reachable in
21 hops. However, it did not respond to HTTP requests on port 80. The TTL value of packets received
from it is 43.In general, hops in this route respond slowly (over 235ms on average).
All hops after hop 6 in network '[Network for 196.22.169.242]' respond particularly slowly.
This slow speed could perhaps be accounted for by the fact that the remote network is located far away.
The DNS lookup was completed almost instantaneously (less than 2ms - this may be the result of caching).

-------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location |
-------------------------------------------------------------------------------------------------
| 0 | | 10.45.5.140 | p02012722.emea.luk.com | |
| 1 | | 10.45.0.1 | r02prt003.emea.luk.com | |
| 2 | | 41.134.89.233 | 41-134-89-233.dsl.mweb.co.za | (South Africa) |
| 3 | | 197.81.146.1 | 197-81-146-1.jhb.mweb.co.za | (Australia) |
| 4 | | 197.81.146.4 | 197-81-146-4.jhb.mweb.co.za | (Australia) |
| 5 | | 196.22.169.242 | tengig0-7-0-2.12.vic-p-2.mweb.co.za | (South Africa) |
| 6 | | 197.80.5.9 | pos0-3-0-0.lon-up-1.mweb.co.za | (Australia) |
| 7 | 30 | 176.67.177.148 | - | (Australia) |
| 8 | | 212.113.14.121 | xe-10-1-3.edge4.London1.Level3.net | London, UK |
| 9 | | 4.69.139.120 | ae-52-52.csw2.London1.Level3.net | London, UK |
| 10 | | 4.69.153.137 | ae-58-223.ebr2.London1.Level3.net | London, UK |
| 11 | | 4.69.137.66 | ae-41-41.ebr1.NewYork1.Level3.net | New York, NY, USA |
| 12 | | 4.69.148.50 | ae-10-10.ebr2.Washington12.Level3.net | Washington, DC, USA |
| 13 | | 4.69.143.221 | ae-5-5.ebr2.Washington1.Level3.net | Washington, DC, USA |
| 14 | | 4.69.134.154 | ae-82-82.csw3.Washington1.Level3.net | Washington, DC, USA |
| 15 | | 4.69.149.144 | ae-3-80.edge2.Washington4.Level3.net | Washington, DC, USA |
| 17 | | 199.16.159.44 | xe-0-2-0.sjc2-cr2.twttr.com | (Australia) |
| 18 | | 199.16.159.41 | xe-1-0-0.smf1-er2.twttr.com | (Australia) |
| 19 | | 199.59.148.82 | twitter.com | (Australia) |
-------------------------------------------------------------------------------------------------
 
I have the same problem at Work Buissnes ADSL

==========================================================================
VisualRoute trace to twitter.com
==========================================================================


This trace was started on 21 Feb 2012 8:42:24 AM.
The host 'twitter.com' (known as r-199-59-148-82.twttr.com) has been found, and is reachable in
21 hops. However, it did not respond to HTTP requests on port 80. The TTL value of packets received
from it is 43.In general, hops in this route respond slowly (over 235ms on average).
All hops after hop 6 in network '[Network for 196.22.169.242]' respond particularly slowly.
This slow speed could perhaps be accounted for by the fact that the remote network is located far away.
The DNS lookup was completed almost instantaneously (less than 2ms - this may be the result of caching).

-------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address | Node Name | Location |
-------------------------------------------------------------------------------------------------
| 0 | | 10.45.5.140 | p02012722.emea.luk.com | |
| 1 | | 10.45.0.1 | r02prt003.emea.luk.com | |
| 2 | | 41.134.89.233 | 41-134-89-233.dsl.mweb.co.za | (South Africa) |
| 3 | | 197.81.146.1 | 197-81-146-1.jhb.mweb.co.za | (Australia) |
| 4 | | 197.81.146.4 | 197-81-146-4.jhb.mweb.co.za | (Australia) |
| 5 | | 196.22.169.242 | tengig0-7-0-2.12.vic-p-2.mweb.co.za | (South Africa) |
| 6 | | 197.80.5.9 | pos0-3-0-0.lon-up-1.mweb.co.za | (Australia) |
| 7 | 30 | 176.67.177.148 | - | (Australia) |
| 8 | | 212.113.14.121 | xe-10-1-3.edge4.London1.Level3.net | London, UK |
| 9 | | 4.69.139.120 | ae-52-52.csw2.London1.Level3.net | London, UK |
| 10 | | 4.69.153.137 | ae-58-223.ebr2.London1.Level3.net | London, UK |
| 11 | | 4.69.137.66 | ae-41-41.ebr1.NewYork1.Level3.net | New York, NY, USA |
| 12 | | 4.69.148.50 | ae-10-10.ebr2.Washington12.Level3.net | Washington, DC, USA |
| 13 | | 4.69.143.221 | ae-5-5.ebr2.Washington1.Level3.net | Washington, DC, USA |
| 14 | | 4.69.134.154 | ae-82-82.csw3.Washington1.Level3.net | Washington, DC, USA |
| 15 | | 4.69.149.144 | ae-3-80.edge2.Washington4.Level3.net | Washington, DC, USA |
| 17 | | 199.16.159.44 | xe-0-2-0.sjc2-cr2.twttr.com | (Australia) |
| 18 | | 199.16.159.41 | xe-1-0-0.smf1-er2.twttr.com | (Australia) |
| 19 | | 199.59.148.82 | twitter.com | (Australia) |
-------------------------------------------------------------------------------------------------

Thank you, this has been noted and escalated accordingly.

Regards
MWEB Guy
 
I have a conversation with the MWEB Premier Support help desk
There tell me everything is ok but I tell them it happen after the 197.80.5.9 | pos0-3-0-0.lon-up-1.mweb.co.za
to 176.67.177.148 this happen mweb home an BUSINESS UNCAPPED ADSL I think the Premier Support dont know there Network
There checkt with trace-rout this is not showing Packet Lost
I'm using VisualRoute
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X