<?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>Curt Creation Status - Incident history</title>
    <link>https://status.curtcreation.net</link>
    <description>Curt Creation</description>
    <pubDate>Thu, 30 Apr 2026 12:33:16 +0000</pubDate>
    
<item>
  <title>cPanel is back up</title>
  <description>
    Type: Incident
    

    
    Apr 30, 12:33:17 GMT+0 - Investigating - cPanel is down at the moment. This incident was automatically created by Instatus monitoring. Apr 30, 13:29:42 GMT+0 - Identified - We are currently aware and issuing a fix over this. Currently our cpanel hosting will be temporarily unavailable and issuing its updates. This is due to an active vulnerability in the cPanel software. More info &lt;https://nvd.nist.gov/vuln/detail/CVE-2026-41940&gt; May 3, 15:07:56 GMT+0 - Monitoring - CPanel has finally released a patch for RockyLinux. We forced update our cpanel and forced reset all cpanel user password.  May 3, 15:15:14 GMT+0 - Resolved - cPanel is back up. This incident was automatically resolved by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:33:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  cPanel is down at the moment. This incident was automatically created by Instatus monitoring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:29:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are currently aware and issuing a fix over this. Currently our cpanel hosting will be temporarily unavailable and issuing its updates. This is due to an active vulnerability in the cPanel software. More info &lt;https://nvd.nist.gov/vuln/detail/CVE-2026-41940&gt;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:07:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  CPanel has finally released a patch for RockyLinux. We forced update our cpanel and forced reset all cpanel user password. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:15:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  cPanel is back up. This incident was automatically resolved by Instatus monitoring..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 30 Apr 2026 12:33:16 +0000</pubDate>
  <link>https://status.curtcreation.net/incident/cmolgsv1c00teweujdxjp7crk</link>
  <guid>https://status.curtcreation.net/incident/cmolgsv1c00teweujdxjp7crk</guid>
</item>

<item>
  <title>Emergency Network Reboot Singapore</title>
  <description>
    Type: Maintenance
    Duration: 15 minutes

    Affected Components: Singapore - Curt Creation
    Jan 18, 07:30:00 GMT+0 - Identified - There will be a Singapore emergency network reboot on exactly 3:30PM GMT +8 due to kernel issues. Connectivity will be down for at least 10 minutes.  Jan 18, 07:30:01 GMT+0 - Identified - Maintenance is now in progress Jan 18, 07:45:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  There will be a Singapore emergency network reboot on exactly 3:30PM GMT +8 due to kernel issues. Connectivity will be down for at least 10 minutes. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:30:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 18 Jan 2026 07:30:00 +0000</pubDate>
  <link>https://status.curtcreation.net/maintenance/cmkjdo39x01slro08wwokrxda</link>
  <guid>https://status.curtcreation.net/maintenance/cmkjdo39x01slro08wwokrxda</guid>
</item>

<item>
  <title>Client Portal, Control Panel and Apps Panel Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 40 minutes

    Affected Components: VPS/vDedicated Control Panel (control.curtcreation.net), Apps/Game Panel (apps.curtcreation.net)
    Dec 12, 17:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Dec 12, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 12, 18:40:26 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 40 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance during that time..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:40:26&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 12 Dec 2025 17:00:00 +0000</pubDate>
  <link>https://status.curtcreation.net/maintenance/cmj33rab307qbxgj2j41hsm5k</link>
  <guid>https://status.curtcreation.net/maintenance/cmj33rab307qbxgj2j41hsm5k</guid>
</item>

<item>
  <title>Singapore is down</title>
  <description>
    Type: Incident
    Duration: 59 minutes

    Affected Components: Global Secure Layer, Singapore - Curt Creation
    Nov 25, 16:19:27 GMT+0 - Investigating -  Nov 25, 16:25:50 GMT+0 - Investigating - We are currently investigating this incident. Nov 25, 16:25:51 GMT+0 - Identified - Network Operation Center Acknowledged the issue and working on a fix. Nov 25, 16:44:33 GMT+0 - Monitoring - GSL NOC implemented a fix and are currently monitoring the result. Nov 25, 17:18:24 GMT+0 - Resolved - This incident has been resolved.

