<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>LiftUp Hosting Status - Incident history</title>
    <link>https://liftupau.instatus.com</link>
    <description>LiftUp Hosting</description>
    <pubDate>Thu, 8 Oct 2026 13:34:47 +0000</pubDate>
    
<item>
  <title>Dedicated/Colo Outage</title>
  <description>
    Type: Incident
    Duration: 2 days and 20 hours

    Affected Components: Colocation, Dedicated Servers
    Oct 8, 14:42:46 GMT+0 - Resolved - We believe the cause was due to a software fault in our device causing it to hard lock itself. We have a standby router we are configuring as a precaution to replace it.  
  
We&#039;ll open a seperate emergency maintenance when we have a cutover time. Oct 8, 14:23:08 GMT+0 - Monitoring - The device was hard rebooted and has come back up. 

We are looking into the root cause for the router locking up. Oct 8, 13:34:47 GMT+0 - Investigating - Our team is currently investigating a potential fault with one of our routers managing dedicated servers and a small amount of colocation customers. We are en route to site to investigate.

Affected customers are being contacted directly for updates 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days and 20 hours</p>
    <p><strong>Affected Components:</strong> , </p>
    <p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>14:42:46</var> GMT+0</small><br><strong>Resolved</strong> -
  We believe the cause was due to a software fault in our device causing it to hard lock itself. We have a standby router we are configuring as a precaution to replace it.  
  
We&#039;ll open a seperate emergency maintenance when we have a cutover time..</p>
<p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>14:23:08</var> GMT+0</small><br><strong>Monitoring</strong> -
  The device was hard rebooted and has come back up. 

We are looking into the root cause for the router locking up..</p>
<p><small>Oct <var data-var='date'> 8</var>, <var data-var='time'>13:34:47</var> GMT+0</small><br><strong>Investigating</strong> -
  Our team is currently investigating a potential fault with one of our routers managing dedicated servers and a small amount of colocation customers. We are en route to site to investigate.

Affected customers are being contacted directly for updates.</p>
]]>
  </content:encoded>
  <pubDate>Thu, 8 Oct 2026 13:34:47 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmuzkw5b7015k0ws39pgeg64j</link>
  <guid>https://liftupau.instatus.com/incident/cmuzkw5b7015k0ws39pgeg64j</guid>
</item>

<item>
  <title>Billing Portal outage</title>
  <description>
    Type: Incident
    Duration: 3 minutes

    Affected Components: Billing Portal
    Oct 6, 06:51:39 GMT+0 - Resolved - Billing Portal is now operational! This update was created by an automated monitoring service. Oct 6, 06:48:46 GMT+0 - Investigating - Billing Portal cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>06:51:39</var> GMT+0</small><br><strong>Resolved</strong> -
  Billing Portal is now operational! This update was created by an automated monitoring service..</p>
<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>06:48:46</var> GMT+0</small><br><strong>Investigating</strong> -
  Billing Portal cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 6 Oct 2026 06:48:46 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmuwbi9um07cc1bl4pazytai7</link>
  <guid>https://liftupau.instatus.com/incident/cmuwbi9um07cc1bl4pazytai7</guid>
</item>

<item>
  <title>VPS Control Panel outage</title>
  <description>
    Type: Incident
    Duration: 3 minutes

    Affected Components: VPS Control Panel
    Oct 6, 06:51:41 GMT+0 - Resolved - VPS Control Panel is now operational! This update was created by an automated monitoring service. Oct 6, 06:48:42 GMT+0 - Investigating - VPS Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>06:51: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>
<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>06:48:42</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>
]]>
  </content:encoded>
  <pubDate>Tue, 6 Oct 2026 06:48:42 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmuwbi6r60fda13lpcrov0t23</link>
  <guid>https://liftupau.instatus.com/incident/cmuwbi6r60fda13lpcrov0t23</guid>
</item>

<item>
  <title>Sydney, Australia outage</title>
  <description>
    Type: Incident
    Duration: 3 minutes

    Affected Components: Sydney, Australia
    Oct 6, 06:51:38 GMT+0 - Resolved - Sydney, Australia is now operational! This update was created by an automated monitoring service. Oct 6, 06:48:41 GMT+0 - Investigating - Sydney, Australia cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>06:51:38</var> GMT+0</small><br><strong>Resolved</strong> -
  Sydney, Australia is now operational! This update was created by an automated monitoring service..</p>
<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>06:48:41</var> GMT+0</small><br><strong>Investigating</strong> -
  Sydney, Australia cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 6 Oct 2026 06:48:41 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmuwbi5y50efm1blpicq5l2t9</link>
  <guid>https://liftupau.instatus.com/incident/cmuwbi5y50efm1blpicq5l2t9</guid>
</item>

<item>
  <title>AS136582 UK Core Router outage</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    Affected Components: UK Core Router
    Oct 1, 11:14:41 GMT+0 - Resolved - AS136582 UK Core Router is now operational! This update was created by an automated monitoring service. Oct 1, 11:08:30 GMT+0 - Investigating - AS136582 UK Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>11:14: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>
