Afrihost Capped DSL Feedback

problem in the east again or something?

AHProbs.jpg


P.S - it's not just you guys, it's IS too atm
 
16% loss on dbn-up2.ip.adsl.co.za with average ping of 125ms
0% loss to bras with average ping of 1ms
 
Hi Guys!

I'm checking with our Team now to see if there are any issues at the moment.
 
I wanted to update you guys quickly, it looks like there has been a drop in capacity in the East. Your speed and latency may be affected by this. I've also made sure that there is a Notice on our site.
 
AfriGenie said:
I wanted to update you guys quickly, it looks like there has been a drop in capacity in the East. Your speed and latency may be affected by this. I've also made sure that there is a Notice on our site.
Click to expand...

thanks so much for the quick feedback, it's really appreciated ;)
 
Hummercellc said:
This seems to be a regular occurrence now?
10 May 2017, 29 May 2017, 06 Jun 2017
Click to expand...

^ This... Can we please have a decent explanation? What is causing these issues, and what is being done to rectify it? Can we expect another east coast outage again? How many more chances do we give before we jump ship?
 
mister said:
^ This... Can we please have a decent explanation? What is causing these issues, and what is being done to rectify it? Can we expect another east coast outage again? How many more chances do we give before we jump ship?
Click to expand...

There was a drop in the available capacity in the East. It doesn't look like a physical break that caused the previous issue.
 
AfriGenie said:
I wanted to update you guys quickly, it looks like there has been a drop in capacity in the East. Your speed and latency may be affected by this. I've also made sure that there is a Notice on our site.
Click to expand...

Have you told your callcentre, who seemed unaware of this a while back and got me calling Telkom to log a fault ( pain in arse )?
 
rwenzori said:
Have you told your callcentre, who seemed unaware of this a while back and got me calling Telkom to log a fault ( pain in arse )?
Click to expand...

You could have a line issue not related to the problem in the East. What was the reason for the fault being logged?
 
Looks like the internet is up **** creek again... oh wait no it's just Afrihost.
Swapped to my WA account and running 100%, I've been patient, but I can't deal with this **** anymore.

Moving on.

Afrihost:
Code: 
ping www.google.com -t
Pinging www.google.com [216.58.223.36] with 32 bytes of data:
Reply from 216.58.223.4: bytes=32 time=153ms TTL=51
Reply from 216.58.223.4: bytes=32 time=154ms TTL=51
Reply from 216.58.223.4: bytes=32 time=155ms TTL=51
Reply from 216.58.223.4: bytes=32 time=155ms TTL=51
Request timed out.
Reply from 216.58.223.4: bytes=32 time=151ms TTL=51
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.223.4: bytes=32 time=155ms TTL=51
Request timed out.
Reply from 216.58.223.4: bytes=32 time=156ms TTL=51
Reply from 216.58.223.4: bytes=32 time=153ms TTL=51
Reply from 216.58.223.4: bytes=32 time=154ms TTL=51
Reply from 216.58.223.4: bytes=32 time=157ms TTL=51
Request timed out.
Reply from 216.58.223.4: bytes=32 time=153ms TTL=51
Reply from 216.58.223.4: bytes=32 time=153ms TTL=51
Reply from 216.58.223.4: bytes=32 time=152ms TTL=51
Reply from 216.58.223.4: bytes=32 time=156ms TTL=51

WebAfrica:
Code: 
ping www.google.com -t
Pinging www.google.com [216.58.223.36] with 32 bytes of data:
Reply from 216.58.223.4: bytes=32 time=27ms TTL=54
Reply from 216.58.223.4: bytes=32 time=25ms TTL=54
Reply from 216.58.223.4: bytes=32 time=26ms TTL=54
Reply from 216.58.223.4: bytes=32 time=24ms TTL=54
Reply from 216.58.223.4: bytes=32 time=25ms TTL=54
Reply from 216.58.223.4: bytes=32 time=27ms TTL=54
Reply from 216.58.223.4: bytes=32 time=24ms TTL=54
Reply from 216.58.223.4: bytes=32 time=24ms TTL=54
Reply from 216.58.223.4: bytes=32 time=26ms TTL=54
Reply from 216.58.223.4: bytes=32 time=27ms TTL=54
Reply from 216.58.223.4: bytes=32 time=25ms TTL=54
Reply from 216.58.223.4: bytes=32 time=26ms TTL=54
Reply from 216.58.223.4: bytes=32 time=28ms TTL=54
Reply from 216.58.223.4: bytes=32 time=23ms TTL=54
Reply from 216.58.223.4: bytes=32 time=23ms TTL=54

I'm not worried about the actual ping, it's the packet loss...
 
Last edited:
Hey Genie! What is up with the internet tonight? Just got home from work and sites dont want to load or loads very slowly at times.

Been perfect last couple of months for me.

Help!
 
:erm:

The issue in the East has been resolved, but it looks like there is a separate problem in the South now. :( I've updated the Network Status page.

Our Team is investigating with our Upstream providers to figure out what's going on!
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X