<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:liftupau.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://liftupau.instatus.com/history.atom"/>
  <title>LiftUp Hosting Status - Incident history</title>
  <updated>2026-03-10T01:51:42.649+00:00</updated>
  <author>
    <name>LiftUp Hosting</name>
  </author>
  
<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmmjyfd4q00xz11jbp5978mpo</id>
  <published>2026-03-10T01:51:42.649+00:00</published>
  <updated>2026-03-10T01:51:42.662+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmmjyfd4q00xz11jbp5978mpo"/>
  <title>AS136582 UK Core Router outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> UK Core Router</p>
    <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>01:51:42</var> GMT+0</small><br /><strong>Investigating</strong> -
  AS136582 UK Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>01:54:22</var> GMT+0</small><br /><strong>Resolved</strong> -
  AS136582 UK Core Router is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmm44tzis0cxd4eyasu0xkyay</id>
  <published>2026-02-27T00:06:43.731+00:00</published>
  <updated>2026-02-27T00:06:43.742+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmm44tzis0cxd4eyasu0xkyay"/>
  <title>UK 02 outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> UK 02</p>
    <p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>00:06:43</var> GMT+0</small><br /><strong>Investigating</strong> -
  UK 02 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>00:12:23</var> GMT+0</small><br /><strong>Resolved</strong> -
  UK 02 is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmm44tlkg0cx74eya1p7ls0vn</id>
  <published>2026-02-27T00:06:25.648+00:00</published>
  <updated>2026-02-27T00:06:25.657+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmm44tlkg0cx74eya1p7ls0vn"/>
  <title>AS136582 UK Core Router outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> UK Core Router</p>
    <p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>00:06:25</var> GMT+0</small><br /><strong>Investigating</strong> -
  AS136582 UK Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>00:12:32</var> GMT+0</small><br /><strong>Resolved</strong> -
  AS136582 UK Core Router is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmllezsty026g2fr9x00qbcqj</id>
  <published>2026-02-13T21:43:33.814+00:00</published>
  <updated>2026-02-13T21:43:33.822+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmllezsty026g2fr9x00qbcqj"/>
  <title>Sydney 03 outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 4 minutes</p>
    <p><strong>Affected Components:</strong> Sydney 03</p>
    <p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>21:43:33</var> GMT+0</small><br /><strong>Investigating</strong> -
  Sydney 03 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Feb <var data-var='date'> 13</var>, <var data-var='time'>22:47:40</var> GMT+0</small><br /><strong>Resolved</strong> -
  Sydney 03 is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmkx91pv803a7qzxl8c8rjirr</id>
  <published>2026-01-27T23:50:37.363+00:00</published>
  <updated>2026-01-27T23:50:37.371+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmkx91pv803a7qzxl8c8rjirr"/>
  <title>AS136582 Core Router outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> AU Core Router</p>
    <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>23:50:37</var> GMT+0</small><br /><strong>Investigating</strong> -
  AS136582 Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>23:51:41</var> GMT+0</small><br /><strong>Resolved</strong> -
  AS136582 Core Router is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmkmenzme0b9zolce7o5cql4l</id>
  <published>2026-01-20T09:42:26.582+00:00</published>
  <updated>2026-01-20T09:42:26.591+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmkmenzme0b9zolce7o5cql4l"/>
  <title>AS136582 UK Core Router outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 minutes</p>
    <p><strong>Affected Components:</strong> UK Core Router</p>
    <p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>09:42:26</var> GMT+0</small><br /><strong>Investigating</strong> -
  AS136582 UK Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>09:49:32</var> GMT+0</small><br /><strong>Resolved</strong> -
  AS136582 UK Core Router is now operational! This update was created by an automated monitoring service..</p>