An Arista network device that handles Global Secure Layer (GSL) local transit connection in Singapore had a hardware issue and crashed.

When it restarted, the network had to recalculate a large number of routes, which temporarily affected local routing within Singapore.

We are sorry for this inconvenience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 59 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:19:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:25:50&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:25:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Network Operation Center Acknowledged the issue and working on a fix..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:44:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  GSL NOC implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:18:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved.

An Arista network device that handles Global Secure Layer (GSL) local transit connection in Singapore had a hardware issue and crashed.

When it restarted, the network had to recalculate a large number of routes, which temporarily affected local routing within Singapore.

We are sorry for this inconvenience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 25 Nov 2025 16:19:27 +0000</pubDate>
  <link>https://status.curtcreation.net/incident/cmies6un9000ycn9kkvadui7r</link>
  <guid>https://status.curtcreation.net/incident/cmies6un9000ycn9kkvadui7r</guid>
</item>

<item>
  <title>Singapore is down</title>
  <description>
    Type: Incident
    

    Affected Components: Singapore - Curt Creation
    Nov 17, 22:39:37 GMT+0 - Investigating -  Nov 17, 23:06:47 GMT+0 - Investigating - We are currently investigating this incident. Nov 17, 23:15:27 GMT+0 - Resolved -  Nov 17, 23:46:05 GMT+0 - Postmortem - At approximately 06:00 (GMT+8) we observed a critical stability issue on our core network infrastructure following an upgrade to the latest Linux kernel. The new kernel introduced a regression in the network stack / NIC driver, which caused the affected network interfaces to crash and reset repeatedly under load. This behavior manifested as intermittent link flaps, packet loss, and periods of full connectivity loss for services routed through the impacted nodes.

Our engineering team immediately initiated a controlled rollback to our previously validated, stable kernel version. This required a reboot of key network systems to safely revert the kernel and restore interface stability. However, the recovery process took longer than expected due to an unforeseen issue with our IPMI. The IPMI interface for the affected device became inaccessible, preventing us from performing the usual remote power-cycle and recovery procedures.

Our on-site engineer was dispatched to the data center to restore IPMI functionality and manually reboot the impacted network equipment. After IPMI access was recovered and the systems were rebooted into the stable kernel, the network interfaces returned to normal operation, and traffic flows were restored.

We are keeping the affected systems on the previous stable kernel while we further analyze the regression in the newer kernel version, review NIC driver compatibility, and tighten our kernel rollout and soak-testing procedures to prevent similar incidents in the future. Continuous monitoring is in place to ensure ongoing stability of the network stack and interfaces. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:39:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:06:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:15:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:46:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Postmortem&lt;/strong&gt; -
  At approximately 06:00 (GMT+8) we observed a critical stability issue on our core network infrastructure following an upgrade to the latest Linux kernel. The new kernel introduced a regression in the network stack / NIC driver, which caused the affected network interfaces to crash and reset repeatedly under load. This behavior manifested as intermittent link flaps, packet loss, and periods of full connectivity loss for services routed through the impacted nodes.

Our engineering team immediately initiated a controlled rollback to our previously validated, stable kernel version. This required a reboot of key network systems to safely revert the kernel and restore interface stability. However, the recovery process took longer than expected due to an unforeseen issue with our IPMI. The IPMI interface for the affected device became inaccessible, preventing us from performing the usual remote power-cycle and recovery procedures.

Our on-site engineer was dispatched to the data center to restore IPMI functionality and manually reboot the impacted network equipment. After IPMI access was recovered and the systems were rebooted into the stable kernel, the network interfaces returned to normal operation, and traffic flows were restored.

We are keeping the affected systems on the previous stable kernel while we further analyze the regression in the newer kernel version, review NIC driver compatibility, and tighten our kernel rollout and soak-testing procedures to prevent similar incidents in the future. Continuous monitoring is in place to ensure ongoing stability of the network stack and interfaces..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 17 Nov 2025 22:39:34 +0000</pubDate>
  <link>https://status.curtcreation.net/incident/cmi3q8vgz001ep6z6qoilgnig</link>
  <guid>https://status.curtcreation.net/incident/cmi3q8vgz001ep6z6qoilgnig</guid>
</item>

