Sorry

This feed does not validate.

Source: https://www.isyourmissioncritical.com/feed/

  1.  
  2. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
  3. xmlns:content="http://purl.org/rss/1.0/modules/content/"
  4. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
  5. xmlns:dc="http://purl.org/dc/elements/1.1/"
  6. xmlns:atom="http://www.w3.org/2005/Atom"
  7. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  8. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
  9. >
  10.  
  11. <channel>
  12. <title>Is your mission critical?</title>
  13. <atom:link href="https://www.isyourmissioncritical.com/feed/" rel="self" type="application/rss+xml" />
  14. <link>https://www.isyourmissioncritical.com</link>
  15. <description>The Sliqua Engineering Blog</description>
  16. <lastBuildDate>Sat, 12 Apr 2014 13:15:29 +0000</lastBuildDate>
  17. <language>en-US</language>
  18. <sy:updatePeriod>hourly</sy:updatePeriod>
  19. <sy:updateFrequency>1</sy:updateFrequency>
  20. <generator>https://wordpress.org/?v=4.7.28</generator>
  21. <item>
  22. <title>Heartbleed Update</title>
  23. <link>https://www.isyourmissioncritical.com/attacks/heartbleed-update/</link>
  24. <comments>https://www.isyourmissioncritical.com/attacks/heartbleed-update/#respond</comments>
  25. <pubDate>Sat, 12 Apr 2014 13:11:02 +0000</pubDate>
  26. <dc:creator><![CDATA[Alexander McMillen]]></dc:creator>
  27. <category><![CDATA[Attacks]]></category>
  28. <category><![CDATA[Security]]></category>
  29.  
  30. <guid isPermaLink="false">http://www.isyourmissioncritical.com/?p=214</guid>
  31. <description><![CDATA[<table cellspacing="0" cellpadding="0">
  32. <tbody>
  33. <tr>
  34. <td valign="top">As you may have heard, a major security vulnerability; dubbed "<a href="http://sliqua.us1.list-manage1.com/track/click?u=43f2d98c72ea976a891d519eb&#38;id=2bdc544841&#38;e=2c30e3ef7b">Heartbleed</a>," was recently discovered in OpenSSL. OpenSSL enables SSL and TLS encryption, which governs HTTPS—the secure communications between your computer and the servers on the Internet. It is used by about 2/3 of the web servers in the world. This vulnerability was the result of a programming error (or bug) in several versions of OpenSSL. At its worst, Heartbleed allowed potential access to a private key for an SSL certificate as well as the encrypted communication itself.This basically means that any individual with the knowledge and skills required to exploit this vulnerability, had a window to grab your user names, passwords and any private information you may have accessed with practically any of your online services that utilize the affected versions of the OpenSSL toolkit.
  35.  
  36. Below is an overview of our response to this security vulnerability by Sliqua's engineering team, and it's impact on our users.
  37.  
  38. &#160;
  39.  
  40. <b>Enterprise Hosting</b>
  41.  
  42. A single server out of our web hosting fleet, tower.sliqua.com, was vulnerable to the OpenSSL Heartbleed Bug. No users on this server utilize SSL certificates for their websites, and thus aren't vulnerable to private key exposure. However, as a precaution, this server was immediately patched and services were restarted by Support Engineering on the morning of April 7, when the bug was initially announced. <b><i>All other servers run a version of OpenSSL that was not vulnerable.</i></b> No further action is required by users, as no user data was exposed.
  43.  
  44. <b>Clustered Mail</b>
  45.  
  46. After a full system audit, we concluded that no public-facing web servers supporting webmail/administration were exposed. We did, however, find a single SMTP end-point which was intermittently vulnerable. We immediately removed this server from rotation, applied the proper updates and proceeded to insulate all remaining servers from potential exploit.
  47.  
  48. At this time we have no reason to believe any sensitive user information was accessed, however, out of an abundance of caution <b>we recommend that all end users change their email passwords at their earliest convenience. This can be completed through our Webmail interface at </b><a href="http://sliqua.us1.list-manage1.com/track/click?u=43f2d98c72ea976a891d519eb&#38;id=df2cc3456d&#38;e=2c30e3ef7b">https://webmail.sliqua.com</a>
  49.  
  50. All users with local email, and those particularly on falcon.sliqua.com, have no need to reset their passwords as there was no impact. This password reset is only necessary for Clustered Mail users.
  51.  
  52. If you have any questions, don't hesitate to reach out to us.</td>
  53. </tr>
  54. </tbody>
  55. </table>]]></description>
  56. <content:encoded><![CDATA[<table cellspacing="0" cellpadding="0">
  57. <tbody>
  58. <tr>
  59. <td valign="top">As you may have heard, a major security vulnerability; dubbed &#8220;<a href="http://sliqua.us1.list-manage1.com/track/click?u=43f2d98c72ea976a891d519eb&amp;id=2bdc544841&amp;e=2c30e3ef7b">Heartbleed</a>,&#8221; was recently discovered in OpenSSL. OpenSSL enables SSL and TLS encryption, which governs HTTPS—the secure communications between your computer and the servers on the Internet. It is used by about 2/3 of the web servers in the world. This vulnerability was the result of a programming error (or bug) in several versions of OpenSSL.At its worst, Heartbleed allowed potential access to a private key for an SSL certificate as well as the encrypted communication itself.This basically means that any individual with the knowledge and skills required to exploit this vulnerability, had a window to grab your user names, passwords and any private information you may have accessed with practically any of your online services that utilize the affected versions of the OpenSSL toolkit.</p>
  60. <p>Below is an overview of our response to this security vulnerability by Sliqua&#8217;s engineering team, and it&#8217;s impact on our users.</p>
  61. <p>&nbsp;</p>
  62. <p><b>Enterprise Hosting</b></p>
  63. <p>A single server out of our web hosting fleet, tower.sliqua.com, was vulnerable to the OpenSSL Heartbleed Bug. No users on this server utilize SSL certificates for their websites, and thus aren&#8217;t vulnerable to private key exposure. However, as a precaution, this server was immediately patched and services were restarted by Support Engineering on the morning of April 7, when the bug was initially announced. <b><i>All other servers run a version of OpenSSL that was not vulnerable.</i></b> No further action is required by users, as no user data was exposed.</p>
  64. <p><b>Clustered Mail</b></p>
  65. <p>After a full system audit, we concluded that no public-facing web servers supporting webmail/administration were exposed. We did, however, find a single SMTP end-point which was intermittently vulnerable. We immediately removed this server from rotation, applied the proper updates and proceeded to insulate all remaining servers from potential exploit.</p>
  66. <p>At this time we have no reason to believe any sensitive user information was accessed, however, out of an abundance of caution <b>we recommend that all end users change their email passwords at their earliest convenience. This can be completed through our Webmail interface at </b><a href="http://sliqua.us1.list-manage1.com/track/click?u=43f2d98c72ea976a891d519eb&amp;id=df2cc3456d&amp;e=2c30e3ef7b">https://webmail.sliqua.com</a></p>
  67. <p>All users with local email, and those particularly on falcon.sliqua.com, have no need to reset their passwords as there was no impact. This password reset is only necessary for Clustered Mail users.</p>
  68. <p>If you have any questions, don&#8217;t hesitate to reach out to us.</td>
  69. </tr>
  70. </tbody>
  71. </table>
  72. ]]></content:encoded>
  73. <wfw:commentRss>https://www.isyourmissioncritical.com/attacks/heartbleed-update/feed/</wfw:commentRss>
  74. <slash:comments>0</slash:comments>
  75. </item>
  76. <item>
  77. <title>Sliqua is one of the first web hosts to implement Cloudflare Railgun Technology</title>
  78. <link>https://www.isyourmissioncritical.com/network-2/sliqua-is-one-of-the-first-web-hosts-to-implement-cloudflares-railgun-technology/</link>
  79. <comments>https://www.isyourmissioncritical.com/network-2/sliqua-is-one-of-the-first-web-hosts-to-implement-cloudflares-railgun-technology/#respond</comments>
  80. <pubDate>Wed, 27 Feb 2013 00:51:02 +0000</pubDate>
  81. <dc:creator><![CDATA[Alexander McMillen]]></dc:creator>
  82. <category><![CDATA[Network]]></category>
  83.  
  84. <guid isPermaLink="false">http://www.isyourmissioncritical.com/?p=180</guid>
  85. <description><![CDATA[<p style="text-align: center;"><img class="aligncenter" alt="" src="http://www.isyourmissioncritical.com/wp-content/uploads/2013/02/host-optimized-badge-250px.png" width="251" height="145" /></p>
  86. <img alt="" src="http://www.isyourmissioncritical.com/wp-content/uploads/2013/02/railgun-map.png" width="509" height="169" />
  87.  
  88. As a CloudFlare Optimized Partner, we are thrilled to offer the CloudFlare Railgun™ technology to all our customers.
  89.  
  90. Railgun is CloudFlare’s latest performance optimization technology that gives you significant improvements in site load times. We are offering the service to customers upon request starting today, as a part of the Cloudflare Railgun launch as seen on <a href="http://arstechnica.com/information-technology/2013/02/cloudflare-blows-hole-in-laws-of-web-physics-with-go-and-railgun/" target="_blank">Ars Technica</a>'s  and <a href="http://techcrunch.com/2013/02/26/cloudflare-partners-with-majority-of-worlds-leading-web-hosts-to-implement-its-railgun-protocol-speeds-up-load-times-by-143/" target="_blank">Techcrunch</a>. Sliqua is one of the first hosting companies to start utilizing this amazing new technology from Cloudflare.
  91.  
  92. Railgun ensures that the connection between the Sliqua Core Network (<a href="http://bgp.he.net/AS32740" target="_blank">AS32740</a>) and the CloudFlare network is as fast as possible. Railgun achieves a 99.6% compression ratio for previously uncacheable web objects by using techniques similar to those used in the compression of high-quality video. The average website can expect a 1.43x performance increase.
  93.  
  94. <img alt="" src="http://www.isyourmissioncritical.com/wp-content/uploads/2013/02/railgun-details.png" width="509" height="292" />
  95.  
  96. When a request is made to a CloudFlare server for a web page that is not in cache CloudFlare makes an HTTP connection to the origin server to request the page. It's that HTTP connection that Railgun accelerates and secures.
  97.  
  98. <h2>Even highly dynamic websites change slowly</h2>
  99.  
  100. Railgun works by recognizing that uncacheable web pages do not change very rapidly. For example, during an experiment, the CNN.com homepage HTML was captured once, and then again after 5 minutes and then again after one hour. The page sizes were 92,516, five minutes still 92,516 and one hour later 93,727.
  101.  
  102. CNN sets the caching on this page to 60 seconds. After one minute, it is necessary to download the entire page again. However, looking inside the page, not much has changed. In fact, the change between versions is on the order of 100s of bytes out of almost 100k. Here’s a screenshot of one of the binary differences between the CNN home page at five minute intervals. The yellow bytes have changed, the rest have not.
  103.  
  104. <img alt="" src="http://www.isyourmissioncritical.com/wp-content/uploads/2013/02/railgun-data.png" width="509" height="333" />
  105.  
  106. Experiments at CloudFlare have revealed similar change values across the web. For example, reddit.com changes by about 2.15% over five minutes and 3.16% over an hour. The New York Times home page changes by about 0.6% over five minutes and 3% over an hour. BBC News changes by about 0.4% over five minutes and 2% over an hour.
  107.  
  108. Although the dynamic web is not cacheable, it is also not changing quickly. That means that from moment to moment there’s only a small change between versions of a page. CloudFlare Railgun uses this fact to achieve very high rates of compression. This is very similar to how video compression looks for changes from frame to frame; Railgun looks for changes on a page from download to download.
  109. <h2>Railgun Technology</h2>
  110. Railgun consists of two components: the sender and the listener. The sender is installed at every CloudFlare data center around the world. The listener is a software component that Sliqua has installed on our network for customers.
  111.  
  112. The sender and listener establish a permanent TCP connection that’s secured by TLS. This TCP connection is used for the Railgun protocol. It’s an all binary multiplexing protocol that allows multiple HTTP requests to be run simultaneously and asynchronously across the link. Or in other words, a persistent connection is opened between CloudFlare’s network and ours and eliminates the overhead of TCP.
  113.  
  114. We have made it simple for our customers to get the benefits of Railgun with one click. For additional information and instructions on how to activate, please contact support via <a href="mailto:support@sliqua.com">support@sliqua.com</a>.]]></description>
  115. <content:encoded><![CDATA[<p style="text-align: center;"><img class="aligncenter" alt="" src="http://www.isyourmissioncritical.com/wp-content/uploads/2013/02/host-optimized-badge-250px.png" width="251" height="145" /></p>
  116. <p><img alt="" src="http://www.isyourmissioncritical.com/wp-content/uploads/2013/02/railgun-map.png" width="509" height="169" /></p>
  117. <p>As a CloudFlare Optimized Partner, we are thrilled to offer the CloudFlare Railgun™ technology to all our customers.</p>
  118. <p>Railgun is CloudFlare’s latest performance optimization technology that gives you significant improvements in site load times. We are offering the service to customers upon request starting today, as a part of the Cloudflare Railgun launch as seen on <a href="http://arstechnica.com/information-technology/2013/02/cloudflare-blows-hole-in-laws-of-web-physics-with-go-and-railgun/" target="_blank">Ars Technica</a>&#8216;s  and <a href="http://techcrunch.com/2013/02/26/cloudflare-partners-with-majority-of-worlds-leading-web-hosts-to-implement-its-railgun-protocol-speeds-up-load-times-by-143/" target="_blank">Techcrunch</a>. Sliqua is one of the first hosting companies to start utilizing this amazing new technology from Cloudflare.</p>
  119. <p>Railgun ensures that the connection between the Sliqua Core Network (<a href="http://bgp.he.net/AS32740" target="_blank">AS32740</a>) and the CloudFlare network is as fast as possible. Railgun achieves a 99.6% compression ratio for previously uncacheable web objects by using techniques similar to those used in the compression of high-quality video. The average website can expect a 1.43x performance increase.</p>
  120. <p><img alt="" src="http://www.isyourmissioncritical.com/wp-content/uploads/2013/02/railgun-details.png" width="509" height="292" /></p>
  121. <p>When a request is made to a CloudFlare server for a web page that is not in cache CloudFlare makes an HTTP connection to the origin server to request the page. It&#8217;s that HTTP connection that Railgun accelerates and secures.</p>
  122. <h2>Even highly dynamic websites change slowly</h2>
  123. <p>Railgun works by recognizing that uncacheable web pages do not change very rapidly. For example, during an experiment, the CNN.com homepage HTML was captured once, and then again after 5 minutes and then again after one hour. The page sizes were 92,516, five minutes still 92,516 and one hour later 93,727.</p>
  124. <p>CNN sets the caching on this page to 60 seconds. After one minute, it is necessary to download the entire page again. However, looking inside the page, not much has changed. In fact, the change between versions is on the order of 100s of bytes out of almost 100k. Here’s a screenshot of one of the binary differences between the CNN home page at five minute intervals. The yellow bytes have changed, the rest have not.</p>
  125. <p><img alt="" src="http://www.isyourmissioncritical.com/wp-content/uploads/2013/02/railgun-data.png" width="509" height="333" /></p>
  126. <p>Experiments at CloudFlare have revealed similar change values across the web. For example, reddit.com changes by about 2.15% over five minutes and 3.16% over an hour. The New York Times home page changes by about 0.6% over five minutes and 3% over an hour. BBC News changes by about 0.4% over five minutes and 2% over an hour.</p>
  127. <p>Although the dynamic web is not cacheable, it is also not changing quickly. That means that from moment to moment there’s only a small change between versions of a page. CloudFlare Railgun uses this fact to achieve very high rates of compression. This is very similar to how video compression looks for changes from frame to frame; Railgun looks for changes on a page from download to download.</p>
  128. <h2>Railgun Technology</h2>
  129. <p>Railgun consists of two components: the sender and the listener. The sender is installed at every CloudFlare data center around the world. The listener is a software component that Sliqua has installed on our network for customers.</p>
  130. <p>The sender and listener establish a permanent TCP connection that’s secured by TLS. This TCP connection is used for the Railgun protocol. It’s an all binary multiplexing protocol that allows multiple HTTP requests to be run simultaneously and asynchronously across the link. Or in other words, a persistent connection is opened between CloudFlare’s network and ours and eliminates the overhead of TCP.</p>
  131. <p>We have made it simple for our customers to get the benefits of Railgun with one click. For additional information and instructions on how to activate, please contact support via <a href="mailto:support@sliqua.com">support@sliqua.com</a>.</p>
  132. ]]></content:encoded>
  133. <wfw:commentRss>https://www.isyourmissioncritical.com/network-2/sliqua-is-one-of-the-first-web-hosts-to-implement-cloudflares-railgun-technology/feed/</wfw:commentRss>
  134. <slash:comments>0</slash:comments>
  135. </item>
  136. <item>
  137. <title>The importance of S/MIME and/or GnuPG for e-mail</title>
  138. <link>https://www.isyourmissioncritical.com/uncategorized/the-importance-of-smime-and-gnupg-for-e-mail/</link>
  139. <comments>https://www.isyourmissioncritical.com/uncategorized/the-importance-of-smime-and-gnupg-for-e-mail/#respond</comments>
  140. <pubDate>Sat, 12 Jan 2013 15:31:30 +0000</pubDate>
  141. <dc:creator><![CDATA[Alexander McMillen]]></dc:creator>
  142. <category><![CDATA[Uncategorized]]></category>
  143.  
  144. <guid isPermaLink="false">http://www.isyourmissioncritical.com/?p=173</guid>
  145. <description><![CDATA[It recently came to my attention that some in the financial services industry believe that the TLS transmission of e-mail from one service provider to another is imposing "extra security measures" to protect a customer's financial information. I wanted to take a moment to reflect on this and provide a small blog post to those concerned about protecting critical information to them - be it personal or commercial financial information, passwords, or intellectual property being sent via e-mail.
  146.  
  147. Obviously, there is some information that should never be transmitted via email. We highly recommend the use of internal, secure file sharing platforms in-house to protect intellectual property.
  148.  
  149. To burst the security bubble for most e-mail users out there that believed in some way their e-mail was "secure" even at rest-
  150.  
  151. <em>Email is <strong>only</strong> TLS encrypted in transmission from one service provider to another. In fact, TLS transmission of e-mail is pretty standard practice in the hosting industry. However, it's a practice which is pretty irrelevant in most cases unless an attacker is sitting between the two service providers watching for the transmission ("Man in the Middle Attacks"). </em>
  152.  
  153. <em>Your e-mail messages are still stored unencrypted at-rest on both service providers, and your local computer. This means that if either hosting provider is compromised (internally or externally), or your computer falls into unwanted hands, the e-mail is sitting there in plain-text for anyone to read. That is, unless you're utilizing your own Encryption mechanism (what we in the industry call "host-proof hosting"). </em>
  154.  
  155. Well, that's great, so how do I get this so-called "host-proof hosting" for e-mail?
  156.  
  157. If security is a concern in transmission and at-rest for your e-mail data, I highly recommend utilizing S/MIME Encryption (essentially, the SSL protocol for E-mail - the same level of security you'd expect when visiting a site with https://). The difference is that the SSL encryption/decryption is occurring on the client machines instead of the server (when sent and received . It's also possible to use another encryption technology called GPG. But for most end-users, the setup for GPG is too complicated and there's not wide enough adoption.
  158.  
  159. When using S/MIME signatures and encryption between two parties - you'll get peace of mind because of the following:
  160.  
  161. 1) You know the person that sent you the message is who they claim they are. This is verified by an accredited Certificate Authority with different levels of verification (either by just their email address at the most basic level, by their name (Personal documents are required), or by Organization (Business documents are required)).
  162.  
  163. 2) If the message is sent as S/MIME Encrypted, it's fully encrypted at rest on the server(s) the message resides on. So even if an attacker were to gain access to your e-mail message, they would need the private key (which resides on your computer) in order to decrypt the message.
  164.  
  165. With all of that said, I would highly recommend that everyone gets an S/MIME certificate through Comodo, or GlobalSign, which are all universally supported S/MIME certificate providers. But getting a certificate for yourself doesn't mean messages are encrypted, both the sending and receiving side need a certificate installed before you can start sending encrypted messages to each other. This is why some CA's such as Comodo even offers these certificates free of charge for individuals! Tell your friends. :-)
  166.  
  167. Some reference sites to get Email Signing Certificates:
  168.  
  169. <a href="http://www.comodo.com/home/email-security/free-email-certificate.php">Comodo Free E-mail Certificate</a>
  170. <a href="https://www.globalsign.com/personalsign/">GlobalSign Personal Sign</a>
  171.  
  172. Enjoy!
  173. Team Sliqua]]></description>
  174. <content:encoded><![CDATA[<p>It recently came to my attention that some in the financial services industry believe that the TLS transmission of e-mail from one service provider to another is imposing &#8220;extra security measures&#8221; to protect a customer&#8217;s financial information. I wanted to take a moment to reflect on this and provide a small blog post to those concerned about protecting critical information to them &#8211; be it personal or commercial financial information, passwords, or intellectual property being sent via e-mail.</p>
  175. <p>Obviously, there is some information that should never be transmitted via email. We highly recommend the use of internal, secure file sharing platforms in-house to protect intellectual property.</p>
  176. <p>To burst the security bubble for most e-mail users out there that believed in some way their e-mail was &#8220;secure&#8221; even at rest-</p>
  177. <p><em>Email is <strong>only</strong> TLS encrypted in transmission from one service provider to another. In fact, TLS transmission of e-mail is pretty standard practice in the hosting industry. However, it&#8217;s a practice which is pretty irrelevant in most cases unless an attacker is sitting between the two service providers watching for the transmission (&#8220;Man in the Middle Attacks&#8221;). </em></p>
  178. <p><em>Your e-mail messages are still stored unencrypted at-rest on both service providers, and your local computer. This means that if either hosting provider is compromised (internally or externally), or your computer falls into unwanted hands, the e-mail is sitting there in plain-text for anyone to read. That is, unless you&#8217;re utilizing your own Encryption mechanism (what we in the industry call &#8220;host-proof hosting&#8221;). </em></p>
  179. <p>Well, that&#8217;s great, so how do I get this so-called &#8220;host-proof hosting&#8221; for e-mail?</p>
  180. <p>If security is a concern in transmission and at-rest for your e-mail data, I highly recommend utilizing S/MIME Encryption (essentially, the SSL protocol for E-mail &#8211; the same level of security you&#8217;d expect when visiting a site with https://). The difference is that the SSL encryption/decryption is occurring on the client machines instead of the server (when sent and received . It&#8217;s also possible to use another encryption technology called GPG. But for most end-users, the setup for GPG is too complicated and there&#8217;s not wide enough adoption.</p>
  181. <p>When using S/MIME signatures and encryption between two parties &#8211; you&#8217;ll get peace of mind because of the following:</p>
  182. <p>1) You know the person that sent you the message is who they claim they are. This is verified by an accredited Certificate Authority with different levels of verification (either by just their email address at the most basic level, by their name (Personal documents are required), or by Organization (Business documents are required)).</p>
  183. <p>2) If the message is sent as S/MIME Encrypted, it&#8217;s fully encrypted at rest on the server(s) the message resides on. So even if an attacker were to gain access to your e-mail message, they would need the private key (which resides on your computer) in order to decrypt the message.</p>
  184. <p>With all of that said, I would highly recommend that everyone gets an S/MIME certificate through Comodo, or GlobalSign, which are all universally supported S/MIME certificate providers. But getting a certificate for yourself doesn&#8217;t mean messages are encrypted, both the sending and receiving side need a certificate installed before you can start sending encrypted messages to each other. This is why some CA&#8217;s such as Comodo even offers these certificates free of charge for individuals! Tell your friends. 🙂</p>
  185. <p>Some reference sites to get Email Signing Certificates:</p>
  186. <p><a href="http://www.comodo.com/home/email-security/free-email-certificate.php">Comodo Free E-mail Certificate</a><br />
  187. <a href="https://www.globalsign.com/personalsign/">GlobalSign Personal Sign</a></p>
  188. <p>Enjoy!<br />
  189. Team Sliqua</p>
  190. ]]></content:encoded>
  191. <wfw:commentRss>https://www.isyourmissioncritical.com/uncategorized/the-importance-of-smime-and-gnupg-for-e-mail/feed/</wfw:commentRss>
  192. <slash:comments>0</slash:comments>
  193. </item>
  194. <item>
  195. <title>The Sliqua Core Network (AS32740)</title>
  196. <link>https://www.isyourmissioncritical.com/network-2/the-sliqua-core-network-as32740/</link>
  197. <pubDate>Sun, 13 Feb 2011 14:57:30 +0000</pubDate>
  198. <dc:creator><![CDATA[Alexander McMillen]]></dc:creator>
  199. <category><![CDATA[Network]]></category>
  200.  
  201. <guid isPermaLink="false">http://www.isyourmissioncritical.com/?p=145</guid>
  202. <description><![CDATA[In case you haven't heard the news, Sliqua officially owns and operates it's own <a href="http://en.wikipedia.org/wiki/Autonomous_System_Number" target="_blank">Autonomous System (AS)</a> on the Internet. The Sliqua Core Network now operates under <a href="http://whois.arin.net/rest/asn/AS32740/pft" target="_blank">AS32740</a>.
  203.  
  204. <strong>What does mean for you?</strong>
  205. We're not just another hosting company relying solely on a single upstream internet provider, claiming to operate it's own network. We speak a protocol known as BGPv4, which is used by Internet Service Providers to share route information over the Internet. This means that even if we lose a connection to a direct upstream Internet provider, our network has the ability to self-heal and continue operating as if nothing happened. It also gives us the ability to adjust routes to improve performance when remote providers are experiencing issues.
  206.  
  207. We also now own our own IP address space, instead of utilizing another provider's allocations, which gives us the ability to have Points of Presence in multiple facilities around the world. We have also started a project to implement <a href="http://en.wikipedia.org/wiki/IPv6" target="_blank">IPv6</a>, the next generation of the Internet Protocol, which is right around the corner.
  208.  
  209. <strong>What does our new network architecture look like?</strong>
  210. <img src="http://www.sliqua.com/sliqua/img/networkdiagram.png" alt="Network Architecture" />
  211.  
  212. <strong>Want to learn more about the Sliqua Core Network?</strong>
  213. We have setup a <a href="http://lg.sliqua.net">Public Looking Glass</a> to display all sorts of geeky details about our network performance. This includes <a href="http://lg.sliqua.net">real-time network utilization</a> between our Core Network and our upstream providers, <a href="http://lg.sliqua.net/cgi-bin/smokeping.cgi">Smokeping statistics</a> for our connectivity between Tier 1 Providers, <a href="http://reports.panopta.com/lg">3rd Party Monitoring</a> of our uplinks to our Internet Service Providers, and the ability to <a href="http://lg.sliqua.net/smokeping/tr.html">Traceroute to remote addresses</a> to see our performance for yourself.
  214.  
  215. <strong>This is a big milestone in Sliqua's history</strong>
  216. We hope that you enjoy the new network performance as much as we do. It has been a long time coming, and we've finally hit this milestone.]]></description>
  217. <content:encoded><![CDATA[<p>In case you haven&#8217;t heard the news, Sliqua officially owns and operates it&#8217;s own <a href="http://en.wikipedia.org/wiki/Autonomous_System_Number" target="_blank">Autonomous System (AS)</a> on the Internet. The Sliqua Core Network now operates under <a href="http://whois.arin.net/rest/asn/AS32740/pft" target="_blank">AS32740</a>.</p>
  218. <p><strong>What does mean for you?</strong><br />
  219. We&#8217;re not just another hosting company relying solely on a single upstream internet provider, claiming to operate it&#8217;s own network. We speak a protocol known as BGPv4, which is used by Internet Service Providers to share route information over the Internet. This means that even if we lose a connection to a direct upstream Internet provider, our network has the ability to self-heal and continue operating as if nothing happened. It also gives us the ability to adjust routes to improve performance when remote providers are experiencing issues. </p>
  220. <p>We also now own our own IP address space, instead of utilizing another provider&#8217;s allocations, which gives us the ability to have Points of Presence in multiple facilities around the world. We have also started a project to implement <a href="http://en.wikipedia.org/wiki/IPv6" target="_blank">IPv6</a>, the next generation of the Internet Protocol, which is right around the corner.</p>
  221. <p><strong>What does our new network architecture look like?</strong><br />
  222. <img src="http://www.sliqua.com/sliqua/img/networkdiagram.png" alt="Network Architecture" /></p>
  223. <p><strong>Want to learn more about the Sliqua Core Network?</strong><br />
  224. We have setup a <a href="http://lg.sliqua.net">Public Looking Glass</a> to display all sorts of geeky details about our network performance. This includes <a href="http://lg.sliqua.net">real-time network utilization</a> between our Core Network and our upstream providers, <a href="http://lg.sliqua.net/cgi-bin/smokeping.cgi">Smokeping statistics</a> for our connectivity between Tier 1 Providers, <a href="http://reports.panopta.com/lg">3rd Party Monitoring</a> of our uplinks to our Internet Service Providers, and the ability to <a href="http://lg.sliqua.net/smokeping/tr.html">Traceroute to remote addresses</a> to see our performance for yourself.</p>
  225. <p><strong>This is a big milestone in Sliqua&#8217;s history</strong><br />
  226. We hope that you enjoy the new network performance as much as we do. It has been a long time coming, and we&#8217;ve finally hit this milestone.</p>
  227. ]]></content:encoded>
  228. </item>
  229. <item>
  230. <title>Sliqua Enterprise Hosting Joins the R1Soft Hosting Partner Program</title>
  231. <link>https://www.isyourmissioncritical.com/press/sliqua-enterprise-hosting-joins-the-r1soft-hosting-partner-program/</link>
  232. <comments>https://www.isyourmissioncritical.com/press/sliqua-enterprise-hosting-joins-the-r1soft-hosting-partner-program/#respond</comments>
  233. <pubDate>Wed, 16 Dec 2009 19:20:37 +0000</pubDate>
  234. <dc:creator><![CDATA[Alexander McMillen]]></dc:creator>
  235. <category><![CDATA[Press]]></category>
  236.  
  237. <guid isPermaLink="false">http://www.isyourmissioncritical.com/?p=139</guid>
  238. <description><![CDATA[<strong><a style="color: #333333; text-decoration: underline;" href="http://www.sliqua.com/index.html">Sliqua</a>, a provider of custom hosting solutions, today announced it has enrolled in the <a style="color: #333333; text-decoration: underline;" href="http://www.r1soft.com/hosting-partners/">R1Soft Hosting Partner Program</a> (R1HPP) to qualify for aggressive volume discounts on R1Soft <a style="color: #333333; text-decoration: underline;" href="http://www.r1soft.com/product-overview/">Continuous Data Protection</a>® (CDP) products.</strong>
  239.  
  240. R1HPP volume license discounts enable Sliqua to offer its Enterprise Shared Hosting customers reliable data protection with a two-week backup retention free of charge. Sliqua Complex Hosting customers benefit from the discounts as well with the option to add CDP for a low fee. As an R1Soft Hosting Partner, Sliqua also acquires access to priority technical support and an assortment of sales and marketing resources to help it effectively market and implement R1Soft CDP software.
  241.  
  242. Sliqua uses R1Soft’s high-performance, disk to disk backup software to protect its customers Linux servers and MySQL databases with consistent, hourly backups and bare-metal restore capabilities. In the event of a disaster, Sliqua can rapidly restore the customers’ websites within minutes from the last point-in-time snapshot of the website data. R1Soft CDP technology allows Sliqua to perform real-time, table-level restores of MySQL databases.
  243.  
  244. “Sliqua’s customer base largely consists of bloggers and businesses that rely on their website as a primary source of income, so we needed a solid data protection strategy that would provide our customers with hourly backups of their critical data. We also needed a solution that uses minimal server resources. R1Soft’s overhead for the backup processes is so low we don’t even notice that R1Soft is running in the background, it just works,” said Alexander McMillen, President and CEO of Sliqua.
  245.  
  246. Since offering R1Soft, Sliqua has received plenty of positive feedback from customers who can appreciate the importance of having reliable backups available.
  247.  
  248. “R1Soft has gotten me out of a jam more times than I can count. There is nothing like the peace of mind you have when you know all of your valuable data is there and ready if the worst should happen, or you break your code,” said Sliqua customer Robb Sutton of RobbSutton.com.
  249.  
  250. <strong>About Sliqua Enterprise Hosting</strong>
  251.  
  252. Providing hosting solutions since 2002, Sliqua is committed to dedicating the time and resources to help its clients achieve success online. Sliqua also maintains a strong dedication to customer service. With resources available to scale your website without downtime and offering multiple mediums of support beyond email, Sliqua is ready to assist you 24x7. Sliqua also ensures a consistent customer experience with a board of directors that works side-by-side with technical support representatives.]]></description>
  253. <content:encoded><![CDATA[<p><strong><a style="color: #333333; text-decoration: underline;" href="http://www.sliqua.com/index.html">Sliqua</a>, a provider of custom hosting solutions, today announced it has enrolled in the <a style="color: #333333; text-decoration: underline;" href="http://www.r1soft.com/hosting-partners/">R1Soft Hosting Partner Program</a> (R1HPP) to qualify for aggressive volume discounts on R1Soft <a style="color: #333333; text-decoration: underline;" href="http://www.r1soft.com/product-overview/">Continuous Data Protection</a>® (CDP) products.</strong></p>
  254. <p>R1HPP volume license discounts enable Sliqua to offer its Enterprise Shared Hosting customers reliable data protection with a two-week backup retention free of charge. Sliqua Complex Hosting customers benefit from the discounts as well with the option to add CDP for a low fee. As an R1Soft Hosting Partner, Sliqua also acquires access to priority technical support and an assortment of sales and marketing resources to help it effectively market and implement R1Soft CDP software.</p>
  255. <p>Sliqua uses R1Soft’s high-performance, disk to disk backup software to protect its customers Linux servers and MySQL databases with consistent, hourly backups and bare-metal restore capabilities. In the event of a disaster, Sliqua can rapidly restore the customers’ websites within minutes from the last point-in-time snapshot of the website data. R1Soft CDP technology allows Sliqua to perform real-time, table-level restores of MySQL databases.</p>
  256. <p>“Sliqua’s customer base largely consists of bloggers and businesses that rely on their website as a primary source of income, so we needed a solid data protection strategy that would provide our customers with hourly backups of their critical data. We also needed a solution that uses minimal server resources. R1Soft’s overhead for the backup processes is so low we don’t even notice that R1Soft is running in the background, it just works,” said Alexander McMillen, President and CEO of Sliqua.</p>
  257. <p>Since offering R1Soft, Sliqua has received plenty of positive feedback from customers who can appreciate the importance of having reliable backups available.</p>
  258. <p>“R1Soft has gotten me out of a jam more times than I can count. There is nothing like the peace of mind you have when you know all of your valuable data is there and ready if the worst should happen, or you break your code,” said Sliqua customer Robb Sutton of RobbSutton.com.</p>
  259. <p><strong>About Sliqua Enterprise Hosting</strong></p>
  260. <p>Providing hosting solutions since 2002, Sliqua is committed to dedicating the time and resources to help its clients achieve success online. Sliqua also maintains a strong dedication to customer service. With resources available to scale your website without downtime and offering multiple mediums of support beyond email, Sliqua is ready to assist you 24&#215;7. Sliqua also ensures a consistent customer experience with a board of directors that works side-by-side with technical support representatives.</p>
  261. ]]></content:encoded>
  262. <wfw:commentRss>https://www.isyourmissioncritical.com/press/sliqua-enterprise-hosting-joins-the-r1soft-hosting-partner-program/feed/</wfw:commentRss>
  263. <slash:comments>0</slash:comments>
  264. </item>
  265. <item>
  266. <title>What is the Sliqua Server Environment?</title>
  267. <link>https://www.isyourmissioncritical.com/sliqua-server-environment/what-is-the-sliqua-server-environment/</link>
  268. <comments>https://www.isyourmissioncritical.com/sliqua-server-environment/what-is-the-sliqua-server-environment/#respond</comments>
  269. <pubDate>Wed, 11 Nov 2009 15:30:22 +0000</pubDate>
  270. <dc:creator><![CDATA[Alexander McMillen]]></dc:creator>
  271. <category><![CDATA[Sliqua Server Environment]]></category>
  272. <category><![CDATA[anycast]]></category>
  273. <category><![CDATA[DNS]]></category>
  274. <category><![CDATA[InterWorx]]></category>
  275. <category><![CDATA[memcached]]></category>
  276. <category><![CDATA[modsecurity]]></category>
  277. <category><![CDATA[php]]></category>
  278. <category><![CDATA[r1soft]]></category>
  279. <category><![CDATA[ruby on rails]]></category>
  280. <category><![CDATA[simplescripts]]></category>
  281.  
  282. <guid isPermaLink="false">http://www.isyourmissioncritical.com/?p=117</guid>
  283. <description><![CDATA[Sliqua Server Environment is a highly customized version of CentOS, the enterprise-grade Linux distribution our servers have been running for years. The Sliqua Labs team has been working diligently on this project for a few months, and have finally put it into production across-the-board with the release of CentOS 5.4 and InterWorx 4.1.
  284.  
  285. <strong>What features are provided for me?</strong>
  286. <ul>
  287. <li><strong>InterWorx 4.1</strong> - The most reliable hosting control panel in the industry. With a proven track record, InterWorx has delivered a highly reliable and secure platform for managing websites and servers. The 4.x upgrade adds many features, including a "snappier" web interface driven by AJAX (an emerging Web 2.0 technology).</li>
  288. <li><strong>SimpleScripts</strong> - A streamlined one-click installer for blogs, photo galleries, forums, and more. From within our SiteWorx control panel, you can install open source scripts, and upgrade them with ease.</li>
  289. <li><strong>Hardened PHP 5.2</strong> - This was a tough move for us to make, as we are strong believers in the nature of Enterprise Linux, which simply back-ports security updates. However, due to popular demand from customers, we have made the leap to PHP 5.2. Our hardened PHP packages are maintained in-house, and include the Suhosin hardening patch and extensions. As with our previous release, PHP executes as the user, within a jailed chroot environment.</li>
  290. <li><strong>Memcached</strong> - We have included memcached as a part of this release, after seeing it's production use on sites like Facebook. Memcached gives our customers the ability to accelerate their websites with a second layer of caching beyond MySQL. Using extensions such as W3 Total Cache in Wordpress, some customers can cut their website load times in half, by caching their Database Queries in memory.</li>
  291. <li><strong>Ruby on Rails</strong> - We have included Ruby Enterprise Edition, Rails, and Phusion Passenger as a part of this release. Ruby on Rails is a web application framework that's optimized for programmer happiness and sustainable productivity.</li>
  292. <li><strong>ModSecurity</strong> - We have included a new series of ModSecurity rulesets, with streamlined updates, to protect your websites against the latest web application attacks. This is our second layer of web application protection, beyond what the Suhosin Patch and Extension can provide.</li>
  293. <li><strong>R1Soft Hourly Incremental Backups</strong>- Our backup systems automatically backup your data hourly (at the block-level), with two week data retention. For our shared hosting customers, we also backup MySQL databases at the table-level every hour. This ensures we can quickly, and reliably restore your website to any hour in the last two weeks.</li>
  294. <li><strong>Configuration Consistency</strong> - With the release of Sliqua Server Environment, we are now able to streamline package and configuration updates, with our latest performance and security optimizations. The update process is entirely scripted and change logs for each server are maintained to ensure consistency. An added benefit is that we eliminate the chance of problems during upgrades and migrations between servers.</li>
  295. <li><strong>Anycast DNS</strong> - This isn't a new feature, but is worth mentioning. We host your domains' DNS off-site on a global Anycast DNS network. Unlike most providers, we host all of our DNS services in this fashion, to provide instant DNS scalability, and eliminate downtime.</li>
  296. </ul>
  297. <strong>
  298. How do I get Sliqua Server Environment?</strong>
  299.  
  300. If your website is hosted on a Shared Hosting or Managed Hosting plan, you're already running on the Sliqua Server Environment. If not, <a href="http://www.sliqua.com/started.html">contact us</a> to find out how Sliqua Server Environment can help your website strive online.
  301.  
  302. As always, we appreciate your business and will continue to develop ways to better serve you.
  303.  
  304. <em>The Sliqua Labs Team</em>
  305. Alexander McMillen, Joe Cooter, Jeff Johnston, Amin Murad
  306. <a href="mailto:support@sliqua.com?subject=Sliqua%20Server%20Environment">support@sliqua.com</a>]]></description>
  307. <content:encoded><![CDATA[<p>Sliqua Server Environment is a highly customized version of CentOS, the enterprise-grade Linux distribution our servers have been running for years. The Sliqua Labs team has been working diligently on this project for a few months, and have finally put it into production across-the-board with the release of CentOS 5.4 and InterWorx 4.1.</p>
  308. <p><strong>What features are provided for me?</strong></p>
  309. <ul>
  310. <li><strong>InterWorx 4.1</strong> &#8211; The most reliable hosting control panel in the industry. With a proven track record, InterWorx has delivered a highly reliable and secure platform for managing websites and servers. The 4.x upgrade adds many features, including a &#8220;snappier&#8221; web interface driven by AJAX (an emerging Web 2.0 technology).</li>
  311. <li><strong>SimpleScripts</strong> &#8211; A streamlined one-click installer for blogs, photo galleries, forums, and more. From within our SiteWorx control panel, you can install open source scripts, and upgrade them with ease.</li>
  312. <li><strong>Hardened PHP 5.2</strong> &#8211; This was a tough move for us to make, as we are strong believers in the nature of Enterprise Linux, which simply back-ports security updates. However, due to popular demand from customers, we have made the leap to PHP 5.2. Our hardened PHP packages are maintained in-house, and include the Suhosin hardening patch and extensions. As with our previous release, PHP executes as the user, within a jailed chroot environment.</li>
  313. <li><strong>Memcached</strong> &#8211; We have included memcached as a part of this release, after seeing it&#8217;s production use on sites like Facebook. Memcached gives our customers the ability to accelerate their websites with a second layer of caching beyond MySQL. Using extensions such as W3 Total Cache in WordPress, some customers can cut their website load times in half, by caching their Database Queries in memory.</li>
  314. <li><strong>Ruby on Rails</strong> &#8211; We have included Ruby Enterprise Edition, Rails, and Phusion Passenger as a part of this release. Ruby on Rails is a web application framework that&#8217;s optimized for programmer happiness and sustainable productivity.</li>
  315. <li><strong>ModSecurity</strong> &#8211; We have included a new series of ModSecurity rulesets, with streamlined updates, to protect your websites against the latest web application attacks. This is our second layer of web application protection, beyond what the Suhosin Patch and Extension can provide.</li>
  316. <li><strong>R1Soft Hourly Incremental Backups</strong>&#8211; Our backup systems automatically backup your data hourly (at the block-level), with two week data retention. For our shared hosting customers, we also backup MySQL databases at the table-level every hour. This ensures we can quickly, and reliably restore your website to any hour in the last two weeks.</li>
  317. <li><strong>Configuration Consistency</strong> &#8211; With the release of Sliqua Server Environment, we are now able to streamline package and configuration updates, with our latest performance and security optimizations. The update process is entirely scripted and change logs for each server are maintained to ensure consistency. An added benefit is that we eliminate the chance of problems during upgrades and migrations between servers.</li>
  318. <li><strong>Anycast DNS</strong> &#8211; This isn&#8217;t a new feature, but is worth mentioning. We host your domains&#8217; DNS off-site on a global Anycast DNS network. Unlike most providers, we host all of our DNS services in this fashion, to provide instant DNS scalability, and eliminate downtime.</li>
  319. </ul>
  320. <p><strong><br />
  321. How do I get Sliqua Server Environment?</strong></p>
  322. <p>If your website is hosted on a Shared Hosting or Managed Hosting plan, you&#8217;re already running on the Sliqua Server Environment. If not, <a href="http://www.sliqua.com/started.html">contact us</a> to find out how Sliqua Server Environment can help your website strive online.</p>
  323. <p>As always, we appreciate your business and will continue to develop ways to better serve you.</p>
  324. <p><em>The Sliqua Labs Team</em><br />
  325. Alexander McMillen, Joe Cooter, Jeff Johnston, Amin Murad<br />
  326. 1-877-4-SLIQUA / Intl: 1-703-621-4813<br />
  327. <a href="mailto:support@sliqua.com?subject=Sliqua%20Server%20Environment">support@sliqua.com</a></p>
  328. ]]></content:encoded>
  329. <wfw:commentRss>https://www.isyourmissioncritical.com/sliqua-server-environment/what-is-the-sliqua-server-environment/feed/</wfw:commentRss>
  330. <slash:comments>0</slash:comments>
  331. </item>
  332. <item>
  333. <title>Outage on 10/14/09</title>
  334. <link>https://www.isyourmissioncritical.com/customers/outage-on-101409/</link>
  335. <comments>https://www.isyourmissioncritical.com/customers/outage-on-101409/#respond</comments>
  336. <pubDate>Wed, 14 Oct 2009 05:07:20 +0000</pubDate>
  337. <dc:creator><![CDATA[Joe Cooter]]></dc:creator>
  338. <category><![CDATA[Customers]]></category>
  339. <category><![CDATA[Outages]]></category>
  340. <category><![CDATA[Services]]></category>
  341. <category><![CDATA[Support]]></category>
  342. <category><![CDATA[disruption]]></category>
  343. <category><![CDATA[network]]></category>
  344. <category><![CDATA[outage]]></category>
  345.  
  346. <guid isPermaLink="false">http://www.isyourmissioncritical.com/?p=115</guid>
  347. <description><![CDATA[On Wednesday, October 14, 2009, at approximately 12:09 AM, we experienced a network outage affecting all customers. Both our primary and backup core router experienced full loss of connectivity. At or around 12:10 AM, our monitoring system alerted us to the network outage, and an investigation was launched to determine the root cause. It was determined by our on-site technician to be an upstream outage that affected their entire network. At or around 12:10 AM, a technician from the upstream provider was dispatched to the site of the outage to correct the issue.
  348.  
  349. At approximately 12:12 AM, the technicians arrived on-site and began diagnostic work on the routers to determine the root cause of the issue. At approximately 12:15 AM, full service was restored.
  350.  
  351. We do not expect any further outages, and have received assurances from our upstream provider that the issue has been corrected. We apologize to all of our customers affected, and promise that we will take every reasonable measure to insure this doesn’t happen again.
  352.  
  353. If you have questions about this, or any other outage - please contact us by emailing support@sliqua.com, or calling our main support line at (877) 475-4782.]]></description>
  354. <content:encoded><![CDATA[<p>On Wednesday, October 14, 2009, at approximately 12:09 AM, we experienced a network outage affecting all customers. Both our primary and backup core router experienced full loss of connectivity. At or around 12:10 AM, our monitoring system alerted us to the network outage, and an investigation was launched to determine the root cause. It was determined by our on-site technician to be an upstream outage that affected their entire network. At or around 12:10 AM, a technician from the upstream provider was dispatched to the site of the outage to correct the issue.</p>
  355. <p>At approximately 12:12 AM, the technicians arrived on-site and began diagnostic work on the routers to determine the root cause of the issue. At approximately 12:15 AM, full service was restored. </p>
  356. <p>We do not expect any further outages, and have received assurances from our upstream provider that the issue has been corrected. We apologize to all of our customers affected, and promise that we will take every reasonable measure to insure this doesn’t happen again.</p>
  357. <p>If you have questions about this, or any other outage &#8211; please contact us by emailing support@sliqua.com, or calling our main support line at (877) 475-4782.</p>
  358. ]]></content:encoded>
  359. <wfw:commentRss>https://www.isyourmissioncritical.com/customers/outage-on-101409/feed/</wfw:commentRss>
  360. <slash:comments>0</slash:comments>
  361. </item>
  362. <item>
  363. <title>Choosing a Reliable Hosting Company for your Blog</title>
  364. <link>https://www.isyourmissioncritical.com/uncategorized/choosing-a-reliable-hosting-company-for-your-blog/</link>
  365. <comments>https://www.isyourmissioncritical.com/uncategorized/choosing-a-reliable-hosting-company-for-your-blog/#respond</comments>
  366. <pubDate>Tue, 25 Aug 2009 13:07:46 +0000</pubDate>
  367. <dc:creator><![CDATA[Alexander McMillen]]></dc:creator>
  368. <category><![CDATA[Uncategorized]]></category>
  369.  
  370. <guid isPermaLink="false">http://www.isyourmissioncritical.com/?p=112</guid>
  371. <description><![CDATA[It's always a good day when customers decide to write testimonials or blog posts about their hosting experiences with Sliqua. Robb Sutton switched to Sliqua Enterprise Hosting due to excessive downtime for his blog network (<a href="http://www.oneninety8.com" target="_blank">OneNinety8</a>) while hosted at a competitor. As a part of the migration process, we moved eight websites for him, same-day without any downtime. Since switching to Sliqua, he's experienced faster page loads and a more personal hosting experience. His testimonial and <a href="http://www.mtbtrailreview.com/blog/" target="_blank">MTB Trail Review</a> are featured on the new <a href="http://www.sliqua.com" target="_self">Sliqua.com</a>.
  372.  
  373. “After trying what felt like all of the so-called reliable hosting services online, I finally hooked up with Sliqua and now I no longer have to worry about my hosting or lost revenue due to down time. They have been perfect from day 1 with top notch support that can not be matched. I have found my last hosting company.”
  374.  
  375. --Robb Sutton, OneNinety8, Hosted since 2009
  376.  
  377. We highly recommend reading his blog post, entitled "<a href="http://robbsutton.com/choosing-a-reliable-hosting-company-for-your-blog/" target="_blank">Choosing a Reliable Hosting Company for your Blog</a>."]]></description>
  378. <content:encoded><![CDATA[<p>It&#8217;s always a good day when customers decide to write testimonials or blog posts about their hosting experiences with Sliqua. Robb Sutton switched to Sliqua Enterprise Hosting due to excessive downtime for his blog network (<a href="http://www.oneninety8.com" target="_blank">OneNinety8</a>) while hosted at a competitor. As a part of the migration process, we moved eight websites for him, same-day without any downtime. Since switching to Sliqua, he&#8217;s experienced faster page loads and a more personal hosting experience. His testimonial and <a href="http://www.mtbtrailreview.com/blog/" target="_blank">MTB Trail Review</a> are featured on the new <a href="http://www.sliqua.com" target="_self">Sliqua.com</a>.</p>
  379. <p>“After trying what felt like all of the so-called reliable hosting services online, I finally hooked up with Sliqua and now I no longer have to worry about my hosting or lost revenue due to down time. They have been perfect from day 1 with top notch support that can not be matched. I have found my last hosting company.”</p>
  380. <p>&#8211;Robb Sutton, OneNinety8, Hosted since 2009</p>
  381. <p>We highly recommend reading his blog post, entitled &#8220;<a href="http://robbsutton.com/choosing-a-reliable-hosting-company-for-your-blog/" target="_blank">Choosing a Reliable Hosting Company for your Blog</a>.&#8221;</p>
  382. ]]></content:encoded>
  383. <wfw:commentRss>https://www.isyourmissioncritical.com/uncategorized/choosing-a-reliable-hosting-company-for-your-blog/feed/</wfw:commentRss>
  384. <slash:comments>0</slash:comments>
  385. </item>
  386. <item>
  387. <title>We are moving to a new datacenter!</title>
  388. <link>https://www.isyourmissioncritical.com/outages/new-datacenter/</link>
  389. <comments>https://www.isyourmissioncritical.com/outages/new-datacenter/#respond</comments>
  390. <pubDate>Fri, 24 Jul 2009 13:11:12 +0000</pubDate>
  391. <dc:creator><![CDATA[Alexander McMillen]]></dc:creator>
  392. <category><![CDATA[Outages]]></category>
  393.  
  394. <guid isPermaLink="false">http://www.isyourmissioncritical.com/?p=93</guid>
  395. <description><![CDATA[<strong>We will be moving all customer equipment into a new Tier III+ datacenter in Ashburn, VA.</strong>
  396.  
  397. As always, if you have any questions or concerns, please do not hesitate to contact us. We are available at +1-703-621-4813, send us a <a style="color: #ae4700; text-decoration: underline; font-weight: normal;" href="http://twitter.com/sliqua">Twitter message</a>, or open a support ticket by e-mailing <a style="color: #ae4700; text-decoration: underline; font-weight: normal;" href="mailto:support@sliqua.com">support@sliqua.com</a>.
  398.  
  399. -----
  400. <strong>Start Date: Saturday , July 25, 2009; 11:59 PM (EDT)
  401. End Date: Sunday, July 26, 2009; 02:00 AM (EDT)</strong>
  402.  
  403. <em>Locations:</em> RES1 (11513 Sunset Hills Rd, Reston, Virginia 20190) and IAD1 (21635 Red Rum Dr. Ashburn, VA 20147)
  404.  
  405. <em>Summary of Work:</em> We will be physically moving all customer equipment from RES1 to IAD1. All network configurations will stay the same.
  406.  
  407. <em>Impact:</em> Due to the nature of physical server migrations, we will experience an extended outage. This outage will affect all Shared, Virtual Private, Dedicated and Co-location servers.
  408.  
  409. We expect this outage to affect all hosting customers for no more than two hours. During this time, we will have an experienced team of 5 systems administrators transporting all of our customer equipment between facilities in an efficient manner. Please be aware that while we are expecting the outage to be under two hours, we've built in an extra hour in the event something doesn't go according to plan.
  410.  
  411. During this outage, the following services will remain available to customers: IP Transit, Postini, Clustered Email, Phone and E-mail Support. All other services will be inaccessible.
  412.  
  413. We recommend that customers concerned about the outage <a style="color: #ae4700; text-decoration: underline; font-weight: normal;" href="http://twitter.com/sliqua">follow us on Twitter</a>, as we will be posting updates throughout the migration.
  414.  
  415. Regards,
  416. Sliqua Network Operations
  417. +1-703-621-4813
  418. <a style="color: #ae4700; text-decoration: underline; font-weight: normal;" href="mailto:noc@sliqua.com?subject=RES1%20Follow-up">noc@sliqua.com</a>
  419. Twitter <a style="color: #ae4700; text-decoration: underline; font-weight: normal;" href="http://twitter.com/sliqua">@sliqua</a>]]></description>
  420. <content:encoded><![CDATA[<p><strong>We will be moving all customer equipment into a new Tier III+ datacenter in Ashburn, VA.</strong></p>
  421. <p>As always, if you have any questions or concerns, please do not hesitate to contact us. We are available at +1-703-621-4813, send us a <a style="color: #ae4700; text-decoration: underline; font-weight: normal;" href="http://twitter.com/sliqua">Twitter message</a>, or open a support ticket by e-mailing <a style="color: #ae4700; text-decoration: underline; font-weight: normal;" href="mailto:support@sliqua.com">support@sliqua.com</a>.</p>
  422. <p>&#8212;&#8211;<br />
  423. <strong>Start Date: Saturday , July 25, 2009; 11:59 PM (EDT)<br />
  424. End Date: Sunday, July 26, 2009; 02:00 AM (EDT)</strong></p>
  425. <p><em>Locations:</em> RES1 (11513 Sunset Hills Rd, Reston, Virginia 20190) and IAD1 (21635 Red Rum Dr. Ashburn, VA 20147)</p>
  426. <p><em>Summary of Work:</em> We will be physically moving all customer equipment from RES1 to IAD1. All network configurations will stay the same.</p>
  427. <p><em>Impact:</em> Due to the nature of physical server migrations, we will experience an extended outage. This outage will affect all Shared, Virtual Private, Dedicated and Co-location servers.</p>
  428. <p>We expect this outage to affect all hosting customers for no more than two hours. During this time, we will have an experienced team of 5 systems administrators transporting all of our customer equipment between facilities in an efficient manner. Please be aware that while we are expecting the outage to be under two hours, we&#8217;ve built in an extra hour in the event something doesn&#8217;t go according to plan.</p>
  429. <p>During this outage, the following services will remain available to customers: IP Transit, Postini, Clustered Email, Phone and E-mail Support. All other services will be inaccessible.</p>
  430. <p>We recommend that customers concerned about the outage <a style="color: #ae4700; text-decoration: underline; font-weight: normal;" href="http://twitter.com/sliqua">follow us on Twitter</a>, as we will be posting updates throughout the migration.</p>
  431. <p>Regards,<br />
  432. Sliqua Network Operations<br />
  433. +1-703-621-4813<br />
  434. <a style="color: #ae4700; text-decoration: underline; font-weight: normal;" href="mailto:noc@sliqua.com?subject=RES1%20Follow-up">noc@sliqua.com</a><br />
  435. Twitter <a style="color: #ae4700; text-decoration: underline; font-weight: normal;" href="http://twitter.com/sliqua">@sliqua</a></p>
  436. ]]></content:encoded>
  437. <wfw:commentRss>https://www.isyourmissioncritical.com/outages/new-datacenter/feed/</wfw:commentRss>
  438. <slash:comments>0</slash:comments>
  439. </item>
  440. <item>
  441. <title>Announcement: Scheduled Maintenance on 5/16/09</title>
  442. <link>https://www.isyourmissioncritical.com/customers/announcement-scheduled-maintenance-on-51609/</link>
  443. <comments>https://www.isyourmissioncritical.com/customers/announcement-scheduled-maintenance-on-51609/#respond</comments>
  444. <pubDate>Thu, 14 May 2009 21:38:47 +0000</pubDate>
  445. <dc:creator><![CDATA[Joe Cooter]]></dc:creator>
  446. <category><![CDATA[Customers]]></category>
  447. <category><![CDATA[Outages]]></category>
  448. <category><![CDATA[Services]]></category>
  449. <category><![CDATA[Support]]></category>
  450. <category><![CDATA[hardware]]></category>
  451. <category><![CDATA[network]]></category>
  452. <category><![CDATA[routers]]></category>
  453. <category><![CDATA[scheduled maintenance]]></category>
  454.  
  455. <guid isPermaLink="false">http://www.isyourmissioncritical.com/?p=87</guid>
  456. <description><![CDATA[We're announcing a scheduled maintenance window on Saturday, May 16, 2009 from 1 - 3AM EDT <strong>(Note: This was mistakenly reported as EST in our email to customers)</strong>.  The maintenance window is a direct response to <a href="http://www.isyourmissioncritical.com/customers/sliqua-outage-on-5309/">our network outage on 5/3</a>.  During the window we'll be replacing our core routers, and (if time permits) performing some additional server maintenance.  Realistically, we expect individual outages to be about 15 minutes, and the entire process to take about an hour.  We've built in an additional hour in the event that something doesn't go according to plan (hope for the best, prepare for the worst kinda thing).  Below is the full maintenance description that was sent out to our clients:
  457.  
  458. <strong>Start Date:</strong> Saturday, May 16, 2009; 01:00 AM <strong>(EDT - reported incorrectly as EST in the email)</strong>
  459.  
  460. <strong>End Date:</strong> Saturday, May 16, 2009; 03:00 AM <strong>(EDT - reported incorrectly as EST in the email)</strong>
  461.  
  462. <strong>Locations:</strong> RES1 (11513 Sunset Hills Rd, Reston, Virginia)
  463.  
  464. <strong>Summary of Work: </strong>We will be replacing our current core network infrastructure with two new routers which we have been burning-in for the last week. These replacements were purchased in response to our outage on 5/3/09. We hope that this upgrade will allow us to provide a more stable hosting environment for your business. This process is fully scripted and should take about an hour to complete. However, due to the implications of replacing routers, we have scheduled an extra hour in this window.
  465.  
  466. If the router maintenance is a success, we will also perform some routine server maintenance tasks including some server reboots to prevent long FSCK (file system checks) in the future.
  467.  
  468. <strong>Impact:</strong> Sliqua server and hosting customers will experience an outage during the maintenance window, as we will be replacing our core routers and possibly rebooting servers. If the maintenance goes successfully, all services will be back online within about an hour. We apologize for any inconvenience this might cause. IP Transit, Postini and Clustered Mail customers will not experience any outages during this period.
  469.  
  470. Best Regards,
  471. Sliqua Network Operations
  472. +1-703-621-4813 x0
  473. <a href="mailto:noc@sliqua.com">noc@sliqua.com</a>
  474. Twitter: <a href="http://www.twitter.com/sliqua">@sliqua</a>]]></description>
  475. <content:encoded><![CDATA[<p>We&#8217;re announcing a scheduled maintenance window on Saturday, May 16, 2009 from 1 &#8211; 3AM EDT <strong>(Note: This was mistakenly reported as EST in our email to customers)</strong>.  The maintenance window is a direct response to <a href="http://www.isyourmissioncritical.com/customers/sliqua-outage-on-5309/">our network outage on 5/3</a>.  During the window we&#8217;ll be replacing our core routers, and (if time permits) performing some additional server maintenance.  Realistically, we expect individual outages to be about 15 minutes, and the entire process to take about an hour.  We&#8217;ve built in an additional hour in the event that something doesn&#8217;t go according to plan (hope for the best, prepare for the worst kinda thing).  Below is the full maintenance description that was sent out to our clients:</p>
  476. <p><strong>Start Date:</strong> Saturday, May 16, 2009; 01:00 AM <strong>(EDT &#8211; reported incorrectly as EST in the email)</strong></p>
  477. <p><strong>End Date:</strong> Saturday, May 16, 2009; 03:00 AM <strong>(EDT &#8211; reported incorrectly as EST in the email)</strong></p>
  478. <p><strong>Locations:</strong> RES1 (11513 Sunset Hills Rd, Reston, Virginia)</p>
  479. <p><strong>Summary of Work: </strong>We will be replacing our current core network infrastructure with two new routers which we have been burning-in for the last week. These replacements were purchased in response to our outage on 5/3/09. We hope that this upgrade will allow us to provide a more stable hosting environment for your business. This process is fully scripted and should take about an hour to complete. However, due to the implications of replacing routers, we have scheduled an extra hour in this window.</p>
  480. <p>If the router maintenance is a success, we will also perform some routine server maintenance tasks including some server reboots to prevent long FSCK (file system checks) in the future.</p>
  481. <p><strong>Impact:</strong> Sliqua server and hosting customers will experience an outage during the maintenance window, as we will be replacing our core routers and possibly rebooting servers. If the maintenance goes successfully, all services will be back online within about an hour. We apologize for any inconvenience this might cause. IP Transit, Postini and Clustered Mail customers will not experience any outages during this period.</p>
  482. <p>Best Regards,<br />
  483. Sliqua Network Operations<br />
  484. +1-703-621-4813 x0<br />
  485. <a href="mailto:noc@sliqua.com">noc@sliqua.com</a><br />
  486. Twitter: <a href="http://www.twitter.com/sliqua">@sliqua</a></p>
  487. ]]></content:encoded>
  488. <wfw:commentRss>https://www.isyourmissioncritical.com/customers/announcement-scheduled-maintenance-on-51609/feed/</wfw:commentRss>
  489. <slash:comments>0</slash:comments>
  490. </item>
  491. </channel>
  492. </rss>
  493.  
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda