Server boru down ????

[bdistler]

Server boru has been more down then up today
but now is down

All time is MST/AZ (-7:00 GMT)

Ping gets us - 13:11 PM
==>
Packets transmitted: 5
Packets received: 0
Successful packets: 0%
<==

Traceroute gets us - 13:14 PM
==>
-=> cut first hop <=-
2 c-3-0-ubr02.orovalley.az.pima.comcast.net 73.109.24.1 10.277ms
3 no reply *
4 no reply *
5 te-1-2-0-4-cr01.losangeles.ca.ibone.comcast.net 68.86.91.37 21.133ms
6 TenGigabitEthernet4-3.ar4.LAX2.gblx.net 64.214.145.53 21.924ms
7 xe-2-0-5.ar2.ord1.us.nlayer.net 69.31.111.222 90.511ms
8 ae2-30g.cr2.ord1.us.nlayer.net 69.31.111.149 89.592ms
9 ae1-20g.ar1.ord6.us.nlayer.net 69.31.110.250 105.693ms
10 as32475.xe-1-0-1.ar1.ord6.us.nlayer.net 69.31.111.30 92.751ms
11 no reply *
12 no reply *
-=> cut off <=-
<==

First thread today 03:07 AM
http://x10hosting.com/forums/free-hosting/147703-site-not-opening.html

Here is a thread where Anna could not get on 07:07 AM
http://x10hosting.com/forums/free-hosting/147709-problem-ftp.html

cPanel logon - both time out 13:21 PM
http://boru.x10hosting.com:2082/
https://boru.x10hosting.com:2083/

My site (domain) and FTP - both time out 13:22 PM

Any info ????

Thanks

 

[stpvoice]

Hello,

Your site and the Boru cPanel are both working fine for me at this time. Please clear your browser cache and try again.

 

[bdistler]

... Please clear your browser cache and try again.

I use ctrl+F5 to reload

14:40 PM
server was up is now down again

ping

Time minimum: 87.40 ms
Time average: 89.89 ms
Time maximum: 96.30 ms
Packets transmitted: 108
Packets received: 15
Successful packets: 13%

15 out of 108

What dose the browser cache have to do with BAD ping ????

Thanks

 

[stpvoice]

The browser cache is to eliminate variables-you said your site itself was down, too, which involves your browser.

Once again I have no issues loading your site, or the cPanel for your server.

 

[Livewire]

Leads me to believe with that traceroute that there's a connection error between you and the server - you're getting lost packets at stages 2 and 3, neither of which are anywhere near singlehop, same with where it dropped at 11 - that's not happening at the datacenter, so while the server is up, however your ISP is trying to route you to us, it's dropping out.

Honestly I'm not sure how to proceed from here, cause it's dropping -extremely- early on which is a major concern...

 

[bdistler]

@Livewire
Did you see this thread today with Anna's posts ????
http://x10hosting.com/forums/free-hosting/147709-problem-ftp.html

have you looked at all the post today about server boru ????

Yesterday I was thinking "To bad about those users on server starka"
today my server is doing the same bad things

16:36 PM my time
No successful ping packets or traceroute

Had someone who is on ISP Qwest try to bring up
cPanel logon - ports 2082 and 2083 no luck
and try to ping boru no luck

My ISP is Comcast

server boru has been up and down more down then up for me today

Thanks

 

[Livewire]

I've been reading plenty; the problem I'm having with figuring that Boru is having problems is that my scanner is reporting that out of the 4 servers, Boru actually has the most unique file hits since 11:45 when I restarted it, and prior to that it was only 1,000 shy of being in first place for the last 36 hours.


Also, One of Anna's 2 posts says this:

Looks more like a routing/network issue at this point. Seeing as you have the browser in Finnish, I guess that would place you in Finland? If so that means we're in the same general area of Internet (I'm located in Sweden).

First line is exactly what I'm suggesting this is - a routing/network issue. There's several ISP's but only a few major "backbone" systems out there, so if one of the backbones is having problems, this is what you end up with.

This also lines up somewhat with what http://www.internethealthreport.com/ is reporting - there are significant delays in many of the nodes, and in 1 node in particular it's experiencing 2% packet-loss. That generally isn't a -good- thing obviously. This also matches up with the check I did with our CEO - Boru has not actually been down all day.


