OpenWeb ADSL Feedback Thread (Pt2)

DiffProbe release. January 2012. Build 1008.
Shaper Detection Module.

Connected to server 64.9.225.179.

Estimating capacity:
Upstream: 334 Kbps.
Downstream: 2557 Kbps.

The measurement will take upto 2.5 minutes. Please wait.

Checking for traffic shapers:

Upstream: No shaper detected.
Median received rate: 317 Kbps.

Downstream: Burst size: 442-478 KB;
Shaping rate: 2072 Kbps.
 
DiffProbe release. January 2012.
Shaper Detection Module.

Connected to server 38.98.51.47.

Estimating capacity:
Upstream: 1451 Kbps.
Downstream: 16755 Kbps.

The measurement will last for about 2.5 minutes. Please wait.

Checking for traffic shapers:

Upstream: No shaper detected.
Median received rate: 1409 Kbps.

Downstream: No shaper detected.
Median received rate: 16426 Kbps.
 
MrBeep goes on holiday. All hell breaks loose :D

LOL!
Yeah well. I don't think people are overreacting though.

You get used to a service, adapt to the limitations etc. and then suddenly one day you're troubleshooting all night long... (almost had to replace another keyboard, internet anger issues, I know :o)

These unexpected protocol shaping acrobatics are the worst!
It's not like apps such as XBMC just gracefully accepts the information that dribbles to it.... some apps/devices/codecs etc. don't have any idea how deal with this "semi-connectivity", resulting in all kinds of problems, I even thought my media PC's codecs were screwed at some point.
 
Agree with most other results posted today.

But, with that said... I think its either an IS or Telkom problem. (99% likely Telkom).

Get yourselves "Pingplotter" (standard edition under trial will work, even with annoying delay).

My first hop to exchange is 500+ ms ping right off the bat!
Been this way all day and night since Tuesday.
Also, Telkom is shifting blame on the issue. Try calling 10210 and try to report a fault (options 1, then 2).
An automated voice starts yabbing on about Eskom loadbalancing... THE FU##?!


So yeah... i tested with Telkom guest account... same results.
Tested with Afrihost 1GB account... same results.
Tested with friend's MWEB account... same results.
Swopped out router for my backup unit and repeated above tests on all 4 accounts... same results.

Therefore: Exchange problem.
Now the issue becomes: There is almost NOTHING we can do about it. Except complain. For months. And then some more.

And then MAYBE... bigass maybe... they might fix it.


My pings etc. look OK man, you've definitely got a case of Telkomilitus (:sick:), will probably take weeks (months? years?) to sort out...
Personally I'm terrified of exchange issues, can't even handle the limitations on a functioning 6Mb line any more, nevermind having to be downgraded...
All the best...

Sincerely,
Anyone-who's-ever-had-to-deal-with-Telkom.
 
Connection. They use the WebAfrica 5-Star system. Even on 1 Star I get full speed 99% of the time on my 4Meg account after 17:30 and all weekend.

Those prices look a bit too cheap for a good service, I dont plan on downloading lots of data but I need all protocols to work like p2p and steam I don't mind if it only works after hours, I'm used to that from openweb. But if I have to get a torrent of something and its 7PM will it actually come through ? also is this adsl from incredible connection ? good for them...
 
Running an OpenWeb Gold uncapped 2mb, but I'm seeing horribly latencies in WoW.

Normally I sit at around 200ms but it goes up as high as 800ms. This has only been a problem these last few days. What's going on?

This is a tracert to the UK:

C:\Users\Brandon>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.244.71]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.1.1
2 276 ms 311 ms 343 ms 196-210-157-1.dynamic.isadsl.co.za [196.210.157
1]
3 418 ms 397 ms 345 ms cdsl1-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.
45]
4 323 ms 319 ms 341 ms cdsl1-umh-bd150.ip.isnet.net [196.26.210.192]
5 313 ms 249 ms 195 ms 196.38.74.176
6 170 ms 168 ms 183 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]

7 215 ms 218 ms 194 ms 168.209.201.73
8 525 ms 590 ms 468 ms bbc-linx.pr01.rbsov.bbc.co.uk [195.66.236.103]
9 * * * Request timed out.
10 * * * Request timed out.
11 422 ms 429 ms 487 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
12 519 ms 877 ms 429 ms 132.185.255.149
13 404 ms 363 ms 343 ms bbc-vip116.telhc.bbc.co.uk [212.58.244.71]