<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>11:08:30</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>
]]>
  </content:encoded>
  <pubDate>Thu, 1 Oct 2026 11:08:30 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmupfl1ix000013ol6v1oxn6a</link>
  <guid>https://liftupau.instatus.com/incident/cmupfl1ix000013ol6v1oxn6a</guid>
</item>

<item>
  <title>Newcastle, United Kingdom outage</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    Affected Components: Newcastle, United Kingdom
    Oct 1, 11:14:35 GMT+0 - Resolved - Newcastle, United Kingdom is now operational! This update was created by an automated monitoring service. Oct 1, 11:08:24 GMT+0 - Investigating - Newcastle, United Kingdom cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>11:14:35</var> GMT+0</small><br><strong>Resolved</strong> -
  Newcastle, United Kingdom is now operational! This update was created by an automated monitoring service..</p>
<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>11:08:24</var> GMT+0</small><br><strong>Investigating</strong> -
  Newcastle, United Kingdom cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 1 Oct 2026 11:08:24 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmupfkwv400q113pcy56oj233</link>
  <guid>https://liftupau.instatus.com/incident/cmupfkwv400q113pcy56oj233</guid>
</item>

<item>
  <title>UK 02 outage</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    Affected Components: UK 02
    Oct 1, 11:14:38 GMT+0 - Resolved - UK 02 is now operational! This update was created by an automated monitoring service. Oct 1, 11:08:21 GMT+0 - Investigating - UK 02 cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>11:14:38</var> GMT+0</small><br><strong>Resolved</strong> -
  UK 02 is now operational! This update was created by an automated monitoring service..</p>
<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>11:08:21</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>
]]>
  </content:encoded>
  <pubDate>Thu, 1 Oct 2026 11:08:21 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmupfkuji00py13pcuo5rb8sl</link>
  <guid>https://liftupau.instatus.com/incident/cmupfkuji00py13pcuo5rb8sl</guid>
</item>

<item>
  <title>Sydney 02 outage</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: Sydney 02
    Sep 30, 22:18:18 GMT+0 - Resolved - Sydney 02 is now operational! This update was created by an automated monitoring service. Sep 30, 22:14:45 GMT+0 - Investigating - Sydney 02 cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>22:18:18</var> GMT+0</small><br><strong>Resolved</strong> -
  Sydney 02 is now operational! This update was created by an automated monitoring service..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>22:14:45</var> GMT+0</small><br><strong>Investigating</strong> -
  Sydney 02 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 30 Sep 2026 22:14:45 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmuonxzol031w13oknu8e32gj</link>
  <guid>https://liftupau.instatus.com/incident/cmuonxzol031w13oknu8e32gj</guid>
</item>

<item>
  <title>VPS Control Panel outage</title>
  <description>
    Type: Incident
    Duration: 3 hours and 15 minutes

    Affected Components: VPS Control Panel
    Sep 30, 18:41:16 GMT+0 - Resolved - VPS Control Panel is now operational! This update was created by an automated monitoring service. Sep 30, 15:26:06 GMT+0 - Investigating - VPS Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>18:41:16</var> GMT+0</small><br><strong>Resolved</strong> -
  VPS Control Panel is now operational! This update was created by an automated monitoring service..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>15:26:06</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>
]]>
  </content:encoded>
  <pubDate>Wed, 30 Sep 2026 15:26:06 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmuo9cgip01gs13ljw517z5vk</link>
  <guid>https://liftupau.instatus.com/incident/cmuo9cgip01gs13ljw517z5vk</guid>
</item>

<item>
  <title>DC Expansion</title>
  <description>
    Type: Maintenance
    Duration: 8 hours

    Affected Components: Sydney, Australia, Sydney 02, On-Site Backups, Colocation, Sydney 03, Dedicated Servers, AU Core Router
    Sep 30, 21:00:00 GMT+0 - Completed - Maintenance has completed successfully Sep 30, 18:41:46 GMT+0 - Identified - Services are beginning to restore. You may still see them come up and down as works are still underway.  
  
VPS&#039;s will be fully booted when network changes are completed. Sep 30, 13:00:01 GMT+0 - Identified - Maintenance is now in progress Sep 26, 10:12:27 GMT+0 - Identified - We&#039;re excited to expand our datacenter space and allow us to expand our offerings.

During this maintenance, we&#039;ll be physically moving our equipment and as such shutdowns on all of our equipment will be required. This move is only directly across so the physical aspect shouldn&#039;t take any unreasonable time. We&#039;ll also be completing software updating on all of our infrastructure to the latest supported versions. We&#039;ll reach out directly to our co-location customers on options for the move.

We have provided a large window for us to complete everything without rushing and making mistakes. We will try minimize the full downtime and move in stages as best we can.

If you have any concerns or issues please reach out! 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 8 hours</p>
    <p><strong>Affected Components:</strong> , , , , , , </p>
    <p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>18:41:46</var> GMT+0</small><br><strong>Identified</strong> -
  Services are beginning to restore. You may still see them come up and down as works are still underway.  
  
VPS&#039;s will be fully booted when network changes are completed..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>13:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>10:12:27</var> GMT+0</small><br><strong>Identified</strong> -
  We&#039;re excited to expand our datacenter space and allow us to expand our offerings.

