Changing to Google DNS solves the issue.
Seems like cloudflare is suffering an outage again…
I’m using it but also using Quad9, Quad9 answers my queries quicker so may have missed any issues with CloudFlare.
Using both Cloudflare and Quad9 for DNS lookups from Lan side.
My Router uses cloudflare and google dns for its latency testing….
Thanks for the update on Cloudflare DNS.
Back to normal now. 5ms 
Love how some people was so quick to blame Yayzi but forgot to check the basics first 
1 Like
I dont see anyone pointing the finger at Yayzi directly other than one post 
I’m using cloudflare and for some reason didn’t see any issues, which I’m not complaining about, just an observation.
Ha, similar here. I have an AdGuard server set up which handles all of the client DNS requests and I didn’t notice any issues - I have 3 different DNS servers configured upstream, quad9, Google and Cloudflare. I have it set up to ping all 3 in parallel so it then just uses the quickest at the time. Also, like you, my UDM is using Cloudflare so have the same sort of graph which I can’t post as it’s only showing on my IOS console for some reason! Good reason to not rely on a single DNS server.
Hand up, my DNS is set to cloudflare.
One for the checklist if it happens again.
Just got a response from support this morning asking me power cycle the ONT and Router
Spoke too soon, it’s gone down again. ONT lights are all good. I’ve now changed the DNS to automatic and rebooted. Internet still not connected, showing a red light. How long should it normally take after reboot?
Is DNS okay set to automatic?
Many thanks
Thanks, just heard back from support and they’re saying it’s an issue on the city fibre side 
1 Like
Can you try a reboot for me and let me know if you’re back up.
Rebooted the router and red light still there 
Thanks for getting back to me, we’ll keep at it
Rebooted the ONT and Router, seems all good now.
For anyone interested.
1 Like
We’re getting there, but still a ways to go until everyone is doing ROV.