Trace complete.
 
While 71 to your exchange is pretty ****ty, it looks like most of your problems really kick in at hop 6 with IS.
Looks like that would be the landing station for submarine cable, due to next hop being London.

Actually hop6 would be IS Docklands (UK) already. Hop5 would be the last hop in ZA.

Michael
 
Running an OpenWeb Gold uncapped 2mb, but I'm seeing horribly latencies in WoW.

Normally I sit at around 200ms but it goes up as high as 800ms. This has only been a problem these last few days. What's going on?

This is a tracert to the UK:

C:\Users\Brandon>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.244.71]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.1.1
2 276 ms 311 ms 343 ms 196-210-157-1.dynamic.isadsl.co.za [196.210.1571]

That hop screams exchange congestion.

Michael
 
Those prices look a bit too cheap for a good service, I dont plan on downloading lots of data but I need all protocols to work like p2p and steam I don't mind if it only works after hours, I'm used to that from openweb. But if I have to get a torrent of something and its 7PM will it actually come through ? also is this adsl from incredible connection ? good for them...
They use IS Bandwidth as well. If you schedule P2P/NNTP downloads between 00:00 and 06:00 it does not affect your star-rating whatsoever. Been with them since November when they launched and thought to give the R250 Titan account a try, see what difference R10 makes. 2 Days later and well, you can read the posts.

The Titan 4Meg account is flying now but its 23:00 and I wanted to watch House of Cards at 20:00 on Netflix in HD with DD5.1, when the connection barely broke 1Meg.
 
Last edited:
Running an OpenWeb Gold uncapped 2mb, but I'm seeing horribly latencies in WoW.

Normally I sit at around 200ms but it goes up as high as 800ms. This has only been a problem these last few days. What's going on?

This is a tracert to the UK:

<snip>

Thats 99% an exchange problem.
If your first hop after router is THAT high, that indicates a definite exchange (Telkom) problem.
Could also be a bad line altogether, but my first suspicion is exchange.
 
Actually hop6 would be IS Docklands (UK) already. Hop5 would be the last hop in ZA.

Michael

Thanks for the correction.
Still points to cable problems under H20 as the main culprit XD

But those local pings being quite a lot higher than what they *SHOULD* be could point to shaping, bad line, or a hundred other things being wrong.

I highly suggest getting a free 1GB Afrihost DSL account for testing purposes.

If the results are generally the same, you have an issue apart from ISP(OpenWeb).
 
Last edited:
Those prices look a bit too cheap for a good service, I dont plan on downloading lots of data but I need all protocols to work like p2p and steam I don't mind if it only works after hours, I'm used to that from openweb. But if I have to get a torrent of something and its 7PM will it actually come through ? also is this adsl from incredible connection ? good for them...

I've used them, they're good, sounds like they will meet your needs. Full speed after 5pm.
 
Last edited:
But those local pings being quite a lot higher than what they *SHOULD* be could point to shaping, bad line, or a hundred other things being wrong.

I highly suggest getting a free 1GB Afrihost DSL account for testing purposes.

If the results are generally the same, you have an issue apart from ISP(OpenWeb).

Well, if I traceroute using my account, sure not OW, but still IS reseller.

Code:
Tracing the route to www.bbc.net.uk (212.58.246.92)

  1 196-210-136-1.dynamic.isadsl.co.za (196.210.136.1) 8 msec 4 msec 4 msec
  2 196.38.73.85 8 msec 8 msec 8 msec
  3 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 8 msec 8 msec 8 msec
  4 core2-pkl-t0-7-0-0.ip.isnet.net (168.209.1.163) 12 msec 12 msec 12 msec
  5 core2b-dock-pos-0-3-4-0.ip.isnet.net (168.209.201.65) 180 msec 176 msec 180 msec
  6 bbc-linx.pr01.rbsov.bbc.co.uk (195.66.236.103) 176 msec 172 msec 176 msec
 7  *  *  *
  8 ae0.er01.cwwtf.bbc.co.uk (132.185.254.93) 172 msec 184 msec 180 msec
  9  *  *  *
 10  *  *  *

The hops with * could be them just blocking that ICMP type since it is pingable

Code:
Sending 5, 100-byte ICMP Echos to 212.58.246.92, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 180/182/184 ms

But as you pointed out, could be line. Best to confirm with a non IS account.

Michael
 
Top
Sign up to the MyBroadband newsletter
X