Been logged in and undocked since the routing change… no DC’s. Looking good.
1 Like
Does this mean that we could see this issue again as the limit has been increased, but we may hit that new limit over time?
I don’t have the details to be able to answer this question – only Virgin Media would be able to tell what the prefix limit was before and after on their equipment, what alerts there are on the limit being breached and their direct peering with Cloudflare therefore being down, how that limit compares to the overall size of the internet’s BGP table and the number of their direct network peers, etc.
My current route, for reference:
1 2 ms 2 ms 3 ms 192.168.0.1
2 16 ms 17 ms 12 ms 10.112.32.109
3 12 ms 16 ms 10 ms brnt-core-2a-xe-3115-0.network.virginmedia.net [62.252.212.65]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 18 ms 22 ms 21 ms tcma-ic-2-ae9-0.network.virginmedia.net [62.253.174.178]
8 17 ms 20 ms 20 ms 162.158.32.254
9 * 18 ms 19 ms 162.158.32.9
10 17 ms 22 ms 16 ms 172.65.201.188
Thank you so much @CCP_Explorer for your hard work on this really frustrating issue!
1 Like
I’ve been stable for a few hours now, off of the VPN.
Thank you @CCP_Explorer, without the pressure from CCP this issue would have taken so, so much longer to diagnose and resolve.
3 Likes
Same here, I have been stable for several hours now looking very good so far
3 Likes
Yep same here stable for at least 4 hrs. Brilliant work @CCP_Explorer Mentioned in dispatches.
3 Likes
seems stable. it about to go 19.00 so waiting to se if it will drop
1 Like
looking good so far
1 Like
Saying its VMs fault is a great get out clause, blame someone else. Utimatly they are one of the few FTTP operators in the UK and probably the largest. I do not have any other issue with any other games and or services. Saying you do not have control of your own servers is pretty lame.
I understand you are ‘trying’ to fix it by getting us the customer to talk to the company rather than you haveing this conversation yourself is fantastic customer service. Its not like its going on for long, only just over a week. Thats 134 plex so far per character not been able to play…
@Lacrimosa: Referring you to my two posts right above, please see
- Right, now I’m interested in hearing if you are all getting new routes?
- Using one of the trace routes from above for some quick analysis
then please note that Virgin Media UK literally fixed the issue themselves by literally fixing
“Issue looks to be due to flapping BGP between Cloudfare and Virgin Media due to prefix limit breach.”
on literally their own equipment, thereby literally fixing/re-establishing their own direct peering with Cloudflare. None of this was or is under CCP’s control or under the control of our internal network partner Advania or our external network partner Cloudflare or any of our network carriers or direct network peers.
3 Likes
It is/was VM’s fault…if you had any clue about networking its clear as day from the countless tracerts above and work many here did to track down the issue.
Id suggest educating yourself a little before you start trying to complain.
5 Likes
@CCP_Explorer & any others involved.
Thank you for all your efforts in helping get this solved when it was clearly Virgin Media’s issue not yours.
I signed in to day at 10:00am, got DC’s at 10:14, 10:24, 10:38 signed off for DT. DC’s at 13:28 and 13:38 but have been stable ever since.
Current Tracert - Eve
1 2 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 12 ms 11 ms 8 ms hers-core-2a-ae67-0.network.virginmedia.net [80.3.33.1]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 17 ms 17 ms 25 ms tcma-ic-2-ae9-0.network.virginmedia.net [62.253.174.178]
8 18 ms 18 ms 19 ms 162.158.32.254
9 19 ms 17 ms 16 ms 162.158.32.9
10 19 ms 18 ms 14 ms 172.65.201.188
Trace complete.
Tracert - Discord
1 2 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 10 ms 10 ms 12 ms hers-core-2a-ae67-0.network.virginmedia.net [80.3.33.1]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 23 ms 31 ms 20 ms m674-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.162]
8 23 ms 19 ms 22 ms 213.46.182.162
9 22 ms 32 ms 29 ms adm-bb4-link.ip.twelve99.net [62.115.137.64]
10 20 ms 25 ms 29 ms adm-b10-link.ip.twelve99.net [62.115.120.229]
11 22 ms 21 ms 36 ms cloudflare-ic342028-adm-b10.ip.twelve99-cust.net [62.115.172.231]
12 25 ms 22 ms 21 ms 162.159.137.232
Trace complete.
1 Like
Looking very good 
2 Likes
I think you need to go outside and give yourself a good talking to. You never know, you might actually see the sun.
3 Likes
I understand what the issue is, but what im saying is the way around it was pretty lame, ie use a VPN or change your ISP.
Neither of which should be suggested. I am happy VM fixed it, however ive had a DC since so we shall see. My point is an alterative should have been offered for over a week of unplayability.
I may have been abit harsh the way I came across however im very frustrated that I loose ships to DC’s and the frustration of having to log in and in again in the same play session. Its not a bout the problem is about how it is/was handled that im annyoed at.
I’m all ears (not literally this time) what that other alternative should have been.
The internet isn’t a single unified entity; it’s a network of networks glued together with BGP and we here at CCP only control our own network.
2 Likes
OK, I remain a bit puzzled here at Virgin Media UK’s decisions, but if it works and is stable, then I’m not going to complain… Not that I have much say in the matter, it’s their network and ultimately I can only advise, recommend, and provide information to VM and VM’s customers need to complain.
But to explain why this is weird:
EVE’s destination is 172.65.201.188, which is a part of the 172.65.128.0/17 CIDR range on AS 13335 (which is Cloudflare, Inc.). Discord’s destination is 162.159.137.232, which is a part of the 162.159.128.0/17 CIDR range, which is also on AS 13335.
Given that Virgin Media UK has direct peering with Cloudflare, then it’s weird to route some of the ranges on AS 13335 one way and other ranges another way. But perhaps there is something in the BGP routing here that I am missing.
2 Likes
I can only guess that because the routing wasn’t causing an issue for anything else (as far as we are aware) they have changed the routing for Eve, but not for the other stuff.
They must have a reason for doing it the way they do, likely cost driven. Maybe they are just taking the hit for this as they can’t see any other immediate solution?
All very speculative, but just hope the Eve fix stays in place.
1 Like