Thanks, sent.I think send me your clientzone email address let me double check that everything is in order and ask Frogfoot to take a look and maybe re-provision the ONT to see if that resolves the issue.
Thanks, sent.I think send me your clientzone email address let me double check that everything is in order and ask Frogfoot to take a look and maybe re-provision the ONT to see if that resolves the issue.
My international speeds are so bad I can't do responsive testing with LambdaTest.
I thought this cable break stuff had been mitigated? Anyone else having problems?
I would assume certain sites. Even the London server I choose in speediest.net makes a big difference, often between 10Mbps and 150Mbps.Latency and speeds are looking good from JHB.
Is it all international speeds or certain sites?
So I had a 50mb line on MFN, did an upgrade 2 days ago to the soon to be 200mb package, did some tests this morning, 200mb all morning, then the afternoon back down to 100mb. Any ideas?
You are lucky ... FrogFoot is terribleInternational latency looking good.
London:
View attachment 1079715
Amsterdam:
View attachment 1079719
Tracing route to nc1.eu [195.201.29.113]
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms XiaoQiang.lan [192.168.31.1]
2 31 ms 31 ms 32 ms 100.98.84.1
3 31 ms 33 ms 31 ms 169-1-21-251.ip.afrihost.co.za [169.1.21.251]
4 33 ms 33 ms 32 ms 169-1-21-253.ip.afrihost.co.za [169.1.21.253]
5 33 ms 34 ms 32 ms jhb-ex0b.ip.adsl.co.za [169.1.5.63]
6 32 ms 33 ms 31 ms aptice.net.afrihost.co.za [169.1.1.44]
7 33 ms 33 ms 31 ms jhb-os2.ip.adsl.co.za [169.1.1.49]
8 33 ms 31 ms 31 ms jhb-ex1.ip.adsl.co.za [169.1.5.60]
9 196 ms 198 ms 195 ms 206.249.1.105
10 199 ms 201 ms 199 ms be2436.ccr21.lon02.atlas.cogentco.com [130.117.0.89]
11 195 ms 196 ms 195 ms be3008.ccr21.lon01.atlas.cogentco.com [130.117.15.21]
12 213 ms 202 ms 203 ms ldn-bb4-link.ip.twelve99.net [62.115.141.246]
13 213 ms 214 ms 214 ms hbg-bb4-link.ip.twelve99.net [62.115.122.160]
14 220 ms 220 ms 221 ms nug-b1-link.ip.twelve99.net [62.115.113.175]
15 222 ms 231 ms 223 ms hetzner-ic340780-nug-b1.ip.twelve99-cust.net [213.248.70.1]
16 231 ms 224 ms 227 ms core12.nbg1.hetzner.com [213.239.245.25]
17 219 ms 219 ms 231 ms spine2.cloud1.nbg1.hetzner.com [85.10.250.214]
18 * * * Request timed out.
19 219 ms 219 ms 219 ms 11873.your-cloud.host [116.203.160.68]
20 220 ms 220 ms 220 ms nc1.eu [195.201.29.113]
Trace complete.
Yes we do not repair or send refurbished units we replace when a router is faulty.
Quick question, I see have been invoiced R250 as a courier charge for the device pickup and I also read on Clientzone that I might be liable for the delivery fee again once the device is picked up?
Can you please clarify this for me? If this is the case, it is going to cost me R750 in total delivery fees to exchange a device that was not working out of the box? Let me know.
And back up ... local pings seem better now
I think it was related to Beacon Bay. We had bad latency since Friday. Maybe they rebooted something.Not seeing any notices for maintenance work that are being done
I’m down in Sunnyridge, East London. I have Vumatel. Any issues?