During this maintenance, we&#039;ll be physically moving our equipment and as such shutdowns on all of our equipment will be required. This move is only directly across so the physical aspect shouldn&#039;t take any unreasonable time. We&#039;ll also be completing software updating on all of our infrastructure to the latest supported versions. We&#039;ll reach out directly to our co-location customers on options for the move.

We have provided a large window for us to complete everything without rushing and making mistakes. We will try minimize the full downtime and move in stages as best we can.

If you have any concerns or issues please reach out!.</p>
]]>
  </content:encoded>
  <pubDate>Wed, 30 Sep 2026 13:00:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/cmui8dp840bbm1blbn29xtmug</link>
  <guid>https://liftupau.instatus.com/maintenance/cmui8dp840bbm1blbn29xtmug</guid>
</item>

<item>
  <title>Full AU Outage</title>
  <description>
    Type: Incident
    Duration: 59 minutes

    Affected Components: Sydney, Australia, VPS Control Panel, Billing Portal, Sydney 02, On-Site Backups, Colocation, Sydney 03, Dedicated Servers, AU Core Router, Dedicated Control Panel
    Sep 24, 21:30:00 GMT+0 - Resolved - Apologies our status page didn’t push the update earlier - This was resolved at 7:30am Sydney time.

The root cause was a configuration disagreement with our upstream that resolved in our network port being shut off on some automation timeline from what we are guessing.

We’ll also doing a review on backup acces to resolve these better and quicker. Sep 24, 21:01:03 GMT+0 - Investigating - We’ve reached out to our network partner for help. We’re also on the way to the datacenter to investigate further Sep 24, 20:30:41 GMT+0 - Investigating - We&#039;re currently looking into whats happening.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 59 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , </p>
    <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>21:30:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Apologies our status page didn’t push the update earlier - This was resolved at 7:30am Sydney time.

The root cause was a configuration disagreement with our upstream that resolved in our network port being shut off on some automation timeline from what we are guessing.

We’ll also doing a review on backup acces to resolve these better and quicker..</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>21:01:03</var> GMT+0</small><br><strong>Investigating</strong> -
  We’ve reached out to our network partner for help. We’re also on the way to the datacenter to investigate further.</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>20:30:41</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re currently looking into whats happening. .</p>
]]>
  </content:encoded>
  <pubDate>Thu, 24 Sep 2026 20:30:41 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmufzl1vx001j1no8xo1m6fve</link>
  <guid>https://liftupau.instatus.com/incident/cmufzl1vx001j1no8xo1m6fve</guid>
</item>

<item>
  <title>Sydney 01 ~ Outage Detected</title>
  <description>
    Type: Incident
    Duration: 1 hour and 16 minutes

    
    Sep 24, 21:27:29 GMT+0 - Resolved - Our automated monitoring has detected the server is back online. If you continue to have any issues, please contact us. Sep 24, 20:11:03 GMT+0 - Investigating - 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 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 16 minutes</p>
    
    <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>21:27:29</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>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>20:11:03</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>
]]>
  </content:encoded>
  <pubDate>Thu, 24 Sep 2026 20:11:03 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmufyvsvz0dhl1arg64oxfay0</link>
  <guid>https://liftupau.instatus.com/incident/cmufyvsvz0dhl1arg64oxfay0</guid>
</item>

<item>
  <title>VPS Control Panel outage</title>
  <description>
    Type: Incident
    Duration: 1 hour and 21 minutes

    Affected Components: VPS Control Panel
    Sep 24, 21:27:41 GMT+0 - Resolved - VPS Control Panel is now operational! This update was created by an automated monitoring service. Sep 24, 20:06:47 GMT+0 - Investigating - VPS Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 21 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>21:27: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>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>20:06:47</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>
]]>
  </content:encoded>
  <pubDate>Thu, 24 Sep 2026 20:06:47 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmufyqb350pk31mqm5b4stqhm</link>
  <guid>https://liftupau.instatus.com/incident/cmufyqb350pk31mqm5b4stqhm</guid>
</item>

<item>
  <title>Sydney, Australia outage</title>
  <description>
    Type: Incident
    Duration: 1 hour and 21 minutes

    Affected Components: Sydney, Australia
    Sep 24, 21:27:36 GMT+0 - Resolved - Sydney, Australia is now operational! This update was created by an automated monitoring service. Sep 24, 20:06:47 GMT+0 - Investigating - Sydney, Australia cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 21 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>21:27:36</var> GMT+0</small><br><strong>Resolved</strong> -
  Sydney, Australia is now operational! This update was created by an automated monitoring service..</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>20:06:47</var> GMT+0</small><br><strong>Investigating</strong> -
  Sydney, Australia cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 24 Sep 2026 20:06:47 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmufyqb1y0pk01mqm8uplzna4</link>
  <guid>https://liftupau.instatus.com/incident/cmufyqb1y0pk01mqm8uplzna4</guid>
</item>