<p><small>Jan <var data-var='date'> 20</var>, <var data-var='time'>11:53:07</var> GMT+0</small><br /><strong>Postmortem</strong> -
  This intermittent downtime was due to a carpet bombing DDoS Attack. We have worked closely with our amazing UK network partners to prevent this in the future..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmj5d2gfw0bfzccxnfeaqz57p</id>
  <published>2025-12-14T06:45:55.003+00:00</published>
  <updated>2025-12-14T06:45:55.024+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmj5d2gfw0bfzccxnfeaqz57p"/>
  <title>Dedicated Control Panel outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> Dedicated Control Panel</p>
    <p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>06:45:55</var> GMT+0</small><br /><strong>Investigating</strong> -
  Dedicated Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>06:46:27</var> GMT+0</small><br /><strong>Resolved</strong> -
  Dedicated Control Panel is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmj598km209p26a9qu1rt6gn5</id>
  <published>2025-12-14T04:58:41.881+00:00</published>
  <updated>2025-12-14T04:58:41.889+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmj598km209p26a9qu1rt6gn5"/>
  <title>AS136582 Core Router outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> AU Core Router</p>
    <p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>04:58:41</var> GMT+0</small><br /><strong>Investigating</strong> -
  AS136582 Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>05:00:37</var> GMT+0</small><br /><strong>Resolved</strong> -
  AS136582 Core Router is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmj4il8qu0hwtba8d487228k2</id>
  <published>2025-12-13T16:32:43.398+00:00</published>
  <updated>2025-12-13T16:32:43.408+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmj4il8qu0hwtba8d487228k2"/>
  <title>Sydney 03 outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 42 minutes</p>
    <p><strong>Affected Components:</strong> Sydney 03</p>
    <p><small>Dec <var data-var='date'> 13</var>, <var data-var='time'>16:32:43</var> GMT+0</small><br /><strong>Investigating</strong> -
  Sydney 03 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Dec <var data-var='date'> 13</var>, <var data-var='time'>17:14:33</var> GMT+0</small><br /><strong>Resolved</strong> -
  Sydney 03 is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/cmiopi8co00b91z4qqgf660r8</id>
  <published>2025-12-08T23:30:00.000+00:00</published>
  <updated>2025-12-08T23:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/cmiopi8co00b91z4qqgf660r8"/>
  <title>Sydney 02 Disk Upgrades</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> Sydney 02</p>
    <p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>23:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be upgrading our Sydney 02 VPS Hypervisor to an NVMe-based SSD. This will allow for a significant performance and reliability increase.

Because of the nature of hardware changes, all services will have to be offline for a period of time. We will work to minimize this as much as possible, and then schedule individual times to move services to the new drive. 

**For anything mission-critical, reach out to us, and we can migrate your service to another hypervisor.**.</p>
<p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>23:30:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>01:23:07</var> GMT+0</small><br /><strong>Identified</strong> -
  Our new disk has been installed and we are running some performance tests to ensure it performs as expected.

We are then going to begin migrating customer services over, which will take some time..</p>
<p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>03:24:14</var> GMT+0</small><br /><strong>Completed</strong> -
  VPS&#039;s are now being booted on the new disk.

We appreciate your patience, and hope you will enjoy the new performance improvement..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmirg5nc003g410jvsb3e0mj6</id>
  <published>2025-12-04T13:03:36.287+00:00</published>
  <updated>2025-12-04T13:03:36.305+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmirg5nc003g410jvsb3e0mj6"/>
  <title>Dedicated Control Panel outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> Dedicated Control Panel</p>
    <p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>13:03:36</var> GMT+0</small><br /><strong>Investigating</strong> -
  Dedicated Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>13:04:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  Dedicated Control Panel is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmipzj1mb03u7925stse13scx</id>
  <published>2025-12-03T12:30:19.939+00:00</published>
  <updated>2025-12-03T12:30:19.939+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmipzj1mb03u7925stse13scx"/>
  <title>Sydney 03 Unresponsive</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> Sydney 03</p>
    <p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>12:30:19</var> GMT+0</small><br /><strong>Identified</strong> -
  We are investigating our Sydney 03 hypervisor becoming unresponsive. Our initial analysis shows this is due to an improper automatic allocation of resources.

We are working on restoring services ASAP. In the case VPS&#039;s have shutdown, we will restart them..</p>
<p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>12:36:33</var> GMT+0</small><br /><strong>Resolved</strong> -
  The unresponsiveness was caused by a failed ram stick and an autoallocation issue. 

