test content
  • Games
  • Social
  • Arc News
  • Support
  • Zen
What is the Arc Client?
Install Arc
Forums > Home› Support› PC, Network, and Other Technical Issues› Windows and General: PC, Network, and Other Technical Issues

Got disconnected twice in one hour. Whats wrong with 198.49.243.253 ?

ewilpwnyewilpwny Member Posts: 22 Arc User
in Windows and General: PC, Network, and Other Technical Issues
Got disconnected twice in one hour. "Server not responding"

Never had this problem before. Anyone else having this issue?

Looks like there is something wrong with 198.49.243.253 close to Cryptics servers.

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms
2 <1 ms <1 ms <1 ms
3 1 ms <1 ms <1 ms
4 <1 ms <1 ms <1 ms
5 2 ms 1 ms 1 ms sto-kn71.sto-cr1.bahnhof.net
6 2 ms 1 ms 1 ms te0-7-0-9.ccr21.sto01.atlas.cogentco.com
7 2 ms 2 ms 2 ms be2397.ccr22.sto03.atlas.cogentco.com
8 17 ms 17 ms 17 ms be2282.ccr42.ham01.atlas.cogentco.com
9 30 ms 30 ms 29 ms be2816.ccr42.ams03.atlas.cogentco.com
10 36 ms 36 ms 36 ms be2183.ccr22.lpl01.atlas.cogentco.com
11 105 ms 105 ms 106 ms be2387.ccr22.bos01.atlas.cogentco.com
12 102 ms 103 ms 102 ms te0-0-0-0.rcr12.b002133-1.bos01.atlas.cogentcom
13 105 ms 106 ms 106 ms 38.104.252.70
14 100 ms 100 ms 129 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.]
15 103 ms 102 ms 102 ms perfectworldent-4.border11.bsn.pnap.net [216.52.1.78]
16 102 ms 102 ms 105 ms 198.49.243.250
17 840 ms 807 ms 810 ms 198.49.243.253
18 * * * Request timed out.
19 99 ms 99 ms 99 ms patchserver2.crypticstudios.com [208.95.185.41]


See you in space :D
Seruk@HoodedSandman

Comments

  • trekpuppytrekpuppy Member Posts: 446 Arc User
    ewilpwny wrote: »
    19 99 ms 99 ms 99 ms patchserver2.crypticstudios.com [208.95.185.41]
    I believe you're misreading your own traceroute. The final line there shows perfectly normal ping response times when your data hits Cryptic's network. Not even a single drop-out on those three attempts. If the high latency on 198.49.243.253 were due to a bottleneck the high latency would persist on every node behind it and your own traceroute shows that this isn't the case. In fact, every traceroute provided by different users recently shows the exact same pattern. This is evidence that 198.49.243.253 forwards data to the game servers without any extra delay but data sent explicitly to 198.49.243.253 has its respons delayed for some unknown reason. 198.49.243.253 is not one of the game servers though (I can provide a list if needed) so the high latency on that specific node is irrelevant to our gameplay as long as it forwards data correctly the way your traceroute shows.

    ---
    "-Grind is good!" --Gordon Geko
    Accolades checklist: https://bit.ly/FLUFFYS
  • ewilpwnyewilpwny Member Posts: 22 Arc User
    trekpuppy wrote: »
    ewilpwny wrote: »
    19 99 ms 99 ms 99 ms patchserver2.crypticstudios.com [208.95.185.41]
    I believe you're misreading your own traceroute. The final line there shows perfectly normal ping response times when your data hits Cryptic's network. Not even a single drop-out on those three attempts. If the high latency on 198.49.243.253 were due to a bottleneck the high latency would persist on every node behind it and your own traceroute shows that this isn't the case. In fact, every traceroute provided by different users recently shows the exact same pattern. This is evidence that 198.49.243.253 forwards data to the game servers without any extra delay but data sent explicitly to 198.49.243.253 has its respons delayed for some unknown reason. 198.49.243.253 is not one of the game servers though (I can provide a list if needed) so the high latency on that specific node is irrelevant to our gameplay as long as it forwards data correctly the way your traceroute shows.

    Thanks for the info!

    You are right, however the slow response from 198.49.243.253 still make me suspect that one it's hamsters have gone to a Christmas party (or something like that).
    See you in space :D
    Seruk@HoodedSandman
Sign In or Register to comment.