<item>
  <title>Billing Portal outage</title>
  <description>
    Type: Incident
    Duration: 1 hour and 21 minutes

    Affected Components: Billing Portal
    Sep 24, 21:27:34 GMT+0 - Resolved - Billing Portal is now operational! This update was created by an automated monitoring service. Sep 24, 20:06:41 GMT+0 - Investigating - Billing Portal cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 21 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>21:27:34</var> GMT+0</small><br><strong>Resolved</strong> -
  Billing Portal is now operational! This update was created by an automated monitoring service..</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>20:06:41</var> GMT+0</small><br><strong>Investigating</strong> -
  Billing Portal cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 24 Sep 2026 20:06:41 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmufyq6ch003b13potaihueyx</link>
  <guid>https://liftupau.instatus.com/incident/cmufyq6ch003b13potaihueyx</guid>
</item>

<item>
  <title>Sydney 02 outage</title>
  <description>
    Type: Incident
    Duration: 1 hour and 21 minutes

    Affected Components: Sydney 02
    Sep 24, 21:27:33 GMT+0 - Resolved - Sydney 02 is now operational! This update was created by an automated monitoring service. Sep 24, 20:06:40 GMT+0 - Investigating - Sydney 02 cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 21 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>21:27:33</var> GMT+0</small><br><strong>Resolved</strong> -
  Sydney 02 is now operational! This update was created by an automated monitoring service..</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>20:06:40</var> GMT+0</small><br><strong>Investigating</strong> -
  Sydney 02 cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 24 Sep 2026 20:06:40 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmufyq5l100391mpotgx0963d</link>
  <guid>https://liftupau.instatus.com/incident/cmufyq5l100391mpotgx0963d</guid>
</item>

<item>
  <title>AS136582 Core Router outage</title>
  <description>
    Type: Incident
    Duration: 1 hour and 21 minutes

    Affected Components: AU Core Router
    Sep 24, 21:27:37 GMT+0 - Resolved - AS136582 Core Router is now operational! This update was created by an automated monitoring service. Sep 24, 20:06:36 GMT+0 - Investigating - AS136582 Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 21 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>21:27: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>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>20:06:36</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>
]]>
  </content:encoded>
  <pubDate>Thu, 24 Sep 2026 20:06:36 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmufyq36p0dg51mrg07xeyflu</link>
  <guid>https://liftupau.instatus.com/incident/cmufyq36p0dg51mrg07xeyflu</guid>
</item>

<item>
  <title>Sydney 03 outage</title>
  <description>
    Type: Incident
    Duration: 1 hour and 21 minutes

    Affected Components: Sydney 03
    Sep 24, 21:27:40 GMT+0 - Resolved - Sydney 03 is now operational! This update was created by an automated monitoring service. Sep 24, 20:06:29 GMT+0 - Investigating - Sydney 03 cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 21 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>21:27:40</var> GMT+0</small><br><strong>Resolved</strong> -
  Sydney 03 is now operational! This update was created by an automated monitoring service..</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>20:06:29</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>
]]>
  </content:encoded>
  <pubDate>Thu, 24 Sep 2026 20:06:29 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmufypxs80dgf1arg0p73pzl9</link>
  <guid>https://liftupau.instatus.com/incident/cmufypxs80dgf1arg0p73pzl9</guid>
</item>

<item>
  <title>AS136582 UK Core Router outage</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: UK Core Router
    Aug 22, 10:35:38 GMT+0 - Resolved - AS136582 UK Core Router is now operational! This update was created by an automated monitoring service. Aug 22, 10:31:43 GMT+0 - Investigating - AS136582 UK Core Router cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>10:35:38</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>Aug <var data-var='date'> 22</var>, <var data-var='time'>10:31:43</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>
]]>
  </content:encoded>
  <pubDate>Sat, 22 Aug 2026 10:31:43 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmt48no3q0mn30kplsgiik8an</link>
  <guid>https://liftupau.instatus.com/incident/cmt48no3q0mn30kplsgiik8an</guid>
</item>

<item>
  <title>Sydney 01 ~ Outage Detected</title>
  <description>
    Type: Incident
    Duration: 6 minutes

    
    Aug 8, 12:42:41 GMT+0 - Resolved - Our automated monitoring has detected the server is back online. If you continue to have any issues, please contact us. Aug 8, 12:36:32 GMT+0 - Investigating - 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 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 minutes</p>
    
    <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>12:42:41</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>
<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>12:36:32</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>
]]>
  </content:encoded>
  <pubDate>Sat, 8 Aug 2026 12:36:32 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmskcy8s90osa0kpq340n5c1v</link>
  <guid>https://liftupau.instatus.com/incident/cmskcy8s90osa0kpq340n5c1v</guid>
</item>

<item>
  <title>Datacenter Works</title>
  <description>
    Type: Maintenance
    Duration: 23 days, 23 hours and 14 minutes

    Affected Components: Dedicated Control Panel, AU Core Router, Sydney, Australia, VPS Control Panel, Billing Portal, Sydney 02, On-Site Backups, Colocation, Sydney 03, Dedicated Servers
    Aug 4, 07:26:26 GMT+0 - Completed - All interruptive works were completed on time within the maintenance window, and additional non-critical/interruptive works were completed outside of the window as intended.

