OpenWeb ADSL Feedback Thread (Pt2)

First day in a long time that I am experiencing problems and it seems many people are complaining today.
Wife, kid and I are just trying to watch some series at home. Hasn't been too pleasant today.
Afrihost Account 100%

Any comment Openweb?
 
Iwojima said:
My feelings exactly. As much as 'ol cableguy over here wants to blame IPC for shaping being a reality the fact is that shaping is becoming significantly worse and worse even on the premium subscriptions, yet they want to still charge the same premium. I'm sorry, but that just doesn't fly in ANY private service industry.

@cableguy: Let me make this abundantly clear on behalf of myself and others on here since you still don't seem to quite get what we're saying here:

- We understand there must be shaping. I am personally not opposed to being shaped during normal 8am-5pm business hours, although the level of shaping during this period (i.e. 10% of line speed) is a little excessive (especially on a Gold acc)

- After business hours (when I use my internet most) I expect to be unshaped and capable of using my line to the fullest extent. I don't mind if you deem peak hours to end at 6 or 7pm, but 11pm/12am is ridiculous.

- Do not move the goalposts as you please. Do not provide a service that people are willing to pay for and then later without consultation with your clients make that service significantly poorer.

- Stop the excuses. Do not lie about traffic/dynamic shaping when it's easy to prove that it is time of day based. Do not try to extort more money out of clients by suggesting they upgrade.

Kindly take the above to Keoma, Leon, Leoni and whoever the hell else needs to see this to effect some changes. I'll mention this a 3rd time: You're becoming MWEB. Look at their reputation and see where you're heading.
Click to expand...

Agree 100% with this, well said!
 
almost 9pm.............NNTP shaped to 25%................"network is busy"............
 
bumbledore said:
Also no word on why the network was shaped so severely today when quite clearly, the http://stats.jinx.net.za/ graphs demonstrate a 50% lower total traffic today than yesterday...
Click to expand...

I fail to understand how that would make a difference seeing that would be local peering only, and to only those local ISPs that wants to peer there. How would that have any bearing on how busy the network would be?

Michael
 
Could you folks run some trace routes to 197.85.190.43? I seem to get a ton of high latency and time outs.
Please indicate what account you're on too.
Thanks
 
Code: 
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:

  1    21 ms     1 ms     1 ms  192.168.1.254
  2     *        *        *     Request timed out.
  3   135 ms    62 ms    55 ms  cdsl2-rba-vl2766-ipc.ip.isnet.net [196.38.73.86]

  4    59 ms    13 ms    12 ms  196.38.73.85
  5    23 ms    74 ms    74 ms  cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
  6    71 ms    68 ms    88 ms  168.209.1.140
  7    56 ms    75 ms    15 ms  196.26.0.10
  8    53 ms    74 ms    75 ms  mweb-1.jinx.net.za [196.223.14.25]
  9    70 ms    74 ms   150 ms  tengig0-0-0-3.vic-p-1.mweb.co.za [197.80.7.1]
 10    44 ms    74 ms   130 ms  tengig0-0-0-0.cpt-p-2.mweb.co.za [197.84.4.46]
 11    65 ms    81 ms   144 ms  197-84-5-238.cpt.mweb.co.za [197.84.5.238]
 12    90 ms    94 ms   114 ms  196.28.178.66
 13   252 ms    80 ms    39 ms  196.41.144.39
 14   119 ms    65 ms    42 ms  intoxicated.co.za [197.85.190.43]

Trace complete.

Gamer's King 4Mbps
 
Woodlands said:
Could you folks run some trace routes to 197.85.190.43? I seem to get a ton of high latency and time outs.
Please indicate what account you're on too.
Thanks
Click to expand...

