<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:bladenode.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://bladenode.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://bladenode.instatus.com/history.atom"/>
  <title>BladeNode.com Status - Incident history</title>
  <updated>2022-10-26T18:00:00.000+00:00</updated>
  <author>
    <name>BladeNode.com</name>
  </author>
  
<entry>
  <id>tag:bladenode.instatus.com,2005:Maintenance/cl9n4w85y20839uoqykj2qpsb</id>
  <published>2022-10-26T18:00:00.000+00:00</published>
  <updated>2022-10-28T05:34:10.268+00:00</updated>
  <link rel="alternate" type="text/html" href="https://bladenode.instatus.com/maintenance/cl9n4w85y20839uoqykj2qpsb"/>
  <title>EMERGENCY MIGRATION 10/24/22 CAB DAL.1400</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day, 11 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> Intel KVM Node 01 - Dallas, TX USA</p>
    <p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>05:34:10</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Due to an urgent cooling situation at our DC 1 in Dallas, TX, we have scheduled an emergency migration for October 26th. This migration will start at 2:00 PM Dallas Time and is expected to be ongoing until 12:00 AM on October 27th. 

The goal of this migration is to move all hardware from cabinet DAL.1400 to a new datacenter nearby. We are extremely sorry for any inconvenience this may cause. 

We migrated cabinet DAL.1300 just a couple months ago in anticipation of the situation worsening. That cabinet will remain unaffected at this time and there will be no disruption to service with that cabinet. 

Please do open a ticket with any questions or concerns you may have. Thank you.

- BladeNode Team.</p>
<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>18:11:19</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware of the ongoing maintenance that is behind schedule. Unfortunately, we have encountered a few obstacles in this migration, but we have narrowed the issues to just network issues. We are actively working with the datacenter to resolve the final issue. We appreciate your patience..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:bladenode.instatus.com,2005:Incident/cl2ht2fyj983636gpohis56u8h2</id>
  <published>2022-04-27T16:42:39.848+00:00</published>
  <updated>2022-04-27T20:21:59.083+00:00</updated>
  <link rel="alternate" type="text/html" href="https://bladenode.instatus.com/incident/cl2ht2fyj983636gpohis56u8h2"/>
  <title>Recent Texas downtime 4-27-2022</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> Intel KVM Node 01 - Dallas, TX USA</p>
    <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>20:21:59</var> GMT+0</small><br /><strong>Resolved</strong> -
  We just resolved the issue!.</p>
<p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>16:42:39</var> GMT+0</small><br /><strong>Investigating</strong> -
   We are aware of this and doing everything we can to resolve the issue as quickly as we can. One of our main Nodes in Dalles texas is having major issues. We are working with the data center to come up with a solution. At this time we do not have a projected time frame one when this will get resolved. We apologize for the inconvenience and thank you for understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:bladenode.instatus.com,2005:Maintenance/cl1oc215u1253624ftnck4ipviep</id>
  <published>2022-04-07T01:36:19.356+00:00</published>
  <updated>2022-12-04T10:22:54.209+00:00</updated>
  <link rel="alternate" type="text/html" href="https://bladenode.instatus.com/maintenance/cl1oc215u1253624ftnck4ipviep"/>
  <title>Core Website &amp; scheduled maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 29 days, 8 hours and 47 minutes</p>
    <p><strong>Affected Components:</strong> BladeNode.com - Website, Client Portal</p>
    <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>10:22:54</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>01:36:19</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for scheduled maintenance during that time. We are going to be working on the client portal and the website. Bladenode.com and portal.bladenod.com might go down for a few hours. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:bladenode.instatus.com,2005:Maintenance/ckos5pf61165683076mzge339u03</id>
  <published>2021-05-21T06:00:00.000+00:00</published>
  <updated>2021-05-22T10:12:35.318+00:00</updated>
  <link rel="alternate" type="text/html" href="https://bladenode.instatus.com/maintenance/ckos5pf61165683076mzge339u03"/>
  <title>(Rescheduled)TX-Semi01,TX-Semi01, and NY-Shared01 Migration to TX-Shared01</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day, 4 hours and 13 minutes</p>
    
    <p><small>May <var data-var='date'> 22</var>, <var data-var='time'>10:12:35</var> GMT+0</small><br /><strong>Completed</strong> -
  migration has been completed successfully. Please allow 24 - 48 hours for your websites to propagate. If you have any questions please contact us. 

Thank you. .</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>05:08:03</var> GMT+0</small><br /><strong>Identified</strong> -
  **migration** is now in progress. Please do not add,edit, or delete your websites. .</p>
<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  ***We Are having some issues with one of the servers. We have rescheduled the migration for 05/21/2021 at 23:00 (11:00 PM)***

We have decided to migrate our shared hosting servers to our Texas data center. **On May 21, 2021, @ 23:00,** we will migrate all accounts from TX-Semi01, TX-Semi01, and NY-Shared01 to TX-Shared01. Our TX-Semi01, TX-Semi01, and NY-Shared01 servers have outgrown themselves and no longer can accept any more accounts. In the past 60 days, we have seen a performance decline and no longer can be used.