Thanks for your patience with us. Aug 4, 04:17:23 GMT+0 - Identified - Core router has been swapped and power to all Dedicated Servers have been restored. Our team is still on-site completing other non-critical works, but we will keep this open until we have left. Aug 4, 02:28:40 GMT+0 - Identified - Maintenance is now in progress. Jul 30, 08:39:12 GMT+0 - Identified - We&#039;re planning on doing some datacenter works to future-proof our datacenter configuration and perform various system updates.  
  
As part of the works, We&#039;ll be swapping our core to a different device. As we need to physically swap the cable, We&#039;re expecting a short downtime, less than 5 mins.

We&#039;ll also be working around power cables, and services such as Dedicated Servers may be affected during the reconfiguration. Please be prepared for servers to shut down if necessary.

We understand that these works can be disruptive, please reach out via our support contacts with any concerns. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 23 days, 23 hours and 14 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , </p>
    <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>07:26:26</var> GMT+0</small><br><strong>Completed</strong> -
  All interruptive works were completed on time within the maintenance window, and additional non-critical/interruptive works were completed outside of the window as intended.

Thanks for your patience with us..</p>
<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>04:17:23</var> GMT+0</small><br><strong>Identified</strong> -
  Core router has been swapped and power to all Dedicated Servers have been restored. Our team is still on-site completing other non-critical works, but we will keep this open until we have left..</p>
<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>02:28:40</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress..</p>
<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>08:39:12</var> GMT+0</small><br><strong>Identified</strong> -
  We&#039;re planning on doing some datacenter works to future-proof our datacenter configuration and perform various system updates.  
  
As part of the works, We&#039;ll be swapping our core to a different device. As we need to physically swap the cable, We&#039;re expecting a short downtime, less than 5 mins.

We&#039;ll also be working around power cables, and services such as Dedicated Servers may be affected during the reconfiguration. Please be prepared for servers to shut down if necessary.

We understand that these works can be disruptive, please reach out via our support contacts with any concerns..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 4 Aug 2026 02:00:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/cms79idf4015n0rr0f7t8oj2b</link>
  <guid>https://liftupau.instatus.com/maintenance/cms79idf4015n0rr0f7t8oj2b</guid>
</item>

<item>
  <title>UK 02 outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: UK 02
    Aug 3, 01:19:37 GMT+0 - Resolved - UK 02 is now operational! This update was created by an automated monitoring service. Aug 3, 01:18:42 GMT+0 - Investigating - UK 02 cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>01:19:37</var> GMT+0</small><br><strong>Resolved</strong> -
  UK 02 is now operational! This update was created by an automated monitoring service..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>01:18:42</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>
]]>
  </content:encoded>
  <pubDate>Mon, 3 Aug 2026 01:18:42 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmscjjajp04k70kswb9tc4cpe</link>
  <guid>https://liftupau.instatus.com/incident/cmscjjajp04k70kswb9tc4cpe</guid>
</item>

<item>
  <title>Newcastle, United Kingdom outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: Newcastle, United Kingdom
    Aug 3, 01:19:41 GMT+0 - Resolved - Newcastle, United Kingdom is now operational! This update was created by an automated monitoring service. Aug 3, 01:18:34 GMT+0 - Investigating - Newcastle, United Kingdom cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>01:19:41</var> GMT+0</small><br><strong>Resolved</strong> -
  Newcastle, United Kingdom is now operational! This update was created by an automated monitoring service..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>01:18:34</var> GMT+0</small><br><strong>Investigating</strong> -
  Newcastle, United Kingdom cannot be accessed at the moment. This incident was created by an automated monitoring service..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 3 Aug 2026 01:18:34 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cmscjj4di04yb0zl8ri140iv8</link>
  <guid>https://liftupau.instatus.com/incident/cmscjj4di04yb0zl8ri140iv8</guid>
</item>

<item>
  <title>Dedicated Control Panel outage</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: Dedicated Control Panel
    Jul 31, 15:51:41 GMT+0 - Resolved - Dedicated Control Panel is now operational! This update was created by an automated monitoring service. Jul 31, 15:47:57 GMT+0 - Investigating - Dedicated Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>15:51:41</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>Jul <var data-var='date'> 31</var>, <var data-var='time'>15:47:57</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:encoded>
  <pubDate>Fri, 31 Jul 2026 15:47:57 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cms949lqw0lge1anzpo8hpgcu</link>
  <guid>https://liftupau.instatus.com/incident/cms949lqw0lge1anzpo8hpgcu</guid>
</item>

<item>
  <title>Dedicated Control Panel outage</title>
  <description>
    Type: Incident
    Duration: 1 minute

    Affected Components: Dedicated Control Panel
    Jul 31, 14:23:42 GMT+0 - Resolved - Dedicated Control Panel is now operational! This update was created by an automated monitoring service. Jul 31, 14:22:51 GMT+0 - Investigating - Dedicated Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>14:23:42</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>Jul <var data-var='date'> 31</var>, <var data-var='time'>14:22:51</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:encoded>
  <pubDate>Fri, 31 Jul 2026 14:22:51 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cms9185wb05rv1aql29gut97q</link>
  <guid>https://liftupau.instatus.com/incident/cms9185wb05rv1aql29gut97q</guid>
