View Full Version : Bye bye NC?
Cant even connect to the launcher..
Anyone else have similar problems?
Yerp, she's dead in the water captain, I told ya not to push her but ya wouldney listen!
Serious_Sam
22-07-07, 09:50
Oh yea, there's a problem alright.
true. no connection. should be back in a few.
...
same here - was great - I was writing on my last Recordable Disc - guess its of no use now - thanks a lot *sigh*
...
Ru-Just-RU
22-07-07, 10:21
same problemm - no connection
Hell-demon
22-07-07, 10:22
They're getting a new hamster...
patience :rolleyes:
I reckon they grow hamsters in fields like the ones in the matrix, and they genetically enhance them too. And they have different ones for different situations. Like when they have the MoTU Niddy turns to Hoder and says "fetch Goliath! And bring David too with his little slingshot, it'll keep him going longer!"
They're getting a new hamster...
patience :rolleyes:
lol.
so no KK reaction ? announcement ? hello ?
Oh, I thought it was a problem with me...well now I feel better.
Hamster was old... It powered NC Beta 1 - NC 2.2....no wonder it died.
Seraphin[69]
22-07-07, 11:11
I wonder why KK isn't informed when the server is going down like that...
Paid service should always be up lol
']I wonder why KK isn't informed when the server is going down like that...
Paid service should always be up lol
riiiiiiiite :)) you're not used yet to KK's professionalism ? :)))))
']I wonder why KK isn't informed when the server is going down like that...
Paid service should always be up lol
mrtrip@*:~/.wine/drive_c/Program Files/Neocron2/ini$ traceroute 62.140.29.50
traceroute to 62.140.29.50 (62.140.29.50), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 0.221 ms 0.200 ms 0.161 ms
2 r74-192-239-1.tyrdcmta02.tylrtx.tl.dh.suddenlink.net (74.192.239.1) 9.856 ms 8.628 ms 7.930 ms
3 tyrmsysc01-gex010002.ma.dl.suddenlink.net (66.76.109.245) 14.479 ms 7.629 ms 10.590 ms
4 cdm-66-76-109-229.tylrtx.suddenlink.net (66.76.109.229) 10.224 ms 12.038 ms 8.526 ms
5 tyrmcrs01.tylrtx.suddenlink.net (66.76.30.17) 14.986 ms 23.550 ms 10.488 ms
6 * * *
7 ae-2-52.bbr2.Dallas1.Level3.net (4.68.122.33) 18.163 ms 12.570 ms ae-2-56.bbr2.Dallas1.Level3.net (4.68.122.161) 14.043 ms
8 ae-1-0.bbr2.Dusseldorf1.Level3.net (212.187.128.21) 137.945 ms 138.164 ms 136.727 ms
9 as-0-0.mp2.Hamburg1.Level3.net (4.68.128.30) 143.658 ms 160.260 ms as-0-0.mp1.Hamburg1.Level3.net (4.68.128.34) 152.952 ms
10 ge-5-1.hsa1.Hamburg1.Level3.net (195.122.140.179) 144.873 ms ge-4-2.hsa1.Hamburg1.Level3.net (195.122.140.195) 147.285 ms 144.452 ms
11 ge-3-0.edge1.ham1.de.inetbone.net (212.162.48.132) 149.466 ms 144.426 ms 142.891 ms
12 * * *
13 * * *
14 * * *
BORKED!
HANG INETBONE!...or whoever comes after.
And fucking fix
8 ae-1-0.bbr2.Dusseldorf1.Level3.net (212.187.128.21) 139.677 ms 145.951 ms 138.095 ms
Holy shit, thats where all my lag starts.
I'm calling Level3.
I don't blame Reakktor for isp problems.
screw inet or whatever. any serious company even if they sell freakin sox not online games, have a backup connection.
[code]
And fucking fix
8 ae-1-0.bbr2.Dusseldorf1.Level3.net (212.187.128.21) 139.677 ms 145.951 ms 138.095 ms
Holy shit, thats where all my lag starts.
I'm calling Level3.
That's one of their connections from the United States to overseas. Not much Level 3, or anyone can do about that.
That's one of their connections from the United States to overseas. Not much Level 3, or anyone can do about that.
I demand they put more hamsters on that line.
http://forum.neocron.com/announcement.php?f=2&announcementid=369
Nymphette79
22-07-07, 11:26
A courtesy "We are aware of the problem and are doing all we can to resolve it" from KK would be nice, its been down a while now.
Nymphette79
22-07-07, 11:26
See what the power of wishful thinking can do ^^
http://forum.neocron.com/announcement.php?f=2&announcementid=369
H.I.O.B..........................=O
Looks like multiple routers are out, or a core router is out.
Doing trace routers from different routers from the U.S., Europe, and Germany It doesn't seem that Level 3 is the problem. The data is being transferred off the Level 3 Network fine.
8 ae-0-54.bbr2.London2.Level3.net (4.68.117.98) [AS 3356] 200 msec 204 msec 200 msec
9 as-0-0.mp1.Hamburg1.Level3.net (4.68.128.34) [AS 3356] 200 msec 200 msec
as-0-0.mp2.Hamburg1.Level3.net (4.68.128.30) [AS 3356] 200 msec
10 ge-5-1.hsa1.Hamburg1.Level3.net (195.122.140.179) [AS 3356] 204 msec
ge-4-2.hsa1.Hamburg1.Level3.net (195.122.140.195) [AS 3356] 48 msec 52 msec
11 ge-3-0.edge1.ham1.de.inetbone.net (212.162.48.132) [AS 3356] 48 msec 52 msec 48 msec
12 * * *
The AS #s are matching up on all of them, which means their edge network is fine. I think Level 3 isn't to blame on this one.
That, or their routing table is fubared
BGP routing table entry for 62.140.0.0/19, version 34917104
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
5400 3356, (aggregated by 3356 4.69.130.74)
212.49.128.35 (metric 210944) from 212.49.128.36 (212.49.128.36)
Origin IGP, metric 0, localpref 100, valid, internal, atomic-aggregate, best
Originator: 212.49.128.35, Cluster list: 212.49.128.36
Ru-Just-RU
22-07-07, 11:44
H.I.O.B..........................=O
Any chance H.I.O.B. could get out from Game world and start sboutageing LVL3 ? :D
btw, i hate this hacker: he talk (write) too much, but dosen`t do nothing realy scared......
Yeah this is quite weird, it also goes through fine for me as well until it hits the router KK's server is connected to.
Level3 is a Tier1 provider so I doubt it's them.
Traceroute from my machine in Amsterdam:
[root@server ~]# traceroute 62.140.29.49
traceroute to 62.140.29.49 (62.140.29.49), 30 hops max, 38 byte packets
1 193.138.204.1 (193.138.204.1) 0.183 ms 0.126 ms 0.110 ms
2 64.209.106.73 (64.209.106.73) 4.040 ms 1.847 ms 0.647 ms
3 te1-2-10g.ar2.AMS1.gblx.net (67.17.108.170) 0.394 ms 0.392 ms 0.364 ms
4 ge-6-17.car1.Amsterdam1.Level3.net (213.244.165.237) 0.516 ms 0.494 ms 0.486 ms
5 ae-0-53.mp1.Amsterdam1.Level3.net (4.68.120.65) 41.658 ms 0.681 ms ae-0-55.mp1.Amsterdam1.Level3.net (4.68.120.129) 24.310 ms
6 as-0-0.mp1.Hamburg1.Level3.net (4.68.128.34) 16.174 ms as-0-0.mp2.Hamburg1.Level3.net (4.68.128.30) 28.655 ms 16.126 ms
7 ge-5-2.hsa1.Hamburg1.Level3.net (195.122.140.203) 16.437 ms ge-4-1.hsa1.Hamburg1.Level3.net (195.122.140.163) 16.718 ms ge-4-2.hsa1.Hamburg1.Level3.net (195.122.140.195) 16.316 ms
8 ge-3-0.edge1.ham1.de.inetbone.net (212.162.48.132) 16.319 ms 16.394 ms 16.270 ms
9 * * *
Hell-demon
22-07-07, 11:55
It's a sunday, pet stores are usually closed on a sunday :rolleyes:
It's not L3.
Here is a traceroute from one of "iNetBone's" routers.
traceroute to 62.140.29.50 (62.140.29.50), 64 hops max, 40 byte packets
1 ge-7-0.1247.edge2.dus1.de.inetbone.net (213.203.192.9) [AS25074] 2 ms 1 ms 2 ms
2 ge-1-0.edge1.ham1.de.inetbone.net (213.203.213.66) [AS25074] 5 ms 5 ms 5 ms
3 * * *
It's one of their core routers that's out. The way the routes are displaying while looking at BGP records, it's the only logical explination. Especailly since the Router/Network ID's (AS #s) are different, apparently the router they converge into is out.
any idea if KK filters ICMP ? wonder if it's worth to ping -t 62.140.29.50 waitin for a reply
It's back up :)
route-server>traceroute 62.140.29.50
Type escape sequence to abort.
Tracing the route to 62.140.29.50
1 white-dwarf.cbbtier3.att.net (12.0.1.1) [AS 7018] 0 msec 0 msec 0 msec
2 ar13.s10-0-0.n54ny.ip.att.net (12.124.182.17) [AS 7018] 4 msec 0 msec 4 msec
3 tbr1.n54ny.ip.att.net (12.123.0.42) [AS 7018] [MPLS: Label 31292 Exp 0] 4 ms
ec 4 msec 4 msec
4 ggr2.n54ny.ip.att.net (12.123.3.105) [AS 7018] 4 msec 0 msec 4 msec
5 192.205.33.94 [AS 7018] 4 msec 4 msec 4 msec
6 ge-1-3-0-79.bbr2.NewYork1.Level3.net (4.68.16.66) [AS 3356] 0 msec 4 msec 4
msec
7 as-1-0.bbr2.Dusseldorf1.Level3.net (4.68.128.214) [AS 3356] 76 msec 76 msec
80 msec
8 as-0-0.mp1.Hamburg1.Level3.net (4.68.128.34) [AS 3356] 84 msec
as-0-0.mp2.Hamburg1.Level3.net (4.68.128.30) [AS 3356] 84 msec
as-0-0.mp1.Hamburg1.Level3.net (4.68.128.34) [AS 3356] 84 msec
9 ge-5-2.hsa1.Hamburg1.Level3.net (195.122.140.203) [AS 3356] 84 msec
ge-4-1.hsa1.Hamburg1.Level3.net (195.122.140.163) [AS 3356] 84 msec 84 msec
10 ge-3-0.edge1.ham1.de.inetbone.net (212.162.48.132) [AS 3356] 84 msec 84 msec
84 msec
11 212.162.3.84 [AS 3356] 84 msec 84 msec 80 msec
12 62.140.29.50 [AS 3356] 80 msec 84 msec 84 msec
route-server>
It's not L3.
It's one of their core routers that's out. The way the routes are displaying while looking at BGP records, it's the only logical explination. Especailly since the Router/Network ID's (AS #s) are different, apparently the router they converge into is out.
Yeah figured as much, they don't seem to be doing very well on that.
They need to hurry up so I can actually subscribe to Neocron again!
It's back up :)
Indeed, it's up with 19ms ping for me. :)
Any chance H.I.O.B. could get out from Game world and start sboutageing LVL3 ? :D
Didn't Star Trek do that already?
Neocron is back, you can login
/close
Hell-demon
22-07-07, 11:59
Meanwhile at KK offices...
KKstaff1: Sheizer unt server haz died! Nein more neocron... :(
KKstaff2: Vait! little Suzie down ze road has gut new hamster!
KKstaff1: To little Suzie's haus!
Powered by vBulletin® Version 4.2.3 Copyright © 2024 vBulletin Solutions, Inc. All rights reserved.