MWEB Uncapped Subscribers Feedback

Status
Not open for further replies.
milomak said:
what is the theoretical lowest ping to sites in europe?

i do notice however that in the UK, my pings to london are higher than to other sites in the UK. Is this a sign of how busy the servers are?
Click to expand...

Due to our distance in theory i dont think we will ever achieve anything lower than 180ms also some ISP's have the worst routing on earth
 
XperiAnce said:
Strange request, please can someone ping www.telkomsa.net and post their results?
Pref. someone with the 384k uncapped MWEB.

Thanks :)
Click to expand...

Pinging www.telkom.net [125.160.17.26] with 32 bytes of data:
Reply from 125.160.17.26: bytes=32 time=647ms TTL=41
Reply from 125.160.17.26: bytes=32 time=651ms TTL=41
Reply from 125.160.17.26: bytes=32 time=650ms TTL=41
Reply from 125.160.17.26: bytes=32 time=645ms TTL=41

Ping statistics for 125.160.17.26:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 645ms, Maximum = 651ms, Average = 648ms
 
kimbo said:
Pinging www.telkom.net [125.160.17.26] with 32 bytes of data:
Reply from 125.160.17.26: bytes=32 time=647ms TTL=41
Reply from 125.160.17.26: bytes=32 time=651ms TTL=41
Reply from 125.160.17.26: bytes=32 time=650ms TTL=41
Reply from 125.160.17.26: bytes=32 time=645ms TTL=41

Ping statistics for 125.160.17.26:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 645ms, Maximum = 651ms, Average = 648ms
Click to expand...

wow those are terrible response times. :mad:

LOL WTF telkom.net traceroute:
semaphore@helix ~ $ traceroute www.telkom.net
traceroute to www.telkom.net (125.160.17.26), 30 hops max, 60 byte packets
1 10.0.0.2 (10.0.0.2) 1.291 ms 1.700 ms 2.083 ms
2 dsl-185-76-1.dynamic.wa.co.za (41.185.76.1) 18.579 ms 18.541 ms 18.616 ms
3 vl108.cr.gw.cpt.za.wa.co.za (196.220.59.238) 45.427 ms 47.495 ms 49.822 ms
4 vl33.er.gw.cpt.za.wa.co.za (41.185.0.30) 53.343 ms vl32.er.gw.cpt.za.wa.co.za (41.185.0.26) 54.499 ms 57.621 ms
5 upstream.vl101.gw.cpt.za.wa.co.za (196.220.59.226) 60.599 ms 61.276 ms upstream.vl102.gw.cpt.za.wa.co.za (196.220.59.230) 64.279 ms
6 196.43.9.54 (196.43.9.54) 227.107 ms 197.464 ms 196.951 ms
7 ge-6-2-903.car5.London1.Level3.net (212.113.10.69) 314.402 ms 314.953 ms 315.299 ms
8 ae-34-52.ebr2.London1.Level3.net (4.69.139.97) 208.347 ms 211.154 ms 213.954 ms
9 ae-41-41.ebr1.NewYork1.Level3.net (4.69.137.66) 285.223 ms ae-44-44.ebr1.NewYork1.Level3.net (4.69.137.78) 288.048 ms ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70) 290.977 ms
10 ae-71-71.csw2.NewYork1.Level3.net (4.69.134.70) 302.275 ms 302.751 ms ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78) 302.201 ms
11 ae-74-74.ebr4.NewYork1.Level3.net (4.69.134.117) 307.820 ms ae-64-64.ebr4.NewYork1.Level3.net (4.69.134.113) 308.092 ms ae-74-74.ebr4.NewYork1.Level3.net (4.69.134.117) 307.556 ms
12 ae-2-2.ebr4.SanJose1.Level3.net (4.69.135.185) 348.674 ms 340.078 ms 352.089 ms
13 ae-64-64.csw1.SanJose1.Level3.net (4.69.134.242) 339.795 ms ae-94-94.csw4.SanJose1.Level3.net (4.69.134.254) 345.153 ms 344.054 ms
14 ae-63-63.ebr3.SanJose1.Level3.net (4.69.134.225) 346.524 ms ae-93-93.ebr3.SanJose1.Level3.net (4.69.134.237) 340.239 ms 353.178 ms
15 ae-2-2.ebr3.LosAngeles1.Level3.net (4.69.132.10) 347.933 ms 343.387 ms 356.387 ms
16 ae-3-80.edge6.LosAngeles1.Level3.net (4.69.144.142) 348.212 ms ae-1-60.edge6.LosAngeles1.Level3.net (4.69.144.14) 341.000 ms ae-3-80.edge6.LosAngeles1.Level3.net (4.69.144.142) 372.949 ms
17 PT-TELEKOMU.edge6.LosAngeles1.Level3.net (4.59.50.122) 529.651 ms 527.164 ms 529.928 ms
18 89.subnet118-98-48.astinet.telkom.net.id (118.98.48.89) 530.944 ms 534.410 ms 536.898 ms
19 125.160.6.97 (125.160.6.97) 567.296 ms 566.000 ms 571.599 ms
Click to expand...
 
