qwertyuiop

Yup now it routes correctly again: 7 13 ms 12 ms 9 ms 50.242.150.34 8 14 ms 14 ms 15 ms 0.ae4.cr2.ord6.scnet.net [204.93.204.87] 9 13 ms 13 ms 14 ms ae2.ar9.ord6.us.scnet.net [204.93.204.79] 10 14 ms 16 ms 13 ms ethernetxe-0-0-0:0-er1-q8.chi2.choopa.net [108.61.138.254] 11 14 ms 21 ms 18 ms vl20-br1.chi2.choopa.net [104.207.137.229] 12 17 ms 13 ms 13 ms 8.9.4.227 You know what's interesting? When I was using a vpn, I got to the server in 7 hops instead of 12. I had way less yellow lag on lagometer with the vpn and minimal impact on my relative ping. I wonder if hops has much to do with playability vs high ping since some players with even 300 ping are very good shooters and others are easier to kill than bots. Just a hypothesis.

Just got off the phone with Tier 3 at Comcast. While he was 'really sorry', they can't reroute to this IP. Won't is more like it. There is no way that Comcast only peers with one backbone. Ah well. It was a long shot.

Just got a call back from Tier 2 support at Comcast. The only thing she could do for me was reset my modem. How this is different from Tier 1 is anybody's guess. Fortunately she's bumped the issue up to Tier 3. So in another 24-48 hours, I'll get another lovely phone call. *insert clever Dante's Inferno joke here* The race is on to see which incompetent tech company responds with a workable solution. BTW, I'd be a little cautious using free VPNs. While it's active, all your internet traffic is routing through them. You have no idea how they may be handling that information. Read ToS and privacy policies carefully. If you want to pay for a vpn, there is a good guide here to vetting various vpn services: https://thatoneprivacysite.net/vpn-comparison-chart/ Edit: Windscribe is on their list and rates pretty well

Response from gameservers: Your request has been updated by Brendan Kiel [staff]. Message Content: Our networking team has been made aware of this. Thanks, Brendan Kiel "Dr. Worm[GS]"

I decided on a little masochism and called Comcast tech support. The tech is very nice and all and verifies the IP is not reachable, but he's forced to ask me crap like whether I'm using wifi or a wired connection and whether I own or lease my equipment. *sigh* Stuck at tier 1... I think we'll have much better luck with trying to talk to these gameservers guys.

Interesting. Red said that euro players cannot connect. They would not be using Comcast. It would be nice if we could find ONE non-comcast user to share a trace to eliminate that variable, but I am still apt to think the problem is not with comcast since they hop to a network outside their own. It's possible that we could wind our way up the Comcast bureaucracy to a tech level where they even understand what BGP is, and that they could reroute for us. But if non Comcast users are also affected, this would be a band-aid and still leave some potential players out in the cold.

Nerbil, I just emailed support@servercentral.net and showed them both our traceroutes. If we could collect more traceroutes from others who cannot connect, we can perhaps find a common loss point at scnet.net . Right now we have two people confirming it, but we are also both at Comcast. In my mind it's conflating two potential fault points and simply isn't a large enough sample to be confident. It would great to see what a european that cannot connect sees. In case you don't know how to traceroute, from a windows command prompt, simply type: tracert jay1.clan-fa.com after you hit enter, you should start to see the trace go. if you start to see endless lines likes this: 12 * * * Request timed out. just hit ctl-c after 3 or 4. Then copy/paste the result here, but if you care about your anonymity, skip the first few lines (or hops as they are known). Oh and this is just a call out to people who CANNOT connect. If you can connect ok, your traceroute is not helpful to us.

I don't mean to be rude, even though everybody always assumes I am 100% of the time, but asking this question shows you did not read anything I wrote and completely fail to understand the problem. We told you we cannot even get a ping response from the server and have shown you what our traceroutes look like. But how can we try a port when we cannot even route to the IP? The only thing that needs to happen is for someone to get a hold of the person that actually owns the server and can get Choopa to fix the network routing issue. I assume this is Daredevil, but there may be other legal admin contacts. If you can do that, please do it. If you can provide further forensics showing the problem affecting a new geographical area, also cool. We really do not know how many people are affected, but it's clearly a handful plus all the people that simply assume the server is offline and don't report it. When I connected last night via my tether, even though it was prime time, the server had bots. That's rare on j1.

I posted to the Tracker forum about this, but nobody seems to go there and read, so I'll just repost here: ---- I confirm this. I spoke with several players who also confirm this (e.g. danger, tommygunz). if europeans are affected it is not ISP specific. My best guess is someone at Choopa screwed up the BGP table. I tried to contact Choopa's support about it, but since I am not the leaseholder of the server, they promptly ignored me. I'm fairly sure that that is the only way to resolve this though. From home, I cannot ping the server, although the IP resolves just fine. Traceroute shows it hitting a black hole around hop 10. Here are the last responsive hops (for me): 7 13 ms 15 ms 27 ms 50.242.150.34 8 13 ms 13 ms 13 ms 0.ae4.cr2.ord6.scnet.net [204.93.204.87] 9 42 ms 13 ms 16 ms ae2.ar9.ord6.us.scnet.net [204.93.204.79] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. That will keep going to hop 30 where traceroute will give up. I'm telling you, messed up BGP table is the most likely culprit. From a remote server located in another part of the US, I can query that the server is up and see the players playing. ----- I wrote that days ago. The reason some people are affected and not others has to do with routing -- depending on where you are and your ISP, your path to the server takes different routes. If I tether to my phone, I can connect no problem. I'm telling you, this is a BGP table screw up somewhere. It COULD be at scnet, but it is most likely at Choopa (or whoever handles their routers). I'm no network admin, but I've seen this before. Do not burden yourself with total reinstalls. This is not user specific issue. If you have access to a VPN or can tether to a cellular network, you should be able to temporarily workaround this. The fact this has been happening for over two days now, imo, smacks of incompetence. Automatic monitoring in data centers is supposed to detect failures like this. With love, 8===D~~~