Anyone else have 11/12ms to some AWS servers in Cape Town and then 16/17ms to some others and 22/23ms to others?
One of the AWS Cape Town server IP's (52.94.30.74 - around 12ms)
To another AWS Cape Town IP (52.94.30.6 - around 17ms)
To another AWS Cape Town IP (52.94.30.132 - around 23ms)...
Trying to make my intercom button press smart (for smartphone notifications) by connecting a Shelly 1
The intercom systems are KCOM devices model KIV102, I have 2 indoor units and 2 Camera outdoor units as below. Wiring for these devices look something like this (taken from...
When I was routed through JHB I still got the packet loss and disconnects
My smokeping to 1.1.1.1 while on JHB routing
Here's the history to 1.1.1.1 since changing back to CPT routing: (worth noting the Cloudflare CPT reroutes from time to time so 1 or 2 of the below spikes might be due to that)
Anyone else's connection just die a few minutes ago?
Edit: Just got notice FF reprovisioned my ONT this morning, a few days after the request to reprovision it, not sure what the reason for the delay was. Hope to be back online in a few minutes.
I'm assuming it is to AWS Frankfurt as I'm also getting 220ms to AWS Frankfurt (whereas at its best it is 170ms). However in my case it is AWS at fault (and not AH) because AH (& most ISPs) makes use of AWS Direct Connect where AWS controls the routing to all AWS servers.
My smokeping indicates...
@Frogfoot Fibre still sitting at 22/23ms instead of 11ms to my 1st hop in Cape Town on Walmer 1.2, any fix coming soon?
@AfriNatic could you please check with FF for me too?
Just tested my speeds & were fine on 200/200 with AH
Your slow speeds might have been due to the packetloss that normally follows the first few minutes after coming back online from an outage
Seems like it just returned for Walmer 1.2 (& now back to 22ms). Honestly feels like someone at FF is fiddling around outside of planned maintenance...