STL-A Network Issue

April 10th, 2009 @ 06:15 AM

Some people are reporting difficulty connecting to STL-A network. We’re investigating the issue now.

UPDATE – This appears to be affecting people coming in over XO network.

UPDATE – We escalated the issue, the NOC engineering team was onsite. They were working on the core router during a non-impacting maintenance window. We’re investigating to determine what caused the problem.

UPDATE 1320 GMT – Some people still having issues, investigating.

UPDATE 1345 GMT – Still working, appears to be EU customers.

UPDATE 1420 GMT – Still working, confirmed via comments not exclusive to EU.

UPDATE 1445 GMT – Should be resolved, issues seems to have been with Cogent in STL-A affecting some customers.

Posted by matt_disabled

Comments:

Tony commented on Fri Apr 10 06:24:57 UTC 2009:

We have many problems with our customers who stay in your server. Can you get us further informations after your investigation, please? Thanks.

keith commented on Fri Apr 10 06:26:59 UTC 2009:

Site down and can not ssh into server.

Appie Verschoor commented on Fri Apr 10 06:44:56 UTC 2009:

After the resolved update, our traceroutes still won’t get passed the XO network 66.236.121.50.ptr.us.xo.net is the last hob on the traceroute that answers

Lucas commented on Fri Apr 10 06:48:10 UTC 2009:

Same here, no hop past 66.236.121.50.ptr.us.xo.net.

lena commented on Fri Apr 10 07:07:58 UTC 2009:

We have the same problems, cannot get past the same hop as the previous commenters, and we had the exact same problem a few weeks ago (I could and can not reach my slice with an ip that starts with 208.78, and also not reach manage.slicehost.com, which also starts with 208.78. I can reach the main slicehost site), though if I remember correctly it was resolved much sooner then. I hope that this will be resolved ASAP and that it will not happen again in a few weeks.

Jo Wouters commented on Fri Apr 10 07:13:07 UTC 2009:

Same trouble here, checking from Belgium (Europe).

This is the last hop tracert shows: 66.236.121.50.ptr.us.xo.net (66.236.121.50)

Dave commented on Fri Apr 10 07:26:59 UTC 2009:

Contrary to what is reported on twitter is issue is still unresolved, at least for me.

MattF commented on Fri Apr 10 07:33:26 UTC 2009:

Same for me, coming from UK. No access to slice or manage.slicehost.com.

Tony commented on Fri Apr 10 07:37:17 UTC 2009:

In Italy it is the same. Any news?

Tim commented on Fri Apr 10 07:39:11 UTC 2009:

Still seeing issues coming from Verizon.

Last hop is 66.236.121.50.ptr.us.xo.net (66.236.121.50)

Rodrigo commented on Fri Apr 10 07:45:51 UTC 2009:

I’m having problems too. Cannot access my slice and slice manager from Portugal.

Gart commented on Fri Apr 10 07:48:08 UTC 2009:

Not just EU… Outage from North Carolina as well.

Ryan Williams commented on Fri Apr 10 07:49:40 UTC 2009:

We’re in Atlanta, Ga and we’re having the same issues. So, it’s not strictly EU.

Bakyt Niyazov commented on Fri Apr 10 07:50:58 UTC 2009:

Also articles.slicehost.com is not accessible for me.

I can access to my slice but it’s quite slow

(from Central Asia)

Dave commented on Fri Apr 10 07:51:21 UTC 2009:

It is not EU only. I’m in Boston with Verizon. Suggestion to those that need access to their site: use a proxy – it worked for me.

J commented on Fri Apr 10 07:52:34 UTC 2009:

still a problem from US east coast coming out of the verizon network

snowbiker commented on Fri Apr 10 08:00:43 UTC 2009:

Ditto the Boston Verizon problem; maybe it was “just an EU” problem because the East Coast was asleep.

gnu2tux commented on Fri Apr 10 08:37:51 UTC 2009:

yeah, my slice is still completely down at 14:30 GMT+1 including management via control panel. Based in UK.

Clive commented on Fri Apr 10 08:45:07 UTC 2009:

Mine is back. Thanks very much guys

Luc commented on Fri Apr 10 08:49:24 UTC 2009:

My sites are back up. Thank you guys!

Dave commented on Fri Apr 10 08:50:18 UTC 2009:

Boston/Verizon is back up now!