That helps point to a routing problem with how your ISP is trying to get to x10hosting - that's not something we can control since it's not actually occurring on the x10hosting system. About all I can suggest for now is to use a proxy to access/administer your site, but since at least 36 hours ago Boru has been up and running steady.

 

[bdistler]

Something to think about....

I can log onto then into my "account control panel" at
https://x10hosting.com/control/login.php

But cPanel - FTP - mydomain - I can not use or get to ????

Thanks

 

[Anna]

The account panel is located on a different server, if I'm not mistaken the same one as these forums are.

Through out the day I have been able to get to the other servers without any issues, it is ONLY Boru I hit a dead end with, and that as early as the default gateway at my ISP. Boru it self is up and running properly, I can access it just fine through proxy.

 

[bdistler]

I can get to my domain via proxy

but I can not use any thing on the cPanel via proxy
like www.Kproxy.com and www.hidemyass.com

Do you have any tips on using cPanel via proxy ????

Thanks

 

[Anna]

You could try this secondary IP for access: http://69.175.121.68:2082 (ssl will give an error since the certificate isn't set for the IP).

 

[bdistler]

Below are two traceroutes one for server 'boru' the other server 'chopin'
note the trace to server 'boru' stops at the front door of x10hosting.com
at hop #10 while the one for server 'chopin' steps right on in at hop #11

I know of other ISPs that can get to other free x10 servers but NOT to 'boru'

Looking at the traceroutes
it is not my computers - firewall - ISP or network to x10hosting.com

Can you escalated this thread to someone to look at this from the backend ????

Thanks

Traceroute for network address: boru.x10hosting.com - 69.175.121.66

1 hot-box.local ***********
1 smoothwall  ***********
1 smoothwall  ***********
2 c-3-0-ubr02.orovalley.az.pima.comcast.net         73.109.24.1      8.270ms
3 no  reply *
4 no  reply *
5 te-1-2-0-4-cr01.losangeles.ca.ibone.comcast.net   68.86.91.37     22.246ms
6 TenGigabitEthernet4-3.ar4.LAX2.gblx.net           64.214.145.53   20.345ms
7 xe-2-0-5.ar2.ord1.us.nlayer.net                   69.31.111.222   90.526ms
8 ae4-52.cr1.ord1.us.nlayer.net                     69.31.111.145   89.178ms
9 ae2-20g.ar1.ord6.us.nlayer.net                    69.31.110.254  121.801ms
10  as32475.xe-2-0-4.ar1.ord6.us.nlayer.net         69.31.110.202   89.854ms
11  no  reply *
12  no  reply *
13  no  reply *
14  no  reply *
15  no  reply *
16  no  reply *
17  no  reply *
18  no  reply *
19  no  reply *
20  no  reply *
21  no  reply *
22  no  reply *
23  no  reply *
24  no  reply *
25  no  reply *
26  no  reply *
27  no  reply *
28  no  reply *
29  no  reply *
30  no  reply *
31  no  reply *


Traceroute for network address: chopin.x10hosting.com - 69.175.104.34

1 hot-box.local ***********
1 smoothwall  ***********
1 smoothwall  ***********
2 c-3-0-ubr02.orovalley.az.pima.comcast.net         73.109.24.1      9.439ms
3 no  reply *
4 no  reply *
5 te-1-2-0-4-cr01.losangeles.ca.ibone.comcast.net   68.86.91.37     22.146ms
6 TenGigabitEthernet4-2.ar4.LAX2.gblx.net           64.214.145.49   21.226ms
7 xe-2-0-5.ar2.ord1.us.nlayer.net                   69.31.111.222   90.524ms
8 ae4-52.cr1.ord1.us.nlayer.net                     69.31.111.145   89.456ms
9 ae2-20g.ar1.ord6.us.nlayer.net                    69.31.110.254  102.624ms
10  as32475.xe-2-0-4.ar1.ord6.us.nlayer.net         69.31.110.202   91.432ms
11  chopin.x10hosting.com                           69.175.104.34   92.761ms

 

[Brandon]

I believe we solved this via IRC; let me know if you need any additional support.

 

[Anna]

Hello,

Are you able to connect to boru now or is there still any problems?

 

[bdistler]

Are you able to connect to boru now or is there still any problems?

Brandon took my IP (here) off the firewall - all is well now

I know why it was on the firewall
but I do not know why this computer did what it did
to get my IP pinned to the firewall