Our system has been rebooted with the stick disabled to restore functionality back to the hypervisor. We will continue to monitor and arrange for replacement parts..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmiksly0v036oua494p1p99ul</id>
  <published>2025-11-29T21:17:48.798+00:00</published>
  <updated>2025-11-29T21:17:48.817+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmiksly0v036oua494p1p99ul"/>
  <title>AS136582 Core Router outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> AU Core Router</p>
    <p><small>Nov <var data-var='date'> 29</var>, <var data-var='time'>21:17:48</var> GMT+0</small><br /><strong>Investigating</strong> -
  AS136582 Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 29</var>, <var data-var='time'>21:18:30</var> GMT+0</small><br /><strong>Resolved</strong> -
  AS136582 Core Router is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmiid6th401tz14ov77hhx7sx</id>
  <published>2025-11-28T04:30:36.471+00:00</published>
  <updated>2025-11-28T04:30:36.493+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmiid6th401tz14ov77hhx7sx"/>
  <title>AS136582 UK Core Router outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> UK Core Router</p>
    <p><small>Nov <var data-var='date'> 28</var>, <var data-var='time'>04:30:36</var> GMT+0</small><br /><strong>Investigating</strong> -
  AS136582 UK Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 28</var>, <var data-var='time'>04:30:41</var> GMT+0</small><br /><strong>Resolved</strong> -
  AS136582 UK Core Router is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmiicu2j6003jhhe8r9m3e5jd</id>
  <published>2025-11-28T04:20:41.682+00:00</published>
  <updated>2025-11-28T04:20:41.708+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmiicu2j6003jhhe8r9m3e5jd"/>
  <title>UK 02 outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> UK 02</p>
    <p><small>Nov <var data-var='date'> 28</var>, <var data-var='time'>04:20:41</var> GMT+0</small><br /><strong>Investigating</strong> -
  UK 02 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 28</var>, <var data-var='time'>04:21:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  UK 02 is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmiictvjp031a1ze8ughb0dkq</id>
  <published>2025-11-28T04:20:32.629+00:00</published>
  <updated>2025-11-28T04:20:32.646+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmiictvjp031a1ze8ughb0dkq"/>
  <title>AS136582 UK Core Router outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> UK Core Router</p>
    <p><small>Nov <var data-var='date'> 28</var>, <var data-var='time'>04:20:32</var> GMT+0</small><br /><strong>Investigating</strong> -
  AS136582 UK Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 28</var>, <var data-var='time'>04:21:39</var> GMT+0</small><br /><strong>Resolved</strong> -
  AS136582 UK Core Router is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmicpe92e07d4jlj3e5cfvdxu</id>
  <published>2025-11-24T05:25:41.605+00:00</published>
  <updated>2025-11-24T05:25:41.613+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmicpe92e07d4jlj3e5cfvdxu"/>
  <title>AS136582 Core Router outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> AU Core Router</p>
    <p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>05:25:41</var> GMT+0</small><br /><strong>Investigating</strong> -
  AS136582 Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>05:29:45</var> GMT+0</small><br /><strong>Resolved</strong> -
  AS136582 Core Router is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmhstche700fkirzs0kw2hd2t</id>
  <published>2025-11-10T07:20:54.030+00:00</published>
  <updated>2025-11-10T07:20:54.049+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmhstche700fkirzs0kw2hd2t"/>
  <title>AS136582 Core Router outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> AU Core Router</p>
    <p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>07:20:54</var> GMT+0</small><br /><strong>Investigating</strong> -
  AS136582 Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 10</var>, <var data-var='time'>07:25:36</var> GMT+0</small><br /><strong>Resolved</strong> -
  AS136582 Core Router is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmhraguk601my12m68o2kykz9</id>
  <published>2025-11-09T05:44:38.824+00:00</published>
  <updated>2025-11-09T05:44:38.848+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmhraguk601my12m68o2kykz9"/>
  <title>Sydney 01 ~ Outage Detected</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    
    <p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>05:44:38</var> GMT+0</small><br /><strong>Investigating</strong> -
  Our automated systems have detected our Sydney 01 server is currently offline. Our team has been notified and we are investigating the incident