</item>

<item>
  <title>Dedicated Control Panel outage</title>
  <description>
    Type: Incident
    Duration: 3 minutes

    Affected Components: Dedicated Control Panel
    Jul 31, 14:21:15 GMT+0 - Resolved - Dedicated Control Panel is now operational! This update was created by an automated monitoring service. Jul 31, 14:17:58 GMT+0 - Investigating - Dedicated Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>14:21:15</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>Jul <var data-var='date'> 31</var>, <var data-var='time'>14:17:58</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:encoded>
  <pubDate>Fri, 31 Jul 2026 14:17:58 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cms911ve90q5s13pfdykyi65y</link>
  <guid>https://liftupau.instatus.com/incident/cms911ve90q5s13pfdykyi65y</guid>
</item>

<item>
  <title>Dedicated Control Panel outage</title>
  <description>
    Type: Incident
    Duration: 1 day, 18 hours and 49 minutes

    Affected Components: Dedicated Control Panel
    Jul 31, 14:07:31 GMT+0 - Resolved - Dedicated Control Panel is now operational! This update was created by an automated monitoring service. Jul 29, 19:18:42 GMT+0 - Investigating - Dedicated Control Panel cannot be accessed at the moment. This incident was created by an automated monitoring service. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 18 hours and 49 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>14:07:31</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>Jul <var data-var='date'> 29</var>, <var data-var='time'>19:18:42</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:encoded>
  <pubDate>Wed, 29 Jul 2026 19:18:42 +0000</pubDate>
  <link>https://liftupau.instatus.com/incident/cms6gwxdw064l0rpaf86nz57l</link>
  <guid>https://liftupau.instatus.com/incident/cms6gwxdw064l0rpaf86nz57l</guid>
</item>

<item>
  <title>Sydney 02 Disk Upgrades</title>
  <description>
    Type: Maintenance
    Duration: 3 hours and 54 minutes

    Affected Components: Sydney 02
    Dec 9, 03:24:14 GMT+0 - Completed - VPS&#039;s are now being booted on the new disk.

We appreciate your patience, and hope you will enjoy the new performance improvement. Dec 9, 01:23:07 GMT+0 - Identified - 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. Dec 8, 23:30:01 GMT+0 - Identified - Maintenance is now in progress Dec 8, 23:30:00 GMT+0 - Identified - 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.** 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> </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>
<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'> 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'> 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>
]]>
  </content:encoded>
  <pubDate>Mon, 8 Dec 2025 23:30:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/cmiopi8co00b91z4qqgf660r8</link>
  <guid>https://liftupau.instatus.com/maintenance/cmiopi8co00b91z4qqgf660r8</guid>
</item>

<item>
  <title>Updates on Panels/Websites</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 30 minutes

    Affected Components: VPS Control Panel, Dedicated Control Panel, Sydney, Australia, Billing Portal
    Sep 10, 02:00:00 GMT+0 - Completed - Maintenance has completed successfully Sep 10, 01:43:43 GMT+0 - Identified - 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. Sep 10, 00:30:01 GMT+0 - Identified - Maintenance is now in progress Sep 10, 00:30:00 GMT+0 - Identified - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 30 minutes</p>
    <p><strong>Affected Components:</strong> , , , </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'>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>
<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'>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>
]]>
  </content:encoded>
  <pubDate>Wed, 10 Sep 2025 00:30:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/cmfcozd1i00ce7o3jpm2xnnmq</link>
  <guid>https://liftupau.instatus.com/maintenance/cmfcozd1i00ce7o3jpm2xnnmq</guid>
</item>

<item>
  <title>Rack Move</title>
  <description>
    Type: Maintenance
    Duration: 3 hours

    Affected Components: Billing Portal, Sydney 03, On-Site Backups, Sydney, Australia, AU Core Router, UK 02, VPS Control Panel, Dedicated Control Panel
    May 18, 03:00:00 GMT+0 - Completed - Maintenance has completed successfully May 18, 02:45:15 GMT+0 - Identified - 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.   
   May 18, 00:00:01 GMT+0 - Identified - Maintenance is now in progress May 18, 00:00:00 GMT+0 - Identified - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> , , , , , , , </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'>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'>00:00:01</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress.</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>
]]>
  </content:encoded>
  <pubDate>Sun, 18 May 2025 00:00:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/cmakhmt4f0001d9nds8yqbcgo</link>
  <guid>https://liftupau.instatus.com/maintenance/cmakhmt4f0001d9nds8yqbcgo</guid>
</item>

<item>
  <title>UK - Upstream Network Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: UK 02, UK Core Router
    Aug 30, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Aug 30, 04:00:01 GMT+0 - Identified - Maintenance is now in progress Aug 30, 04:00:00 GMT+0 - Identified - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> , </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:encoded>
  <pubDate>Fri, 30 Aug 2024 04:00:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/cm0eda6j20002opcdz4rzk380</link>
  <guid>https://liftupau.instatus.com/maintenance/cm0eda6j20002opcdz4rzk380</guid>
