Jump to content
IGNORED

Anyone having problems connecting?


EarthQuake

Recommended Posts

I've been having one hell of a time staying connected to AA. I keep getting network timeout errors and posting in the forums is painfully excruciating. This started happening only recently and I have no other problems with other websites.

 

Something going on with the servers or is it just me? :?

Link to comment
Share on other sites

Yeah, I can only test from this laptop at the moment, but I haven't changed any of my network configuration and it only seems to be doing this on AtariAge. I'll go to make a forum post or just visit the main page and it hangs like my internet went out. After it displays the error page, I can immediately reconnect fine, and everything is okay for a minute or so and it happens all over again. I've been browsing the internet like crazy, and I haven't experienced any problems elsewhere. :(

Link to comment
Share on other sites

This is really getting to be a pain... :mad:

 

I tried a few more things and the problem still persists. I connected directly to my router as opposed to using my wireless, and there was no change. I also try pinging the server during several episodes, and it reported a 25% packet loss each time. One time I was loading a page and it didn't fetch the stylesheet, confirming the packet loss. Not sure exactly what's going on, but from my end, it seems like something is blocking or interfering with my connection. It could be a firewall, or possibly even my ISP. I've been able to view other forums using the same software without any problems whatsoever. It's solely AtariAge which is giving me problems...

 

I really don't know what to do aside from calling my ISP and seeing what's up... :(

Link to comment
Share on other sites

Thanks for the suggestion. I did as you instructed and these were the results. The first trace is during one of the epidsodes. These are in sequential order, I assume? If that's the case, it's definitely not on my end. What does this mean in terms of solving the problem?

 

Tracing route to atariage.com [216.40.231.66]
over a maximum of 30 hops:

1  50 ms  48 ms  48 ms 10.34.37.1
2  50 ms  48 ms  48 ms so-0-3-3-0.CORE-RTR1.CHI01.verizon-gni.net [130.81.36.180]
3  52 ms  51 ms  50 ms so-7-2-0-0.BB-RTR1.CHI01.verizon-gni.net [130.81.20.56]
4  51 ms  51 ms  48 ms so-6-0-0-0.PEER-RTR1.CHI80.verizon-gni.net [130.81.16.11]
5  49 ms  48 ms  48 ms 130.81.15.166
6 101 ms 102 ms 102 ms hagg-03-ge-0-0-0-540.hsto.twtelecom.net [66.192.246.206]
7  80 ms  78 ms  77 ms et3-3.ibr01.hstntx1.theplanet.com [70.87.253.153]
8  79 ms  78 ms  80 ms po1.car01.hstntx1.theplanet.com [207.218.223.2]
9   *	  *	  *	Request timed out.
10  78 ms  77 ms  80 ms stella.atariage.net [216.40.231.66]

Trace complete.

Tracing route to atariage.com [216.40.231.66]
over a maximum of 30 hops:

1  50 ms  48 ms  51 ms 10.34.37.1
2  48 ms  48 ms  48 ms so-0-3-3-0.CORE-RTR1.CHI01.verizon-gni.net [130.81.36.180]
3  52 ms  51 ms  51 ms so-7-2-0-0.BB-RTR1.CHI01.verizon-gni.net [130.81.20.56]
4  50 ms  50 ms  48 ms so-6-0-0-0.PEER-RTR1.CHI80.verizon-gni.net [130.81.16.11]
5  48 ms  48 ms  48 ms 130.81.15.166
6 103 ms 107 ms 103 ms hagg-03-ge-0-0-0-540.hsto.twtelecom.net [66.192.246.206]
7  76 ms  78 ms  78 ms et3-3.ibr01.hstntx1.theplanet.com [70.87.253.153]
8  79 ms  78 ms  79 ms po1.car01.hstntx1.theplanet.com [207.218.223.2]
9  78 ms  77 ms  79 ms stella.atariage.net [216.40.231.66]

Trace complete.

Link to comment
Share on other sites

Thanks for verifying, pangasinan. At least it's not something I did. When and if you get a chance, can you do a trace route as I did and see what it reveals for you?

 

The problem (for me at least) seems to be somewhere between theplanet.com's servers/network and AtariAge. From reading all the angry custom feedback and threads dealing with downtime on their forums, I'm guessing the problem is there. I might consider posting there to see if I can uncover anything, but since I'm not a customer, I'm not sure they would listen to what I have to say.

Link to comment
Share on other sites

I am having the same problem,it started about 9 days ago and i keep getting timed out and the pages wont load sometimes it takes 2-3 times before a page loads,before this i never had a problem. :(

 

 

ok then its not me then!!!!! this is happening to me too. getting alittle tired of it

Link to comment
Share on other sites

I am having the same problem,it started about 9 days ago and i keep getting timed out and the pages wont load sometimes it takes 2-3 times before a page loads,before this i never had a problem. :(

 

 

ok then its not me then!!!!! this is happening to me too. getting alittle tired of it

Same here. Since about 1-2 weeks it happens quite often that a page won't load and i also have to reload a page several times before it works...

Link to comment
Share on other sites

Excellent, I was hoping people would come forward. I was almost 100% positive that it was not just me.

 

The problem lies with theplanet.com, I'm guessing is which where AtariAge is hosted. Doing a domain lookup seems to confirm this. Probably the reason why most people aren't having problems is due to their connection to the site using a different "path" of servers and networks.

 

Hopefully someone who runs the site can contact them and see if the issue can be resolved... Here's hoping though. :(

Link to comment
Share on other sites

This is happening to me as well. Sometimes a page will sit there and try to load unsuccessfully before I get a page load error screen, Then I will hit "reload" and it will come up instantly. Not sure what that could mean but as you all are, I am glad to hear that it is not just me. I am using AT&T DSL. How about you guys?

 

Chris

Link to comment
Share on other sites

Verizon DSL, here.

 

Might I suggest, Albert, if you want to get to the bottom of this sooner, you could perhaps make a front page post about it to get more information. It might even draw in more people who are experiencing the problem.

 

For those having this problem and are running Windows, you can do a trace route by going to Run in the start menu, typing in "cmd" to bring up the command prompt, and then typing "tracert atariage.com". If you do it when you're experiencing an 'outage', it should show some stars on some of servers instead of ping times. Usually for me, the stars are on the last or second to the last server listed. If you catch a full-fledged outage instead of just lost packets, it will time out on one of the servers showing 3 stars.

 

Post your results here, so Albert can help resolve the problem. :)

Link to comment
Share on other sites

Thanks for the suggestion. I did as you instructed and these were the results. The first trace is during one of the epidsodes.

What's interesting between those two is that the in first one that was failing, there was an extra hop taking place between ThePlanet & Atariage.

 

If other people can send me traceroutes, that would be useful as I can pass them onto ThePlanet. I'll also look to see if other people are complaining about this issue. Kind of strange if it's in ThePlanet's internal network and only affecting some people visiting AtariAge.

Do you want from people where it's working too? Or just when it's not?

 

Every once in a while, I have problems connecting too, but never thought to do a tracert because it only ever lasts a minute or two. Next time it does, I'll capture one.

 

Anywho, here is mine when everything is working.

Tracing route to atariage.com [216.40.231.66]

over a maximum of 30 hops:

 

1 <10 ms <10 ms <10 ms 192.168.1.1

2 6 ms 9 ms 9 ms c-98-203-88-1.hsd1.fl.comcast.net [98.203.88.1]

3 7 ms 7 ms 5 ms ge-1-4-ur02.northdade.fl.pompano.comcast.net [68.85.228.217]

4 6 ms 5 ms 6 ms po-1-ur01.northdade.fl.pompano.comcast.net [68.85.229.194]

5 8 ms 18 ms 8 ms te-9-4-ur01.davie.fl.pompano.comcast.net [68.86.164.109]

6 7 ms 7 ms 9 ms te-0-0-0-4-cr01.miami.fl.ibone.comcast.net [68.86.91.81]

7 21 ms 23 ms 21 ms pos-0-11-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.85.193]

8 42 ms 44 ms 42 ms pos-1-12-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.157]

9 45 ms 43 ms 43 ms 68.86.88.50

10 58 ms 49 ms 49 ms et1-1.ibr01.hstntx2.theplanet.com [70.87.253.50]

11 48 ms 49 ms 48 ms et3-3.ibr01.hstntx1.theplanet.com [70.87.253.153]

12 51 ms 49 ms 58 ms po1.car01.hstntx1.theplanet.com [207.218.223.2]

13 50 ms 47 ms 49 ms stella.atariage.net [216.40.231.66]

 

Trace complete.

Link to comment
Share on other sites

I went to search a thread and got a blank page, so I did a trace:

 

Tracing route to atariage.com [216.40.231.66]

over a maximum of 30 hops:

 

1 20 ms 7 ms 7 ms 10.96.128.1

2 10 ms 14 ms 9 ms gig0-3.gnboncash-ubr1.triad.rr.com [24.28.228.133]

3 9 ms 9 ms 10 ms gig2-2.gnboncash-rtr1.triad.rr.com [24.28.229.245]

4 10 ms 9 ms 12 ms srp14-0.gnboncsg-rtr1.triad.rr.com [24.28.224.193]

5 13 ms 12 ms 16 ms ge-3-1-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.178]