This migration will vastly improve our service to our clients. Also, on top of that, TX-Shared01 will have almost twice the number of resources as the old servers combined, allowing us to expand for future growth and development of the company.

We will start the migration by moving all websites and domains to our TX-Shared01 server on May 121, 2021, @ 23:00 {11:30 PM EST}.

The migration will take around 6 hours to complete. Please make sure you have your domain pointed to the Nameservers below on the date of the migration. Please also allow 24 to 48 hours for your domain to propagate to the new server.

If you have already indicated your domains to the nameservers below, then no further action is required. Just sit back, and relax, while we do everything for you.

If you are using Cloudflare or a custom DNS server that is not BladeNode, please point your domain’s A record to 50.2.213.18. Please be aware that this IP address can only be used for your domain’s A record, not for custom DNS. For custom DNS, please use the following IP addresses:

ns1.yourdomain.com - 149.248.59.171

ns2.yourdomain.com - 66.42.98.231

please make sure you have your domain pointed to the Nameservers below

ns1.bladenode.com - 149.248.59.171

ns2.bladenode.com - 66.42.98.231.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:bladenode.instatus.com,2005:Maintenance/ckoezwrc6908080d2olabz2u12j</id>
  <published>2021-05-16T03:00:00.000+00:00</published>
  <updated>2021-05-16T03:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://bladenode.instatus.com/maintenance/ckoezwrc6908080d2olabz2u12j"/>
  <title>TX-Semi01,TX-Semi01, and NY-Shared01 Migration to TX-Shared01</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    
    <p><small>May <var data-var='date'> 16</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress..</p>
<p><small>May <var data-var='date'> 16</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have decided to migrate one of our shared hosting servers to our Texas data center. On May 15, 2021, @ 23:00, we will migrate all accounts from TX-Semi01, TX-Semi01, and NY-Shared01 to TX-Shared01. Our TX-Semi01, TX-Semi01, and NY-Shared01 servers have outgrown themselves and no longer can accept any more accounts. In the past 60 days, we have seen a performance decline and no longer can be used. 

This migration will vastly improve our service to our clients. Also, on top of that, TX-Shared01 will have almost twice the number of resources as the old servers combined, allowing us to expand for future growth and development of the company.

We will start the migration by moving all websites and domains to our TX-Shared01 server on May 15, 2021, @ 23:00 {11:30 PM EST}. 

The migration will take around 6 hours to complete. Please make sure you have your domain pointed to the Nameservers below on the date of the migration. Please also allow 24 to 48 hours for your domain to propagate to the new server.  

If you have already indicated your domains to the nameservers below, then no further action is required. Just sit back, and relax, while we do everything for you. 

If you are using Cloudflare or a custom DNS server that is not BladeNode, please point your domain’s A record to  	**170.130.210.53**. Please be aware that this IP address can only be used for your domain’s A record, not for custom DNS. For custom DNS, please use the following IP addresses:

ns1.yourdomain.com - 149.248.59.171

ns2.yourdomain.com - 66.42.98.231


please make sure you have your domain pointed to the Nameservers below

ns1.bladenode.com - 149.248.59.171

