Shocking service from OpenWeb

ISP cash cow said:
a simple tracert should be able to see if it due to congested exchanges.

however I just find it a bit funny that this issue is not occurring on any of the other OP's ISP accounts except for Openweb. If it was congested exchanges or a required port reset would this not also reflect on the other accounts?
Click to expand...

Indeed. Here are the tracerts that I sent to OpenWeb:

Local (via OpenWeb) -

ric-mac:~ ric$ traceroute sexybikinis.co.za
traceroute to sexybikinis.co.za (41.86.113.44), 64 hops max, 52 byte packets
1 home (10.0.0.2) 2.624 ms 2.439 ms 2.450 ms
2 196-210-150-1.dynamic.isadsl.co.za (196.210.150.1) 30.125 ms 42.802 ms 40.120 ms
3 cdsl1-ctn-vl2173.ip.isnet.net (196.38.72.113) 38.641 ms 34.033 ms 38.604 ms
4 196.35.115.128 (196.35.115.128) 30.698 ms 26.997 ms 24.610 ms
5 core2a-ctn-gi0-1.ip.isnet.net (168.209.2.6) 36.480 ms 27.081 ms 32.363 ms
6 168.209.2.131 (168.209.2.131) 32.132 ms 25.024 ms 23.604 ms
7 mweb-2.cinx.net.za (196.223.22.25) 21.768 ms 24.746 ms 19.797 ms
8 197-84-4-224.cpt.mweb.co.za (197.84.4.224) 51.958 ms 49.894 ms 51.382 ms
9 tengig0-0-0-0.vic-p-2.mweb.co.za (197.84.4.35) 56.190 ms 54.310 ms 49.167 ms
10 vl-12.vic-hscore-2.mweb.co.za (196.22.169.243) 52.061 ms 58.884 ms 71.468 ms
11 tengig-3-2.vic-core-sw2.mweb.co.za (196.22.169.70) 57.587 ms 59.705 ms 62.071 ms
12 197-81-229-4.jhb.mweb.co.za (197.81.229.4) 53.655 ms 48.716 ms 65.318 ms
13 197-81-229-11.jhb.mweb.co.za (197.81.229.11) 52.278 ms 54.699 ms 56.198 ms
14 164.75.28.196.netactive.net (196.28.75.164) 50.035 ms 48.670 ms 51.656 ms
15 vz8-jnb.vps.za-dns.com (41.86.113.70) 49.784 ms 60.517 ms 51.268 ms
16 geartri.be (41.86.113.44) 53.112 ms 49.436 ms 55.142 ms

International (via OpenWeb) -

ric-mac:~ ric$ traceroute rp.geartri.be
traceroute to rp.geartri.be (94.102.50.54), 64 hops max, 52 byte packets
1 home (10.0.0.2) 4.156 ms 2.090 ms 2.075 ms
2 196-210-150-1.dynamic.isadsl.co.za (196.210.150.1) 43.641 ms 44.383 ms 45.604 ms
3 cdsl2-ctn-vl2276.ip.isnet.net (196.38.72.125) 45.109 ms 41.564 ms 39.107 ms
4 196.35.115.136 (196.35.115.136) 38.541 ms 38.434 ms 38.356 ms
5 core2b-ctn-gi0-2.ip.isnet.net (168.209.6.3) 39.229 ms 41.033 ms 39.441 ms
6 168.209.246.3 (168.209.246.3) 196.779 ms 194.237 ms 412.359 ms
7 xe-0-4-0-6.r02.londen03.uk.bb.gin.ntt.net (83.231.235.221) 232.670 ms 381.369 ms 218.404 ms
8 ae-4.r23.londen03.uk.bb.gin.ntt.net (129.250.5.40) 204.766 ms 203.544 ms
ae-4.r22.londen03.uk.bb.gin.ntt.net (129.250.5.24) 208.148 ms
9 linx.lon12.ip.tiscali.net (195.66.224.32) 197.456 ms
linx.lon20.ip.tiscali.net (195.66.236.32) 399.286 ms 217.714 ms
10 m247-gw.ip4.tinet.net (141.136.96.230) 191.356 ms 204.733 ms
xe-3-1-2.lon10.ip4.tinet.net (89.149.185.169) 217.319 ms
11 m247-gw.ip4.tinet.net (141.136.96.230) 208.331 ms
po-7-0-0.bb1.lon1.uk.m247.com (193.27.64.157) 404.364 ms 232.254 ms
12 po-7-0-0.bb1.lon1.uk.m247.com (193.27.64.157) 382.230 ms 257.543 ms
te-4-3-0.bb1.ams3.nl.m247.com (77.243.180.49) 458.436 ms
13 * * *
14 * * 94.102.50.54 (94.102.50.54) 391.638 ms