LiftUp Hosting services that may be impacted:
- Web Hosting
- Billing Portal.</p>
<p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>05:49:39</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our automated monitoring has detected the server is back online. If you continue to have any issues, please contact us..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmhqtxd2l02g16c9lwv5dyg8s</id>
  <published>2025-11-08T22:01:35.853+00:00</published>
  <updated>2025-11-08T22:01:35.867+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmhqtxd2l02g16c9lwv5dyg8s"/>
  <title>Dedicated Control Panel outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    <p><strong>Affected Components:</strong> Dedicated Control Panel</p>
    <p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>22:01:35</var> GMT+0</small><br /><strong>Investigating</strong> -
  Dedicated Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>22:21:33</var> GMT+0</small><br /><strong>Resolved</strong> -
  Dedicated Control Panel is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmhqcfbeh0001284yo87s149f</id>
  <published>2025-11-08T13:51:40.408+00:00</published>
  <updated>2025-11-08T13:51:40.424+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmhqcfbeh0001284yo87s149f"/>
  <title>AS136582 Core Router outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> AU Core Router</p>
    <p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>13:51:40</var> GMT+0</small><br /><strong>Investigating</strong> -
  AS136582 Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>13:52:36</var> GMT+0</small><br /><strong>Resolved</strong> -
  AS136582 Core Router is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmhqbi8jr03yj7k3xz81z5c66</id>
  <published>2025-11-08T13:25:57.062+00:00</published>
  <updated>2025-11-08T13:25:57.083+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmhqbi8jr03yj7k3xz81z5c66"/>
  <title>VPS Control Panel outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 20 minutes</p>
    <p><strong>Affected Components:</strong> VPS Control Panel</p>
    <p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>13:25:57</var> GMT+0</small><br /><strong>Investigating</strong> -
  VPS Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>21:45:38</var> GMT+0</small><br /><strong>Resolved</strong> -
  VPS Control Panel is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmfdkpa0v01bsi1j409bvmebd</id>
  <published>2025-09-10T06:02:57.151+00:00</published>
  <updated>2025-09-10T06:02:57.175+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmfdkpa0v01bsi1j409bvmebd"/>
  <title>VPS Control Panel outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> VPS Control Panel</p>
    <p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>06:02:57</var> GMT+0</small><br /><strong>Investigating</strong> -
  VPS Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>06:03:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  VPS Control Panel is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmfdjmny3000srujtsb96uys3</id>
  <published>2025-09-10T05:32:55.611+00:00</published>
  <updated>2025-09-10T05:32:55.646+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmfdjmny3000srujtsb96uys3"/>
  <title>VPS Control Panel outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> VPS Control Panel</p>
    <p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>05:32:55</var> GMT+0</small><br /><strong>Investigating</strong> -
  VPS Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>05:33:38</var> GMT+0</small><br /><strong>Resolved</strong> -
  VPS Control Panel is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmfdfijms00uq14e28tmbnezb</id>
  <published>2025-09-10T03:37:44.931+00:00</published>
  <updated>2025-09-10T03:37:44.952+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmfdfijms00uq14e28tmbnezb"/>
  <title>VPS Control Panel outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 46 minutes</p>
    <p><strong>Affected Components:</strong> VPS Control Panel</p>
    <p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>03:37:44</var> GMT+0</small><br /><strong>Investigating</strong> -
  VPS Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>05:23:41</var> GMT+0</small><br /><strong>Resolved</strong> -
  VPS Control Panel is now operational! This update was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Incident/cmfdeov6000fx4nnh9aukffky</id>
  <published>2025-09-10T03:14:40.200+00:00</published>
  <updated>2025-09-10T06:45:36.576+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/incident/cmfdeov6000fx4nnh9aukffky"/>
  <title>Dedicated Control Panel outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> Dedicated Control Panel</p>
    <p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>06:45:36</var> GMT+0</small><br /><strong>Resolved</strong> -
  Dedicated Control Panel is now operational! This update was created by an automated monitoring service..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>03:14:40</var> GMT+0</small><br /><strong>Investigating</strong> -
  Dedicated Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/cmfcozd1i00ce7o3jpm2xnnmq</id>
  <published>2025-09-10T00:30:00.000+00:00</published>
  <updated>2025-09-10T00:30:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/cmfcozd1i00ce7o3jpm2xnnmq"/>
  <title>Updates on Panels/Websites</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> VPS Control Panel, Dedicated Control Panel, Sydney, Australia, Billing Portal</p>
    <p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>00:30:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>00:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are going to be completing updates on the hypervisor that hosts various panels and software we use, including both the hypervisor and VMs hosting them.

