Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > SecuredServers
SecuredServers
| Posted by KnownHost-Jonathan, 07-15-2011, 12:27 AM |
|
Anyone else experiencing issues? I can access neither my server hosting there, or their corporate site. |
| Posted by MichelleH, 07-15-2011, 12:34 AM |
|
Site loads right up for me.. |
| Posted by QuickWeb-Roel, 07-15-2011, 12:35 AM |
yeah looks like massive packet losses, not all servers though... seems like becoming common these days  |
| Posted by KnownHost-Jonathan, 07-15-2011, 12:37 AM |
Yeah this is a bummer. I can't ping or load the site, I got the corp site to load up once from Hidemyass, but not Anonymouse.
Also I can't get www.phoenixnap.com either so I think it's a whole DC issue and not just SecuredServers. |
| Posted by JordanJ, 07-15-2011, 12:41 AM |
Global crossing is having network problems. The glbx peer was shut down now they are trying to figure out where the ISPs peer with them off network and route around them.
The Datacenter has had no problems. This is just a serious global crossing issue. |
| Posted by QuickWeb-Roel, 07-15-2011, 12:41 AM |
Quote:
|
Originally Posted by EHJonathan
Yeah this is a bummer. I can't ping or load the site, I got the corp site to load up once from Hidemyass, but not Anonymouse.
Also I can't get www.phoenixnap.com either so I think it's a whole DC issue and not just SecuredServers. |
phoenixnap site is loading ok here. |
| Posted by JordanJ, 07-15-2011, 12:44 AM |
|
Please email me trace routes for either site if you cannot get through please. Jordanj@phoenixnap.com. |
| Posted by QuickWeb-Roel, 07-15-2011, 12:44 AM |
Quote:
|
Originally Posted by JordanJ
Global crossing is having network problems. The glbx peer was shut down now they are trying to figure out where the ISPs peer with them off network and route around them.
The Datacenter has had no problems. This is just a serious global crossing issue.
|
seems like you are not using multiple carrier blend on some racks so there is no fail over? |
| Posted by JordanJ, 07-15-2011, 12:48 AM |
|
We are, but lots of carriers peer with glbx, that's why it is only down for a small % of people. For example it's up for me. |
| Posted by QuickWeb-Roel, 07-15-2011, 12:49 AM |
Quote:
|
Originally Posted by JordanJ
We are, but lots of carriers peer with glbx, that's why it is only down for a small % of people. For example it's up for me.
|
check this out to give you idea which locations are down http://just-ping.com/index.php?vh=securedservers.com |
| Posted by KnownHost-Jonathan, 07-15-2011, 12:51 AM |
Quote:
|
Originally Posted by JordanJ
|
Sent. It does appear to be failing on global crossing. |
| Posted by JordanJ, 07-15-2011, 12:53 AM |
|
No email from you yet, mind posting it here? |
| Posted by KnownHost-Jonathan, 07-15-2011, 12:57 AM |
Quote:
|
Originally Posted by JordanJ
No email from you yet, mind posting it here?
|
Sent from a new address. Check your spam folder from the other one, for some reason the emails from that address keep getting pegged as spam. |
| Posted by stablehost, 07-15-2011, 12:59 AM |
traceroute to (64.38.229.x), 30 hops max, 40 byte packets
1 64.22.106.73 (64.22.106.73) 0.501 ms 0.565 ms 0.592 ms
2 64.22.106.9 (64.22.106.9) 0.367 ms 0.410 ms 0.470 ms
3 atl-core-g-g1-6.gnax.net (63.247.69.178) 0.354 ms 0.369 ms 0.453 ms
4 209.118.220.45 (209.118.220.45) 0.602 ms 0.588 ms 0.606 ms
5 vb1200.rar3.atlanta-ga.us.xo.net (216.156.0.65) 3.145 ms 4.487 ms 3.108 ms
6 ae0d1.cir1.atlanta6-ga.us.xo.net (207.88.13.157) 1.043 ms 1.051 ms 1.076 ms
7 67.111.23.10.ptr.us.xo.net (67.111.23.10) 0.858 ms 0.838 ms 0.849 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * * |
| Posted by RyanD, 07-15-2011, 01:00 AM |
Quote:
|
Originally Posted by nerdie
traceroute to (64.38.229.x), 30 hops max, 40 byte packets
1 64.22.106.73 (64.22.106.73) 0.501 ms 0.565 ms 0.592 ms
2 64.22.106.9 (64.22.106.9) 0.367 ms 0.410 ms 0.470 ms
3 atl-core-g-g1-6.gnax.net (63.247.69.178) 0.354 ms 0.369 ms 0.453 ms
4 209.118.220.45 (209.118.220.45) 0.602 ms 0.588 ms 0.606 ms
5 vb1200.rar3.atlanta-ga.us.xo.net (216.156.0.65) 3.145 ms 4.487 ms 3.108 ms
6 ae0d1.cir1.atlanta6-ga.us.xo.net (207.88.13.157) 1.043 ms 1.051 ms 1.076 ms
7 67.111.23.10.ptr.us.xo.net (67.111.23.10) 0.858 ms 0.838 ms 0.849 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
|
That looks like XO sucking, not SS's fault, XO is well... XO |
| Posted by JordanJ, 07-15-2011, 01:00 AM |
|
Nothing yet, mind posting it here or via pm? |
| Posted by stablehost, 07-15-2011, 01:02 AM |
Quote:
|
Originally Posted by RyanD
That looks like XO sucking, not SS's fault, XO is well... XO
|
Ehh, it may be where Xo hands it off to GBLX -- who knows.
It just started an hour ago, right when GBLX hit the floor. |
| Posted by QuickWeb-Roel, 07-15-2011, 01:02 AM |
1 1 0 0 8.9.232.73 xe-5-3-0.edge3.dallas1.level3.net
2 0 0 0 4.69.145.141 ae-3-80.edge4.dallas3.level3.net
3 0 0 0 64.208.27.9 te2-2-10g.ar5.dal2.gblx.net
4 28 Timed out Timed out 67.16.131.114 te1-2-10g.ar6.phx1.gblx.net
5 Timed out Timed out Timed out -
6 Timed out Timed out Timed out -
7 Timed out Timed out Timed out -
8 Timed out 27 Timed out 67.16.131.114 te1-2-10g.ar6.phx1.gblx.net
9 Timed out Timed out Timed out -
10 27 27 28 67.16.131.114 te1-2-10g.ar6.phx1.gblx.net
11 Timed out 28 Timed out 67.16.131.113 te4-2-10g.ar2.phx1.gblx.net
12 Timed out Timed out Timed out -
13 Timed out Timed out Timed out - |
| Posted by JordanJ, 07-15-2011, 01:07 AM |
Quote from the NOC
I had spoken to Global Crossing a short while ago by phone and they confirmed the issues were due to a major routing issue in California. |
| Posted by IGobyTerry, 07-15-2011, 01:12 AM |
Yep, I'm dead at GLBX too.
Terrance-Myerss-MacBook-Pro:~ terrancemyers$ traceroute phoenixnap.com
traceroute to phoenixnap.com (209.188.10.25), 64 hops max, 52 byte packets
1 192.168.1.254 (192.168.1.254) 5.328 ms 1.431 ms 1.731 ms
2 99-140-84-2.lightspeed.bcvloh.sbcglobal.net (99.140.84.2) 23.074 ms 21.900 ms 22.378 ms
3 75.25.192.72 (75.25.192.72) 22.539 ms 22.893 ms 23.581 ms
4 * * *
5 * * *
6 bb1-g4-0.bcvloh.sbcglobal.net (151.164.241.134) 22.406 ms
151.164.103.236 (151.164.103.236) 22.705 ms
bb1-g4-0.bcvloh.sbcglobal.net (151.164.241.134) 22.459 ms
7 151.164.99.129 (151.164.99.129) 32.976 ms 29.925 ms 30.168 ms
8 asn3549-glbx.eqchil.sbcglobal.net (151.164.248.18) 29.824 ms 29.976 ms 29.639 ms |
| Posted by stablehost, 07-15-2011, 01:15 AM |
|
I can now reach our stuff, it's going XO -> Highwinds -> Phoenix NAP now. |
| Posted by JordanJ, 07-15-2011, 01:17 AM |
|
Can everyone try it now please? |
| Posted by KnownHost-Jonathan, 07-15-2011, 01:17 AM |
|
I'm able to get through now as well! |
| Posted by JordanJ, 07-15-2011, 01:20 AM |
|
Great! |
| Posted by MichelleH, 07-15-2011, 01:21 AM |
Quote:
|
Originally Posted by JordanJ
Great!
|
Awesome! Jordan is all over it as usual 
It never went down for me  |
| Posted by QuickWeb-Roel, 07-15-2011, 01:21 AM |
|
yeah looks ok now, about 1 hour issue. |
| Posted by arthur8, 07-15-2011, 01:21 AM |
|
Working fine now! |
| Posted by contenidosonline, 07-15-2011, 08:59 AM |
My server is down from Argentina. I have a ticket open with SS.
roberto |
| Posted by arthur8, 07-15-2011, 09:38 AM |
|
All my dedicated servers is not working more from Brasil. |
| Posted by JordanJ, 07-15-2011, 10:59 AM |
|
Please make sure you open a ticket. |
| Posted by stablehost, 07-15-2011, 11:09 AM |
|
It does look like the issue is back, we're starting to hear complaints again. |
| Posted by contenidosonline, 07-15-2011, 11:12 AM |
Quote:
|
Originally Posted by nerdie
It does look like the issue is back, we're starting to hear complaints again.
|
where are you located ?
From Argentina my server still down.
roberto |
| Posted by stablehost, 07-15-2011, 11:14 AM |
|
Can you paste a traceroute? We're getting complaints of people in Brazil unable to reach us. |
| Posted by contenidosonline, 07-15-2011, 11:21 AM |
Quote:
|
Originally Posted by nerdie
Can you paste a traceroute? We're getting complaints of people in Brazil unable to reach us.
|
This is my traceroute from Telecom Argentina:
server1:~# traceroute 184.95.58.210
traceroute to 184.95.58.210 (184.95.58.210), 30 hops max, 40 byte packets
1 169.254.10.80 (169.254.10.80) 0.052 ms 0.014 ms 0.012 ms
2 host229.190-224-24.telecom.net.ar (190.224.24.229) 71.119 ms 71.377 ms 72.926 ms
3 host17.200-117-126.telecom.net.ar (200.117.126.17) 78.695 ms 78.885 ms 79.546 ms
4 host53.190-227-0.telecom.net.ar (190.227.0.53) 83.956 ms 84.151 ms 84.226 ms
5 host110.190-224-165.telecom.net.ar (190.224.165.110) 85.591 ms 85.708 ms 86.179 ms
6 te1-3.baires3.bai.seabone.net (195.22.220.97) 83.630 ms 82.799 ms 83.231 ms
7 64.212.107.77 (64.212.107.77) 101.457 ms 40.991 ms 41.116 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
server1:~#
roberto |
| Posted by JordanJ, 07-15-2011, 11:38 AM |
|
Thanks! If you are having problems connecting please send me trace routes. We are tracking down why only certain ip blocks and only out of certain locations are unable to be reached. |
| Posted by contenidosonline, 07-15-2011, 11:38 AM |
now looks up from Argentina.
From Brazil ?
roberto |
| Posted by JordanJ, 07-15-2011, 01:09 PM |
So I just met with our Director of Network Ops, and let me try and explain what is currently going on.
We have multiple ISPs, GLBX is just one of them. When they had issues we shut them down.
The different ISPs in South America also has a number of ISPs including GLBX however they did not shut down GLBX.
GLBX is reporting to the ISP that it is both fine and has a route to us.
GLBX has no route to us because we have stopped peering with them.
There are additional routes from the South American ISP to us, and we can see them, however the South American ISPs are pushing the traffic through GLBX because they see it as the best route even though the route is not there.
In order for the "failover" to the other carriers to work for the SA ISP, one of two things need to happen.
1) GLBX correct reports that we do not peer with them
2) The SA ISP stops peering with GLBX or static routes traffic to us away from them.
So what can we do?
If you guys can tell us the ISP of the customers having issues. We will attempt to contact them and tell them that GLBX is having issues. Because GLBX is "reporting" as working correctly, these ISPs have not taken the peer offline. |
Add to Favourites 
Print this Article
Also Read
VolumeDrive (Views: 960)
Versaweb down (Views: 979)
Shared Hosting
Shared Hosting
