Bad Latency on MWEB 4mb uncapped

[Apyrael]

im probably way off here, but i find this line interesting

5 72 ms 65 ms 62 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]

the next one is:

6 376 ms 367 ms 374 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]

perhaps there is an issue with the 10gb testing? noticing the tengig part of the dns name. bottleneck that needs to be sorted out or something.

my trace was fine:

6 37 ms 37 ms 37 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]

which could mean that there is faulty hardware or something. i dont know. i think i should stick to programming.

[Tanya35]

Yeah it's more likely a technical problem somewhere down the line, though annoying as it is they will fix it.....I hope....

How long they take is the question. I've raised some support tickets early last month which they haven't even started to look at.

[killadoob]

Mine is fine this morning.

[Pada]

At least your latency didn't go up to 1800ms like I had on my OpenWeb account in the beginning of last month. Fortunately that only lasted a single morning & afternoon

I think if you want better latencies you should stick with 384/512kbps ADSL accounts.

[GTAMCN]

My SpeedTest.net results ar not that bad but as soon as I want to DL something Http I only get a max of 256KB/s and int ping is horrible why is this ?

[tUrbZ]

seems mweb has sorted out the problem

[AeroVPS]

seems mweb has sorted out the problem

It's better, but it's not sorted out completely- still getting drops now and again.

[MWEB]

Hi All,

For those still experiencing out of the ordinary local latency, please keep posting traceroutes (to mybroadband.co.za) also indicating the region or suburb you're in. If you get a chance also try to sabela.saix.net (server sits on the other side of our peer links) e.g.

Tracing route to sabela.saix.net [196.43.1.9]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms router.local [192.168.1.1]
2 15 ms 15 ms 15 ms tengig-0-0-0.vic-lns-2.mweb.co.za [196.22.189.12]
3 15 ms 15 ms 15 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
4 21 ms 19 ms 20 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
5 15 ms 15 ms 15 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
6 16 ms 15 ms 15 ms rrba-ip-essr-2-ge-4-1.telkom-ipnet.co.za [196.43.23.106]
7 15 ms 14 ms 14 ms sabela.saix.net [196.43.1.9]

Trace complete.

Any additional info will assist in diagnosing.

MWB.

[texo]

Tracing route to sabela.saix.net [196.43.1.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 114 ms 88 ms 92 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218]
4 89 ms 102 ms 156 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 110 ms 164 ms 164 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 117 ms 102 ms 85 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 119 ms 88 ms 95 ms rrba-ip-essr-2-ge-4-1.telkom-ipnet.co.za [196.43.23.106]
8 142 ms 119 ms 102 ms sabela.saix.net [196.43.1.9]

Tracing route to a1129.g.akamai.net [92.122.127.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 84 ms 89 ms 95 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
4 129 ms 98 ms 112 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 132 ms 198 ms 188 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 86 ms 81 ms 83 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 367 ms 429 ms 298 ms lon-ip-dir-telecity-gig-1-0-2.telkom-ipnet.co.za [196.43.9.217]
8 341 ms 360 ms 379 ms 45-254-167-89.packetexchange.net [89.167.254.45]
9 328 ms 346 ms 346 ms 26-255-167-89.packetexchange.net [89.167.255.26]
10 419 ms 370 ms 354 ms 195.66.226.168 11 350 ms 396 ms 389 ms a92-122-127-10.deploy.akamaitechnologies.com [92.122.127.10]

Trace complete.

From Fish Hoek.

[Apyrael]

I know my latency is in acceptable ranges, but i was wondering why there is a jump to double the latency between step 4 and 5, and step 6 and 7 on my tracert. is this normal? Judging from the one posted here by MWEB it seems that his connection is far more stable. here is my tracert.

Tracing route to saix.net [196.25.1.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 8 ms 8 ms 8 ms 41-132-40-1.dsl.mweb.co.za [41.132.40.1]
3 37 ms 37 ms 38 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.169.146]
4 30 ms 30 ms 31 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 56 ms 59 ms 54 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 36 ms 36 ms 36 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 72 ms 71 ms 71 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30]
8 64 ms 65 ms 64 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

I am in the Somerset West area

