OpenWeb ADSL Feedback Thread

Status
Not open for further replies.
MrBEEP said:
This sounds like a line fault.

It seems your your copper cannot handle the higher speed. I would strongly suggest you call Telkom on 10210 and log a fault.

Of course, my verdict is used at own risk until we receive your ADSL username via support
Click to expand...

But it happens very often at night (around 11pm - 1am) :confused: My line is always 100% fine during daytime.
 
timmie23 said:
MrBeep. How is the network looking today? Still busy? PSN downloads are just impossibly slow during the daytime. I know you say download at night, but sometimes you want/need to download in the day.
Click to expand...

isnt the psn store throttled during the day? or 'managed' like other download sources.
 
Great. Just great. My connection just went down for a few minutes AFTER restarting my router because it claims that the DNS servers were offline.

Sent my compliant to the support department.
 
Last edited:
Having some serious issues here with OpenWeb account. Timeouts and very slow response time. Seems to be a DNS related issue. It seems me and DarkSpectre are in the same boat. Anyone else? Mr. Beep, Internet Solutions having issues again or some problems on your DNS servers? I am on a gold uncapped account. Have tested with other ISP accounts and they work 100%.

Tracert (though I don't think the problem is here, I think its a DNS issue):

1 <1 ms <1 ms <1 ms WBRT2 [192.168.0.2]
2 8 ms 7 ms 7 ms 196-210-117-1.dynamic.isadsl.co.za [196.210.117.
1]
3 10 ms 10 ms 9 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
4 9 ms 10 ms 10 ms 196.35.115.136
5 12 ms 12 ms 12 ms core2b-ctn-gi0-1.ip.isnet.net [168.209.2.3]
6 164 ms 162 ms 163 ms 168.209.246.3
7 198 ms 162 ms 163 ms bbc-linx.pr01.rbsov.bbc.co.uk [195.66.236.103]
8 * * * Request timed out.
9 * * * Request timed out.
10 158 ms 158 ms 160 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 162 ms 163 ms 162 ms 132.185.255.140
12 163 ms 163 ms 163 ms www-vip.telhc.bbc.co.uk [212.58.251.195]

Trace complete.
 
Last edited:
There are no general issues currently.

Kindly email [email protected] so that we can investigate

phil1982 said:
Having some serious issues here with OpenWeb account. Timeouts and very slow response time. Seems to be a DNS related issue. It seems me and DarkSpectre are in the same boat. Anyone else? Mr. Beep, Internet Solutions having issues again or some problems on your DNS servers? I am on a gold uncapped account. Have tested with other ISP accounts and they work 100%.

Tracert (though I don't think the problem is here, I think its a DNS issue):

1 <1 ms <1 ms <1 ms WBRT2 [192.168.0.2]
2 8 ms 7 ms 7 ms 196-210-117-1.dynamic.isadsl.co.za [196.210.117.
1]
3 10 ms 10 ms 9 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
4 9 ms 10 ms 10 ms 196.35.115.136
5 12 ms 12 ms 12 ms core2b-ctn-gi0-1.ip.isnet.net [168.209.2.3]
6 164 ms 162 ms 163 ms 168.209.246.3
7 198 ms 162 ms 163 ms bbc-linx.pr01.rbsov.bbc.co.uk [195.66.236.103]
8 * * * Request timed out.
9 * * * Request timed out.
10 158 ms 158 ms 160 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 162 ms 163 ms 162 ms 132.185.255.140
12 163 ms 163 ms 163 ms www-vip.telhc.bbc.co.uk [212.58.251.195]

Trace complete.
Click to expand...
 
Well after dealing with the Telkom Rep and looking at my data again it really does seem Openweb. Only at night during "peak" times and after rebooting router takes ages to authenticate:

So what I did was have a constant ping going. And whenever I had dropped packets I did a tracert. To try get the problem as it happened. Kep in mind though that even without dropped packets I still had slow speeds.

Reply from 109.123.84.221: bytes=32 time=187ms TTL=52
Reply from 109.123.84.221: bytes=32 time=186ms TTL=52
Reply from 109.123.84.221: bytes=32 time=186ms TTL=52
Reply from 109.123.84.221: bytes=32 time=186ms TTL=52
Reply from 109.123.84.221: bytes=32 time=186ms TTL=52
Request timed out.
Request timed out.
Reply from 109.123.84.221: bytes=32 time=197ms TTL=52
Reply from 109.123.84.221: bytes=32 time=186ms TTL=52
Request timed out.
Reply from 109.123.84.221: bytes=32 time=186ms TTL=52
Reply from 109.123.84.221: bytes=32 time=186ms TTL=52
Reply from 109.123.84.221: bytes=32 time=186ms TTL=52
Request timed out.
Request timed out.
Reply from 109.123.84.221: bytes=32 time=186ms TTL=52
Reply from 109.123.84.221: bytes=32 time=186ms TTL=52
Reply from 109.123.84.221: bytes=32 time=186ms TTL=52
Reply from 109.123.84.221: bytes=32 time=186ms TTL=52
Click to expand...

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 8 ms * * 196-210-134-129.dynamic.isadsl.co.za [196.210.13
4.129]
3 ^C
Click to expand...

So seems more and more to be the account itself.

I know Mr.Beep keeps saying IS stats is wrong, but seems that our accounts are shared and when the other person uses too much we get shafted.
 
Kindly drop me a PM so that I can investigate your account.

Chevron said:
Well after dealing with the Telkom Rep and looking at my data again it really does seem Openweb. Only at night during "peak" times and after rebooting router takes ages to authenticate:

So what I did was have a constant ping going. And whenever I had dropped packets I did a tracert. To try get the problem as it happened. Kep in mind though that even without dropped packets I still had slow speeds.





So seems more and more to be the account itself.

I know Mr.Beep keeps saying IS stats is wrong, but seems that our accounts are shared and when the other person uses too much we get shafted.
Click to expand...
 
Chevron said:
Well after dealing with the Telkom Rep and looking at my data again it really does seem Openweb. Only at night during "peak" times and after rebooting router takes ages to authenticate:

So what I did was have a constant ping going. And whenever I had dropped packets I did a tracert. To try get the problem as it happened. Kep in mind though that even without dropped packets I still had slow speeds.





So seems more and more to be the account itself.

I know Mr.Beep keeps saying IS stats is wrong, but seems that our accounts are shared and when the other person uses too much we get shafted.
Click to expand...

THIS IS EXACTLY WHAT I HAVE BEEN EXPERIENCING FOR THE PAST 2 MONTHS!!!!! I have sent an e-mail to the support department today. I doubt it's due to my line being faulty because I tested my MWEB account last month (before it got cancelled) and it worked like a well-oiled V12 engine.
 
Kindly PM me your ADSL username and details of your issue to that I can investigate.

DarkSpectre said:
THIS IS EXACTLY WHAT I HAVE BEEN EXPERIENCING FOR THE PAST 2 MONTHS!!!!! I have sent an e-mail to the support department today. I doubt it's due to my line being faulty because I tested my MWEB account last month (before it got cancelled) and it worked like a well-oiled V12 engine.
Click to expand...
 
Anyone else have problems connecting to Usenet?

Everything else works fine except usenet :confused:

Edit: Working again.
 
Last edited:
Keeper said:
Anyone else have problems connecting to Usenet?

Everything else works fine except usenet :confused:
Click to expand...

Awesome. What a cool upgrade. Openweb accounts getting better and better. :)




^^Not sarcasm.

Tongue in cheek response to people who still use usenet.
 
timmie23 said:
MrBeep. How is the network looking today? Still busy? PSN downloads are just impossibly slow during the daytime. I know you say download at night, but sometimes you want/need to download in the day.
Click to expand...

so whats the official word? is this 'managed' during the day?
 
PSN falls under downloads, thus if the network is busy, this protocol will be shaped.

This has always been the case.

akescpt said:
so whats the official word? is this 'managed' during the day?
Click to expand...
 
900ms ping, in local game. Tracert:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>tracert www.openweb.co.za

Tracing route to www.openweb.co.za [41.72.150.7]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 32 ms 8 ms 196-215-156-1.dynamic.isadsl.co.za [196.215.156.
1]
3 12 ms 12 ms 12 ms cdsl1-ctn-vl2376.ip.isnet.net [196.38.72.205]
4 14 ms 15 ms 13 ms 196.35.115.128
5 13 ms 13 ms 11 ms 168.209.6.12
6 24 ms 27 ms 34 ms 168.209.6.130
7 13 ms 16 ms 14 ms 41-208-29-210.mtnns.net [41.208.29.210]
8 12 ms 32 ms 14 ms 196.44.0.75
9 32 ms 32 ms 32 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.25
0]
10 112 ms 73 ms 96 ms 196.44.31.97
11 30 ms 34 ms 32 ms ge10-1-9sub0.te3.jnb6.za.mtnbusiness.net [196.31
.220.12]
12 30 ms 32 ms 51 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.n
et [196.31.220.25]
13 49 ms 31 ms 30 ms tengigabitethernet5-1.hr9.jnb6.za.mtnbusiness.ne
t [196.31.63.146]
14 36 ms 32 ms 32 ms core-router1.jnb2.host-h.net [196.30.213.108]
15 33 ms 32 ms 31 ms core-access-switch1-vlan1001.jnb.host-h.net [41.
72.136.53]
16 33 ms 30 ms 30 ms mail.openweb.co.za [41.72.150.7]

Trace complete.

C:\Users\Administrator>
Click to expand...
 
Well I haven't noticed any other issues tonight.

Thanks Mr. Beep.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X