We explicitly suggested to VM on Monday evening that they “try a different egress point to reach 172.65.192.0/20”.
Prior, early in the morning on that same day, we had suggested they could “perhaps change that for 172.65.201.188 (or for Cloudflare in general, AS13335) and route directly within the UK to Cloudflare? Perhaps even initially only as a test to see if a new route makes a difference.”
BTW, the fault was that VM’s systems were trying to establish this direct peering (that they ended up with) but their systems were failing because of prefix limits being breached.
Indeed. Very early on I believe that was your suggestion just to test and see if it worked.
Can’t say I was familiar with prefix limits, but did a little googling to see
Ah well, we have a resolution for now and can only hope it holds up.
We can play again at least in relative safety, as much as Eve is ever safe
Remained logged in all day things are indeed looking very promising, Thank you @CCP_Explorer an the rest of the guys who have put time into this constructively, very much appreciated
I admit I was frustrated and probably took my frustration out on CCP. However as everyone has already said thank you @CCP_Explorer and your team for your efforts.
This thread is only about the disconnect issues that were affecting Virgin Media UK customers. For your issue, which is of a different nature and with a different ISP, please create a technical support request.
Thank you CCP Explorer Senior Development Director and team for all your hard work over all issues you and your team set the standard for other devs and teams to achieve excellent work