</item>

<item>
  <title>Core Router Upgrade</title>
  <description>
    Type: Maintenance
    

    Affected Components: VPS Control Panel, Billing Portal, AU Core Router, Sydney 02, Sydney 03
    May 17, 13:15:00 GMT+0 - Completed - 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 :) May 17, 13:14:31 GMT+0 - Identified - 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 May 17, 12:00:00 GMT+0 - Identified - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> , , , , </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>
<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'>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>
]]>
  </content:encoded>
  <pubDate>Fri, 17 May 2024 12:00:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/clw5eixb676011b4n24o9pjcw8</link>
  <guid>https://liftupau.instatus.com/maintenance/clw5eixb676011b4n24o9pjcw8</guid>
</item>

<item>
  <title>Upstream Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 6 hours

    Affected Components: AU Core Router
    Mar 8, 17:00:00 GMT+0 - Completed - Maintenance has completed successfully Mar 8, 11:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 8, 11:00:00 GMT+0 - Identified - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 6 hours</p>
    <p><strong>Affected Components:</strong> </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>
<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>
]]>
  </content:encoded>
  <pubDate>Fri, 8 Mar 2024 11:00:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/clt3xghrs128146b8my0yubjbev</link>
  <guid>https://liftupau.instatus.com/maintenance/clt3xghrs128146b8my0yubjbev</guid>
</item>

<item>
  <title>UK VPS Maintenance </title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 45 minutes

    
    Feb 22, 15:55:38 GMT+0 - Completed - Maintenance has been completed.

Apologies for the late completion, we&#039;ve been monitoring to ensure network stability Feb 22, 14:10:36 GMT+0 - Identified - Maintenance is now in progress.

Apologies for the doubled-up emails Feb 22, 12:50:00 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![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'>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>
<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>
]]>
  </content:encoded>
  <pubDate>Thu, 22 Feb 2024 12:50:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/clswtlnur781787cboiu05cyi51</link>
  <guid>https://liftupau.instatus.com/maintenance/clswtlnur781787cboiu05cyi51</guid>
</item>

<item>
  <title>Move to Full Rack</title>
  <description>
    Type: Maintenance
    Duration: 7 hours and 56 minutes

    Affected Components: On-Site Backups, VPS Control Panel, Billing Portal, Sydney 02, AU Core Router
    Feb 2, 21:12:33 GMT+0 - Completed - 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 Feb 2, 16:08:59 GMT+0 - Identified - 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 Feb 2, 13:16:21 GMT+0 - Identified - Now in progress Feb 2, 10:30:00 GMT+0 - Identified - 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 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 7 hours and 56 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </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>
<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'>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>
]]>
  </content:encoded>
  <pubDate>Fri, 2 Feb 2024 10:30:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/clrr6von276220biojo3hx1gbd</link>
  <guid>https://liftupau.instatus.com/maintenance/clrr6von276220biojo3hx1gbd</guid>
</item>

<item>
  <title>SYD03 Hardware</title>
  <description>
    Type: Maintenance
    Duration: 5 hours and 47 minutes

    
    Feb 3, 10:00:00 GMT+0 - Identified - Maintenance time and date have been updated and pushed back to be in line with our already upcoming maintenance Feb 2, 16:07:56 GMT+0 - Completed - Hardware has been swapped Feb 2, 10:21:00 GMT+0 - Identified - Maintenance has begun on SYD03\. All clients were moved off during the week Feb 2, 10:00:00 GMT+0 - Identified - 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 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours and 47 minutes</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>
<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'> 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>
]]>
  </content:encoded>
  <pubDate>Fri, 2 Feb 2024 10:00:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/clrr79dbw80929biojpxpbti1z</link>
  <guid>https://liftupau.instatus.com/maintenance/clrr79dbw80929biojpxpbti1z</guid>
</item>

<item>
  <title>Emergency Maintenence - SYD03</title>
  <description>
    Type: Maintenance
    Duration: 6 hours and 10 minutes

    
    Jan 10, 15:09:40 GMT+0 - Completed - Hypervisor has been re-provisioned and servers are being moved onto this to balance the load Jan 10, 12:08:53 GMT+0 - Identified - 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. Jan 10, 10:44:24 GMT+0 - Identified - 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.



 Jan 10, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 10, 09:00:00 GMT+0 - Identified - 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 
  </description>
  <content:encoded>
    <![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'>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: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'>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:encoded>
  <pubDate>Wed, 10 Jan 2024 09:00:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/clr7jpy5i156830bmorwn26nzcm</link>
  <guid>https://liftupau.instatus.com/maintenance/clr7jpy5i156830bmorwn26nzcm</guid>
</item>

<item>
  <title>Upstream Maintence</title>
  <description>
    Type: Maintenance
    Duration: 2 hours and 10 minutes

    Affected Components: On-Site Backups, VPS Control Panel, Billing Portal, Sydney 02, AU Core Router
    Dec 30, 13:10:02 GMT+0 - Completed - The network has come back online. We were informed that the extended delay was due to route convergence. Dec 30, 12:53:27 GMT+0 - Identified - 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. Dec 30, 11:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 30, 11:00:00 GMT+0 - Identified - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </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>
<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: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'>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>
]]>
  </content:encoded>
  <pubDate>Sat, 30 Dec 2023 11:00:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/clqpwxyir13804bkob6iwqc3w1</link>
  <guid>https://liftupau.instatus.com/maintenance/clqpwxyir13804bkob6iwqc3w1</guid>