We are expecting minimal customer impact other than being unable to access these services in short intervals as they are restarted.

If any customers intend to complete work during this window, including an hour before and after the scheduled times, please reach out via our support channels so we can best minimise the impact..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>01:43:43</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified a software issue in our hypervisor requiring it to be reinstalled. 

We&#039;re moving some of our critical services to another hypervisor to keep online as best as possible, and other services will become or remain offline..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/cmakhmt4f0001d9nds8yqbcgo</id>
  <published>2025-05-18T00:00:00.000+00:00</published>
  <updated>2025-05-18T00:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/cmakhmt4f0001d9nds8yqbcgo"/>
  <title>Rack Move</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> Billing Portal, Sydney 03, On-Site Backups, Sydney, Australia, AU Core Router, UK 02, VPS Control Panel, Dedicated Control Panel</p>
    <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are moving from a shared rack to our dedicated half rack within the same datacenter.

We&#039;re expecting an estimated downtime of under 2 hours, but have allowed additional time to bring up the rest of our services.

We will be prioritising bringing online Dedicated Servers &amp; VPSs before any of the relevant control panels..</p>
<p><small>May <var data-var='date'> 18</var>, <var data-var='time'>02:45:15</var> GMT+0</small><br /><strong>Identified</strong> -
  Most of our services our beginning to restore now. There may be some instability in networking as we continue to reconfigure and move cables around.   
  .</p>
<p><small>May <var data-var='date'> 18</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>May <var data-var='date'> 18</var>, <var data-var='time'>00:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/cm0eda6j20002opcdz4rzk380</id>
  <published>2024-08-30T04:00:00.000+00:00</published>
  <updated>2024-08-30T05:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/cm0eda6j20002opcdz4rzk380"/>
  <title>UK - Upstream Network Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> UK 02, UK Core Router</p>
    <p><small>Aug <var data-var='date'> 30</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Aug <var data-var='date'> 30</var>, <var data-var='time'>04:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 30</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Our UK Upstream is conducting essential maintenance on a core router in response to an outage around the time we began migrating customers to our new infrastructure. This will allow them to proactively prevent this same issue re-occurring in the future.

This maintenance means that we will have a brief period of network outage (around 10 mins) whilst they re-configure that router. They expect the actual duration to be less though..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/clw5eixb676011b4n24o9pjcw8</id>
  <published>2024-05-17T12:00:00.000+00:00</published>
  <updated>2024-05-17T12:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/clw5eixb676011b4n24o9pjcw8"/>
  <title>Core Router Upgrade</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> VPS Control Panel, Billing Portal, AU Core Router, Sydney 02, Sydney 03</p>
    <p><small>May <var data-var='date'> 17</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We’ll be upgrading our core network’s equipment alongside our secondary network partner who are also doing the same.

We’ll attempt to minimise the amount of downtime caused, and make a best effort to do it as late as possible..</p>
<p><small>May <var data-var='date'> 17</var>, <var data-var='time'>13:14:31</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;re beginning work on the swapover. 

At some point, we will have some downtime to start swapping links between the switches. We&#039;ll try to minimize how long the downtime is for and work on swapping over our secondary network, then our primary one.</p>
<p><small>May <var data-var='date'> 17</var>, <var data-var='time'>13:15:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Long story short, we were unable to complete our configuration and establish a link on our new equipment, and as such will reschedule for another day when we&#039;ve got it working :).</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/clt3xghrs128146b8my0yubjbev</id>
  <published>2024-03-08T11:00:00.000+00:00</published>
  <updated>2024-03-08T11:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/clt3xghrs128146b8my0yubjbev"/>
  <title>Upstream Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 6 hours</p>
    <p><strong>Affected Components:</strong> AU Core Router</p>
    <p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Our secondary upstream is planning maintenance for the 8th overnight to do some network upgrades and configuration. We&#039;ll be on standby and at the data center during the maintenance and are ensuring our primary upstream will pick up the network..</p>