Local (via WebAfrica) -

ric-mac:~ ric$ traceroute sexybikinis.co.za
traceroute to sexybikinis.co.za (41.86.113.44), 64 hops max, 52 byte packets
1 home (10.0.0.2) 2.573 ms 2.331 ms 2.280 ms
2 196-210-150-1.dynamic.isadsl.co.za (196.210.150.1) 113.219 ms 118.877 ms 111.829 ms
3 cdsl2-ctn-vl2276.ip.isnet.net (196.38.72.125) 112.613 ms 98.111 ms 96.882 ms
4 196.35.115.136 (196.35.115.136) 93.417 ms 85.653 ms 87.232 ms
5 core2a-ctn-gi0-2.ip.isnet.net (168.209.6.6) 92.244 ms 90.391 ms 99.052 ms
6 168.209.2.131 (168.209.2.131) 99.892 ms 92.778 ms 78.113 ms
7 mweb-2.cinx.net.za (196.223.22.25) 90.300 ms 93.305 ms 88.851 ms
8 197-84-4-224.cpt.mweb.co.za (197.84.4.224) 115.080 ms 121.547 ms 128.878 ms
9 tengig0-0-0-0.vic-p-2.mweb.co.za (197.84.4.35) 142.748 ms 149.185 ms 141.472 ms
10 vl-12.vic-hscore-2.mweb.co.za (196.22.169.243) 144.982 ms 136.785 ms 151.015 ms
11 tengig-3-2.vic-core-sw2.mweb.co.za (196.22.169.70) 159.754 ms 161.029 ms 155.485 ms
12 197-81-229-4.jhb.mweb.co.za (197.81.229.4) 144.729 ms 138.668 ms 131.723 ms
13 197-81-229-15.jhb.mweb.co.za (197.81.229.15) 122.906 ms 125.553 ms 117.270 ms
14 164.75.28.196.netactive.net (196.28.75.164) 123.651 ms 115.185 ms 116.558 ms
15 vz8-jnb.vps.za-dns.com (41.86.113.70) 122.839 ms 118.304 ms 124.982 ms
16 geartri.be (41.86.113.44) 127.843 ms 135.946 ms 130.386 ms

International (via WebAfrica) -

ric-mac:~ ric$ traceroute rp.geartri.be
traceroute to rp.geartri.be (94.102.50.54), 64 hops max, 52 byte packets
1 home (10.0.0.2) 2.524 ms 2.227 ms 2.257 ms
2 196-210-150-1.dynamic.isadsl.co.za (196.210.150.1) 120.828 ms 122.251 ms 137.068 ms
3 cdsl1-ctn-vl2173.ip.isnet.net (196.38.72.113) 132.842 ms 134.708 ms 136.790 ms
4 196.35.115.128 (196.35.115.128) 128.021 ms 123.722 ms 143.143 ms
5 core1b-ctn-gi0-2.ip.isnet.net (168.209.6.4) 129.490 ms 135.403 ms 114.319 ms
6 168.209.246.3 (168.209.246.3) 287.726 ms 258.231 ms 246.297 ms
7 xe-0-4-0-6.r02.londen03.uk.bb.gin.ntt.net (83.231.235.221) 240.157 ms 249.768 ms 249.797 ms
8 ae-4.r22.londen03.uk.bb.gin.ntt.net (129.250.5.24) 243.019 ms 236.911 ms
ae-4.r23.londen03.uk.bb.gin.ntt.net (129.250.5.40) 211.664 ms
9 linx.lon20.ip.tiscali.net (195.66.236.32) 237.832 ms
linx.lon12.ip.tiscali.net (195.66.224.32) 410.716 ms 284.073 ms
10 xe-5-2-0.lon10.ip4.tinet.net (89.149.185.74) 432.258 ms
xe-2-2-1.lon10.ip4.tinet.net (89.149.180.94) 256.980 ms
m247-gw.ip4.tinet.net (141.136.96.230) 263.801 ms
11 po-7-0-0.bb1.lon1.uk.m247.com (193.27.64.157) 262.232 ms
m247-gw.ip4.tinet.net (141.136.96.230) 256.743 ms 267.419 ms
12 te-4-3-0.bb1.ams3.nl.m247.com (77.243.180.49) 476.604 ms 257.835 ms
po-7-0-0.bb1.lon1.uk.m247.com (193.27.64.157) 231.711 ms
13 te-4-3-0.bb1.ams3.nl.m247.com (77.243.180.49) 431.161 ms 232.162 ms 381.818 ms
14 94.102.50.54 (94.102.50.54) 235.199 ms 378.910 ms *

