Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Neox

Member
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Neox

Profile Information

  • Primary GC Server
    CS:GO
  • Secondary GC Server
    NA
  • Gender
    Male
  1. Neox

    Saturday Night Customs Prize Night February 7, 2012

    Cheers guys, was a fun night full of suspense at what the prize winning stipulation was going to be. Somehow I lucked out and grabbed this bad boy right here:
  2. Sup guys, I've been having an issue and I'm sure it's affecting others as well. One of the routers before the server (on my route at least) goes haywire dropping over 100ms between two routers along the way shortly before reaching the server. Tracing route to c-74-91-124-246.managed-vds.internap-chicago.nfoservers.com [74 .91.124.246] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1] 2 * * * Request timed out. 3 * * * Request timed out. 4 1 ms 1 ms 1 ms floyd-edge1.swva.net [66.37.64.153] 5 19 ms 10 ms 14 ms 10ge13-4.core1.ash1.he.net [209.51.161.113] 6 9 ms 9 ms 9 ms 206.111.7.93.ptr.us.xo.net [206.111.7.93] 7 16 ms 19 ms 15 ms 207.88.14.170.ptr.us.xo.net [207.88.14.170] 8 31 ms 32 ms 31 ms 207.88.14.62.ptr.us.xo.net [207.88.14.62] 9 159 ms 161 ms 164 ms 207.88.184.146.ptr.us.xo.net [207.88.184.146] 10 162 ms 164 ms 164 ms border10.po2-bbnet2.chg.pnap.net [64.94.32.87] 11 159 ms 154 ms * c-74-91-124-246.managed-vds.internap-chicago.nfo servers.com [74.91.124.246] 12 157 ms 162 ms 162 ms c-74-91-124-246.managed-vds.internap-chicago.nfo servers.com [74.91.124.246] It's pretty random when it occurs, but tonight it's been happening since I've been connected, hour or so. I'll try to post a trace when my ping returns to normal so you can see the difference, could be a different route for all I know.
  3. Neox

    Results are in Your adds and drops

    de_cbble needs more people to vote for it. I haven't seen it played yet.
  4. Neox

    CEVO/Gamebanana Mapping contest 2014

    Yea, all those top maps definitely are some eye candy from what I see. If canyon was polished up to GO engine standards it would be sitting with the rest of them right now. Keep at it turn.
  5. Neox

    !!!!!!Ban requests!!!!!!

    # 198 13 "PimpDaddyJuan#bebackonda25th" STEAM_1:0:43263573 27:42 56 0 active 128000 # 145 7 "Buster" STEAM_1:1:93408 1:30:37 62 0 active 128000 # 218 3 "swayz-" STEAM_1:1:8406839 14:00 70 0 active 128000 These three, in CS:GO TKing everyone for the past two maps. Edit, demo attached GCTKers_5_31.zip
  6. Neox

    !!!!!!Ban requests!!!!!!

    Can agree with Buster, just started team killing on Dust2, few others in here that are also doing it. http://imgur.com/sDP2sRX http://imgur.com/ak7uLA0
  7. Neox

    High ping during primetime

    Here's one from last night at 11:30 Tracing route to c-74-91-124-246.managed-vds.internap-chicago.nfoservers.com [74 .91.124.246] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1] 2 17 ms 18 ms 24 ms 173.212.35.1 3 17 ms 16 ms 16 ms 10.200.0.10 4 16 ms 16 ms 17 ms 173-212-38-194.cpe.surry.net [173.212.38.194] 5 22 ms 21 ms 25 ms 204.116.77.13 6 46 ms 22 ms 22 ms cha-b1-link.telia.net [213.248.68.1] 7 29 ms 29 ms 29 ms ash-bb3-link.telia.net [62.115.138.42] 8 90 ms 35 ms 35 ms nyk-bb1-link.telia.net [213.155.134.126] 9 65 ms 65 ms 65 ms chi-bb1-link.telia.net [80.91.246.166] 10 55 ms 59 ms 56 ms internap-ic-150762-chi-bb1.c.telia.net [213.248. 81.142] 11 53 ms 55 ms 53 ms border11.po2-bbnet2.chg.pnap.net [64.94.32.88] 12 53 ms 53 ms 52 ms c-74-91-124-246.managed-vds.internap-chicago.nfo servers.com [74.91.124.246] And one more from just now Tracing route to c-74-91-124-246.managed-vds.internap-chicago.nfoservers.com [74 .91.124.246] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1] 2 18 ms 25 ms 25 ms 173.212.35.1 3 16 ms 17 ms 16 ms 10.200.0.10 4 16 ms 16 ms 16 ms 173-212-38-194.cpe.surry.net [173.212.38.194] 5 22 ms 22 ms 24 ms 204.116.77.13 6 22 ms 22 ms 21 ms cha-b1-link.telia.net [213.248.68.1] 7 29 ms 29 ms 29 ms ash-bb3-link.telia.net [62.115.138.42] 8 35 ms 35 ms 35 ms nyk-bb1-link.telia.net [213.155.134.126] 9 75 ms 66 ms 65 ms chi-bb1-link.telia.net [80.91.246.166] 10 55 ms 56 ms 55 ms internap-ic-150762-chi-bb1.c.telia.net [213.248. 81.142] 11 53 ms 53 ms 53 ms border11.po2-bbnet2.chg.pnap.net [64.94.32.88] 12 54 ms 53 ms 52 ms c-74-91-124-246.managed-vds.internap-chicago.nfo servers.com [74.91.124.246] Let me know if you need some more info, I could use PingPlotter or WinMTR to monitor it for a day or two.
  8. Neox

    High ping during primetime

    The ping dropped to normal just after 11:00 last night. Have another traceroute at the house showing that its routing through the exact same path. I'm in NC here as well Turnbull, hoping to get some fiber here shortly as my local telco has been laying a bunch of it down over the past six months. Fiber would only help marginally on my second hop of my previous traceroute. Those routers around chicago may be overloaded with traffic. Can anyone else who isn't having an issue post a traceroute to the server at night? Just to see if you hit the same routers going in to the server.
  9. Has anyone else been noticing high ping during prime time? 1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1] 2 21 ms 26 ms 23 ms 3 17 ms 16 ms 16 ms 4 17 ms 18 ms 19 ms 5 47 ms 23 ms 22 ms 204.116.77.13 6 22 ms 46 ms 22 ms cha-b1-link.telia.net [213.248.68.1] 7 32 ms 31 ms 30 ms ash-bb3-link.telia.net [62.115.138.42] 8 51 ms 47 ms 86 ms nyk-bb1-link.telia.net [213.155.134.126] 9 67 ms 67 ms 66 ms chi-bb1-link.telia.net [80.91.246.166] 10 154 ms 212 ms 163 ms internap-ic-150762-chi-bb1.c.telia.net [213.248. 81.142] 11 169 ms 165 ms 164 ms border11.po2-bbnet2.chg.pnap.net [64.94.32.88] 12 172 ms 177 ms 178 ms c-74-91-124-246.managed-vds.internap-chicago.nfo servers.com [74.91.124.246] My net is usually pretty okay for being in the back end of forever. Looks like I'm gaining 100ms of ping just between two hops in Chicago. Super annoying, I'll try to post a traceroute when my ping goes back down to normal to see if it's taking the same route. Definitely could be something up with the router if so.
×