Last edited:
XperiAnce said:
Guys guys guys :D :D

www.telkomSA.net

You're leaving out the SA :)
Click to expand...

Pinging telkomsa.net [196.25.211.40] with 32 bytes of data:
Reply from 196.25.211.40: bytes=32 time=48ms TTL=119
Reply from 196.25.211.40: bytes=32 time=48ms TTL=119
Reply from 196.25.211.40: bytes=32 time=47ms TTL=119
Reply from 196.25.211.40: bytes=32 time=47ms TTL=119

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

Soz, it's early in the morning lol
 
Last edited:
kimbo said:
Pinging telkomsa.net [196.25.211.40] with 32 bytes of data:
Reply from 196.25.211.40: bytes=32 time=48ms TTL=119
Reply from 196.25.211.40: bytes=32 time=48ms TTL=119
Reply from 196.25.211.40: bytes=32 time=47ms TTL=119
Reply from 196.25.211.40: bytes=32 time=47ms TTL=119

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

Soz, it's early in the morning lol
Click to expand...

LOL that looks much better, and really good for 384k :)

Will see how things run with my free mweb account for April before I sign up.
 
Eek no that's terrible :( My IS (Openweb) account pings telkomsa at 26ms...

...although that is after hours. Do you think that tonight at around 8pm you could ping it again and let me know the results? I'll post here to remind :)
Thanks :)
 
Has anyone else noticed slow international speeds this weekend?
Got the 4MB uncapped on Friday and things were pretty fast, could stream 480p from Youtube with no delay and 720p with just a little bit of an initial buffer.
Saturday was ok, didn't really check it out too much but Sunday was very slow.
Speedtest to Joburg was ~2Mbps while speedtest to London was 1Mbps and NY was 700kbps.
This morning the Joburg link is just over 3 which is great, but the international is the same speed.
Anyone else having this issue?
I'm hoping that these are just load balancing issues that will be sorted out when the product 'officially launches' on Mon / Tue?
 
XperiAnce said:
Eek no that's terrible :( My IS (Openweb) account pings telkomsa at 26ms...

...although that is after hours. Do you think that tonight at around 8pm you could ping it again and let me know the results? I'll post here to remind :)
Thanks :)
Click to expand...

k :)
 
XperiAnce said:
Eek no that's terrible :( My IS (Openweb) account pings telkomsa at 26ms...

...although that is after hours. Do you think that tonight at around 8pm you could ping it again and let me know the results? I'll post here to remind :)
Thanks :)
Click to expand...

Well I get that with my Openweb (IS local only) account at the moment, so for me its good.

But let's wait and see if it improves after 8pm, but still 40ms is still awesome for me during business hours.
 
Quick question, on a 384k account realistically what would be an "excellent" speed on speedtest.net? Theoretically maximum line speed would be 0.38Mbps down and 0.13Mbps up right, but in reality one can't expect that speed.

These are my latest results on the 384k Uncapped:

LOCAL:
756992687.png
and
13108193.png

INT UK:
756996360.png
and
13108249.png


I think the above is absolutely fantastic, would someone have a look though and confirm whether this is in fact good?
 
My mweb has just gone downhill. Downloads,uploads and browsing is terribly slow!
anyone else having the same issue?

EDIT: Nevermind, it had a slow moment for 2min. now its going well again
 
Garyvdh said:
Nope. All weekdays are shaped. All ISPs do this.
Click to expand...

Most do. But with Mweb p2p is going at full speed. So it either that the traffic on the network is low or that they have included today as off peak.
 
Give me a torrent your dling at full speed pls cause I just got back home and yoh, still cant get more than like 180kb on anything :(
 
Technically the shaping rules are active at all times, but due to the reduced demand for priority protocols in off-peak hours, all excess capacity will be made avaliable to non-priority protocols and the service will behave in a completely unshaped manner. In other words the rules are always active but only effective when demand exceeds supply (for priority bandwidth).
Click to expand...

This is what the Mweb rep said on the Mweb Q&A thread.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X