<item>
  <title>SG Node 4 &amp; Node 8 - Server Migration</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: SGP-4, SGP-8
    Oct 17, 21:30:00 GMT+0 - Identified - **For customers on Singapore - Node 4 &amp; Node 8**: We will be migrating your server/s to our newest nodes. Your server files will remain the same but your server&#039;s ip will change.

**Affects:** Singapore - Node 4 &amp; Node 8

**What do expect:** During maintenance, your server will shut down automatically and will be inaccessible for a maximum of 30 minutes. It will be powered back on once the migration to the new node is successful.

**How to know my server node?** Here&#039;s a guide &lt;https://help.curtcreation.net/t/how-to-know-my-servers-node/22/1&gt; Oct 17, 21:30:01 GMT+0 - Identified - Maintenance is now in progress Oct 17, 22:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  **For customers on Singapore - Node 4 &amp; Node 8**: We will be migrating your server/s to our newest nodes. Your server files will remain the same but your server&#039;s ip will change.

**Affects:** Singapore - Node 4 &amp; Node 8

**What do expect:** During maintenance, your server will shut down automatically and will be inaccessible for a maximum of 30 minutes. It will be powered back on once the migration to the new node is successful.

**How to know my server node?** Here&#039;s a guide &lt;https://help.curtcreation.net/t/how-to-know-my-servers-node/22/1&gt;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:30:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 17 Oct 2025 21:30:00 +0000</pubDate>
  <link>https://status.curtcreation.net/maintenance/cmgs65t1a00flbz85tu9gc6xl</link>
  <guid>https://status.curtcreation.net/maintenance/cmgs65t1a00flbz85tu9gc6xl</guid>
</item>

<item>
  <title>SG Node 7 - Server Migration</title>
  <description>
    Type: Maintenance
    

    Affected Components: SGP-7
    Oct 15, 21:43:08 GMT+0 - Identified - In Progress Oct 15, 21:43:08 GMT+0 - Identified - **For customers on Singapore - Node 4 &amp; Node 8**: We will be migrating your server/s to our newest nodes. Your server files will remain the same but your server&#039;s ip will change.

**Affects:** Singapore - Node 7

**What do expect:** During maintenance, your server will shut down automatically and will be inaccessible for a maximum of 30 minutes. It will be powered back on once the migration to the new node is successful.

**How to know my server node?** Here&#039;s a guide &lt;https://help.curtcreation.net/t/how-to-know-my-servers-node/22/1&gt; Oct 15, 21:43:08 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:43:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  In Progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:43:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  **For customers on Singapore - Node 4 &amp; Node 8**: We will be migrating your server/s to our newest nodes. Your server files will remain the same but your server&#039;s ip will change.

**Affects:** Singapore - Node 7

**What do expect:** During maintenance, your server will shut down automatically and will be inaccessible for a maximum of 30 minutes. It will be powered back on once the migration to the new node is successful.

**How to know my server node?** Here&#039;s a guide &lt;https://help.curtcreation.net/t/how-to-know-my-servers-node/22/1&gt;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:43:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 15 Oct 2025 21:43:08 +0000</pubDate>
  <link>https://status.curtcreation.net/maintenance/cmgsa5q3f018ex8z58cxrug22</link>
  <guid>https://status.curtcreation.net/maintenance/cmgsa5q3f018ex8z58cxrug22</guid>
</item>

<item>
  <title>[PH-NETWORK] International Transit Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Makati, Philippines - Curt Creation
    Oct 14, 20:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 14, 21:00:00 GMT+0 - Completed - Maintenance has completed successfully Oct 14, 20:00:00 GMT+0 - Identified - International Traffic for our Philippine Network will be interrupted on this maintenance. Local Traffic will not be affected. As we switch our core router in Singapore. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  International Traffic for our Philippine Network will be interrupted on this maintenance. Local Traffic will not be affected. As we switch our core router in Singapore..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 14 Oct 2025 20:00:00 +0000</pubDate>
  <link>https://status.curtcreation.net/maintenance/cmgqmmz0d00fcwf1ca34ve7mn</link>
  <guid>https://status.curtcreation.net/maintenance/cmgqmmz0d00fcwf1ca34ve7mn</guid>
</item>

  </channel>
  </rss>