Code: 
C:\Windows\System32>tracert 197.85.190.43

Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  H0M3nE11 [192.168.0.1]
  2    24 ms    28 ms    12 ms  ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
  3    24 ms    25 ms    12 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
  4    32 ms    30 ms    28 ms  compj-cpt-1.mtnns.net [196.44.18.2]
  5    26 ms    19 ms    29 ms  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
  6    26 ms    29 ms    24 ms  196.44.0.74
  7    21 ms    24 ms    29 ms  196-28-178-141.adsl.mweb.co.za [196.28.178.141]
  8    26 ms    29 ms    29 ms  197-84-7-1.cpt.mweb.co.za [197.84.7.1]
  9    28 ms    29 ms    28 ms  197-84-5-254.cpt.mweb.co.za [197.84.5.254]
 10    24 ms    18 ms    29 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
 11    26 ms    29 ms    25 ms  196.41.144.39
 12    25 ms    29 ms    29 ms  intoxicated.co.za [197.85.190.43]

Trace complete.

Afrihost Business Unshaped Uncapped 2Mbs
 
My net was working 100% from 3pm-ish today up until 8pm then it died again. GG OpenWeb, I suppose it isn't you again as always. Seems you operate like Eskom with their Electricity outages. From "X"-am to "X"-pm no electricity for you or in OpenWeb's case: from "X"-am to "X"-pm no internet for you aka shapping you to death(you cant call 8-10kb/s transfer rate internet). I have monitored this for the past 3days.

16th - 5pm-6pm(only one hour unshaped the entire day - rest was shapped to death)
17th - 12am-onwards(was dead again by the time i woke up around 10am)
18th - roughly 3pm-8pm(dead again after this)

This is impossible to be a problem on my side no matter what you say Cableguy. I'm going to end this by saying one thing, FIX YOUR PROBLEMS, if you cant handle your bandwidth or customer base, stop giving more and more subscriptions everyday just because your company is hungry for more money.

Woodlands said:
Could you folks run some trace routes to 197.85.190.43? I seem to get a ton of high latency and time outs.
Please indicate what account you're on too.
Thanks
Click to expand...

I am on 1MB "Gamers" King package

Code: 
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  login.router [10.0.0.2]
  2     9 ms     8 ms     8 ms  196-210-150-1.dynamic.isadsl.co.za [196.210.150.1]
  3    10 ms    10 ms     9 ms  cdsl2-ctn-vl2276.ip.isnet.net [196.38.72.125]
  4    10 ms     9 ms     9 ms  196.35.115.136
  5    10 ms    11 ms    10 ms  168.209.6.13
  6    12 ms    10 ms     9 ms  168.209.6.131
  7    13 ms    10 ms    10 ms  mweb.cinx.net.za [196.223.22.32]
  8    14 ms    15 ms    16 ms  197-84-7-1.cpt.mweb.co.za [197.84.7.1]
  9    10 ms    10 ms    10 ms  197-84-5-254.cpt.mweb.co.za [197.84.5.254]
 10    11 ms    10 ms    10 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
 11   183 ms    13 ms    12 ms  196.41.144.39
 12    15 ms    15 ms    15 ms  intoxicated.co.za [197.85.190.43]

Trace complete.
 
No problem, i tried loading the page in my browser but it doesn't seem to even open, just loads into infinity. Can be from either side, can't quite say for sure.
Ran tracert again just now and got different results.

Code: 
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  login.router [10.0.0.2]
  2     8 ms     8 ms     *     196-210-150-1.dynamic.isadsl.co.za [196.210.150.
1]
  3    10 ms    10 ms    10 ms  cdsl2-ctn-vl2276.ip.isnet.net [196.38.72.125]
  4    10 ms     9 ms     9 ms  196.35.115.136
  5     *        *       11 ms  168.209.6.13
  6    10 ms    10 ms     9 ms  168.209.6.131
  7     *       11 ms    10 ms  mweb.cinx.net.za [196.223.22.32]
  8    15 ms    15 ms    15 ms  197.84.7.1
  9    12 ms    10 ms    11 ms  197-84-5-254.cpt.mweb.co.za [197.84.5.254]
 10    12 ms    11 ms    11 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
 11   196 ms    19 ms    12 ms  196.41.144.39
 12     *        *        *     Request timed out.
 13     *       12 ms    11 ms  intoxicated.co.za [197.85.190.43]

Trace complete.
 
Your ADSL line is losing sync to the exchange, based on the error logs.

Kindly call Telkom on 10210 and log a fault

shadowstalker said:
No problem, i tried loading the page in my browser but it doesn't seem to even open, just loads into infinity. Can be from either side, can't quite say for sure.
Ran tracert again just now and got different results.

Code: 
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  login.router [10.0.0.2]
  2     8 ms     8 ms     *     196-210-150-1.dynamic.isadsl.co.za [196.210.150.
1]
  3    10 ms    10 ms    10 ms  cdsl2-ctn-vl2276.ip.isnet.net [196.38.72.125]
  4    10 ms     9 ms     9 ms  196.35.115.136
  5     *        *       11 ms  168.209.6.13
  6    10 ms    10 ms     9 ms  168.209.6.131
  7     *       11 ms    10 ms  mweb.cinx.net.za [196.223.22.32]
  8    15 ms    15 ms    15 ms  197.84.7.1
  9    12 ms    10 ms    11 ms  197-84-5-254.cpt.mweb.co.za [197.84.5.254]
 10    12 ms    11 ms    11 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
 11   196 ms    19 ms    12 ms  196.41.144.39
 12     *        *        *     Request timed out.
 13     *       12 ms    11 ms  intoxicated.co.za [197.85.190.43]

Trace complete.
Click to expand...
 
Morning Woodlands,

I see Leon is working on your query. He has set a fail proof test which needs to be completed to confirm where the fault is.

Many faults are pinned on the ISP nowadays. My theory is that the ISP is alot more accessible than Telkom, therefore it is easier to blame the ISP, as there would at least be a response.

Last week a staggering 80% of all support tickets logged were Telkom or router faults.

Woodlands said:
Thanks!
Looks like an IS issue.
Click to expand...
 
Hi Cableguy,
I've let the administrator of the server I'm trying to use know about the issues and I'm awaiting feedback from him.
Thanks and enjoy your weekend!
 
I cant always "lose sync" to the Exchange, i have had perfect internet at random times the past 3 days at random times, i smell bs to this. Please read my posts and don't just reply on the ones you only want to reply. I phoned telkom and they told me if my dsl light doesnt go dead or flashes i lose sync to the exchange, well guess what, my dsl light never goes off it has been solid for the past two years i had internet for.

cableguy said:
Your ADSL line is losing sync to the exchange, based on the error logs.

Kindly call Telkom on 10210 and log a fault
Click to expand...

Can you please reply to my post?????? Im getting real sick of you dodging the questions we post on this forum.
shadowstalker said:
My net was working 100% from 3pm-ish today up until 8pm then it died again. GG OpenWeb, I suppose it isn't you again as always. Seems you operate like Eskom with their Electricity outages. From "X"-am to "X"-pm no electricity for you or in OpenWeb's case: from "X"-am to "X"-pm no internet for you aka shapping you to death(you cant call 8-10kb/s transfer rate internet). I have monitored this for the past 3days.

16th - 5pm-6pm(only one hour unshaped the entire day - rest was shapped to death)
17th - 12am-onwards(was dead again by the time i woke up around 10am)
18th - roughly 3pm-8pm(dead again after this)

This is impossible to be a problem on my side no matter what you say Cableguy. I'm going to end this by saying one thing, FIX YOUR PROBLEMS, if you cant handle your bandwidth or customer base, stop giving more and more subscriptions everyday just because your company is hungry for more money.



I am on 1MB "Gamers" King package

