routing problems to Google DNS?

[penguin42]

(Manchester, VM broadband wired, everything else is working fine)

It looks like there's some routing problems, only to Google's DNS servers, and I'm failing to resolve any google.com or similar;

traceroute/mtr to the IPs of ns2.google.com ( 216.239.34.10 ) and ns4 ( 216.239.38.10 ) shows it intermittently failing in manc-core-2b-ae93-650.network.virginmedia.net

It's working fine from my none virgin-media connections.

Down-detector is showing a big spike in Google problems centred around Manchester and London, so not just me; not sure if it's only VM or not.

Please forward to someone with a hammer near VMs corp routers.

[PMilne87]

Re SharePoint, you are accessing the document library but bypassing the SSO element required to access the web page itself.

[Sasquatch-Sco]

Clouldlfare is my main one. That stopped working on Tuesday for me and Google and default VM DNS's are the same. Fine as soon as I connect to 4G mobile hotspot or go through a VPN.

[unisoft]

---

@Sasquatch-Sco wrote:

Clouldlfare is my main one. That stopped working on Tuesday for me and Google and default VM DNS's are the same. Fine as soon as I connect to 4G mobile hotspot or go through a VPN.

---

Exactly what I experience on family member's broadband with Virgin but Ok on 4G/5G or though another ISP to same site behind Cloudflare. The silence on this is annoying, but the family member will know how to give VM the boot if this is not fixed soon and another long term customer gone never to return as they have other FTTP providers in their area now and this could be the nudge to have temporary hassle of install of new fibre and ONT instead.