And here is typical behavior when connected to OpenWeb:

ric-mac:~ ric$ ping openweb.co.za
PING openweb.co.za (41.72.150.7): 56 data bytes
64 bytes from 41.72.150.7: icmp_seq=0 ttl=51 time=256.125 ms
64 bytes from 41.72.150.7: icmp_seq=1 ttl=51 time=128.281 ms
64 bytes from 41.72.150.7: icmp_seq=2 ttl=51 time=138.995 ms
64 bytes from 41.72.150.7: icmp_seq=3 ttl=51 time=157.123 ms
64 bytes from 41.72.150.7: icmp_seq=4 ttl=51 time=125.274 ms
64 bytes from 41.72.150.7: icmp_seq=5 ttl=51 time=134.179 ms
64 bytes from 41.72.150.7: icmp_seq=6 ttl=51 time=134.996 ms
64 bytes from 41.72.150.7: icmp_seq=7 ttl=51 time=127.122 ms
64 bytes from 41.72.150.7: icmp_seq=8 ttl=51 time=71.285 ms
64 bytes from 41.72.150.7: icmp_seq=9 ttl=51 time=78.350 ms
64 bytes from 41.72.150.7: icmp_seq=10 ttl=51 time=126.051 ms
64 bytes from 41.72.150.7: icmp_seq=11 ttl=51 time=103.863 ms
64 bytes from 41.72.150.7: icmp_seq=12 ttl=51 time=150.119 ms
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
 
I wish you the best in any action against OW fluffy, clearly they are arrogantly brushing you off, so do the same and go the legal route.
 
techead said:
hehe fluffypony just got pwned

:D

/munch munch

PEACE
Click to expand...

How so? This is not a game, the NCT can impose administrative fines of up to 10 percent of a company’s annual turnover in the previous financial year, or R1 million.
 
fluffy, post some speedtest results here. Local and international on both the OW and WA accounts. Looks to me like both those accounts are using exactly the same routes.
 
DrJohnZoidberg said:
fluffy, post some speedtest results here. Local and international on both the OW and WA accounts. Looks to me like both those accounts are using exactly the same routes.
Click to expand...

Check the traceroutes on page 3 - it is exactly the same route. So it is not congestion or the backhaul or Telkom.
 
If a line keeps dropping its almost always Telkom, sometimes the router. Almost never the account.
 
ghoti said:
If a line keeps dropping its almost always Telkom, sometimes the router. Almost never the account.
Click to expand...

I never once said the line dropped. It was syncing and connected, but all traffic (UDP/TCP/ICMP) suddenly had no route. It would magically start working again after a few minutes, with no action from my side. Importantly, this behaviour could not be reproduced when connected to other ISPs.
 
I got to stick up for OpenWeb here. I've worked for a ISP myself and I have seen issues with certain ISP accounts not connecting from certain points on the Telkom network. Using other ISP accounts worked fine however. These same ADSL accounts that had problems worked fine from other locations. Usually these issue are to with routing on the Telkom side of things, unfortunately getting them sorted out is a pain.

Note, I am not a OpenWeb user/employee/affiliate, just thought I'd give my 2 cents.
 
Last edited:
ernstn said:
Mr Beep,

just my penny's worth:

You are damaging your company's image by your stance of a no refund.
Click to expand...

Agreed, it's must be quite frustrating to pay for a service that you can't use. Why not just process a refund?
 
ghoti said:
Have you ever gotten a refund for a phone or electricity bill?
Click to expand...

I would hope that I get a refund when the fault, off non delivery, lies with the service provider.
 
Openweb is not Telkom and yes I did get a refund from Telkom once when ADSL was down in my area. Lately I even managed to get a refund from my bank, now that is something.

But that was not the point of my post, Telkom does not give a stuff about their image.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X