</item>

<item>
  <title>Datacentre Move - VPS &amp; Web Outage</title>
  <description>
    Type: Maintenance
    Duration: 4 days, 21 hours and 54 minutes

    Affected Components: On-Site Backups, VPS Control Panel, Billing Portal, Sydney 02, AU Core Router
    Dec 19, 08:33:53 GMT+0 - Completed - 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. Dec 18, 21:40:54 GMT+0 - Identified - 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


 Dec 18, 11:09:26 GMT+0 - Identified - Still in progress - Running a bit over. Currently troubleshooting network configuration.

Will update ASAP Dec 18, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 18, 07:00:00 GMT+0 - Identified - 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.



 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 days, 21 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> , , , , </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'>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>
<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'>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'>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>
]]>
  </content:encoded>
  <pubDate>Mon, 18 Dec 2023 07:00:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/clq6i6ls06098b9n75vtb5ccg</link>
  <guid>https://liftupau.instatus.com/maintenance/clq6i6ls06098b9n75vtb5ccg</guid>
</item>

<item>
  <title>Storage Fixes</title>
  <description>
    Type: Maintenance
    Duration: 1 day, 12 hours and 46 minutes

    Affected Components: Sydney 02
    Aug 28, 20:28:39 GMT+0 - Completed - 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. Aug 28, 20:02:34 GMT+0 - Identified - 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. Aug 28, 13:00:00 GMT+0 - Identified - Maintenance is now in progress. Aug 28, 11:29:54 GMT+0 - Identified - 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. Aug 27, 07:43:00 GMT+0 - Identified - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day, 12 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> </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'> 28</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  Maintenance is now in progress..</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'> 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>
]]>
  </content:encoded>
  <pubDate>Mon, 28 Aug 2023 13:00:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/cllt58ib416312bhoaidw7dxfz</link>
  <guid>https://liftupau.instatus.com/maintenance/cllt58ib416312bhoaidw7dxfz</guid>
</item>

<item>
  <title>Network Upgrades</title>
  <description>
    Type: Maintenance
    Duration: 3 hours and 35 minutes

    Affected Components: Sydney 02
    Jul 18, 09:35:16 GMT+0 - Completed - 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. Jul 18, 07:17:18 GMT+0 - Identified - 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.



 Jul 18, 06:38:08 GMT+0 - Identified - Maintenance is now in progress. Jul 18, 06:00:00 GMT+0 - Identified - 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 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours and 35 minutes</p>
    <p><strong>Affected Components:</strong> </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>
<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>
]]>
  </content:encoded>
  <pubDate>Tue, 18 Jul 2023 06:00:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/clk6vn66p151236bgofpjy79n5o</link>
  <guid>https://liftupau.instatus.com/maintenance/clk6vn66p151236bgofpjy79n5o</guid>
</item>

<item>
  <title>Hardware Upgrade</title>
  <description>
    Type: Maintenance
    Duration: 30 minutes

    Affected Components: Sydney 02
    Mar 21, 03:21:01 GMT+0 - Completed - Maintenance has been completed successfully. All VPS&#039;s are booting back online. Mar 21, 02:30:00 GMT+0 - Identified - Maintenance is now in progress. During this time, VPS&#039;s will turn off and back on. Mar 21, 02:30:00 GMT+0 - Identified - 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
 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> </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:encoded>
  <pubDate>Tue, 21 Mar 2023 02:30:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/clfckuhpc251551nodky6o0r2t</link>
  <guid>https://liftupau.instatus.com/maintenance/clfckuhpc251551nodky6o0r2t</guid>
</item>

<item>
  <title>Hardware Upgrade / Swap</title>
  <description>
    Type: Maintenance
    Duration: 50 minutes

    Affected Components: Sydney 02
    Jan 12, 02:53:39 GMT+0 - Completed - The hardware swap and upgrade has been completed. We are monitoring and expect no further issues Jan 12, 02:04:07 GMT+0 - Identified - Our team is at the datacenter and performing the hardware swap. This should take no longer than 10-15 mins. Jan 10, 02:10:00 GMT+0 - Identified - 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 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 50 minutes</p>
    <p><strong>Affected Components:</strong> </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:encoded>
  <pubDate>Thu, 12 Jan 2023 02:10:00 +0000</pubDate>
  <link>https://liftupau.instatus.com/maintenance/clcl8v42f0972i8oab6ujpxs7</link>
  <guid>https://liftupau.instatus.com/maintenance/clcl8v42f0972i8oab6ujpxs7</guid>
</item>

  </channel>
  </rss>