test content
Logo
What is the Arc Client?
Install Arc
AFK Penalty for lag?
gabeoz1
Member Posts: 161 Arc User
So I started a match of Crystalline Cataclysm (Advanced), but as soon as the match started I got some extreme rubber-banding. This continued on for 3-4 minutes, but it randomly kicked me out of the match. So after I return to ESD, I go back in the PVE Selection screen. And for some unknown reason, I was given an AFK Penalty for lagging. Cryptic really needs to fix this.
0
Comments
I was moving around, firing, and launching hangar pets. It's just I had extreme rubber banding. I would classify that as doing something.
gabeoz1, we need more information to determine what is causing the issue.
Don't know what more information to give. I was perfectly fine before starting the match. But while I was in the map, it was terrible. When I was forced to return to ESD, my connection was normal and remained so.
Dealing with it is identifying the poor link in the network, and communicating with the party who has the closest line of support to it. In my case, it was Cryptic and whoever provides their Class C Ip ranges.. and yes.. I might know a thing or two about how the internet works given I work for an ISP. If Cryptic doesn't have a budget for a stronger connection then there may not be a viable solution if the issue is on their end and it is holiday bandwidth as I suspect. Give constructive input, and if you don't have the information to do it, ask for it.. or move on.
This is a help forum, try to help people.
It's cryptic's server, if there is an issue with it. THey have a responsibility to fix it, its not mine or any other player's responsibility to fix it. I don't think you know what rubber banding is, and I don't think you ahve a basic understanding of how cryptic's servers work. The last time I checked, in order for your ship to move, fire weapons, launch hangar pets, or anything else to move, the cryptic server has to reconise it. And I have a couple of other Armada/Fleet members who have had this issue. So I highly doubt this is %100 my issue.
tracert us1.proxy.crypticstudios.com
Copy and paste your results here. If you can't do that we can't really tell you the origin of your problem because we cannot narrow down the source of your network problem. Try not to post the first through third hops of your tracert as it can tell us your IP. We don't need that much information. However if any of those first three hops is over 75 MS, then your internal network at your home could be causing your problem.
Alternatively if you are willing to trust me and don't want to post your trace here, you can pm me with the results - the first few hops and I'll do what I can to help make sense of the information.
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\Gabe>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
<SNIP>
4 11 ms 15 ms * 192.168.0.85
5 12 ms 15 ms 10 ms 192.168.0.86
6 11 ms 11 ms 12 ms 192.168.0.89
7 15 ms 13 ms 20 ms 192.168.0.93
8 17 ms 12 ms 17 ms 192.168.0.69
9 27 ms 18 ms 22 ms 64.53.15.117
10 19 ms 21 ms 19 ms cha-b1-link.telia.net [213.248.68.1]
11 32 ms 39 ms 39 ms ash-bb3-link.telia.net [80.91.245.204]
12 * 34 ms 99 ms nyk-bb1-link.telia.net [213.155.131.226]
13 45 ms 57 ms 43 ms bost-b1-link.telia.net [62.115.115.204]
14 39 ms 37 ms 41 ms internap-ic-304640-bost-b1.c.telia.net [62.115.38.110]
15 40 ms 41 ms 47 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
16 40 ms 38 ms 40 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
17 43 ms 41 ms 73 ms 198.49.243.250
18 637 ms 658 ms 809 ms 198.49.243.253
19 * * * Request timed out.
20 45 ms 40 ms 47 ms xboxpatchserver.crypticstudios.com [208.95.185.41]
Trace complete.
You literally hare having the same problem I am. Cryptic's response, "It's not our fault, it's our ISP's fault or the connection between your ISP and our ISP." It'll probably subside as the Thanksgiving Holiday rush ebbs. I suspect they're near or over max capacity for bandwidth. I think it's even the exact same bottle neck and it's a cryptic owned IP.
14 819 ms * 816 ms 198.49.243.253
Yup, same, exact bottle neck. Wonder how they'll respond knowing two people on different network origins are getting the same result.
I wish for everyone to note that every single other hop on the server pathways on both my trace route and this users has normal expected trace responses. Only that singular cryptic owned IP is having any issue communicating with prior or subsequent hops.
It also appears that the singular IP is a shared link between all of crpytic's various proxy servers. If so that means it handles extra-ordinary loads.
You're misreading your data. Also, you typo'd in the domain you traced to. It's us1.proxy.crypticstudios.com. You will note that your data terminated at a non-cryptic address, which means your test is wrong. Go to arin.net nad plug in 79.125.3.30 and you will see that the address does not belong to them.
Net Range 79.0.0.0 - 79.255.255.255
CIDR 79.0.0.0/8
Name 79-RIPE
Handle NET-79-0-0-0-1
Parent
Net Type Allocated to RIPE NCC
Origin AS
Organization RIPE Network Coordination Centre (RIPE)
Registration Date 2006-08-29
Last Updated 2009-05-18
Comments These addresses have been further assigned to users in
the RIPE NCC region. Contact information can be found in
the RIPE database at https://www.ripe.net/whois
RESTful Link https://whois.arin.net/rest/net/NET-79-0-0-0-1
See Also Related organization's POC records.
See Also Resource links.
See Also Related delegations.
In fact you probably have routed to someone that spoofs cryptic. You shouldn't be lagging because.. you literally tested the wrong routed/traced the wrong connection. That said. If you're going to present data, please at least double check to make sure your tests are accurate and that you aren't simply presenting misinformation to attempt to support what you are trying to turn into an argument, than helping this person. Please, test again, this time use the right address and see what happens. Use this: us1.proxy.crypticstudios.com [208.95.184.152]
Also, it's very possible based on the man packets dropped in your test (all the asterisks) that you are testing from a firewalled or secured network which may be preventing accurate returns on the tracert test. Tracert only works if certain ports (icmp echo requests) are open all along the network to permit the test. The test works for me and for gabeoz1 because those ports are open on our network path. They're also open on cryptics.. which is why we know that one specific IP is dropping packets periodically and returning high ping return results. I am interested in the results if your test if you would like to try again with the corrected data. If you're saying that :
26 172 ms 171 ms 172 ms ec2-79-125-3-30.eu-west-1.compute.amazonaws.com
[79.125.3.30]
Is the host that shows up on your game when your menu loads, then I would have to say to you that it appears something else may be wrong with your game, because that's not even a cryptic address and I'm fairly sure (but could be wrong) that cryptic isn't leasing out its server farm. But your network path is so divergent from mine and gabeoz1's at this point I'm fairly sure you simply tested to the wrong location.
BTW, I am dealing. I am dealing with it like I typically do with networking issues and being one with the knowledge and capability to identify and resolve them. I am collecting data and reporting it to the service vendor and seeking a solution. I'm sorry you don't seem to like it that other's prefer to solve their problems than simply accept them.
I have paid for this content and if I can find ways to assist Cryptic in determining where access problems may arise, I am going to assist them. I am fulfilling my part of our mutual responsibility. Mine to ensure everything is good on my end and to help them identify if something is wrong on theirs.
This is a test from my work place computer, which I don't even have the game installed on. I figured it'd be a good way to determine from yet a third source as to whether the delay still exists from yet a different network:
5 24 ms 24 ms 24 ms xe-3-1-1.er5.iad10.us.above.net [208.184.118.117]
6 26 ms 26 ms 25 ms ae15.cr2.dca2.us.zip.zayo.com [64.125.31.41]
7 35 ms 35 ms 35 ms ae0.mpr4.bos2.us.zip.zayo.com [64.125.20.29]
8 36 ms 37 ms 36 ms ae2.mpr3.bos2.us.zip.zayo.com [64.125.25.41]
9 32 ms 32 ms 32 ms 208.184.110.70.IPYX-072053-002-ZYO.above.net [208.184.110.70]
10 32 ms 32 ms 32 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
11 41 ms 33 ms 32 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
12 32 ms 32 ms 32 ms 198.49.243.250
13 828 ms 678 ms 741 ms 198.49.243.253
14 32 ms 32 ms 32 ms us1.proxy.crypticstudios.com [208.95.184.152]
Trace complete.
Still there, same IP. 3 different networks. I also am curious about Cryptic's statements it's a connection to their ISP when both the IP for the network nodes before and after the network node that has the issue, belongs to them. This doesn't look like a gateway.