6 17 ms 19 ms 17 ms ae-3-0.cr0.dca10.tbone.rr.com [66.109.6.80]

7 18 ms 18 ms 30 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]

8 20 ms 22 ms 19 ms te-6-2-pr01.ashburn.va.ibone.comcast.net [68.86.88.141]

9 26 ms 37 ms 33 ms pos-0-15-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.85.69]

10 47 ms 47 ms 58 ms pos-0-15-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.149]

11 47 ms 43 ms 46 ms 68.86.88.50

12 53 ms 49 ms 53 ms et1-1.ibr01.hstntx2.theplanet.com [70.87.253.50]

13 52 ms 49 ms 50 ms et3-3.ibr01.hstntx1.theplanet.com [70.87.253.153]

14 51 ms 52 ms 51 ms po1.car01.hstntx1.theplanet.com [207.218.223.2]

15 50 ms 49 ms 51 ms stella.atariage.net [216.40.231.66]

 

Trace complete.

 

It was just a temporary thing. The problem was probably over before I did the trace.

Link to comment
Share on other sites

F:\Documents and Settings\Administrator>tracert atariage.com

Tracing route to atariage.com [216.40.231.66]
over a maximum of 30 hops:

 1	 1 ms	 1 ms	<1 ms  192.168.1.1
 2   462 ms   404 ms   456 ms  bras1-l0.scrm01.sbcglobal.net [151.164.185.12]
 3   403 ms   427 ms   459 ms  dist2-vlan60.scrm01.pbi.net [64.171.152.131]
 4   321 ms   320 ms   407 ms  151.164.93.214
 5   465 ms   345 ms   358 ms  ex2-p10-0.pxpaca.sbcglobal.net [151.164.190.83]

 6   453 ms   448 ms   437 ms  as4323-twtelecom.pxpaca.sbcglobal.net [151.164.2
48.110]
 7   391 ms   318 ms   367 ms  hagg-03-ge-0-0-0-540.hsto.twtelecom.net [66.192.
246.206]
 8   360 ms   417 ms   439 ms  et3-3.ibr01.hstntx1.theplanet.com [70.87.253.153
]
 9   285 ms   170 ms   277 ms  po1.car01.hstntx1.theplanet.com [207.218.223.2]

10   472 ms   498 ms   435 ms  stella.atariage.net [216.40.231.66]

Trace complete.

F:\Documents and Settings\Administrator>

 

I was experiencing the problem a few mins ago and this is what I got.

 

Chris

Edited by Jibbajaba
Link to comment
Share on other sites

Still occurs for me, although it tends to come and go, and certain times of the day are worse it seems. I've pretty much gotten used to it by now, although posting and editing posts are still pretty annoying.

 

JibbaJaba: Nothing unusual there, so it probably ended before you could do the trace route. I find it's best to keep the command prompt open, do a tracert, and just leave it minimized until another outage happens. That way I can just pull up the window, press up (to repeat the last command) and hit enter. Usually catches it every time.

Edited by EarthQuake
Link to comment
Share on other sites

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...