shands64
On our wavelength
Joined 10 months ago
User Profile
User Widgets
Contributions
Re: Network Routing Issue
I've checked some previously unavailable hosts within euw1-az1 - and they're now working sporadically. However, they seem to have now broken the route to euw1-az2. A trace route to any of those az2 hosts drops off at our old friend, bagu-core-2b-ae91-650.network.virginmedia.net/80.5.162.69.Re: Network Routing Issue
Cheers Apollo. Yup, I'm all too familiar with their automated service checker (see my previous screenshots!). But I'd replied to his comment without seeing the screenshot first as it couldn't fetch the image (and I'm seeing a few other oddities with community.virginmedia.com). Interestingly, community.virginmedia.com is a CNAME for virgin.lithium.com, which itself is a CNAME for d24skr96sa0j6o.cloudfront.net. CloudFront being an AWS provided CDN.Re: Network Routing Issue
I've chased Virgin for an update on ticket F011273523. First line weren't aware of a call reference of that format, but 2nd line eventually assured me that they were aware of the issue and that it was currently sat with their "IT Department". He went on to read back that exact reference number. Before hanging up, I asked for an ETA of a fix, and "32 hours" was given (but was possibly simply quoting the default SLA)Re: Network Routing Issue
Thanks for picking this up, ModTeam. However, as you can see, there are numerous users that have been affected by this issue (presumably at Baguley) and it's incredibly frustrating, as a loyal customer of VirginMedia, to be stonewalled by your first-line support desk from being allowed to speak to anyone that isn't permitted to deviate from a set diagnostic script ("are the lights on?", and such like) Furthermore, we identified the issue over 24 hours ago and have only now received any sort of acknowledgement that the issue is being investigated. Should anything like this happen again, is there a number/contact/email/etc to submit these issues directly without having to deal with tedious first-line questions? (which, incidentally, seldom yield any sort of warm-and-cuddly-feeling of any sort of progress).Re: Network Routing Issue
Ha, south Warrington here, too. Yup, the Okta endpoint I'm using is a CNAME for*.awsglobalaccelerator.com - so that's explained away. What's interesting is it only seems to be limited to a single AWS datacentre (euw1-az1) - the other DCs seem to be fine for me. No reply to the ticket yet, but I've left a bunch of "ping -t"s running. Hopefully some network bod will notice the increased packet loss (one can hope!)
