2-19-14 Connection issues  (Read 1606 times)

0 Members and 1 Guest are viewing this topic.

GaimMode

2-19-14 Connection issues
« on: 20 Feb 2014, 00:37:08 »
Anyone else having issues with connecting to the server tonight?  Not sure if it's an East Coast US thing or what.

sombrerodude

Re: 2-19-14 Connection issues
« Reply #1 on: 20 Feb 2014, 00:39:25 »
I believe that is an ongoing issue they have been talking about here http://www.noobscraft.com/server-issues/server-down-for-me-anyone-else/

lukestar04

Re: 2-19-14 Connection issues
« Reply #2 on: 20 Feb 2014, 00:39:58 »
Its only down for Comcast users

GaimMode

Re: 2-19-14 Connection issues
« Reply #3 on: 20 Feb 2014, 01:12:30 »
Another reason why I hate Comcast.  Ugh!   >:( -- I think it's something on this servers end because all the rest of the servers are up and running. 
« Last Edit: 20 Feb 2014, 01:21:01 by GaimMode »

icebox3d

Re: 2-19-14 Connection issues
« Reply #4 on: 20 Feb 2014, 02:42:58 »
I thought I would chime in here just because I can :)

The issue is with Comcast and only Comcast, I have tested from around the world and only people on Comcast have this issue.

Here is a traceroute (hope you understand it) from a Comcast based system.

Tracing the route to ***** (108.60.135.*)

  1 te-1-4-0-6-102-cr01.newyork.ny.ibone.comcast.net (66.208.229.6) 52 msec 48 msec 48 msec
  2 23.30.206.166 48 msec 48 msec 48 msec
  3 po7-20G.ar4.CHI2.gblx.net (67.16.142.249) [AS 3549] 48 msec
    po6-20G.ar4.CHI2.gblx.net (67.16.148.166) [AS 3549] 48 msec 48 msec
  4 208.178.62.50 [AS 3549] 52 msec 76 msec 52 msec
  5  *  *  *
  6  *  *  *

basically the first hop is the comcast system and then it goes all the way to Chicago, why I don't know not their sysadmin but that makes no sense as the box is in CHI, then it bounces between two switches and drops.

Here is a traceroute from Time Warner which isn't even a bandwidth provider in NY just like Comcast....but.... it works :)

traceroute to 108.60.135.* (108.60.135.*), 30 hops max, 40 byte packets
 1  66-195-95-173.static.twtelecom.net (66.195.95.173)  0.697 ms  0.637 ms  0.580 ms
 2  den2-ar3-xe-1-0-0-0.us.twtelecom.net (66.192.241.118)  1.453 ms den2-ar4-xe-1-0-0-0.us.twtelecom.net (66.192.241.114)  1.362 ms  51.945 ms
 3  dal2-pr2-xe-0-3-0-0.us.twtelecom.net (66.192.241.70)  16.497 ms  16.566 ms  16.757 ms
 4  xe-0.equinix.dllstx09.us.bb.gin.ntt.net (206.223.118.12)  17.464 ms  18.023 ms  17.319 ms
 5  ae-6.r21.dllstx09.us.bb.gin.ntt.net (129.250.3.80) [AS  2914]  17.294 ms  17.039 ms  17.555 ms
     MPLS Label=770962 CoS=0 TTL=1 S=1
 6  ae-4.r21.chcgil09.us.bb.gin.ntt.net (129.250.2.201) [AS  2914]  35.880 ms  32.096 ms  39.989 ms
     MPLS Label=299792 CoS=0 TTL=1 S=1
 7  ae-2.r06.chcgil09.us.bb.gin.ntt.net (129.250.4.202) [AS  2914]  55.962 ms  38.477 ms  32.363 ms
 8  ge-0-7-0-3-51.r06.chcgil09.us.ce.gin.ntt.net (128.242.180.146) [AS  2914]  32.051 ms  39.514 ms  32.317 ms
 9  ve769.cr1.lga3.amcbb.net (69.9.33.137) [AS  29838]  63.247 ms  74.281 ms  56.999 ms
10  ve7.cr1.lga7.amcbb.net (108.60.128.70) [AS  29838]  58.301 ms  54.418 ms  56.891 ms
11 ****** (108.60.135.*) [AS  29838]  54.739 ms  57.994 ms  57.032 ms


The issue is between Level3/Global Crossing and Comcast far outside of what is used in NY for direct upstream which currently it is Atlantic Metro, its being worked on but has to go via the correct channels

Jackmwoodall14

Re: 2-19-14 Connection issues
« Reply #5 on: 23 Feb 2014, 02:18:02 »