Code: 
Tracing route to intoxicated.co.za [197.85.190.43]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  login.router [10.0.0.2]
  2     9 ms     8 ms     8 ms  196-210-150-1.dynamic.isadsl.co.za [196.210.150.1]
  3    10 ms    10 ms     9 ms  cdsl2-ctn-vl2276.ip.isnet.net [196.38.72.125]
  4    10 ms     9 ms     9 ms  196.35.115.136
  5    10 ms    11 ms    10 ms  168.209.6.13
  6    12 ms    10 ms     9 ms  168.209.6.131
  7    13 ms    10 ms    10 ms  mweb.cinx.net.za [196.223.22.32]
  8    14 ms    15 ms    16 ms  197-84-7-1.cpt.mweb.co.za [197.84.7.1]
  9    10 ms    10 ms    10 ms  197-84-5-254.cpt.mweb.co.za [197.84.5.254]
 10    11 ms    10 ms    10 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
 11   183 ms    13 ms    12 ms  196.41.144.39
 12    15 ms    15 ms    15 ms  intoxicated.co.za [197.85.190.43]

Trace complete.
Click to expand...

What do you have to say about this, a clear tracert and EXACT times of perfect internet and when i get shapped to ****. Please explain this.
 
Last edited:
Downloaded the 'linetool' DrJohnZoidberg recommended and got the following results:

Code: 
Zertop's "Is it my Line" Results 
Basic Report: 
Your average ping was 20ms 
Your maximum ping was 97ms 
 
Looking at your average ping, your line seems to be running perfectly :-) 
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice. 
 
Detailed Report 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 


Pinging 41.181.54.86 with 32 bytes of data:



Request timed out.

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Request timed out.

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Reply from 41.181.54.86: bytes=32 time=31ms TTL=60

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Reply from 41.181.54.86: bytes=32 time=31ms TTL=60

Request timed out.

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Request timed out.

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=11ms TTL=60

Reply from 41.181.54.86: bytes=32 time=17ms TTL=60

Reply from 41.181.54.86: bytes=32 time=31ms TTL=60

Reply from 41.181.54.86: bytes=32 time=13ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=11ms TTL=60

Reply from 41.181.54.86: bytes=32 time=11ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=53ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Request timed out.

Reply from 41.181.54.86: bytes=32 time=97ms TTL=60



Ping statistics for 41.181.54.86:

    Packets: Sent = 30, Received = 25, Lost = 5 (16% loss),

Approximate round trip times in milli-seconds:

    Minimum = 11ms, Maximum = 97ms, Average = 20ms

 
2014/04/19 10:30:08.89

Anyone who can shed some light on this, give some advice or something?
 
shadowstalker said:
Downloaded the 'linetool' DrJohnZoidberg recommended and got the following results:

Code: 
Zertop's "Is it my Line" Results 
Basic Report: 
Your average ping was 20ms 
Your maximum ping was 97ms 
 
Looking at your average ping, your line seems to be running perfectly :-) 
Looking at your maximum ping, however, it seems as though there could be a serious intermittent fault on the line. This could be a cause of an issue. Please post the results (at the end of the program) into the forum for advice. 
 
Detailed Report 
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 


Pinging 41.181.54.86 with 32 bytes of data:



Request timed out.

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Request timed out.

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Reply from 41.181.54.86: bytes=32 time=31ms TTL=60

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Reply from 41.181.54.86: bytes=32 time=31ms TTL=60

Request timed out.

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Request timed out.

Reply from 41.181.54.86: bytes=32 time=15ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=11ms TTL=60

Reply from 41.181.54.86: bytes=32 time=17ms TTL=60

Reply from 41.181.54.86: bytes=32 time=31ms TTL=60

Reply from 41.181.54.86: bytes=32 time=13ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=11ms TTL=60

Reply from 41.181.54.86: bytes=32 time=11ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=53ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Reply from 41.181.54.86: bytes=32 time=12ms TTL=60

Request timed out.

Reply from 41.181.54.86: bytes=32 time=97ms TTL=60



Ping statistics for 41.181.54.86:

    Packets: Sent = 30, Received = 25, Lost = 5 (16% loss),

Approximate round trip times in milli-seconds:

    Minimum = 11ms, Maximum = 97ms, Average = 20ms

 
2014/04/19 10:30:08.89

Anyone who can shed some light on this, give some advice or something?
Click to expand...

Post line stats, those timeouts don't look good.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X