<p><small>Mar <var data-var='date'> 8</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/clswtlnur781787cboiu05cyi51</id>
  <published>2024-02-22T12:50:00.000+00:00</published>
  <updated>2024-02-22T14:10:36.745+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/clswtlnur781787cboiu05cyi51"/>
  <title>UK VPS Maintenance </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 45 minutes</p>
    
    <p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>14:10:36</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.

Apologies for the doubled-up emails.</p>
<p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>12:50:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Feb <var data-var='date'> 22</var>, <var data-var='time'>15:55:38</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has been completed.

Apologies for the late completion, we&#039;ve been monitoring to ensure network stability.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/clrr6von276220biojo3hx1gbd</id>
  <published>2024-02-02T10:30:00.000+00:00</published>
  <updated>2024-02-02T13:16:21.407+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/clrr6von276220biojo3hx1gbd"/>
  <title>Move to Full Rack</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 7 hours and 56 minutes</p>
    <p><strong>Affected Components:</strong> On-Site Backups, VPS Control Panel, Billing Portal, Sydney 02, AU Core Router</p>
    <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>13:16:21</var> GMT+0</small><br /><strong>Identified</strong> -
  Now in progress.</p>
<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>10:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Our co-location partner is upgrading the rack to a full rack from a half, and as such we will have to move our equipment. This is directly across and should be a relatively quick and straightforward process.

We are allowing upto 4 hours of total downtime during the move in case we have unexpected issues or we start/finish later, however, expect to be done within an hour.</p>
<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>16:08:59</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;ve got all of our hardware moved accross and have networking restored. We are in the process of turning all of our servers back on.</p>
<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>21:12:33</var> GMT+0</small><br /><strong>Completed</strong> -
  We&#039;ve completed our rack move.  
  
We do have some growing pains to work though, such as our limited network capacity due to some issues that occurred. We&#039;ll work through them proactively and without interruption to your service.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/clrr79dbw80929biojpxpbti1z</id>
  <published>2024-02-02T10:00:00.000+00:00</published>
  <updated>2024-02-02T10:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/clrr79dbw80929biojpxpbti1z"/>
  <title>SYD03 Hardware</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours and 47 minutes</p>
    
    <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Our hardware-based raid card for SYD03 has arrived. We&#039;ll also be setting up a 10gig network card to ensure quicker on-site backups

We&#039;ll be doing the following:
- Before the maintenance, we&#039;ll manually initiate backups during the day as a failsafe
- We&#039;ll fill capacity on our other servers, prioritizing Shark &amp; Kangaroo and any remainder we don&#039;t have capacity for will be temporarily suspended with SLA Credit if requested
- Hardware will be installed and a fresh OS will be installed with RAID10
- Clients will be migrated back onto the server, prioritizing anyone who is temporarily suspended 

There&#039;s a chance the overall process of moving people will run overtime but we will minimize any impact working during late night/early morning hours.</p>
<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>10:21:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance has begun on SYD03\. All clients were moved off during the week.</p>
<p><small>Feb <var data-var='date'> 3</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance time and date have been updated and pushed back to be in line with our already upcoming maintenance.</p>
<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>16:07:56</var> GMT+0</small><br /><strong>Completed</strong> -
  Hardware has been swapped.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/clr7jpy5i156830bmorwn26nzcm</id>
  <published>2024-01-10T09:00:00.000+00:00</published>
  <updated>2024-01-10T09:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/clr7jpy5i156830bmorwn26nzcm"/>
  <title>Emergency Maintenence - SYD03</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 6 hours and 10 minutes</p>
    
    <p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>15:09:40</var> GMT+0</small><br /><strong>Completed</strong> -
  Hypervisor has been re-provisioned and servers are being moved onto this to balance the load.</p>
<p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>12:08:53</var> GMT+0</small><br /><strong>Identified</strong> -
  All VPS&#039;s have been moved to other hypervisors. We are now re-installing our OS with Software RAID10 as a temporary solution until our dedicated hardware for RAID arrives..</p>
<p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>10:44:24</var> GMT+0</small><br /><strong>Identified</strong> -
  Everyone has almost been moved off and we are preparing to reinstall the OS. We&#039;ll be installing without RAID but backing up nightly.

We were planning on waiting for our raid card to arrive but are rushing this to fix present issues affecting everyone. Once it arrives, maintenance will be scheduled well in advance to fix it permantly.



