Yeah clearly the browser makes a difference.
Thanks for sending this!
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Yeah clearly the browser makes a difference.
It's possible that Telkom has not closed the reference we have opened. I'm sure it will be closed soon.My Openserve line has a cancelation date of 2020/05/31... still active though....
View attachment 849257
Will check again tomorrow...It's possible that Telkom has not closed the reference we have opened. I'm sure it will be closed soon.
You are most welcome to inbox me, I'll check what I can.Will check again tomorrow...
As long as I don't get charged for it, that line can stay active until kingdom come/the pandemic has passed... whichever is firstYou are most welcome to inbox me, I'll check what I can.
Haha! There should have not been a charged if it was cancelled before our billing period.As long as I don't get charged for it, that line can stay active until kingdom come/the pandemic has passed... whichever is first![]()
Yip... see screenshot above (#6442) . Was cancelled at the start of May.. and not invoiced in JuneHaha! There should have not been a charged if it was cancelled before our billing period.
Yip... see screenshot above (#6442) . Was cancelled at the start of May.. and not invoiced in June![]()
@AfriGuy Hi
I just took this 1 min ago. Ticket ID: [#RQJ-304-85790] / [FF #585109] . This has been ongoing for 3 weeks and I have received 1 x phonecall from an incompetent technician. But my debit order went off without a hitch. Lekker julle.
ping 8.8.8.8 -t
Reply from 8.8.8.8: bytes=32 time=22ms TTL=55
Reply from 8.8.8.8: bytes=32 time=23ms TTL=55
Reply from 8.8.8.8: bytes=32 time=20ms TTL=55
Reply from 8.8.8.8: bytes=32 time=21ms TTL=55
Reply from 8.8.8.8: bytes=32 time=22ms TTL=55
Reply from 8.8.8.8: bytes=32 time=23ms TTL=55
Reply from 8.8.8.8: bytes=32 time=20ms TTL=55
Reply from 8.8.8.8: bytes=32 time=20ms TTL=55
Reply from 8.8.8.8: bytes=32 time=22ms TTL=55
Reply from 8.8.8.8: bytes=32 time=23ms TTL=55
Reply from 8.8.8.8: bytes=32 time=20ms TTL=55
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=19ms TTL=55
Reply from 8.8.8.8: bytes=32 time=23ms TTL=55
Reply from 8.8.8.8: bytes=32 time=20ms TTL=55
Reply from 8.8.8.8: bytes=32 time=21ms TTL=55
Reply from 8.8.8.8: bytes=32 time=2783ms TTL=55
Reply from 8.8.8.8: bytes=32 time=25ms TTL=55
Reply from 8.8.8.8: bytes=32 time=20ms TTL=55
Reply from 8.8.8.8: bytes=32 time=21ms TTL=55
Reply from 8.8.8.8: bytes=32 time=21ms TTL=55
Reply from 8.8.8.8: bytes=32 time=21ms TTL=55
Ping statistics for 8.8.8.8:
Packets: Sent = 90, Received = 87, Lost = 3 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 2783ms, Average = 53ms
Still going strongIt's possible that Telkom has not closed the reference we have opened. I'm sure it will be closed soon.
@cavedog Forgot to reply to this one... Windows app doesn't allow for server country change, only shows servers in SA.....unless I'm missing somethingCould just be windows related.
If you test with the speedtest windows app or maybe on Android you should notice an improvement.
@cavedog Forgot to reply to this one... Windows app doesn't allow for server country change, only shows servers in SA.....unless I'm missing something
I hear you, but local uploads is fine across browsers... it's the intl portion that's the issue... so what would make Edge screw up intl uploads ?Yeah but it does rule out the possibility of browser giving the wrong results. I saw that when I did a speedtest on a browser in a Amazon ec2 instance.
I hear you, but local uploads is fine across browsers... it's the intl portion that's the issue... so what would make Edge screw up intl uploads ?
Hi Nibiru, I'm really sorry to hear that your issue has gone on this long. I went over the ticket ID you quoted and see that you copies the results and pasted them. Can you rather send a screenshot of your results, a screenshot reveals a lot more details, like the connection type, dates and times. Please attach the results on the same ticket and I will get our network team to have a look urgently.@AfriGuy I ran a windows ping command from 9-11:30 am. In this 2.5 hours my line disconnected multiple times and every ping spike from 20ms - 2000ms feels like a disconnect. I sent this to my ticket email.
I have now (for the past 3 weeks) sent traceroutes, pingtests, speed tests (connected to router / ONT), packetloss tests and what has Afrihost done? Told me my ticket with Frogfoot does not exist anymore and nothing is wrong.
Hi Nibiru, I'm really sorry to hear that your issue has gone on this long. I went over the ticket ID you quoted and see that you copies the results and pasted them. Can you rather send a screenshot of your results, a screenshot reveals a lot more details, like the connection type, dates and times. Please attach the results on the same ticket and I will get our network team to have a look urgently.