GMS Server Status Discussion 2012-01

I can't connect to the website or the game either. When using a webproxy I CAN view the website. When running a tracert things seem to go wrong here:
16 177 ms 177 ms 178 ms NexonNXGames.demarc.cogentco.com [38.104.76.142]
17 * * * Time-out bij opdracht.

Googling that domain shows me there have been issues like this before. What's causing it though is a riddle to me. Hope they fix it soon.

Interesting. I don't see any address like that in my tracert at all (and I connect just fine).
I get a whole bunch of ...LosAngeles1.Level3.net hosts, and then this
NEXON-AMERI.car1.LosAngeles1.Level3.net (4.59.56.186)

(a lot of hops after that, but none of them return tracert info)

Well....i downloaded Hotspot to try.
It let me go on the gamelauncher. So i put in my information and i get the "trouble logging in?" pop up.
I go on the site and itsays my account has been deactivated. It refuses to let me change my profile information and it doesnt give me the verification code to reactivate my account. I tried every email i could w/ no success.
So i uninstalled hotspot and i cannot get to the login screen or the site now.
Why is my account deactivated? =__=

Interesting. I don't see any address like that in my tracert at all (and I connect just fine).

Right, this is why I suspect an ISP might be able to reroute to an alternate path and successfully connect. So far no one who can connect sees that node.

Interesting. I don't see any address like that in my tracert at all (and I connect just fine).
I get a whole bunch of ...LosAngeles1.Level3.net hosts, and then this
NEXON-AMERI.car1.LosAngeles1.Level3.net (4.59.56.186)

(a lot of hops after that, but none of them return tracert info)

Interestingly I can't get to that one either, even though I never see the cogentco node.

Code:

Tracing route to NEXON-AMERI.car1.LosAngeles1.Level3.net [4.59.56.186]
  1    99 ms   101 ms   101 ms  192.168.2.1
  2   136 ms   102 ms   204 ms  bas10-london14_lo0_SYMP.net.bell.ca [64.230.200.221]
  3   127 ms   102 ms   101 ms  dis20-london14_5-1-0_100.net.bell.ca [64.230.56.132]
  4    50 ms    70 ms    71 ms  bx1-torontoxn_xe0-0-0.net.bell.ca [64.230.48.57]
  5    92 ms   101 ms   102 ms  level3_bx4-toronto12.net.bell.ca [67.69.246.158]
  6    76 ms    57 ms    89 ms  ae-3-3.bar1.Toronto1.Level3.net [4.69.153.81]
  7   110 ms   101 ms   101 ms  ae-0-11.bar1.Toronto1.Level3.net [4.69.151.241]
  8   121 ms   101 ms   101 ms  ae-9-9.ebr1.Chicago1.Level3.net [4.69.151.110]
  9   122 ms    70 ms   132 ms  ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
10   154 ms    80 ms    72 ms  ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]
11   144 ms   102 ms   101 ms  ae-14-14.ebr1.Dallas1.Level3.net [4.69.151.118]
12   111 ms   129 ms   101 ms  ae-81-81.csw3.Dallas1.Level3.net [4.69.151.149]
13   122 ms   101 ms   101 ms  ae-83-83.ebr3.Dallas1.Level3.net [4.69.151.158]
14   123 ms   128 ms   165 ms  ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]
15   156 ms   119 ms   129 ms  ae-82-82.csw3.LosAngeles1.Level3.net [4.69.137.26]
16   148 ms   204 ms   204 ms  ae-31-80.car1.LosAngeles1.Level3.net [4.69.144.131]
17     *        *        *     Request timed out.

Code:

Tracing route to www.nexon.net [63.251.217.189]
over a maximum of 30 hops:

  1    97 ms   101 ms   101 ms  192.168.2.1
  2   129 ms   101 ms   101 ms  bas10-london14_lo0_SYMP.net.bell.ca [64.230.200.221]
  3   120 ms    97 ms   106 ms  dis20-london14_5-1-0_100.net.bell.ca [64.230.56.132]
  4   124 ms   101 ms   101 ms  bx6-chicago23_POS0-3-0-0.net.bell.ca [64.230.186.202]
  5   122 ms   101 ms   101 ms  te4-1.ccr01.ord09.atlas.cogentco.com [154.54.11.29]
  6   124 ms   101 ms   101 ms  te0-4-0-6.ccr21.ord01.atlas.cogentco.com [154.54.29.189]
  7   123 ms   101 ms   101 ms  te0-3-0-0.ccr21.mci01.atlas.cogentco.com [154.54.7.185]
  8   121 ms   101 ms   101 ms  te0-4-0-2.ccr21.dfw01.atlas.cogentco.com [154.54.46.202]
  9   125 ms   102 ms   101 ms  te0-0-0-3.mpd21.iah01.atlas.cogentco.com [154.54.2.205]