.</p>
<p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Both our SYD02 and SYD03 node are having major performance issue with our disks. This seems to be due to the high amount of clients running Windows and high-operation setups (ie FiveM servers) which ultimately has the entire hypervisor in a limbo state during peak usage.

As our SYD03 node has the least clients on it, we are going to be migrating everyone to other hypervisors temporarily and rebuilding the disk setup. Once this is done and we have stable disk performance, I&#039;m going to balance out VPS&#039;s between the nodes and performance should then sort itself out

This can take anywhere from 10 mins to a few hours, and i&#039;ll provide regular updates where possible.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/clqpwxyir13804bkob6iwqc3w1</id>
  <published>2023-12-30T11:00:00.000+00:00</published>
  <updated>2023-12-30T11:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/clqpwxyir13804bkob6iwqc3w1"/>
  <title>Upstream Maintence</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> On-Site Backups, VPS Control Panel, Billing Portal, Sydney 02, AU Core Router</p>
    <p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>12:53:27</var> GMT+0</small><br /><strong>Identified</strong> -
  Unfortunately, our Upstream&#039;s maintenance is running severely over what we were informed us due to an unknown issue on their end. 

Like all of you, we are awaiting further updates from them..</p>
<p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Our upstream provider has a planned network maintenence starting at 30/12/2023 10PM Sydney Time and concluding at 31/12/2023 2AM Sydney Time. Downtime should be less than 1 hour..</p>
<p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>13:10:02</var> GMT+0</small><br /><strong>Completed</strong> -
  The network has come back online. We were informed that the extended delay was due to route convergence..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/clq6i6ls06098b9n75vtb5ccg</id>
  <published>2023-12-18T07:00:00.000+00:00</published>
  <updated>2023-12-19T08:33:53.905+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/clq6i6ls06098b9n75vtb5ccg"/>
  <title>Datacentre Move - VPS &amp; Web Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 days, 21 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> On-Site Backups, VPS Control Panel, Billing Portal, Sydney 02, AU Core Router</p>
    <p><small>Dec <var data-var='date'> 19</var>, <var data-var='time'>08:33:53</var> GMT+0</small><br /><strong>Completed</strong> -
  We’re confident that all of our networking is back online.

Services have been brought back online fully. Web Hosting is expected to come back online around midnight.

We will have a full post-mortem available tommorow morning for full transparency about the issues..</p>
<p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are moving all of our equipment from NextDC S1 to Equinix SY5. During this time, All VPS&#039;s will be shut down &amp; Web Hosting will be taken offline during the move.



.</p>
<p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>11:09:26</var> GMT+0</small><br /><strong>Identified</strong> -
  Still in progress - Running a bit over. Currently troubleshooting network configuration.

Will update ASAP.</p>
<p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>21:40:54</var> GMT+0</small><br /><strong>Identified</strong> -
  To say we are currently disappointed in our current network situation is an understatement.

Everything is connected at our new data center, however, our IP range getting filtered via EdgeIX.

We believe this is due to a typo from our upstream. We are awaiting IRR changes to be picked up globally, and hope this won&#039;t be much longer


.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/cllt58ib416312bhoaidw7dxfz</id>
  <published>2023-08-28T13:00:00.000+00:00</published>
  <updated>2023-08-28T11:29:54.235+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/cllt58ib416312bhoaidw7dxfz"/>
  <title>Storage Fixes</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day, 12 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> Sydney 02</p>
    <p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>11:29:54</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware that most customers are receiving errors with their backups stating they have failed. 

This is caused by the massive amount being done at once, and are currently being staggered more to allow them to complete fully..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>20:28:39</var> GMT+0</small><br /><strong>Completed</strong> -
  Unfortunately, we were unable to complete the backup within a time frame that we were happy with and as such we have stopped our maintenance.

We will revisit the issue at some point in the very near future and work on ways to minimize the potential downtime next time we attempt this..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>20:02:34</var> GMT+0</small><br /><strong>Identified</strong> -
  It seems that taking the backup of data is currently taking a lot more time than initially anticipated. 

