South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Port card faults are pretty rare, it's unlikely to have occurred twice on the same line, but I guess it is possible. We will have to convince Telkom that this could be the issue, so TelkomZa may be able to help to get someone to investigate a little quicker. Either way we should be able to get an answer![]()
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=378ms TTL=63
Reply from 155.239.255.250: bytes=32 time=485ms TTL=63
Reply from 155.239.255.250: bytes=32 time=273ms TTL=63
Reply from 155.239.255.250: bytes=32 time=373ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 273ms, Maximum = 485ms, Average = 377ms
PS C:\WINDOWS\system32> ping bras.afrihost.com
Already logged a fault with you guys.
Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=378ms TTL=63
Reply from 155.239.255.250: bytes=32 time=485ms TTL=63
Reply from 155.239.255.250: bytes=32 time=273ms TTL=63
Reply from 155.239.255.250: bytes=32 time=373ms TTL=63
Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 273ms, Maximum = 485ms, Average = 377ms
PS C:\WINDOWS\system32> ping bras.afrihost.com
That looks like plain and simple exchange congestion to me, had the exact same issue in the past. TelkomZA on Facebook assisted me in resolving it by raising the DSLAM throughput limit or something.
I can't remember exactly what he said, but it was along the lines of the throughput on my specific DSLAM was set to 150Mb/s and it was exceeding that to roughly around 180 during peak times, they raised the limit and all the issues went away.
This was quite a few years ago, before I was transferred to an MSAN.
That looks like plain and simple exchange congestion to me, had the exact same issue in the past. TelkomZA on Facebook assisted me in resolving it by raising the DSLAM throughput limit or something.
I can't remember exactly what he said, but it was along the lines of the throughput on my specific DSLAM was set to 150Mb/s and it was exceeding that to roughly around 180 during peak times, they raised the limit and all the issues went away.
This was quite a few years ago, before I was transferred to an MSAN.
Can i change my package and have it change with effect from the 1st of feb or will it only change by march 1
Thanks,nope it's a downgrade.you can just by the before the 24th of a month, which will come into effect for the new month. So if your change your package now, it will change on the 1st Feb. However, if you upgrade a package now, you will be given x amount of data and a pro rata charge
I logged a fault yesterday at 7am and got feedback to retest and confirmed after 11am it is actually worse than before (syncing at 320kbps only)
I followed up this morning after 8am and again after 12pm...still waiting for any sort of reply
Thanks,nope it's a downgrade.
So in conclusion, everyone that has had issues over the past week and a half with streaming has been told it's all in your head?
Because when we have an issue we get the same response "Everything was fine on my end" from the REPS??
View attachment 411936
Have you been in touch with an Openserve technician directly at all?
No. I don't know if Afrihost has logged it yet. Normally I get a reference no when it is logged with Telkom/Openserve. Hence my concern that time is going by and I can't do my work