Afrihost Uncapped ADSL Feedback (Pt2)

[Wraithlord]

Looks like a classic case of exchange congestion Do you mostly see these issues after hours?

Most of the time yes (thought that's the only time I'm really online at home).

Just seems to be a sporadic issue. After half an hour everything seemed fine again.

 

[Zertop]

Most of the time yes (thought that's the only time I'm really online at home).

Just seems to be a sporadic issue. After half an hour everything seemed fine again.

That's a good indication of exchange issues :/ One thing you could try is get all your neighbours to report faults, therefore raising the importance of the issue

 

[dculverwell]

Same here

PING telkom.co.za (196.43.22.222) 56(84) bytes of data.
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=1 ttl=241 time=637 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=2 ttl=241 time=710 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=3 ttl=241 time=690 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=4 ttl=241 time=444 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=5 ttl=241 time=489 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=6 ttl=241 time=574 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=7 ttl=241 time=815 ms
^C
--- telkom.co.za ping statistics ---
8 packets transmitted, 7 received, 12% packet loss, time 20431ms
rtt min/avg/max/mdev = 444.954/623.326/815.446/120.417 ms

After rebooting the router, the ping is good for a few minutes, then it degrades to this.

 

[aybbleek]

My Afrihost Uncapped 4MB connection has been amazing the last 2 days, very little shaping! Thank you so much guys, whatever you did to rectify the situation!

 

[vicv]

PING telkom.co.za (196.43.22.222) 56(84) bytes of data.
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=1 ttl=241 time=637 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=2 ttl=241 time=710 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=3 ttl=241 time=690 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=4 ttl=241 time=444 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=5 ttl=241 time=489 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=6 ttl=241 time=574 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=7 ttl=241 time=815 ms
^C
--- telkom.co.za ping statistics ---
8 packets transmitted, 7 received, 12% packet loss, time 20431ms
rtt min/avg/max/mdev = 444.954/623.326/815.446/120.417 ms

After rebooting the router, the ping is good for a few minutes, then it degrades to this.

First ping is high, might be a router fault?

 

[AfriMan]

Most of the time yes (thought that's the only time I'm really online at home).

Just seems to be a sporadic issue. After half an hour everything seemed fine again.

Congestion is a cumulative effect, so it's like predicting traffic. It's not always going to be exactly the same, and it's also amazing how everyone seems to have the same idea of when to be on the road at the same time. Congestion is like waves, so it will appear intermittently

 

[AfriMan]

PING telkom.co.za (196.43.22.222) 56(84) bytes of data.
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=1 ttl=241 time=637 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=2 ttl=241 time=710 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=3 ttl=241 time=690 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=4 ttl=241 time=444 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=5 ttl=241 time=489 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=6 ttl=241 time=574 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=7 ttl=241 time=815 ms
^C
--- telkom.co.za ping statistics ---
8 packets transmitted, 7 received, 12% packet loss, time 20431ms
rtt min/avg/max/mdev = 444.954/623.326/815.446/120.417 ms

After rebooting the router, the ping is good for a few minutes, then it degrades to this.

Congestion will be momentarily relieved when you reset your connect and gradually settle into what the exchange can offer. Just remember that when you reset and get good throughput for a few minutes, everyone else sees a spike in latency as well.

It's a pretty horrible experience generally

 

[aktor]

What doesn't help is that there are people running WISP's via ADSL, and that plays hell with exchange congestion. I know a guy who's got 10 lines (probably more now, that was a couple of years ago), all running at 4mbps, in other words now 10mbps. All of them running at full capacity to service his WISP customers.

I get why WISP's are needed, and why people open them - but man, I get furious when they screw over the experience for us "normal" ADSL users in the process.

 

[burn]

What's the name of such a WISP? Isn't this a violation of Telkom and most ISP terms?

 

[dculverwell]

First ping is high, might be a router fault?

New Router :

ping telkom.co.za
PING telkom.co.za (196.43.22.222) 56(84) bytes of data.
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=1 ttl=241 time=243 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=2 ttl=241 time=277 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=3 ttl=241 time=404 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=4 ttl=241 time=79.5 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=5 ttl=241 time=203 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=6 ttl=241 time=252 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=7 ttl=241 time=289 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=8 ttl=241 time=331 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=9 ttl=241 time=435 ms
^C
--- telkom.co.za ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8009ms
rtt min/avg/max/mdev = 79.529/279.681/435.342/100.376 ms

What's strange is if I reboot the router, the ping is around 34ms for about a minute or so.

 

[aktor]

What's the name of such a WISP? Isn't this a violation of Telkom and most ISP terms?

I have the name, and I've given it to numerous people at Telkom over the years. They don't seem to care.

 

[dculverwell]

Hoa man!

I've logged numerous faults over the last 2 months. Telkom keeps doing the same thing over and over expecting a different outcome.
This Bergvliet exchange is a problem.

I guess I'm going to have to look at 3g or Wireless

 

[Zertop]

I have the name, and I've given it to numerous people at Telkom over the years. They don't seem to care.

I think there are certain restrictions, but nothing to really enforce them. If you think about it - the wisp is giving them business

 

[aktor]

I think there are certain restrictions, but nothing to really enforce them. If you think about it - the wisp is giving them business

Exactly. Well, I can always use a sidecutter.

 

[Zertop]

Exactly. Well, I can always use a sidecutter.

 

[aktor]

Just got a PM from TelkomZA - they are going to upgrade the backhaul capacity within the next 2 weeks.
*weeps for joy*

I'm still cutting some lines, though

 

[AfriMan]

What doesn't help is that there are people running WISP's via ADSL, and that plays hell with exchange congestion. I know a guy who's got 10 lines (probably more now, that was a couple of years ago), all running at 4mbps, in other words now 10mbps. All of them running at full capacity to service his WISP customers.

I get why WISP's are needed, and why people open them - but man, I get furious when they screw over the experience for us "normal" ADSL users in the process.

It's dififcult to say, but as far as I know Telkom don't officially allow WISP or WUGs

 

[AfriMan]

New Router :

ping telkom.co.za
PING telkom.co.za (196.43.22.222) 56(84) bytes of data.
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=1 ttl=241 time=243 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=2 ttl=241 time=277 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=3 ttl=241 time=404 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=4 ttl=241 time=79.5 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=5 ttl=241 time=203 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=6 ttl=241 time=252 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=7 ttl=241 time=289 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=8 ttl=241 time=331 ms
64 bytes from nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za (196.43.22.222): icmp_seq=9 ttl=241 time=435 ms
^C
--- telkom.co.za ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8009ms
rtt min/avg/max/mdev = 79.529/279.681/435.342/100.376 ms

What's strange is if I reboot the router, the ping is around 34ms for about a minute or so.

Looks like not much has changed. Like I said, you find that speeds seem good just after a reset, but it won't usually last

 

[AfriMan]

Just got a PM from TelkomZA - they are going to upgrade the backhaul capacity within the next 2 weeks.
*weeps for joy*

I'm still cutting some lines, though

Awesome. Let's hope it gets delivered on time

 

[minerva]

Good day Afrihost forum! I just flipped my lid and cancelled my Telkom Internet uncapped account and I need to find another ISP quickly. Seems like AH is doing well at the moment. Any comments from users? I watch loads of Netflix, some PTP and loads of Youtube. Average usage is around 200Gb per month on a 4mbps account.