We will update you as soon as we get any new information/when it has completed..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>07:43:00</var> GMT+0</small><br /><strong>Identified</strong> -
  In order to fix a partitioning mistake from when our cluster was first set up, we will perform maintenance to repair this.

The process for our maintenance will be as follows:
1. Anytime between 7-11pm we will be taking a snapshot of your vps via the backup system as a redundancy
2. At 11pm, we will safely shut down all VPS&#039;s and begin copying the data onto our backup server
3. One data has been moved and integrity is verified, we will reset and recreate the partition with the correct settings
4. Data will then be moved back onto our hypervisor and VPS&#039;s will be booted back up.

We estimate that this may take up to 6 hours to complete but will work to make it as quick as possible

Any customers who are hosting critical systems can reach out to our support team and be moved to a temporary server. This request should be done as soon as possible. Other customers are eligible for SLA Credit..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/clk6vn66p151236bgofpjy79n5o</id>
  <published>2023-07-18T06:00:00.000+00:00</published>
  <updated>2023-07-18T06:38:08.552+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/clk6vn66p151236bgofpjy79n5o"/>
  <title>Network Upgrades</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours and 35 minutes</p>
    <p><strong>Affected Components:</strong> Sydney 02</p>
    <p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>06:38:08</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress..</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are upgrading our core network&#039;s routing and as such some downtime will occur.

We will ensure that we minimize this as much as possible, however, server&#039;s may lose connectivity for multiple brief periods.</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>09:35:16</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.

Gateway for our network has changed. For most customers, it has been automatically updated for you.

Please reach out to us via our billing/support panel if you encounter any issues..</p>
<p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>07:17:18</var> GMT+0</small><br /><strong>Identified</strong> -
  We are currently experiencing some complications with the network configuration and are working through them currently.

To allow us to do this easier, We are shutting down VPS&#039;s and out infrastructure to recable and re-rack some of our servers.



.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/clfckuhpc251551nodky6o0r2t</id>
  <published>2023-03-21T02:30:00.000+00:00</published>
  <updated>2023-03-21T03:21:01.559+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/clfckuhpc251551nodky6o0r2t"/>
  <title>Hardware Upgrade</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> Sydney 02</p>
    <p><small>Mar <var data-var='date'> 21</var>, <var data-var='time'>03:21:01</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has been completed successfully. All VPS&#039;s are booting back online..</p>
<p><small>Mar <var data-var='date'> 21</var>, <var data-var='time'>02:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress. During this time, VPS&#039;s will turn off and back on..</p>
<p><small>Mar <var data-var='date'> 21</var>, <var data-var='time'>02:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are upgrading our hardware to increase capacity over our VPS Node. This maintenance will be relatively quick and consist of shutting servers and services down, installing the new hardware, and booting everything back up. 

This should take no longer than 15 mins if there are no issues
.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:liftupau.instatus.com,2005:Maintenance/clcl8v42f0972i8oab6ujpxs7</id>
  <published>2023-01-12T02:10:00.000+00:00</published>
  <updated>2023-01-12T02:53:39.576+00:00</updated>
  <link rel="alternate" type="text/html" href="https://liftupau.instatus.com/maintenance/clcl8v42f0972i8oab6ujpxs7"/>
  <title>Hardware Upgrade / Swap</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 50 minutes</p>
    <p><strong>Affected Components:</strong> Sydney 02</p>
    <p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>02:53:39</var> GMT+0</small><br /><strong>Completed</strong> -
  The hardware swap and upgrade has been completed. We are monitoring and expect no further issues.</p>
<p><small>Jan <var data-var='date'> 12</var>, <var data-var='time'>02:04:07</var> GMT+0</small><br /><strong>Identified</strong> -
  Our team is at the datacenter and performing the hardware swap. This should take no longer than 10-15 mins..</p>
<p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>02:10:00</var> GMT+0</small><br /><strong>Identified</strong> -
  In relation to our previous issues around hardware failure, we expect the hardware to arrive on Monday and be ready to deploy on Tuesday. 

The exact time during the day is still TBD and affected clients will be contacted with the exact details of the maintenance. 

The expected time this should take is ~15 minutes however a full hour has been allocated in the severe case that issues arise during deployment.</p>

        ]]>
  </content>
</entry>

</feed>