[Gordon_R]

Much better than Wendesday, but very odd that hop 5 (& sometimes 6) keeps on fluctuating? I'm in Kenilworth, Cape Town.

Tracing route to sabela.saix.net [196.43.1.9]
over a maximum of 30 hops:

1 1 ms <10 ms <10 ms home.gateway [192.168.1.254]
2 7 ms 8 ms 8 ms 41-132-48-1.dsl.mweb.co.za [41.132.48.1]
3 28 ms 29 ms 28 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.169.134]
4 29 ms 29 ms 29 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 49 ms 55 ms 88 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 29 ms 29 ms 30 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 29 ms 29 ms 30 ms rrba-ip-essr-2-ge-4-1.telkom-ipnet.co.za [196.43.23.106]
8 29 ms 30 ms 29 ms sabela.saix.net [196.43.1.9]

Trace complete.

[Rosaudio]

Tracing route to sabela.saix.net [196.43.1.9]
over a maximum of 30 hops:

1 15 ms 15 ms 9 ms 10.0.0.2
2 40 ms 22 ms 22 ms 41-132-42-1.dsl.mweb.co.za [41.132.42.1]
3 65 ms 41 ms * tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.16
9.134]
4 44 ms 49 ms 65 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 66 ms 69 ms 67 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 72 ms 42 ms 45 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
7 53 ms 43 ms 44 ms rrba-ip-essr-1-ge-4-1.telkom-ipnet.co.za [196.43
.23.102]
8 126 ms 43 ms 42 ms sabela.saix.net [196.43.1.9]

Trace complete.

Bergvliet, Cape Town

[Nuro]

Erratic ping times.....

Pinging sabela.saix.net [196.43.1.9] with 32 bytes of data:
Reply from 196.43.1.9: bytes=32 time=118ms TTL=246
Reply from 196.43.1.9: bytes=32 time=70ms TTL=246
Reply from 196.43.1.9: bytes=32 time=216ms TTL=246
Reply from 196.43.1.9: bytes=32 time=125ms TTL=246

Traceroute...
Tracing route to sabela.saix.net [196.43.1.9]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 82 ms 9 ms 9 ms 41-132-22-1.dsl.mweb.co.za [41.132.22.1]
3 41 ms 81 ms 50 ms tengig-0-0-0-110.vic-ipc-1.mweb.co.za [196.22.169.170]
4 161 ms 209 ms 228 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 57 ms 126 ms 80 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.169.241]
6 10 ms 10 ms 10 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 112 ms 100 ms 115 ms rrba-ip-essr-1-ge-4-1.telkom-ipnet.co.za [196.43.23.102]
8 170 ms 183 ms 108 ms sabela.saix.net [196.43.1.9]

[texo]

It looks like the Akamai problem has been fixed at last, which is good news:

ping akamai.texo.co.za

Pinging a1129.g.akamai.net [196.36.108.170] with 32 bytes of data:
Reply from 196.36.108.170: bytes=32 time=30ms TTL=50
Reply from 196.36.108.170: bytes=32 time=30ms TTL=50
Reply from 196.36.108.170: bytes=32 time=30ms TTL=50
Reply from 196.36.108.170: bytes=32 time=30ms TTL=50

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

Over the last two days, pings were ranging from 200-300+ms

[TonyA]

Tracing route to sabela.saix.net [196.43.1.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 * * * Request timed out.
3 189 ms 217 ms 116 ms tengig-0-0-0-104.vic-ipc-1.mweb.co.za [196.22.16
9.146]
4 29 ms 37 ms 107 ms vl-92.vic-hscore-2.mweb.co.za [196.22.189.3]
5 172 ms 147 ms 249 ms tengig-0-0-0-0-12.vic-up-1.mweb.co.za [196.22.16
9.241]
6 146 ms 119 ms 163 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
7 161 ms 174 ms 155 ms rrba-ip-essr-2-ge-4-1.telkom-ipnet.co.za [196.43
.23.106]
8 154 ms 166 ms 171 ms sabela.saix.net [196.43.1.9]

Trace complete.

C:\Users\Tony>


Note high latency at hop 3
Capri cape Town 4096 line.