10   133 ms   192 ms   152 ms  te0-2-0-5.mpd21.lax01.atlas.cogentco.com [154.54.0.141]
11   210 ms   204 ms   197 ms  te9-4.mpd01.lax06.atlas.cogentco.com [154.54.26.202]
12   218 ms   204 ms   204 ms  NexonNXGames.demarc.cogentco.com [38.104.76.142]
13     *        *        *     Request timed out.

Not sure what to make of that.


Here's another from the colo I use which also doesn't work. (kimsufi.com hosts it, 46.105.x.x block)

Code:

traceroute to www.nexon.net (63.251.217.189), 30 hops max, 60 byte packets
1  vss-5b-6k.fr.eu (46.105.103.252)  107.870 ms * *
2  rbx-g1-a9.fr.eu (178.33.100.49)  1.054 ms  1.408 ms  1.415 ms
3  ldn-1-6k.uk.eu (213.251.130.74)  4.331 ms * *
4  gblx.as3549.uk.eu (94.23.122.77)  138.251 ms  137.990 ms  137.996 ms
5  ae5-20g.scr4.lon3.gblx.net (67.16.133.129)  4.264 ms  4.275 ms  4.273 ms
6  lag2.ar9.LON3.gblx.net (67.17.106.149)  4.276 ms  4.224 ms  9.443 ms
7  level3-2.ar9.lon3.gblx.net (208.50.13.194)  4.432 ms xe-4-2-0.edge3.london1.level3.net (4.68.62.245)  4.278 ms level3-2.ar9.lon3.gblx.net (208.50.13.194)  4.284 ms
8  ae-52-52.csw2.London1.Level3.net (4.69.139.120)  4.549 ms  4.539 ms  4.524 ms
9  ae-59-224.ebr2.London1.Level3.net (4.69.153.141)  4.428 ms ae-57-222.ebr2.London1.Level3.net (4.69.153.133)  4.593 ms ae-58-223.ebr2.London1.Level3.net (4.69.153.137)  5.083 ms
10  ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70)  107.396 ms  107.192 ms  107.182 ms
11  ae-71-71.csw2.NewYork1.Level3.net (4.69.134.70)  92.412 ms ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66)  115.294 ms  114.826 ms
12  ae-72-72.ebr2.NewYork1.Level3.net (4.69.148.37)  106.518 ms ae-92-92.ebr2.NewYork1.Level3.net (4.69.148.45)  106.637 ms ae-82-82.ebr2.NewYork1.Level3.net (4.69.148.41)  106.880 ms
13  ae-2-2.ebr4.SanJose1.Level3.net (4.69.135.185)  154.693 ms  154.941 ms  154.633 ms
14  ae-2-2.ebr3.LosAngeles1.Level3.net (4.69.132.10)  150.236 ms  150.233 ms  150.214 ms
15  ae-63-63.csw1.LosAngeles1.Level3.net (4.69.137.34)  149.180 ms  149.157 ms  149.104 ms
16  ae-41-90.car1.LosAngeles1.Level3.net (4.69.144.195)  154.263 ms ae-21-70.car1.LosAngeles1.Level3.net (4.69.144.67)  149.411 ms ae-31-80.car1.LosAngeles1.Level3.net (4.69.144.131)  155.058 ms
17  NEXON-AMERI.car1.LosAngeles1.Level3.net (4.59.56.186)  157.998 ms  158.269 ms  158.376 ms
18  * * *
19  * * *
20  * * *
21  * * *

Interesting. I don't see any address like that in my tracert at all (and I connect just fine).
I get a whole bunch of ...LosAngeles1.Level3.net hosts, and then this
NEXON-AMERI.car1.LosAngeles1.Level3.net (4.59.56.186)

(a lot of hops after that, but none of them return tracert info)

Hmm let me post my full tracert then, I'm curious about yours!

Code:

1     1 ms    <1 ms    <1 ms  192.168.0.1
  2    23 ms    22 ms    21 ms  ip1-176-173-82.adsl2.static.versatel.nl [82.173.176.1]
  3    24 ms    22 ms    30 ms  ge-0-1-0-1404.ncr01asd2.versatel.net [217.16.44.201]
  4    23 ms    23 ms    58 ms  xe-1-0-0-668.br04sara.versatel.net [212.53.18.26]
  5    26 ms    26 ms    27 ms  ams-core-1.tengige0-11-0-0.tele2.net [130.244.21.85]
  6    24 ms    25 ms    25 ms  te2-2.ccr01.ams05.atlas.cogentco.com [130.117.14.25]
  7    24 ms    25 ms    24 ms  te0-3-0-6.ccr21.ams03.atlas.cogentco.com [130.117.1.81]
  8   113 ms   114 ms   113 ms  te0-3-0-0.ccr21.lon13.atlas.cogentco.com [130.117.48.141]
  9   109 ms   108 ms   108 ms  te0-0-0-4.ccr21.bos01.atlas.cogentco.com [154.54.5.161]
10   115 ms   116 ms   116 ms  te0-2-0-1.mpd22.jfk02.atlas.cogentco.com [154.54.44.21]
11   116 ms   116 ms   115 ms  te0-1-0-7.mpd22.dca01.atlas.cogentco.com [154.54.1.141]
12   140 ms   140 ms   139 ms  te0-3-0-7.mpd22.atl01.atlas.cogentco.com [154.54.27.98]
13   141 ms   141 ms   141 ms  te0-2-0-7.mpd22.iah01.atlas.cogentco.com [154.54.42.221]
14   178 ms   176 ms   176 ms  te0-1-0-6.mpd22.lax01.atlas.cogentco.com [154.54.0.245]
15   271 ms   212 ms   210 ms  te8-2.mpd01.lax06.atlas.cogentco.com [154.54.26.206]
16   178 ms   178 ms   178 ms  NexonNXGames.demarc.cogentco.com [38.104.76.142]
17     *        *        *     Time-out bij opdracht.

Interesting. I don't see any address like that in my tracert at all (and I connect just fine).
I get a whole bunch of ...LosAngeles1.Level3.net hosts, and then this
NEXON-AMERI.car1.LosAngeles1.Level3.net (4.59.56.186)

(a lot of hops after that, but none of them return tracert info)

What do you get after that line?

Well....i downloaded Hotspot to try.
It let me go on the gamelauncher. So i put in my information and i get the "trouble logging in?" pop up.
I go on the site and itsays my account has been deactivated. It refuses to let me change my profile information and it doesnt give me the verification code to reactivate my account. I tried every email i could w/ no success.
So i uninstalled hotspot and i cannot get to the login screen or the site now.
Why is my account deactivated? =__=

I read somewhere that using hotspot causes your account to be deactivated, since if you use hotspot then you're obviously a hacker. Naturally I read that after I tried using it. I've never been deactivated before so I don't know what is involved in getting reactivated. Hopefully not that horrible email to billing business.

RE: above
last line for tracert for me is also:
NexonNXGames.demarc.cogentco.com
after that just has 'request timed out'

Code:

Tracing route to maplestory.nexon.net [63.251.217.159]

over a maximum of 30 hops:



  1     1 ms    <1 ms     1 ms  192.168.2.1
  2    doesn't
  3    matter
  4    14 ms    14 ms    14 ms  212.199.21.46.forward.012.net.il [212.199.21.46]
  5     *        *       16 ms  BRDR-PT-ae0-2091.ip4.012.net.il [212.199.73.105]
  6    92 ms    96 ms    92 ms  EDGE-LON-MX-01-so-2-0-0-0.ip4.012.net.il [80.179.165.154]
  7    83 ms    81 ms    84 ms  77.67.61.65
  8   155 ms   158 ms   151 ms  xe-4-2-0.nyc32.ip4.tinet.net [213.200.81.253]
  9     *      151 ms     *     Te-3-4.car3.NewYork1.Level3.net [4.68.110.77]
