Well, I just got off of a very informative and dare I say, enjoyable call with comcast's technical department. The response was that they are not doing any sort of packet filtering nor have anything on record for flags with any of the server addresses according to the tracert results. However, the tech has flagged the address for cryptic-1.border12.bsn.pnap.net and any further support calls that reference that address will be added together for review. So if you are a Comcast customer, call up your technical support department, reference that address, and tell them the issues you are having. The more they hear from, the faster and easier they can push it up the chain and get any problems resolved, whether on their end, or on the receiving end, if the issues actually are primarily with Comcast-based connections.
Side note: the tech I spoke too is also in the process of signing up for access to the beta, he seemed quite interested, and assured me that if he also experiences frequent disconnect issues himself, "you can be sure management will hear about it" over at Comcast .
Side note: the tech I spoke too is also in the process of signing up for access to the beta, he seemed quite interested, and assured me that if he also experiences frequent disconnect issues himself, "you can be sure management will hear about it" over at Comcast .
Now thats what we need!! Good job bro, many props to you Would also be good to have a Comcast guy on our side lmao
Also on comcast and irritated myself, more by the fact the Devs post in the most TRIBBLE threads on this forum but continue to ignore this issue and all posts related to it. Just tells me they have no idea what is going on and don't want to say anything till they have a clue, and after 3 days, I expected them to have a clue.
Well, I just got off of a very informative and dare I say, enjoyable call with comcast's technical department. The response was that they are not doing any sort of packet filtering nor have anything on record for flags with any of the server addresses according to the tracert results. However, the tech has flagged the address for cryptic-1.border12.bsn.pnap.net and any further support calls that reference that address will be added together for review. So if you are a Comcast customer, call up your technical support department, reference that address, and tell them the issues you are having. The more they hear from, the faster and easier they can push it up the chain and get any problems resolved, whether on their end, or on the receiving end, if the issues actually are primarily with Comcast-based connections.
Side note: the tech I spoke too is also in the process of signing up for access to the beta, he seemed quite interested, and assured me that if he also experiences frequent disconnect issues himself, "you can be sure management will hear about it" over at Comcast .
let me first say, I am NOT trying to jarate you off or anything.
But you spoke with a CSR not a tech. EVERYTHING he said is SOP for dealing with customers who feel like their service is poor for whatever reason. I have an INTIMATE relationship with Comcast and know their SOP your call changed nothing. Beyond that calling PA head office is the ONLY way to get an issue with them resolved if it's a continuing issue (read has gone on for more than a few line tech visits) and in this case I can assure you that customers calling PA head offices will do absolutely nothing. They will not have a Senior Tech hunting down things you don't even know for sure is a problem with their network EVEN IF IT WERE! Cryptic needs to get involved.
i am also getting a timeout at cryptic-1.border12.bsn.pnap.net [62.251.130.10] still googling to see what all i can find, having more fun with this than going through all the disconnects
Im with BT 'British Telecom' and have had this issue on and off for days, but just now it does not even get past the Connecting to account server, just tried it one more time and got to the character select screen though.
i am also getting a timeout at cryptic-1.border12.bsn.pnap.net [62.251.130.10] still googling to see what all i can find, having more fun with this than going through all the disconnects
Didnt even think to do that, good idea. But doesn't bode well if this is the network we have to use to access the game. Systemic problem outside of their control...
Well, I just got off of a very informative and dare I say, enjoyable call with comcast's technical department. The response was that they are not doing any sort of packet filtering nor have anything on record for flags with any of the server addresses according to the tracert results. However, the tech has flagged the address for cryptic-1.border12.bsn.pnap.net and any further support calls that reference that address will be added together for review. So if you are a Comcast customer, call up your technical support department, reference that address, and tell them the issues you are having. The more they hear from, the faster and easier they can push it up the chain and get any problems resolved, whether on their end, or on the receiving end, if the issues actually are primarily with Comcast-based connections.
Side note: the tech I spoke too is also in the process of signing up for access to the beta, he seemed quite interested, and assured me that if he also experiences frequent disconnect issues himself, "you can be sure management will hear about it" over at Comcast .
Thanks for this Raccoon. But really, I just proved myself that its nothing else but cryptic servers. I was running 2 simultaneous pings, pinging cryptic patch server at the same time as as one of the pnap servers. Pnap is doing ok all the time, while I am getting time outs on Cryptic patch server. And it happens only when I log into the game. Which means that as soon as my account connects to the cryptic server only then I start having problems, again note that pnap IP replying without any timeouts.
Other people also confirmed that while they get disconnected on one account they don't get disconnected on the other account. Cryptic login server is having some issues. But having them for 3 days without devs acknowledging it and especially AFTER 2 BIG PATCHES.... its just not normal.
I can only wonder what will happen to the game if it will get released like this... I think there will be a riot. We are a week away from Early start and state of the game is simply not acceptable.
Scratch that, tried to load another area and boomb, server disconnect... ...
1 39 ms 98 ms 99 ms BThomehub.home [192.168.1.254]
2 31 ms 35 ms 34 ms 217.47.249.122
3 33 ms 33 ms 34 ms 217.47.203.145
4 37 ms 33 ms 46 ms 217.47.203.6
5 36 ms 36 ms 36 ms 217.41.172.9
6 33 ms 34 ms 34 ms 217.41.172.66
7 34 ms 33 ms 36 ms 217.41.172.134
8 34 ms 35 ms 34 ms 217.41.172.62
9 37 ms 36 ms 37 ms 217.47.86.50
10 37 ms 35 ms 36 ms core1-pos15-0.birmingham.ukcore.bt.net [195.99.
0.85]
11 39 ms 37 ms 41 ms 62.172.103.82
12 43 ms 44 ms 44 ms transit1-xe0-0-0.ealing.ukcore.bt.net [62.6.200
06]
13 37 ms 37 ms 38 ms t2c1-ge14-0-0.uk-eal.eu.bt.net [166.49.168.25]
14 36 ms 35 ms 36 ms t2c2-p3-1.uk-lon1.eu.bt.net [166.49.208.110]
15 36 ms 37 ms 36 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.110]
16 41 ms 41 ms 40 ms 195.66.224.130
17 40 ms 36 ms 40 ms p5-0-0d0.rar1.london-en.uk.xo.net [71.5.174.133
18 117 ms 117 ms 248 ms p1-0-0d0.rar1.nyc-ny.us.xo.net [65.106.0.118]
19 122 ms 126 ms 122 ms te-3-1-0.rar3.nyc-ny.us.xo.net [65.106.1.18]
20 112 ms 113 ms 162 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26
21 126 ms 123 ms 125 ms 216.55.4.18
22 112 ms 111 ms 112 ms patchserver.crypticstudios.com [208.95.184.25]
Scratch that, tried to load another area and boomb, server disconnect... ...
1 39 ms 98 ms 99 ms BThomehub.home [192.168.1.254]
2 31 ms 35 ms 34 ms 217.47.249.122
3 33 ms 33 ms 34 ms 217.47.203.145
4 37 ms 33 ms 46 ms 217.47.203.6
5 36 ms 36 ms 36 ms 217.41.172.9
6 33 ms 34 ms 34 ms 217.41.172.66
7 34 ms 33 ms 36 ms 217.41.172.134
8 34 ms 35 ms 34 ms 217.41.172.62
9 37 ms 36 ms 37 ms 217.47.86.50
10 37 ms 35 ms 36 ms core1-pos15-0.birmingham.ukcore.bt.net [195.99.
0.85]
11 39 ms 37 ms 41 ms 62.172.103.82
12 43 ms 44 ms 44 ms transit1-xe0-0-0.ealing.ukcore.bt.net [62.6.200
06]
13 37 ms 37 ms 38 ms t2c1-ge14-0-0.uk-eal.eu.bt.net [166.49.168.25]
14 36 ms 35 ms 36 ms t2c2-p3-1.uk-lon1.eu.bt.net [166.49.208.110]
15 36 ms 37 ms 36 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.110]
16 41 ms 41 ms 40 ms 195.66.224.130
17 40 ms 36 ms 40 ms p5-0-0d0.rar1.london-en.uk.xo.net [71.5.174.133
18 117 ms 117 ms 248 ms p1-0-0d0.rar1.nyc-ny.us.xo.net [65.106.0.118]
19 122 ms 126 ms 122 ms te-3-1-0.rar3.nyc-ny.us.xo.net [65.106.1.18]
20 112 ms 113 ms 162 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26
21 126 ms 123 ms 125 ms 216.55.4.18
22 112 ms 111 ms 112 ms patchserver.crypticstudios.com [208.95.184.25]
Good example here that comcast has nothing to do with this. Littica's connection is going through a different route.
216.55.4.18:
Network Owner:
Cryptic Studios (294198-1)
Registered on: network:Created:20091105
Updated on: network:Updated:20091217
Expires on: unknown
Netblock(s): 216.55.4.16/30
Cryptic, come clean and tell us what the heck you did to the game. Hiding in the dark just rubs the public the wrong way, and once bitten twice shy. Remember that.
As I said in the other post with this same information. Charter User: Same issues, d/c constantly
Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:
3 10 ms 8 ms 9 ms swc03aldlmi-gbe-2-5.aldl.mi.charter.com [96.34.3
6.8]
4 31 ms 22 ms 8 ms 96-34-32-1.static.unas.mi.charter.com [96.34.32.
1]
5 11 ms 9 ms 9 ms 96-34-32-26.static.unas.mi.charter.com [96.34.32
.26]
6 16 ms 11 ms 11 ms crr01sgnwmi-gbe-6-1-0.sgnw.mi.charter.com [96.34
.32.31]
7 12 ms 13 ms 11 ms bbr01sgnwmi-tge-0-0-0-0.sgnw.mi.charter.com [96.
34.2.56]
8 25 ms 24 ms 25 ms cer-edge-13.inet.qwest.net [63.239.212.13]
9 26 ms 24 ms 24 ms chp-brdr-03.inet.qwest.net [67.14.8.194]
10 26 ms 25 ms 25 ms 206.111.2.85.ptr.us.xo.net [206.111.2.85]
11 55 ms 52 ms 52 ms vb2001.rar3.nyc-ny.us.xo.net [207.88.13.10]
12 59 ms 78 ms 60 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
13 64 ms 57 ms 67 ms 216.55.4.18
14 64 ms 65 ms 65 ms patchserver.crypticstudios.com [208.95.184.25]
and this seems to be just fine now, but still having the issues which concludes that it is a cryptic related problem.
Oh Yes and BTW this happened towards the end of CB for me as well and then Cryptic did a mini patch one night and wham worked great ever since. Until the last big patch that is.
let me first say, I am NOT trying to jarate you off or anything.
But you spoke with a CSR not a tech. EVERYTHING he said is SOP for dealing with customers who feel like their service is poor for whatever reason. I have an INTIMATE relationship with Comcast and know their SOP your call changed nothing. Beyond that calling PA head office is the ONLY way to get an issue with them resolved if it's a continuing issue (read has gone on for more than a few line tech visits) and in this case I can assure you that customers calling PA head offices will do absolutely nothing. They will not have a Senior Tech hunting down things you don't even know for sure is a problem with their network EVEN IF IT WERE! Cryptic needs to get involved.
Actually no, I first spoke to a CSR, who of course was unable to do anything about it and gave me the standard brush-off (while also suggesting upgrades to my service, duh) - however, I've both worked in and dealt with standard call centers many times, and was able to get routed to an actual service tech. Admittedly, it did not happen right away, and I had to wait a bit over an hour for a call back, but it DID happen eventually.
(Side note: he also had significantly more access to my usage info and modem signal results than the standard CSR people do - if only they made this info available to the frontline CSRs my modem issues from last October could have been dealt with MUCH faster and easier...)
As for the rest, yes, he flat out told me that while he personally can keep an eye on things, it is unlikely that they will be able to push it further until/unless they have more customers reporting the same issues - especially if it is NOT a Comcast issue (as I suspect that it is not) but rather an issue on the "other end". However, this does not mean that they CAN'T make said phone calls if there ARE enough customers having the problem - and they ARE the largest internet access provider in the US right now. When they get in touch with another ISP about their customers having connection issues, the other ISP DOES listen. So if this is an isp related issue, even if not Comcast directly, say with savvis or pnap getting enough customers to notify their support departments WILL get it noticed and resolved.
Many have brought up the issue with WoW; while Comcast was partially at fault there, Verizon and AT&T were also involved. However, Comcast was the one able to resolve those issues with VZ and ATT - the customers themselves would have been able to do NOTHING about it (if you think you get slow/lackluster problems when calling the CS dept of a company you are a customer of, just imagine how poor the reception is when you call a competitor company that you are NOT a customer of, and ask to get things fixed, even if the problem is on their end...).
TL;DR - even if they can't do anything immediately, IF it is a routing issue and not an internal cryptic server issue, calling Comcast, referencing that address, and giving them info about the problem, CAN make a difference if enough people do so. AND it doesn't cost you anything except for your time (and possible frustration dealing with the first level CSRs who are not given enough information/power to actually do anything to help - but the actual techs I have spoken to at Comcast on numerous occasions have always been helpful, knowledgeable, and quite friendly - in fact we often end up getting distracted just chatting about other things, rather than the issue itself - but then I am a techie myself so I enjoy those sorts of conversations :P)
I am having this issue as well, on Comcast in SLC, UT.
Have been playing beta since it started last week, and until a couple days ago I never had any connection issues. Now I'm getting DC'd as often as every minute, with staying connected for as long as 10-15 minutes if I'm lucky...but typically it's on the much shorter end.
Have a lifetime sub...really hoping this gets fixed before release.
Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 9 ms 9 ms ge-1-13-ur01.f1fayette.ga.atlanta.comcast.net [6
8.85.32.65]
4 10 ms 9 ms 9 ms te-9-4-ur01.f2peachtree.ga.atlanta.comcast.net [
68.86.106.69]
5 9 ms 9 ms 9 ms te-9-4-ur01.f3sfulton.ga.atlanta.comcast.net [68
.86.106.65]
6 11 ms 11 ms 12 ms te-9-4-ur01.e1eastpoint.ga.atlanta.comcast.net [
68.86.106.61]
7 9 ms 9 ms 9 ms te-9-2-ur01.a5atlanta.ga.atlanta.comcast.net [68
.86.106.57]
8 11 ms 11 ms 28 ms te-9-4-ur01.a6atlanta.ga.atlanta.comcast.net [68
.86.106.21]
9 11 ms 11 ms 11 ms te-0-2-0-4-crs01.b0atlanta.ga.atlanta.comcast.ne
t [68.86.106.17]
10 13 ms 11 ms 12 ms pos-1-3-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.90.125]
11 34 ms 33 ms 33 ms pos-1-15-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.149]
12 34 ms 33 ms 33 ms pos-0-1-0-0-pe01.1950stemmons.tx.ibone.comcast.n
et [68.86.86.94]
13 164 ms 254 ms 193 ms 208.175.175.97
14 34 ms 33 ms 33 ms dpr1-ge-2-0-0.dallasequinix.savvis.net [204.70.2
04.146]
15 32 ms 33 ms 33 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196
.29]
16 76 ms 74 ms 74 ms cr1-pos-0-0-0-0.NewYork.savvis.net [204.70.192.1
02]
17 75 ms 76 ms 77 ms er1-te-9-0-0.newyorknyd.savvis.net [204.70.198.1
65]
18 86 ms 83 ms 86 ms cr2-tengig-0-3-0-0.boston.savvis.net [204.70.198
.174]
19 81 ms 81 ms 81 ms acr2-pos-3-0-0.boston.savvis.net [204.70.195.170
]
20 81 ms 81 ms 81 ms acr1-as0-0.Boston.savvis.net [208.172.51.53]
21 63 ms 64 ms 62 ms internap.Boston.savvis.net [208.172.51.230]
22 63 ms 62 ms 62 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
05]
23 * * * Request timed out.
24 * * * Request timed out.
25 * * 75 ms patchserver.crypticstudios.com [208.95.184.25]
Trace complete.
also the forums stop responding when this happens and i finally got one in on time
Actually no, I first spoke to a CSR, who of course was unable to do anything about it and gave me the standard brush-off (while also suggesting upgrades to my service, duh) - however, I've both worked in and dealt with standard call centers many times, and was able to get routed to an actual service tech. Admittedly, it did not happen right away, and I had to wait a bit over an hour for a call back, but it DID happen eventually.
(Side note: he also had significantly more access to my usage info and modem signal results than the standard CSR people do - if only they made this info available to the frontline CSRs my modem issues from last October could have been dealt with MUCH faster and easier...)
As for the rest, yes, he flat out told me that while he personally can keep an eye on things, it is unlikely that they will be able to push it further until/unless they have more customers reporting the same issues - especially if it is NOT a Comcast issue (as I suspect that it is not) but rather an issue on the "other end". However, this does not mean that they CAN'T make said phone calls if there ARE enough customers having the problem - and they ARE the largest internet access provider in the US right now. When they get in touch with another ISP about their customers having connection issues, the other ISP DOES listen. So if this is an isp related issue, even if not Comcast directly, say with savvis or pnap getting enough customers to notify their support departments WILL get it noticed and resolved.
Many have brought up the issue with WoW; while Comcast was partially at fault there, Verizon and AT&T were also involved. However, Comcast was the one able to resolve those issues with VZ and ATT - the customers themselves would have been able to do NOTHING about it (if you think you get slow/lackluster problems when calling the CS dept of a company you are a customer of, just imagine how poor the reception is when you call a competitor company that you are NOT a customer of, and ask to get things fixed, even if the problem is on their end...).
TL;DR - even if they can't do anything immediately, IF it is a routing issue and not an internal cryptic server issue, calling Comcast, referencing that address, and giving them info about the problem, CAN make a difference if enough people do so. AND it doesn't cost you anything except for your time (and possible frustration dealing with the first level CSRs who are not given enough information/power to actually do anything to help - but the actual techs I have spoken to at Comcast on numerous occasions have always been helpful, knowledgeable, and quite friendly - in fact we often end up getting distracted just chatting about other things, rather than the issue itself - but then I am a techie myself so I enjoy those sorts of conversations :P)
Keep wasting your time with them while I'm trying to help you understand that it's a waste of time. I have an INTIMATE relationship with Comcast and you got their SOP from a CSR. Oh by the way, distracted talking about other things HELLO SOP! But you either get it or you don't, you don't.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
It is Comcastic!!! Please fix!
Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 11 ms 10 ms te-3-4-ur10.sanjose.ca.sfba.comcast.net [68.85.1
90.165]
4 14 ms 11 ms 14 ms 68.85.155.54
5 13 ms 14 ms 14 ms pos-0-4-0-0-cr01.sacramento.ca.ibone.comcast.net
[68.86.90.141]
6 17 ms 15 ms 16 ms pos-0-8-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.85.78]
7 15 ms 16 ms 16 ms er1-tengig2-4.sanjoseequinix.savvis.net [206.24.
222.1]
8 16 ms 18 ms 16 ms cr1-tenge-0-3-5-0.sanfrancisco.savvis.net [204.7
0.200.198]
9 102 ms 112 ms 105 ms cr2-bundle-pos-1.newyork.savvis.net [204.70.197.
34]
10 102 ms 102 ms 103 ms er1-te-1-0-0.newyorknyd.savvis.net [204.70.196.7
0]
11 115 ms 121 ms 130 ms cr2-tengig-0-3-0-0.boston.savvis.net [204.70.198
.174]
12 109 ms 107 ms 107 ms acr2-pos-3-0-0.boston.savvis.net [204.70.195.170
]
13 108 ms 107 ms 107 ms acr1-as0-0.Boston.savvis.net [208.172.51.53]
14 109 ms 107 ms 107 ms internap.Boston.savvis.net [208.172.51.230]
15 106 ms 107 ms 105 ms border12.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
2]
16 112 ms 107 ms 109 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
17 111 ms 107 ms 108 ms patchserver.crypticstudios.com [208.95.184.25]
I do not have Comcast, as I am from Europe, Norway.
I do however get frequent disconnects. I might be so lucky as to get in a good 10 minutes before disconnecting, and having to wait 5 minutes to be able to log in again.
1 <1 ms <1 ms <1 ms 10.0.0.1
2 20 ms 15 ms 16 ms 1.80-202-16.nextgentel.com [80.202.16.1]
3 25 ms 24 ms 24 ms 217-13-1-61.dd.nextgentel.com [217.13.1.61]
4 24 ms 26 ms 25 ms 34.84-48-3.nextgentel.com [84.48.3.34]
5 100 ms 42 ms 25 ms 62.84-48-3.nextgentel.com [84.48.3.62]
6 24 ms 25 ms 24 ms 213.248.104.117
7 32 ms 31 ms 33 ms kbn-bb1-link.telia.net [80.91.250.139]
8 116 ms 115 ms 117 ms nyk-bb1-link.telia.net [80.91.249.24]
9 120 ms 119 ms 119 ms nyk-b5-link.telia.net [80.91.253.102]
10 118 ms 118 ms 118 ms 206.111.13.89.ptr.us.xo.net [206.111.13.89]
11 125 ms 125 ms 125 ms te0-12-2-0.rar3.nyc-ny.us.xo.net [207.88.12.173]
12 122 ms 123 ms 123 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
13 132 ms 127 ms 121 ms 216.55.4.18
14 125 ms 125 ms 122 ms patchserver.crypticstudios.com [208.95.184.25]
either way it doesnt matter which company you talk to AT&T was worse than comcast in my opinion, i got dropped non stop every day every hour every 30 minutes sometimes every 5 minutes this is nothing compared to putting up with that sorry excuse for an isp provider the newyork.savvis hub/router/whatever isnt the main problem its on cryptics side
heres another
Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 9 ms 9 ms ge-1-13-ur01.f1fayette.ga.atlanta.comcast.net [6
8.85.32.65]
4 9 ms 9 ms 9 ms te-9-4-ur01.f2peachtree.ga.atlanta.comcast.net [
68.86.106.69]
5 11 ms 13 ms 9 ms te-9-4-ur01.f3sfulton.ga.atlanta.comcast.net [68
.86.106.65]
6 10 ms 11 ms 9 ms te-9-4-ur01.e1eastpoint.ga.atlanta.comcast.net [
68.86.106.61]
7 11 ms 9 ms 9 ms te-9-2-ur01.a5atlanta.ga.atlanta.comcast.net [68
.86.106.57]
8 9 ms 12 ms 11 ms te-9-4-ur01.a6atlanta.ga.atlanta.comcast.net [68
.86.106.21]
9 11 ms 11 ms 12 ms te-0-2-0-4-crs01.b0atlanta.ga.atlanta.comcast.ne
t [68.86.106.17]
10 11 ms 12 ms 11 ms pos-1-3-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.90.125]
11 33 ms 33 ms 33 ms pos-1-15-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.149]
12 36 ms 33 ms 33 ms pos-0-1-0-0-pe01.1950stemmons.tx.ibone.comcast.n
et [68.86.86.94]
13 32 ms 33 ms 65 ms 208.175.175.97
14 34 ms 33 ms 33 ms dpr1-ge-2-0-0.dallasequinix.savvis.net [204.70.2
04.146]
15 46 ms 33 ms 33 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196
.29]
16 75 ms 76 ms 76 ms cr1-pos-0-0-0-0.NewYork.savvis.net [204.70.192.1
02]
17 75 ms 76 ms 79 ms er1-te-9-0-0.newyorknyd.savvis.net [204.70.198.1
65]
18 91 ms 83 ms 85 ms cr2-tengig-0-3-0-0.boston.savvis.net [204.70.198
.174]
19 83 ms 81 ms 197 ms acr2-pos-3-0-0.boston.savvis.net [204.70.195.170
]
20 81 ms 81 ms 81 ms acr1-as0-0.Boston.savvis.net [208.172.51.53]
21 63 ms 62 ms 62 ms internap.Boston.savvis.net [208.172.51.230]
22 72 ms 64 ms 62 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
05]
23 * * * Request timed out.
24 * 62 ms 62 ms patchserver.crypticstudios.com [208.95.184.25]
CSR = script-driven flunky who I spoke to on first call. NOT the person who I spoke to on the second one. The level of technical understanding, deviation from "the script", willingness to discuss "how things really work" rather than "policy states that", etc show the difference very clearly to anyone who has even a passing understanding with how call centers work.
However, there is a very big difference between speaking to a CSR and an actual support tech - for all your "intimate" knowledge of Comcast, you of all people should know that...
Yes, I know that it is "SOP" to wait for multiple customer issues, or multiple issues and usually a physical line tech showing up on site to inspect connections, before being able to do anything if the issue cannot be clearly attributed to the company at that exact moment that you are speaking to the tech. That is why I said that anyone having issues should ALSO contact Comcast and report the problem - even if it is not an issue with Comcast directly, IF it IS a routing issue of any sort aside from issues within cryptic's own local network, they CAN do something about it given enough people contacting them.
I think that if you only allow people to post here who are having trouble you'll make it seem like Comcast is the problem when it most likely isn't. A number of other threads have referred to this "savvis," which seems to be the culprit. Some sort of backbone related issue, maybe?
Anyway, I'm a Comcast customer, have been since early December when I was invited to Closed Beta and have never had an ISP-related issue.
Comments
Side note: the tech I spoke too is also in the process of signing up for access to the beta, he seemed quite interested, and assured me that if he also experiences frequent disconnect issues himself, "you can be sure management will hear about it" over at Comcast
Now thats what we need!! Good job bro, many props to you
No, the City of Heroes (NCSoft) servers are not in the same place as the STO (Cryptic/Atari) servers.
let me first say, I am NOT trying to jarate you off or anything.
But you spoke with a CSR not a tech. EVERYTHING he said is SOP for dealing with customers who feel like their service is poor for whatever reason. I have an INTIMATE relationship with Comcast and know their SOP your call changed nothing. Beyond that calling PA head office is the ONLY way to get an issue with them resolved if it's a continuing issue (read has gone on for more than a few line tech visits) and in this case I can assure you that customers calling PA head offices will do absolutely nothing. They will not have a Senior Tech hunting down things you don't even know for sure is a problem with their network EVEN IF IT WERE! Cryptic needs to get involved.
http://www.google.com/search?hl=en&q=cr1-pos-0-0-0-0.newyork.savvis.net&btnG=Search&aq=f&aql=&aqi=&oq=
i am also getting a timeout at cryptic-1.border12.bsn.pnap.net [62.251.130.10] still googling to see what all i can find, having more fun with this than going through all the disconnects
Ok, didnt know that.
Didnt even think to do that, good idea. But doesn't bode well if this is the network we have to use to access the game. Systemic problem outside of their control...
Thanks for this Raccoon. But really, I just proved myself that its nothing else but cryptic servers. I was running 2 simultaneous pings, pinging cryptic patch server at the same time as as one of the pnap servers. Pnap is doing ok all the time, while I am getting time outs on Cryptic patch server. And it happens only when I log into the game. Which means that as soon as my account connects to the cryptic server only then I start having problems, again note that pnap IP replying without any timeouts.
Other people also confirmed that while they get disconnected on one account they don't get disconnected on the other account. Cryptic login server is having some issues. But having them for 3 days without devs acknowledging it and especially AFTER 2 BIG PATCHES.... its just not normal.
I can only wonder what will happen to the game if it will get released like this... I think there will be a riot. We are a week away from Early start and state of the game is simply not acceptable.
1 39 ms 98 ms 99 ms BThomehub.home [192.168.1.254]
2 31 ms 35 ms 34 ms 217.47.249.122
3 33 ms 33 ms 34 ms 217.47.203.145
4 37 ms 33 ms 46 ms 217.47.203.6
5 36 ms 36 ms 36 ms 217.41.172.9
6 33 ms 34 ms 34 ms 217.41.172.66
7 34 ms 33 ms 36 ms 217.41.172.134
8 34 ms 35 ms 34 ms 217.41.172.62
9 37 ms 36 ms 37 ms 217.47.86.50
10 37 ms 35 ms 36 ms core1-pos15-0.birmingham.ukcore.bt.net [195.99.
0.85]
11 39 ms 37 ms 41 ms 62.172.103.82
12 43 ms 44 ms 44 ms transit1-xe0-0-0.ealing.ukcore.bt.net [62.6.200
06]
13 37 ms 37 ms 38 ms t2c1-ge14-0-0.uk-eal.eu.bt.net [166.49.168.25]
14 36 ms 35 ms 36 ms t2c2-p3-1.uk-lon1.eu.bt.net [166.49.208.110]
15 36 ms 37 ms 36 ms t2a1-ge7-0-0.uk-lon1.eu.bt.net [166.49.135.110]
16 41 ms 41 ms 40 ms 195.66.224.130
17 40 ms 36 ms 40 ms p5-0-0d0.rar1.london-en.uk.xo.net [71.5.174.133
18 117 ms 117 ms 248 ms p1-0-0d0.rar1.nyc-ny.us.xo.net [65.106.0.118]
19 122 ms 126 ms 122 ms te-3-1-0.rar3.nyc-ny.us.xo.net [65.106.1.18]
20 112 ms 113 ms 162 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26
21 126 ms 123 ms 125 ms 216.55.4.18
22 112 ms 111 ms 112 ms patchserver.crypticstudios.com [208.95.184.25]
Good example here that comcast has nothing to do with this. Littica's connection is going through a different route.
216.55.4.18:
Network Owner:
Cryptic Studios (294198-1)
Registered on: network:Created:20091105
Updated on: network:Updated:20091217
Expires on: unknown
Netblock(s): 216.55.4.16/30
Charter User: Same issues, d/c constantly
Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:
3 10 ms 8 ms 9 ms swc03aldlmi-gbe-2-5.aldl.mi.charter.com [96.34.3
6.8]
4 31 ms 22 ms 8 ms 96-34-32-1.static.unas.mi.charter.com [96.34.32.
1]
5 11 ms 9 ms 9 ms 96-34-32-26.static.unas.mi.charter.com [96.34.32
.26]
6 16 ms 11 ms 11 ms crr01sgnwmi-gbe-6-1-0.sgnw.mi.charter.com [96.34
.32.31]
7 12 ms 13 ms 11 ms bbr01sgnwmi-tge-0-0-0-0.sgnw.mi.charter.com [96.
34.2.56]
8 25 ms 24 ms 25 ms cer-edge-13.inet.qwest.net [63.239.212.13]
9 26 ms 24 ms 24 ms chp-brdr-03.inet.qwest.net [67.14.8.194]
10 26 ms 25 ms 25 ms 206.111.2.85.ptr.us.xo.net [206.111.2.85]
11 55 ms 52 ms 52 ms vb2001.rar3.nyc-ny.us.xo.net [207.88.13.10]
12 59 ms 78 ms 60 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
13 64 ms 57 ms 67 ms 216.55.4.18
14 64 ms 65 ms 65 ms patchserver.crypticstudios.com [208.95.184.25]
and this seems to be just fine now, but still having the issues which concludes that it is a cryptic related problem.
Oh Yes and BTW this happened towards the end of CB for me as well and then Cryptic did a mini patch one night and wham worked great ever since. Until the last big patch that is.
Actually no, I first spoke to a CSR, who of course was unable to do anything about it and gave me the standard brush-off (while also suggesting upgrades to my service, duh) - however, I've both worked in and dealt with standard call centers many times, and was able to get routed to an actual service tech. Admittedly, it did not happen right away, and I had to wait a bit over an hour for a call back, but it DID happen eventually.
(Side note: he also had significantly more access to my usage info and modem signal results than the standard CSR people do - if only they made this info available to the frontline CSRs my modem issues from last October could have been dealt with MUCH faster and easier...)
As for the rest, yes, he flat out told me that while he personally can keep an eye on things, it is unlikely that they will be able to push it further until/unless they have more customers reporting the same issues - especially if it is NOT a Comcast issue (as I suspect that it is not) but rather an issue on the "other end". However, this does not mean that they CAN'T make said phone calls if there ARE enough customers having the problem - and they ARE the largest internet access provider in the US right now. When they get in touch with another ISP about their customers having connection issues, the other ISP DOES listen. So if this is an isp related issue, even if not Comcast directly, say with savvis or pnap getting enough customers to notify their support departments WILL get it noticed and resolved.
Many have brought up the issue with WoW; while Comcast was partially at fault there, Verizon and AT&T were also involved. However, Comcast was the one able to resolve those issues with VZ and ATT - the customers themselves would have been able to do NOTHING about it (if you think you get slow/lackluster problems when calling the CS dept of a company you are a customer of, just imagine how poor the reception is when you call a competitor company that you are NOT a customer of, and ask to get things fixed, even if the problem is on their end...).
TL;DR - even if they can't do anything immediately, IF it is a routing issue and not an internal cryptic server issue, calling Comcast, referencing that address, and giving them info about the problem, CAN make a difference if enough people do so. AND it doesn't cost you anything except for your time (and possible frustration dealing with the first level CSRs who are not given enough information/power to actually do anything to help - but the actual techs I have spoken to at Comcast on numerous occasions have always been helpful, knowledgeable, and quite friendly - in fact we often end up getting distracted just chatting about other things, rather than the issue itself - but then I am a techie myself so I enjoy those sorts of conversations :P)
Have been playing beta since it started last week, and until a couple days ago I never had any connection issues. Now I'm getting DC'd as often as every minute, with staying connected for as long as 10-15 minutes if I'm lucky...but typically it's on the much shorter end.
Have a lifetime sub...really hoping this gets fixed before release.
Win7x64
AVG
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 9 ms 9 ms ge-1-13-ur01.f1fayette.ga.atlanta.comcast.net [6
8.85.32.65]
4 10 ms 9 ms 9 ms te-9-4-ur01.f2peachtree.ga.atlanta.comcast.net [
68.86.106.69]
5 9 ms 9 ms 9 ms te-9-4-ur01.f3sfulton.ga.atlanta.comcast.net [68
.86.106.65]
6 11 ms 11 ms 12 ms te-9-4-ur01.e1eastpoint.ga.atlanta.comcast.net [
68.86.106.61]
7 9 ms 9 ms 9 ms te-9-2-ur01.a5atlanta.ga.atlanta.comcast.net [68
.86.106.57]
8 11 ms 11 ms 28 ms te-9-4-ur01.a6atlanta.ga.atlanta.comcast.net [68
.86.106.21]
9 11 ms 11 ms 11 ms te-0-2-0-4-crs01.b0atlanta.ga.atlanta.comcast.ne
t [68.86.106.17]
10 13 ms 11 ms 12 ms pos-1-3-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.90.125]
11 34 ms 33 ms 33 ms pos-1-15-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.149]
12 34 ms 33 ms 33 ms pos-0-1-0-0-pe01.1950stemmons.tx.ibone.comcast.n
et [68.86.86.94]
13 164 ms 254 ms 193 ms 208.175.175.97
14 34 ms 33 ms 33 ms dpr1-ge-2-0-0.dallasequinix.savvis.net [204.70.2
04.146]
15 32 ms 33 ms 33 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196
.29]
16 76 ms 74 ms 74 ms cr1-pos-0-0-0-0.NewYork.savvis.net [204.70.192.1
02]
17 75 ms 76 ms 77 ms er1-te-9-0-0.newyorknyd.savvis.net [204.70.198.1
65]
18 86 ms 83 ms 86 ms cr2-tengig-0-3-0-0.boston.savvis.net [204.70.198
.174]
19 81 ms 81 ms 81 ms acr2-pos-3-0-0.boston.savvis.net [204.70.195.170
]
20 81 ms 81 ms 81 ms acr1-as0-0.Boston.savvis.net [208.172.51.53]
21 63 ms 64 ms 62 ms internap.Boston.savvis.net [208.172.51.230]
22 63 ms 62 ms 62 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
05]
23 * * * Request timed out.
24 * * * Request timed out.
25 * * 75 ms patchserver.crypticstudios.com [208.95.184.25]
Trace complete.
also the forums stop responding when this happens and i finally got one in on time
Cablevision
Zero disconnects until today.
Why does that make me think patch?:eek:
No issues with other online games or internet connectivity in general. Just STO.
Using comcast internet.
Before I only had problems logging into the game... after I was in... I rarely ever got disconnected.
After the most recent patch, I can get into the game just fine.... but im getting disconnected from the server about every 5 to 10 minutes.
Keep wasting your time with them while I'm trying to help you understand that it's a waste of time. I have an INTIMATE relationship with Comcast and you got their SOP from a CSR. Oh by the way, distracted talking about other things HELLO SOP! But you either get it or you don't, you don't.
This problem exactly. It's only since the patch on the 19th that I've had multiple fairly rapid disconnections.
(C) Copyright 1985-2001 Microsoft Corp.
It is Comcastic!!! Please fix!
Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 11 ms 10 ms te-3-4-ur10.sanjose.ca.sfba.comcast.net [68.85.1
90.165]
4 14 ms 11 ms 14 ms 68.85.155.54
5 13 ms 14 ms 14 ms pos-0-4-0-0-cr01.sacramento.ca.ibone.comcast.net
[68.86.90.141]
6 17 ms 15 ms 16 ms pos-0-8-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.85.78]
7 15 ms 16 ms 16 ms er1-tengig2-4.sanjoseequinix.savvis.net [206.24.
222.1]
8 16 ms 18 ms 16 ms cr1-tenge-0-3-5-0.sanfrancisco.savvis.net [204.7
0.200.198]
9 102 ms 112 ms 105 ms cr2-bundle-pos-1.newyork.savvis.net [204.70.197.
34]
10 102 ms 102 ms 103 ms er1-te-1-0-0.newyorknyd.savvis.net [204.70.196.7
0]
11 115 ms 121 ms 130 ms cr2-tengig-0-3-0-0.boston.savvis.net [204.70.198
.174]
12 109 ms 107 ms 107 ms acr2-pos-3-0-0.boston.savvis.net [204.70.195.170
]
13 108 ms 107 ms 107 ms acr1-as0-0.Boston.savvis.net [208.172.51.53]
14 109 ms 107 ms 107 ms internap.Boston.savvis.net [208.172.51.230]
15 106 ms 107 ms 105 ms border12.te7-1-bbnet1.bsn.pnap.net [63.251.128.4
2]
16 112 ms 107 ms 109 ms cryptic-1.border12.bsn.pnap.net [63.251.130.10]
17 111 ms 107 ms 108 ms patchserver.crypticstudios.com [208.95.184.25]
Trace complete.
I do however get frequent disconnects. I might be so lucky as to get in a good 10 minutes before disconnecting, and having to wait 5 minutes to be able to log in again.
1 <1 ms <1 ms <1 ms 10.0.0.1
2 20 ms 15 ms 16 ms 1.80-202-16.nextgentel.com [80.202.16.1]
3 25 ms 24 ms 24 ms 217-13-1-61.dd.nextgentel.com [217.13.1.61]
4 24 ms 26 ms 25 ms 34.84-48-3.nextgentel.com [84.48.3.34]
5 100 ms 42 ms 25 ms 62.84-48-3.nextgentel.com [84.48.3.62]
6 24 ms 25 ms 24 ms 213.248.104.117
7 32 ms 31 ms 33 ms kbn-bb1-link.telia.net [80.91.250.139]
8 116 ms 115 ms 117 ms nyk-bb1-link.telia.net [80.91.249.24]
9 120 ms 119 ms 119 ms nyk-b5-link.telia.net [80.91.253.102]
10 118 ms 118 ms 118 ms 206.111.13.89.ptr.us.xo.net [206.111.13.89]
11 125 ms 125 ms 125 ms te0-12-2-0.rar3.nyc-ny.us.xo.net [207.88.12.173]
12 122 ms 123 ms 123 ms ae0d0.mcr1.cambridge-ma.us.xo.net [216.156.0.26]
13 132 ms 127 ms 121 ms 216.55.4.18
14 125 ms 125 ms 122 ms patchserver.crypticstudios.com [208.95.184.25]
Trace complete.
heres another
Tracing route to patchserver.crypticstudios.com [208.95.184.25]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 9 ms 9 ms ge-1-13-ur01.f1fayette.ga.atlanta.comcast.net [6
8.85.32.65]
4 9 ms 9 ms 9 ms te-9-4-ur01.f2peachtree.ga.atlanta.comcast.net [
68.86.106.69]
5 11 ms 13 ms 9 ms te-9-4-ur01.f3sfulton.ga.atlanta.comcast.net [68
.86.106.65]
6 10 ms 11 ms 9 ms te-9-4-ur01.e1eastpoint.ga.atlanta.comcast.net [
68.86.106.61]
7 11 ms 9 ms 9 ms te-9-2-ur01.a5atlanta.ga.atlanta.comcast.net [68
.86.106.57]
8 9 ms 12 ms 11 ms te-9-4-ur01.a6atlanta.ga.atlanta.comcast.net [68
.86.106.21]
9 11 ms 11 ms 12 ms te-0-2-0-4-crs01.b0atlanta.ga.atlanta.comcast.ne
t [68.86.106.17]
10 11 ms 12 ms 11 ms pos-1-3-0-0-cr01.atlanta.ga.ibone.comcast.net [6
8.86.90.125]
11 33 ms 33 ms 33 ms pos-1-15-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.149]
12 36 ms 33 ms 33 ms pos-0-1-0-0-pe01.1950stemmons.tx.ibone.comcast.n
et [68.86.86.94]
13 32 ms 33 ms 65 ms 208.175.175.97
14 34 ms 33 ms 33 ms dpr1-ge-2-0-0.dallasequinix.savvis.net [204.70.2
04.146]
15 46 ms 33 ms 33 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196
.29]
16 75 ms 76 ms 76 ms cr1-pos-0-0-0-0.NewYork.savvis.net [204.70.192.1
02]
17 75 ms 76 ms 79 ms er1-te-9-0-0.newyorknyd.savvis.net [204.70.198.1
65]
18 91 ms 83 ms 85 ms cr2-tengig-0-3-0-0.boston.savvis.net [204.70.198
.174]
19 83 ms 81 ms 197 ms acr2-pos-3-0-0.boston.savvis.net [204.70.195.170
]
20 81 ms 81 ms 81 ms acr1-as0-0.Boston.savvis.net [208.172.51.53]
21 63 ms 62 ms 62 ms internap.Boston.savvis.net [208.172.51.230]
22 72 ms 64 ms 62 ms border12.te8-1-bbnet2.bsn.pnap.net [63.251.128.1
05]
23 * * * Request timed out.
24 * 62 ms 62 ms patchserver.crypticstudios.com [208.95.184.25]
Trace complete.
However, there is a very big difference between speaking to a CSR and an actual support tech - for all your "intimate" knowledge of Comcast, you of all people should know that...
Yes, I know that it is "SOP" to wait for multiple customer issues, or multiple issues and usually a physical line tech showing up on site to inspect connections, before being able to do anything if the issue cannot be clearly attributed to the company at that exact moment that you are speaking to the tech. That is why I said that anyone having issues should ALSO contact Comcast and report the problem - even if it is not an issue with Comcast directly, IF it IS a routing issue of any sort aside from issues within cryptic's own local network, they CAN do something about it given enough people contacting them.
Anyway, I'm a Comcast customer, have been since early December when I was invited to Closed Beta and have never had an ISP-related issue.