If you are on ex SADV IE Vumatel Villages it is an ongoing issue with Vumatel, I will have our SDM send you the report we have from Vumatel.That just proves my point that this is a cool ideas issue and not a vuma issue in my area as I am constantly told by cool ideas support.
Can't connect to my work VPN via CISP DNS server but 1.1.1.1 connected first time...Anyone having DNS issues? in Cape Town
We use root servers so usually an issue with the entry, but with the likes of quad 9 or Google DNS they often cache stuff for longer. Happy to have a look if you like?Can't connect to my work VPN via CISP DNS server but 1.1.1.1 connected first time...
We run an app based in the UK and a lot of users have been reporting issues with it this morning (multiple ISPs both mobile and fibre - both CT & JHB) and the error popping up in the app is a unable to resolve host name and now work VPN (Liquid telecom local) is the same so somewhere there seems to be a DNS service not doing so well.We use root servers so usually an issue with the entry, but with the likes of quad 9 or Google DNS they often cache stuff for longer. Happy to have a look if you like?
Nope, wired on an Asus AX56U.So you dropping as I assume you are on wifi and its adding that extra loss to push you over. What kit do you have? Try improving the wifi and you might still have latency but no drop.
I am getting very similar speeds on a 50/25 line with Vodacom. What speed is normal for a single connection test overseas?The problem I have, is that TTConnect seems to have intimidated every ISP into having a workaraound for this pitiful service.
This is a 100/100 line. View attachment 1435907
The point is you still have local loss to your router.Nope, wired on an Asus AX56U.
Thanks PBCool but how long will this be an ongoing issue? I have been hearing its a vuma villages issue for the past 7 months and nobody is doing anything to resolve it. I have no point of contact with vuma and cool ideas refuses to provide me with any contact information stating that the escalation should go through them but nothing happens regardless of the escalations. I am paying for a service that I am not receiving and nobody is willing to take accountability for it. This is really not fair.If you are on ex SADV IE Vumatel Villages it is an ongoing issue with Vumatel, I will have our SDM send you the report we have from Vumatel.
Hi @PBCool @CoolChick @TheRoDent I requested a line speed upgrade this morning, now I have no internet and nobody responding to me, can you please check?
COOL-20221206-1079157
It hasn't been an active issue for 7 months, at least we or Vumatel are only aware of it for the last 2 months or so. It is related to disruptions on their backhaul providers network who is DFA. As mentioned certain ETAs are around 6 weeks for permanent resolution.Thanks PBCool but how long will this be an ongoing issue? I have been hearing its a vuma villages issue for the past 7 months and nobody is doing anything to resolve it. I have no point of contact with vuma and cool ideas refuses to provide me with any contact information stating that the escalation should go through them but nothing happens regardless of the escalations. I am paying for a service that I am not receiving and nobody is willing to take accountability for it. This is really not fair.
Ditto. If its wired there should be no packet loss. 0%.The point is you still have local loss to your router.
Quad 9 should return via a local latency path now.We're looking at resolving this with the Quad9 NOC. Their return path seems to prefer international.
ThanksQuad 9 should return via a local latency path now.
$ ping 9.9.9.9 -c 5
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
64 bytes from 9.9.9.9: icmp_seq=1 ttl=56 time=4.07 ms
64 bytes from 9.9.9.9: icmp_seq=2 ttl=56 time=4.20 ms
64 bytes from 9.9.9.9: icmp_seq=3 ttl=56 time=4.27 ms
64 bytes from 9.9.9.9: icmp_seq=4 ttl=56 time=4.09 ms
64 bytes from 9.9.9.9: icmp_seq=5 ttl=56 time=4.06 ms
--- 9.9.9.9 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 4.061/4.138/4.274/0.083 ms
Hi there, please note that we are looking into it. Our teams seemed to have discovered the issue4 hrs still no internet