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.

[Matthew_ML]

Hey penguini42, thank you for reaching out and  am sorry to hear this,

We are aware of an issue and we are looking into this as we speak. 

[Zach_R]

Hi @tomaird,

Thank you for your post and welcome to our community forums. We're here to help.

I'm very sorry to hear that you seem to have some issues when trying to access certain websites. We're aware of the issue you're referring to and are currently investigating this to be resolved ASAP.

Apologies for any inconvenience caused whilst we work on this.

Thanks,
 

[PaulR78]

Same issue BA11. No Google related or owned services are working through Virgin Media WiFi. 

[El_Loro]

Having the same problems here in the Gloucester area (GL2)

[razvanpop]

It's amazing how long it took you to realize or to accept you have a problem, when it's simple Google platforms work on Vodafone for example on yours do not. They work on VPN, and also you guys have a recaptcha just to sign up for this VM community, which does not work as recaptcha or google analytics is owned by them. So it was so so so simple to realize that VM servers are down and that your server technicians are sleeping on their job. I do hope someone will get fired over this, and we will receive at least an appologetic email from VM if not a discount for the crappy service you provided over the last 24 hours.

[Matthew_ML]

Hey all on this thread, as mentioned we are aware of an issue effecting this and we are working on this, 

[pete_wc]

Thanks for letting us know.

[Matthew_ML]

No problem at all.

[slyzephyr]

Same issue in Weston area (BS22/BS24)

[mmelbourne]

This seemed to be working in the Gloucester area around 13:50, but has now stopped again. Definitely feels like a routing issue between VM and Google, as it's not (just) DNS resolution (though I note the comments about other non-Google services). However, having been on the wrong end of some Cisco/Juniper BGP and RIB/FIB weirdness, I'd be fairly confident that it's more involved than first appears.