ns2.bladenode.com - 66.42.98.231.</p>
<p><small>May <var data-var='date'> 16</var>, <var data-var='time'>05:20:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We Are having some issues with one of the servers. We have rescheduled the migration for **05/21/2021 at 23:00 (11:00 PM)** Please see [https://bladenode.instatus.com/maintenance/ckos5pf61165683076mzge339u03]https://bladenode.instatus.com/maintenance/ckos5pf61165683076mzge339u03).</p>
<p><small>May <var data-var='date'> 16</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:bladenode.instatus.com,2005:Maintenance/ckofdph49437107c8okuvyi25ia</id>
  <published>2021-05-10T17:30:00.000+00:00</published>
  <updated>2021-05-10T17:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://bladenode.instatus.com/maintenance/ckofdph49437107c8okuvyi25ia"/>
  <title>Client Portal Move.</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 11 days, 16 hours and 45 minutes</p>
    <p><strong>Affected Components:</strong> Client Portal</p>
    <p><small>May <var data-var='date'> 10</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for scheduled maintenance during that time. We are going to be moving the client portal to a better server. .</p>
<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>10:15:05</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:bladenode.instatus.com,2005:Incident/ckoeygvc2765758c0onhkzj776g</id>
  <published>2021-04-29T23:33:00.000+00:00</published>
  <updated>2021-04-30T02:50:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://bladenode.instatus.com/incident/ckoeygvc2765758c0onhkzj776g"/>
  <title>Recnet Texas downtime 4-29-2021</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 days and 5 hours</p>
    <p><strong>Affected Components:</strong> Intel KVM Node 01 - Dallas, TX USA</p>
    <p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>02:50:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We just resolved the issue!.</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>23:33:00</var> GMT+0</small><br /><strong>Identified</strong> -
  As most people aware that everything is down in our texas data center.  We are aware of this and doing everything we can to resolve the issue as quickly as we can. One of our main Nodes in Dalles texas is having major issues with one of its cores. We are working with the data center to come up with a solution. At this time we do not have a projected time frame one when this will get resolved. We apologies for the inconvenience and thank you for understanding..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:bladenode.instatus.com,2005:Incident/ckoeyljso801267c0onz5tglzsa</id>
  <published>2021-04-25T06:36:00.000+00:00</published>
  <updated>2021-04-25T06:36:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://bladenode.instatus.com/incident/ckoeyljso801267c0onz5tglzsa"/>
  <title>Texas network dowm.4-25-2021</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days and 14 hours</p>
    <p><strong>Affected Components:</strong> Intel KVM Node 01 - Dallas, TX USA</p>
    <p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>06:36:00</var> GMT+0</small><br /><strong>Identified</strong> -
  The TX Nwtwok 01 data center is down. We do not know when it will be back up, but we are working with the data center and doing everything we can to resolve this as soon as possible. Sorry for the inconvenience, and thank you for your understanding. We will update this as soon as we know more..</p>
<p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>07:38:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We just resolved the issue!.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:bladenode.instatus.com,2005:Maintenance/ckoeyq8ey503086d2ol6gr6daj9</id>
  <published>2021-03-27T03:39:00.000+00:00</published>
  <updated>2021-05-07T23:43:52.356+00:00</updated>
  <link rel="alternate" type="text/html" href="https://bladenode.instatus.com/maintenance/ckoeyq8ey503086d2ol6gr6daj9"/>
  <title>Server Maintenance 3-26-21</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 10 days, 20 hours and 5 minutes</p>
    <p><strong>Affected Components:</strong> Intel KVM Node 01 - Dallas, TX USA</p>
    <p><small>May <var data-var='date'> 7</var>, <var data-var='time'>23:43:52</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>03:39:00</var> GMT+0</small><br /><strong>Identified</strong> -
  UPDATE: Server Maintenance has been completed.
We would like to inform you that tonight Friday, 26 March 2021 from 23:00 to 03:00 AM EST, there will be scheduled maintenance for approximately three (3) hours. BladeNode will be using this time to add more capacity to the server which hosts your account to improve its performance and speed up our overall service. During this maintenance window, Your VPS services will be inaccessible.

We appreciate your patience and understanding. If you have any questions, please send us a ticket @ https://portal.bladenode.com/ and we’ll be happy to assist you..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:bladenode.instatus.com,2005:Maintenance/ckoeyvmr6552698d2ol56vm0df1</id>
  <published>2021-03-12T07:15:00.000+00:00</published>
  <updated>2021-03-12T09:47:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://bladenode.instatus.com/maintenance/ckoeyvmr6552698d2ol56vm0df1"/>
  <title>vps.easyserverweb.com Migration to vps.bladenode.com</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 32 minutes</p>
    <p><strong>Affected Components:</strong> VPS Control Panel</p>
    <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>09:47:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>07:15:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We would like to inform you that we will be moving our VPS control panel to a new name and server. Don&#039;t worry no KVM Containers will be affected. While this migration is in process. You will be unable to access your VPS. The migration will take no longer than 2 hours.

We appreciate your patience and understanding. If you have any questions, please send us an email at support@bladenode.com and we’ll be happy to assist you.

Thank you.

BladeNode Support Team.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:bladenode.instatus.com,2005:Maintenance/ckoez2n5w611480d2ol5ys8u5ic</id>
  <published>2020-11-30T04:00:00.000+00:00</published>
  <updated>2020-11-30T09:02:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://bladenode.instatus.com/maintenance/ckoez2n5w611480d2ol5ys8u5ic"/>
  <title>(Resolved) VA-Shared01 Migration to TX-Shared01</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours and 2 minutes</p>
    
    <p><small>Nov <var data-var='date'> 30</var>, <var data-var='time'>09:02:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Nov <var data-var='date'> 30</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  we have decided to migrate one of our shared hosting servers to our Texas data center. on November 29, 2020, @ 23:00 we are going to migrate all accounts from VA-Shared01 to TX-Shared01. Our VA-Shared01 server has outgrown itself and no longer can accept any more accounts. In the past 30 days, we have seen a performance decline and no longer can be used. 

This migration will vastly improve our service to our clients. Also, on top of that, TX-Shared01 will have almost twice the number of resources as VA-Shared01, allowing us to expand for future growth and development of the company.

We will start the migration by moving all websites and domains to our TX-Shared01 server on November 29, 2020, @ 23:00 {11:30 PM EST}. 

The migration will take around 4 hours to complete. On the date of the migration, please make sure you have your domain pointed to the Nameservers below. Please also allow 24 to 48 hours for your domain to propagate to the new server.  

If you have already indicated your domains to the nameservers below, then no further action is required. Just sit back, and relax, while we do everything for you. 

If you are using Cloudflare or a custom DNS server that is not BladeNode, please point your domain’s A record to 173.232.117.77. Please be aware that this IP address can only be used for your domain’s A record, not for custom DNS. For custom DNS, please use the following IP addresses: 173.232.117.77

please make sure you have your domain pointed to the Nameservers below

ns1.bladenode.com

ns2.bladenode.com.</p>

        ]]>
  </content>
</entry>

</feed>