<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <title>Slicehost - Home</title>
  <id>tag:status.slicehost.com,2008:mephisto/</id>
  <generator version="0.7.3" uri="http://mephistoblog.com">Mephisto Noh-Varr</generator>
  <link href="http://status.slicehost.com/feed/atom.xml" rel="self" type="application/atom+xml"/>
  <link href="http://status.slicehost.com/" rel="alternate" type="text/html"/>
  <updated>2008-11-28T19:05:14Z</updated>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-11-28:105</id>
    <published>2008-11-28T17:30:00Z</published>
    <updated>2008-11-28T19:05:14Z</updated>
    <link href="http://status.slicehost.com/2008/11/28/nov-28-credit-card-processing-issues" rel="alternate" type="text/html"/>
    <title>Nov 28 - Credit Card Processing Issues</title>
<content type="html">
            &lt;p&gt;We&#8217;re having issues with our credit card processor, they&#8217;ve been alerted and are investigating. Some charges (new signups) are not going through when they should. Updates to follow.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;&lt;span class=&quot;caps&quot;&gt;UPDATE&lt;/span&gt;&lt;/strong&gt; &#8211; new signups are going through again and the issue for monthly charges will be resolved shortly.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-11-21:98</id>
    <published>2008-11-21T18:56:00Z</published>
    <updated>2008-11-21T18:57:12Z</updated>
    <link href="http://status.slicehost.com/2008/11/21/stl-b-packet-loss-from-some-locations" rel="alternate" type="text/html"/>
    <title>STL-B Packet loss from some locations</title>
<content type="html">
            &lt;p&gt;Seeing packet loss from Europe and Chicago, issue appears to be upstream, investigating now. 1855GMT.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-11-04:79</id>
    <published>2008-11-04T17:31:00Z</published>
    <updated>2008-11-04T17:33:58Z</updated>
    <link href="http://status.slicehost.com/2008/11/4/slicehoststatus-on-twitter" rel="alternate" type="text/html"/>
    <title>Slicehoststatus on Twitter</title>
<content type="html">
            &lt;p&gt;Per customer requests, we have created a tech status update only Twitter account similar to status.slicehost.com &#8211; &lt;a href=&quot;http://twitter.com/slicehoststatus&quot;&gt;@slicehoststatus&lt;/a&gt;. Our regular Twitter account &lt;a href=&quot;http://twitter.com/slicehost&quot;&gt;@slicehost&lt;/a&gt; can be used for quick questions and general tweets.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-11-04:77</id>
    <published>2008-11-04T04:19:00Z</published>
    <updated>2008-11-04T04:37:09Z</updated>
    <link href="http://status.slicehost.com/2008/11/4/stl-b-network-trouble-tue-nov-4-04-00-utc-2008" rel="alternate" type="text/html"/>
    <title>STL-B Network Trouble Tue Nov  4 04:00 UTC 2008</title>
<content type="html">
            &lt;p&gt;We are tracking some packet loss to &lt;span class=&quot;caps&quot;&gt;STL&lt;/span&gt;-B datacenter.  Will update when we have more info.&lt;/p&gt;


	&lt;p&gt;&lt;strong&gt;&lt;span class=&quot;caps&quot;&gt;UPDATE&lt;/span&gt;&lt;/strong&gt; 0430 &lt;span class=&quot;caps&quot;&gt;GMT&lt;/span&gt;, looking better appears to have been a Level3 issue.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-10-21:76</id>
    <published>2008-10-21T00:27:00Z</published>
    <updated>2008-10-21T00:27:58Z</updated>
    <link href="http://status.slicehost.com/2008/10/21/stl-b-dos-0000-gmt" rel="alternate" type="text/html"/>
    <title>STL-B DoS 0000 GMT</title>
<content type="html">
            &lt;p&gt;Had a small DoS that was resolved quickly, some people may have experienced connectivity issues including packet loss.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-10-14:73</id>
    <published>2008-10-14T22:50:00Z</published>
    <updated>2008-10-14T23:29:17Z</updated>
    <link href="http://status.slicehost.com/2008/10/14/stl-a-network-problems-2245-gmt" rel="alternate" type="text/html"/>
    <title>STL-A Network Problems 2245 GMT [RESOLVED]</title>
<content type="html">
            &lt;p&gt;Various locations are seeing packet loss to &lt;span class=&quot;caps&quot;&gt;STL&lt;/span&gt;-A. We have someone onsite and have escalated to our providers, as it appears to be an upstream problem at the moment.&lt;/p&gt;


	&lt;p&gt;&lt;span class=&quot;caps&quot;&gt;UPDATE&lt;/span&gt; &#8211; upstream issue affecting some locations, being worked by providers.&lt;/p&gt;


	&lt;p&gt;&lt;span class=&quot;caps&quot;&gt;UPDATE 2&lt;/span&gt; &#8211; looks good from all locations once again (2325).&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>jason</name>
    </author>
    <id>tag:status.slicehost.com,2008-10-13:72</id>
    <published>2008-10-13T01:08:00Z</published>
    <updated>2008-10-13T01:25:01Z</updated>
    <link href="http://status.slicehost.com/2008/10/13/stl-b-network-issue-01-05-utc-resolved" rel="alternate" type="text/html"/>
    <title>STL-B Network issue Oct 13 01:05 UTC (resolved)</title>
<content type="html">
            &lt;p&gt;A network issue lasting 5-10 minutes appears to have affected some but not all slices in &lt;span class=&quot;caps&quot;&gt;STL&lt;/span&gt;-B.  This appears to be an issue only within the network (i.e. switching) and not related to uplinks or internet connectivity.  Things appear to be back to normal, please let us know if you see any continued problems.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-07-31:54</id>
    <published>2008-07-31T18:12:00Z</published>
    <updated>2008-07-31T18:22:57Z</updated>
    <link href="http://status.slicehost.com/2008/7/31/1800-gmt-july-31-stl-b-ddos" rel="alternate" type="text/html"/>
    <title>1800 GMT July 31 STL-B DDoS</title>
<content type="html">
            &lt;p&gt;Some of you may be noticing packet loss in &lt;span class=&quot;caps&quot;&gt;STL&lt;/span&gt;-B. We&#8217;re working a DDoS as we speak and conditions should improve soon.&lt;/p&gt;


	&lt;p&gt;&lt;span class=&quot;caps&quot;&gt;UPDATE&lt;/span&gt;: www.slicehost.com was the target of the flood and you might be unable to reach it temporarily. Packet loss should be improving.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-07-30:53</id>
    <published>2008-07-30T18:49:00Z</published>
    <updated>2008-07-31T13:12:50Z</updated>
    <link href="http://status.slicehost.com/2008/7/30/stl-a-network-issues-wed-jul-30-18-48-48-utc-2008" rel="alternate" type="text/html"/>
    <title>STL-A Network Issues Wed Jul 30 18:48:48 UTC 2008</title>
<content type="html">
            &lt;p&gt;Some customers are seeing connectivity issues to &lt;span class=&quot;caps&quot;&gt;STL&lt;/span&gt;-A depending on their provider.  It&#8217;s unclear what the issue is at this point, but it doesn&#8217;t appear to be directly on our network.  We have opened a trouble ticket with our upstream and they are investigating.&lt;/p&gt;


	&lt;p&gt;&lt;span class=&quot;caps&quot;&gt;UPDATE&lt;/span&gt; Wed Jul 30 18:55:32 &lt;span class=&quot;caps&quot;&gt;UTC 2008&lt;/span&gt;:
No official update from any providers, but the customers seeing issues now report that things are back in working order.  We&#8217;ll still post an official response when our ticket is answered.&lt;/p&gt;


	&lt;p&gt;&lt;span class=&quot;caps&quot;&gt;FINAL UPDATE&lt;/span&gt;
Apparently there was an unexpected downtime on the XO uplink and the issues we saw presented at some point after the link was restored.  We don&#8217;t have any technical details on the cause of the issue other than identification of a routing loop that was introduced and corrective measures were taken after it was reported.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-07-30:52</id>
    <published>2008-07-30T16:07:00Z</published>
    <updated>2008-07-30T16:13:35Z</updated>
    <link href="http://status.slicehost.com/2008/7/30/stl-b-network-maintenance-friday-aug-1" rel="alternate" type="text/html"/>
    <title>STL-B Network Maintenance Friday Aug 1</title>
<content type="html">
            &lt;p&gt;One of our network providers (Cogent) has scheduled a maintenance window for Friday, August 1 from 0800-1200 &lt;span class=&quot;caps&quot;&gt;GMT&lt;/span&gt;. There will be a hardware replacement which means our circuit will be down. It should be non-impacting because we have multiple carriers and will move traffic to other circuits prior to the window. If you experience any network issues during this timeframe, please contact our support team.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-07-27:51</id>
    <published>2008-07-27T22:09:00Z</published>
    <updated>2008-07-27T22:22:25Z</updated>
    <link href="http://status.slicehost.com/2008/7/27/sunday-july-27-2200-gmt" rel="alternate" type="text/html"/>
    <title>Sunday July 27 2200 GMT</title>
<content type="html">
            &lt;p&gt;We&#8217;re experiencing a large DDoS attack at the &lt;span class=&quot;caps&quot;&gt;STL&lt;/span&gt;-B facility. Currently we are working the issue and speaking with our upstream providers. We apologize for the intermittent network disruptions you might be experiencing, it should be resolved soon.&lt;/p&gt;


	&lt;p&gt;2220 &lt;span class=&quot;caps&quot;&gt;GMT&lt;/span&gt; &#8211; Issue resolved (traffic blocks in place). Please contact us if you&#8217;re still having trouble with packet loss.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-06-10:50</id>
    <published>2008-06-10T17:22:00Z</published>
    <updated>2008-06-10T17:25:00Z</updated>
    <link href="http://status.slicehost.com/2008/6/10/1820-gmt-traffic-issues-between-data-centers" rel="alternate" type="text/html"/>
    <title>1820 GMT Traffic issues between data centers</title>
<content type="html">
            &lt;p&gt;We experienced about 15 minutes of trouble passing traffic between &lt;span class=&quot;caps&quot;&gt;STL&lt;/span&gt;-A and &lt;span class=&quot;caps&quot;&gt;STL&lt;/span&gt;-B (Internet connectivity remained fine), affecting people with slices communicating between data centers. We are investigating this issue with Level3 at the moment.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>paul</name>
    </author>
    <id>tag:status.slicehost.com,2008-06-10:49</id>
    <published>2008-06-10T12:05:00Z</published>
    <updated>2008-06-10T12:26:24Z</updated>
    <link href="http://status.slicehost.com/2008/6/10/1200gmt-jun-10th-2008" rel="alternate" type="text/html"/>
    <title>1200GMT Jun 10th 2008</title>
<content type="html">
            &lt;p&gt;We are experiencing a Denial of Service attack at our STL-A facility.&lt;/p&gt;

&lt;p&gt;Although it is located at the STL-A facility, you may experience some temporary issues with the SliceManager.&lt;/p&gt;

&lt;p&gt;We are isolating the IPs in question and will update you as soon as we have more information.&lt;/p&gt;

&lt;p&gt;The issue is improving but not completely settled.&lt;/p&gt;

&lt;p&gt;We have appropriate packet blocks in place and packet loss should now be corrected.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-06-05:47</id>
    <published>2008-06-05T00:52:00Z</published>
    <updated>2008-06-05T00:54:36Z</updated>
    <link href="http://status.slicehost.com/2008/6/5/stl-b-dos" rel="alternate" type="text/html"/>
    <title>STL-B DoS</title>
<content type="html">
            &lt;p&gt;We experienced a denial of service attack at our &lt;span class=&quot;caps&quot;&gt;STL&lt;/span&gt;-B facility beginning at 0140 &lt;span class=&quot;caps&quot;&gt;GMT&lt;/span&gt;. We&#8217;re aware of the issue and working to isolate it. Some locations are seeing minor packet loss to Slicehost IPs and that should improve soon.&lt;/p&gt;
          </content>  </entry>
  <entry xml:base="http://status.slicehost.com/">
    <author>
      <name>matt</name>
    </author>
    <id>tag:status.slicehost.com,2008-05-23:46</id>
    <published>2008-05-23T02:10:00Z</published>
    <updated>2008-05-23T02:13:23Z</updated>
    <link href="http://status.slicehost.com/2008/5/23/upstream-maintenance-stl-b" rel="alternate" type="text/html"/>
    <title>Upstream maintenance STL-B</title>
<content type="html">
            &lt;p&gt;&lt;span class=&quot;caps&quot;&gt;FYI&lt;/span&gt; &#8211; one of our carriers is performing some maintenance on 5-23-2008 from 0400-0600 &lt;span class=&quot;caps&quot;&gt;GMT&lt;/span&gt;. This shouldn&#8217;t impact overall connectivity, though some routes may change as the circuit is being worked on.&lt;/p&gt;
          </content>  </entry>
</feed>