10   168 ms   166 ms   162 ms  vlan90.csw4.NewYork1.Level3.net [4.69.155.254]
11   161 ms   160 ms   161 ms  ae-92-92.ebr2.NewYork1.Level3.net [4.69.148.45]
12   232 ms   229 ms   235 ms  ae-2-2.ebr4.SanJose1.Level3.net [4.69.135.185]
13   231 ms   236 ms   234 ms  ae-2-2.ebr3.LosAngeles1.Level3.net [4.69.132.10]
14   239 ms   244 ms   247 ms  ae-73-73.csw2.LosAngeles1.Level3.net [4.69.137.38]
15   258 ms   238 ms   236 ms  ae-21-70.car1.LosAngeles1.Level3.net [4.69.144.67]
16   243 ms   241 ms   240 ms  NEXON-AMERI.car1.LosAngeles1.Level3.net [4.59.56.186]
17     *        *        *     Request timed out.

After this I get another 13 lines of " * * * Request timed out". I do connect tho.

I read somewhere that using hotspot causes your account to be deactivated, since if you use hotspot then you're obviously a hacker. Naturally I read that after I tried using it. I've never been deactivated before so I don't know what is involved in getting reactivated. Hopefully not that horrible email to billing business.

.....well then. I had no idea.
Well ths is great. What am i supposed to do now?
Whats email to billing?

Well, on the bright side:

This may be preventing some hackers from doing their thing

Locked out as well, my ISP is TELUS. I contacted tech support and they were not much help. Apparently they seem to be able to access nexon.net from their office but had no idea why I could not from my home. I did all the usual fixits that have been mentioned here with no good results.
A thought: I was in Golden Temple when I got dc'd Friday night. I have a guildee who was blocked from her account for two days last week after dc'ing from Escape pq.

I'm blocked out as well, living in Louisiana with Cox as my ISP. Nexon seems to be having lots of regional problems with some games lately, such as on DFO I got switched to being a western US player after a major update at the same time as the Chaos patches started and a few weeks ago, I was moved back to being an eastern player. Also a few weeks ago, I was blocked from DFO for being out of region, but that was fixed by using the top-right play button which can't be accessed if we can't even access the website...

Website is working fine on Rogers in Toronto.

Edit: normal but with lag spikes

dat yellow...

Wonder if this means all the people who were blocked suddenly connected at once.

Wonder if this means all the people who were blocked suddenly connected at once.

Na, it is still blocked.

Yay for compounded suckage.

Locked out as well, my ISP is TELUS. I contacted tech support and they were not much help. Apparently they seem to be able to access nexon.net from their office but had no idea why I could not from my home. I did all the usual fixits that have been mentioned here with no good results.
A thought: I was in Golden Temple when I got dc'd Friday night. I have a guildee who was blocked from her account for two days last week after dc'ing from Escape pq.

Howdy - I also have Telus as an ISP.
Unfortunately their 'help' desk is in Philippines.
So Im guessing that when they told you they could access the site, it was from there & not Canada.
Just a guess but could be very likely.
Anyways, (no offense to ppl in Philippines), but EVERY
time I call Telus for ANYTHING, I immediately ask them where the call was routed to. Then I politely ask them to connect me to someone in Canada.
ofc they will tell you "we can help you just as well",
but from personal experience Ive found that when dealing with any sort of call center, the closer you can be to the person on the other end of the phone,
the better results you get. I theory is they care more when its someone from their own part of the world, than some random person 13 time zones removed.
When / If you are able to get ahold of someone (actually skilled) - ask them to do a tracert also.
Assume that the 1st person you speak to is just a phone answer'r & ask to be connected to someone in their 'technical / internet' dept. If they still insist that they are able to get to the site & claim to be 'tech-savvy', then come back with: "How many hops did you get on your Trace Route?" If they stumble on that, then ask again to be connected to someone who can answer that question lol.
Fortunately for myself, I only recently aquired Telus for my ISP, but I still have Shaw connected also.
Ive been able to play (until about 5 mins ago) when the ever so dependable Nexon servers flatlined.
PS> Apologies for Wall'oText = ^0

Got this on the official basil thread

Generally if it's such a large scale issue with specific ISP's it's most likely not an IP issue.
In this case, as it includes the website which is not generally something Nexon blocks like that it's indeed looking like a node issue.

It's rare to happen, but nodes between various servers can fail, and when they do users end up not being able to connect to specific servers that normally follow such paths. Proxies tend to take different pathways, and would be why it works. Usually these tend to target specific ISP's only and resolve in a day or so.