
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      
      <title>Civo Ltd</title>
      <link>https://status.civo.com/</link>
      <description>Incident history</description>
      <generator>github.com/cstate</generator>
      <language>en</language>
      
      <lastBuildDate>Tue, 30 Jun 2026 19:57:00 +0000</lastBuildDate>
      
      
      
        <atom:link href="https://status.civo.com/index.xml" rel="self" type="application/rss+xml" />
      
      
      
        <item>
          <title>[Resolved] Service disruption in FRA1</title>
          <link>https://status.civo.com/issues/2026-06-30-fra1-disruption/</link>
          <pubDate>Tue, 30 Jun 2026 19:57:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-06-30-fra1-disruption/</guid>
          <category>2026-07-01 21:58:00</category>
          <description>&lt;p&gt;2026-07-02 06:14 UTC&lt;/p&gt;
&lt;p&gt;This incident is now resolved. Service was restored at approximately 21:58 UTC on 1 July 2026. Our engineering team has monitored throughout the night and confirmed that compute and Kubernetes cluster instance services in the FRA1 region are operating normally. This incident is now closed.&lt;/p&gt;
&lt;p&gt;We apologise for the disruption and any impact to your services.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-07-01 21:11 UTC&lt;/p&gt;
&lt;p&gt;Our engineering team is still actively investigating the issues affecting some compute and Kubernetes cluster instances in the FRA1 region. We will provide a further update as soon as we have more information.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-07-01 20:00 UTC&lt;/p&gt;
&lt;p&gt;We are currently experiencing issues affecting some compute and Kubernetes cluster instances in the FRA1 region. Our engineering team is actively investigating and working to restore normal service as soon as possible.&lt;/p&gt;
&lt;p&gt;We will provide further updates as more information becomes available.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-07-01 06:07 UTC&lt;/p&gt;
&lt;p&gt;All compute and Kubernetes cluster instance services in the FRA1 region have been restored.&lt;/p&gt;
&lt;p&gt;We are aware of some residual volume-attachment issues affecting a limited number of instances, which our engineering team is actively working to resolve. We will provide a further update once these have been fully cleared.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-06-30 22:00 UTC&lt;/p&gt;
&lt;p&gt;We are seeing recovery across the affected compute and Kubernetes cluster instances in the FRA1 region. Our engineering team is now monitoring to confirm the issue is fully resolved.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;We are aware of an issue impacting some compute instances and Kubernetes cluster instances in the FRA1 region.&lt;/p&gt;
&lt;p&gt;Our engineering team is actively investigating and we are working to restore service as soon as possible. We will provide further updates as more information becomes available.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Storage and compute instability in FRA1</title>
          <link>https://status.civo.com/issues/2026-06-30-fra1-storage-compute-instability/</link>
          <pubDate>Tue, 30 Jun 2026 09:45:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-06-30-fra1-storage-compute-instability/</guid>
          <category>2026-06-30 14:22:00</category>
          <description>&lt;p&gt;2026-06-30 14:22 UTC&lt;/p&gt;
&lt;p&gt;This incident is now resolved. Storage and compute services in the FRA1 region are operating normally.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-06-30 11:15 UTC&lt;/p&gt;
&lt;p&gt;We have applied a fix and storage and compute services in the FRA1 region have recovered. We are now monitoring to confirm the issue is fully resolved.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-06-30 10:30 UTC&lt;/p&gt;
&lt;p&gt;We continue to investigate the storage and compute instability in the FRA1 region.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-06-30 09:45 UTC&lt;/p&gt;
&lt;p&gt;We are investigating storage and compute instability in the FRA1 region. Some customer instances and volumes may be experiencing degraded performance or be unavailable. Our engineering team is actively investigating the cause and we will provide further updates as more information becomes available.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Civo dashboard &amp; API issues accessing NYC1</title>
          <link>https://status.civo.com/issues/2026-06-26-nyc1-issues/</link>
          <pubDate>Fri, 26 Jun 2026 04:00:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-06-26-nyc1-issues/</guid>
          <category>2026-06-26 05:50:00</category>
          <description>&lt;p&gt;2026-06-26 04:00 UTC&lt;/p&gt;
&lt;p&gt;We are aware of issues accessing the Civo dashboard and API with error pages occurring for some users accessing their NYC1 resources. We are investigating the cause.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-06-26 05:10 UTC&lt;/p&gt;
&lt;p&gt;We have applied a mitigation and access to NYC1 resources via the Civo dashboard and API has recovered. Error rates have returned to normal and we are monitoring to confirm the fix holds.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-06-26 05:50 UTC&lt;/p&gt;
&lt;p&gt;The issue is now resolved.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Scheduled Emergency Maintenance in PHX1</title>
          <link>https://status.civo.com/issues/2026-06-24-emergency_maintenance_phx1/</link>
          <pubDate>Wed, 24 Jun 2026 09:00:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-06-24-emergency_maintenance_phx1/</guid>
          <category>2026-07-01 13:00:00</category>
          <description>&lt;p&gt;2026-07-01 13:00 UTC&lt;/p&gt;
&lt;p&gt;This maintenance is now complete. All planned work across the Phoenix (PHX1) region has finished — ahead of the scheduled window — with no data loss and no impact to persistent storage, running instances, or clusters. Thank you for your patience.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;We will be carrying out emergency maintenance across the Phoenix (PHX1) region between 24 June and 8 July 2026 to improve platform stability and reliability.&lt;/p&gt;
&lt;p&gt;All disruptive work will be performed out of hours (overnight, region local time), and disruption will be kept to a minimum. Instances and clusters should not be impacted. Router and load balancer services will undergo quick restarts out of hours, causing brief network disruption of a few seconds.&lt;/p&gt;
&lt;p&gt;There will be no data loss and persistent storage will be unaffected. Updates will be posted here as the work progresses.&lt;/p&gt;
&lt;hr&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Planned Maintenance in FRA1</title>
          <link>https://status.civo.com/issues/2026-04-13-planned_maintenance_in_fra1/</link>
          <pubDate>Mon, 13 Apr 2026 00:00:01 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-04-13-planned_maintenance_in_fra1/</guid>
          <category>2026-04-21 21:30:00</category>
          <description>&lt;p&gt;2026-04-21 21:30:00 UTC&lt;/p&gt;
&lt;p&gt;This scheduled maintenance is now complete. All FRA1 compute nodes have been successfully upgraded with no customer-impacting issues. Thank you for your patience.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;We will be performing scheduled maintenance in the FRA1 region starting the week of 13 April 2026, with a duration of approximately two weeks.&lt;/p&gt;
&lt;p&gt;Compute instances and Kubernetes nodes will be live migrated with no expected downtime. A small number of other services may experience brief interruptions of a few seconds as they are restarted.&lt;/p&gt;
&lt;p&gt;No action is required on your part. We will continue to monitor the situation closely and provide updates as maintenance progresses.&lt;/p&gt;
&lt;hr&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] API actions to workloads disrupted in FRA1</title>
          <link>https://status.civo.com/issues/2026-03-24-fra1-api-disruption/</link>
          <pubDate>Tue, 24 Mar 2026 07:07:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-03-24-fra1-api-disruption/</guid>
          <category>2026-03-24 08:31:00</category>
          <description>&lt;p&gt;2026-03-24 08:31:00 UTC&lt;/p&gt;
&lt;p&gt;The issue affecting API actions to workloads in the FRA1 region has been resolved. All services have returned to normal operation.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-03-24 07:33:00 UTC&lt;/p&gt;
&lt;p&gt;A fix has been implemented for the issue affecting API actions to workloads in the FRA1 region. We are now monitoring to confirm services have returned to normal. We will provide further updates as needed.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;We are aware of an issue affecting API actions to workloads in the FRA1 region. Our engineering team is actively investigating and we will provide updates as more information becomes available.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Partial GPU outage in LON1</title>
          <link>https://status.civo.com/issues/2026-03-14-partial-gpu-outage-lon1/</link>
          <pubDate>Sat, 14 Mar 2026 08:40:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-03-14-partial-gpu-outage-lon1/</guid>
          <category>2026-03-15 09:00:00</category>
          <description>&lt;p&gt;2026-03-15 09:00:00 UTC&lt;/p&gt;
&lt;p&gt;All services have been restored and are stable. The issue is now resolved.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-03-14 13:46:00 UTC&lt;/p&gt;
&lt;p&gt;All customer workload has been restored. We are continuing to monitor the region for stability before closing this incident.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-03-14 08:40:00 UTC&lt;/p&gt;
&lt;p&gt;We are aware of an issue affecting some GPU compute instances (B200 nodes) in the LON1 region. Our team is actively investigating and working with the data centre provider to restore service. We will provide further updates as more information becomes available.&lt;/p&gt;
&lt;hr&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Service disruption in FRA1</title>
          <link>https://status.civo.com/issues/2026-02-24-fra1-disruption/</link>
          <pubDate>Tue, 24 Feb 2026 15:12:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-02-24-fra1-disruption/</guid>
          <category>2026-03-25 10:00:00</category>
          <description>&lt;p&gt;2026-03-25 10:00:00 UTC&lt;/p&gt;
&lt;p&gt;This incident is now resolved. The root causes have been identified and fixes have been deployed to the FRA1 region. All services are operating normally and we continue to monitor.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-02-25 15:41:00 UTC&lt;/p&gt;
&lt;p&gt;We continue to monitor the FRA1 region. All services are online and we will provide further updates as more information becomes available.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-02-25 01:00:00 UTC&lt;/p&gt;
&lt;p&gt;We are continuing to monitor the FRA1 region. Affected customer instances and volumes may still be experiencing impact. We will provide further updates as more information becomes available.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-02-24 20:56:00 UTC&lt;/p&gt;
&lt;p&gt;Our investigation into the FRA1 disruption is ongoing. Affected customer instances and volumes in the FRA1 region continue to be impacted. We will provide further updates as more information becomes available.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-02-24 18:28:00 UTC&lt;/p&gt;
&lt;p&gt;We are continuing to investigate the disruption in the FRA1 region and are working towards a resolution. Affected customer instances and volumes remain impacted while we work to restore services. We will provide another update shortly.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-02-24 17:40:00 UTC&lt;/p&gt;
&lt;p&gt;Our engineering team is actively investigating the disruption affecting customer instances and volumes in the FRA1 region. We are working to restore full functionality as soon as possible. We will provide further updates as more information becomes available.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;A subset of customer instances and volumes are being impacted on the FRA1 region, this
is preventing these instances from starting and volumes being attached to them.&lt;/p&gt;
&lt;p&gt;We are currently working on resolving these.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Plannned Maintenance in FRA1 2026-02-09</title>
          <link>https://status.civo.com/issues/fra1_maintenance_2026-02-09/</link>
          <pubDate>Mon, 09 Feb 2026 00:00:01 +0000</pubDate>
          <guid>https://status.civo.com/issues/fra1_maintenance_2026-02-09/</guid>
          <category>2026-02-27 09:00:00</category>
          <description>&lt;p&gt;2026-02-27 09:00:00 UTC&lt;/p&gt;
&lt;p&gt;The scheduled maintenance for the FRA1 region has been completed successfully. Thank you for your patience during this period.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&#34;we-will-continue-to-monitor-the-situation-closely-and-appreciate-your-understanding-in-this-matter&#34;&gt;Our FRA1 region will be undergoing scheduled upgrades commencing on February 9th, with a duration of approximately three weeks.
While we anticipate no service disruptions during this period, we are designating this as a precautionary maintenance window to ensure the highest level of safety and reliability.
We will continue to monitor the situation closely and appreciate your understanding in this matter.&lt;/h2&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] High latencies accessing NYC1 resources</title>
          <link>https://status.civo.com/issues/2026-02-06-nyc1-latencies/</link>
          <pubDate>Fri, 06 Feb 2026 07:21:23 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-02-06-nyc1-latencies/</guid>
          <category>2026-01-29 09:55:00</category>
          <description>&lt;p&gt;2026-02-06 07:21:23 UTC&lt;/p&gt;
&lt;p&gt;Network instabilities are causing high latencies when accessing some resources in NYC1 region. Our engineers are looking at this issue.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-02-06 09:55:00 UTC&lt;/p&gt;
&lt;p&gt;The issue is now resolved.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Nodes Not Ready LON1 2025-09-10</title>
          <link>https://status.civo.com/issues/2026-01-29-lon1-customer-nodes-not-ready/</link>
          <pubDate>Thu, 29 Jan 2026 13:13:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-01-29-lon1-customer-nodes-not-ready/</guid>
          <category>2026-01-29 17:05:00</category>
          <description>&lt;h2 id=&#34;in-order-to-fully-resolve-some-customer-workloads-may-need-to-be-restarted&#34;&gt;Network instabilities are causing some clusters to fall into not ready state.
In order to fully resolve some customer workloads may need to be restarted.&lt;/h2&gt;
&lt;p&gt;2026-01-12 17:05 UTC&lt;/p&gt;
&lt;p&gt;The issue is now resolved; some customer workloads were restarted whilst resolving this.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Issues provisioning instances and volumes in MUM1</title>
          <link>https://status.civo.com/issues/2026-01-21-mum1-provisioning-issues/</link>
          <pubDate>Wed, 21 Jan 2026 14:10:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-01-21-mum1-provisioning-issues/</guid>
          <category>2026-01-21 15:00:00</category>
          <description>&lt;p&gt;2026-01-21 14:10:00&lt;/p&gt;
&lt;p&gt;We are aware of issues provisioning new instances and volumes in the MUM1 region. We are actively working to resolve this issue. Existing workloads are not affected.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-01-21 15:00:00&lt;/p&gt;
&lt;p&gt;The issue is now resolved.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Planned Network Maintenance in LON1 2026-01-13</title>
          <link>https://status.civo.com/issues/2026-01-13-planned_maintenance_in_lon1/</link>
          <pubDate>Tue, 13 Jan 2026 21:00:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-01-13-planned_maintenance_in_lon1/</guid>
          <category>2026-01-13 22:10:00</category>
          <description>&lt;h2 id=&#34;scheduled-maintenance-will-take-place-in-the-lon1-region-on-tuesday-13-january-2026-starting-at-2100-utc-this-work-involves-network-equipment-supporting-our-gpu-services-we-do-not-expect-any-impact-to-running-services&#34;&gt;Scheduled maintenance will take place in the LON1 region on Tuesday 13 January 2026, starting at 21:00 UTC. This work involves network equipment supporting our GPU services. We do not expect any impact to running services.&lt;/h2&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Civo website issues</title>
          <link>https://status.civo.com/issues/2026-01-12-website-issues/</link>
          <pubDate>Mon, 12 Jan 2026 09:29:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2026-01-12-website-issues/</guid>
          <category>2026-01-12 09:55:00</category>
          <description>&lt;p&gt;2026-01-12 09:29 UTC&lt;/p&gt;
&lt;p&gt;We are aware of issues accessing the Civo.com website and dashboard with error pages occurring for some users. We are investigating the cause.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2026-01-12 09:55 UTC&lt;/p&gt;
&lt;p&gt;The issue is now resolved.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Planned Network Maintenance in LON1 2025-12-17</title>
          <link>https://status.civo.com/issues/2025-12-17-planned_maintenance_in_lon1/</link>
          <pubDate>Wed, 17 Dec 2025 21:00:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-12-17-planned_maintenance_in_lon1/</guid>
          <category>2025-12-17 21:20:00</category>
          <description>&lt;h2 id=&#34;scheduled-maintenance-will-take-place-in-the-lon1-region-on-wednesday-17-december-2025-starting-at-2100-utc-this-work-involves-network-equipment-supporting-our-gpu-services-we-do-not-expect-any-impact-to-running-services&#34;&gt;Scheduled maintenance will take place in the LON1 region on Wednesday 17 December 2025, starting at 21:00 UTC. This work involves network equipment supporting our GPU services. We do not expect any impact to running services.&lt;/h2&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Planned Network Maintenance in LON1 2025-12-16</title>
          <link>https://status.civo.com/issues/2025-12-16-planned_maintenance_in_lon1/</link>
          <pubDate>Tue, 16 Dec 2025 21:00:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-12-16-planned_maintenance_in_lon1/</guid>
          <category>2025-12-16 21:30:00</category>
          <description>&lt;h2 id=&#34;scheduled-maintenance-will-take-place-in-the-lon1-region-on-tuesday-16-december-2025-starting-at-2100-utc-this-work-involves-network-equipment-supporting-our-gpu-services-we-do-not-expect-any-impact-to-running-services&#34;&gt;Scheduled maintenance will take place in the LON1 region on Tuesday 16 December 2025, starting at 21:00 UTC. This work involves network equipment supporting our GPU services. We do not expect any impact to running services.&lt;/h2&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Plannned Maintenance in FRA1 2025-12-11</title>
          <link>https://status.civo.com/issues/2025-12-11-planned_maintenance_in_fra1/</link>
          <pubDate>Thu, 11 Dec 2025 21:00:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-12-11-planned_maintenance_in_fra1/</guid>
          <category>2025-12-11 22:30:00</category>
          <description>&lt;h2 id=&#34;were-performing-scheduled-maintenance-in-the-fra1-region-on-thursday-11-december-2025-from-2100-utc-to-improve-network-resiliency-during-this-window-services-may-experience-short-periods-of-network-interuption-of-up-to-a-few-seconds&#34;&gt;We&amp;rsquo;re performing scheduled maintenance in the FRA1 region on Thursday 11 December 2025, from 21:00 UTC to improve network resiliency. During this window services may experience short periods of network interuption of up to a few seconds.&lt;/h2&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Plannned Maintenance in LON1 2025-12-10</title>
          <link>https://status.civo.com/issues/2025-12-10-planned_maintenance_in_lon1/</link>
          <pubDate>Wed, 10 Dec 2025 21:00:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-12-10-planned_maintenance_in_lon1/</guid>
          <category>2025-12-10 22:30:00</category>
          <description>&lt;h2 id=&#34;were-performing-scheduled-maintenance-in-the-lon1-region-on-wednesday-10-december-2025-from-2100-utc-to-improve-network-resiliency-during-this-window-services-may-experience-short-periods-of-network-interuption-of-up-to-a-few-seconds&#34;&gt;We&amp;rsquo;re performing scheduled maintenance in the LON1 region on Wednesday 10 December 2025, from 21:00 UTC to improve network resiliency. During this window services may experience short periods of network interuption of up to a few seconds.&lt;/h2&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Plannned Maintenance in NYC1 2025-12-09</title>
          <link>https://status.civo.com/issues/2025-12-09-planned_maintenance_in_nyc1/</link>
          <pubDate>Tue, 09 Dec 2025 10:00:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-12-09-planned_maintenance_in_nyc1/</guid>
          <category>2025-12-09 13:10:00</category>
          <description>&lt;h2 id=&#34;were-performing-scheduled-maintenance-in-the-nyc1-region-on-tuesday-09-december-2025-from-1000-utc-to-improve-network-resiliency-during-this-window-services-may-experience-short-periods-of-network-interuption-of-up-to-a-few-seconds&#34;&gt;We&amp;rsquo;re performing scheduled maintenance in the NYC1 region on Tuesday 09 December 2025, from 10:00 UTC to improve network resiliency. During this window services may experience short periods of network interuption of up to a few seconds.&lt;/h2&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] GPU Service disruption LON2</title>
          <link>https://status.civo.com/issues/2025-10-15-further-disruption-lon2/</link>
          <pubDate>Wed, 15 Oct 2025 15:55:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-10-15-further-disruption-lon2/</guid>
          <category>2025-10-15 21:03:00</category>
          <description>&lt;p&gt;2025-10-15 21:03:00 UTC&lt;/p&gt;
&lt;p&gt;The engineers have resolved the electrical fault and all customer services have been restored.&lt;/p&gt;
&lt;p&gt;Civo engnineers will continue to monitor the region.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-10-15 19:48:00 UTC&lt;/p&gt;
&lt;p&gt;Engineers continue to work on reslving the cause of the electrical fault. We will provide further updates in 1 hour.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-10-15 18:26:00 UTC&lt;/p&gt;
&lt;p&gt;Engineers have identified the cause of the fault in the electrical loop and are working to get this resolved. We will provide further updates in 1 hour.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-10-15 16:45:00 UTC&lt;/p&gt;
&lt;p&gt;The issue has been identified as an fault in the electrical loop for the cooling system.
Engineers are working to get this resolved. We will provide further updates in 1 hour.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-10-15 15:55:00 UTC&lt;/p&gt;
&lt;p&gt;We are having to shut down GPU workloads due to technical issues onsite.&lt;/p&gt;
&lt;hr&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Service disruption LON2</title>
          <link>https://status.civo.com/issues/2025-10-15-disruption-lon2/</link>
          <pubDate>Wed, 15 Oct 2025 04:08:45 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-10-15-disruption-lon2/</guid>
          <category>2025-10-15 08:15:00</category>
          <description>&lt;p&gt;2025-10-15 08:15:00 UTC&lt;/p&gt;
&lt;p&gt;All services have been restored and are stable. The issue is now resolved.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-10-15 07:42:00 UTC&lt;/p&gt;
&lt;p&gt;All customer workload is now started. We will continue to monitor the region stability before closing the status.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-10-15 07:10:00 UTC&lt;/p&gt;
&lt;p&gt;The data center temperatures are back under control and we are working with the data center team to gradually power servers on and monitor the situation.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-10-15 06:45:00 UTC&lt;/p&gt;
&lt;p&gt;The data center provider are working to restore temperatures to operational levels. We will provide a further update within the next 30 minutes.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-10-15 06:30:00 UTC&lt;/p&gt;
&lt;p&gt;The data center provider are working to restore temperatures to operational levels. We will provide a further update within the next 15 minutes.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-10-15 06:15:00 UTC&lt;/p&gt;
&lt;p&gt;The data center provider are working to restore temperatures to operational levels. We will provide a further update within the next 15 minutes.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-10-15 06:00:00 UTC&lt;/p&gt;
&lt;p&gt;The incident was identified as a cooling issue in the data center and we are working with the data center provider to restore service. This will be impacting all GPU based instances.&lt;/p&gt;
&lt;p&gt;The cause has been resolved and temperatures are returning to an operational level, at which point we will begin restoring customer services.&lt;/p&gt;
&lt;p&gt;We will provide another update in 15 minutes.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-10-15 04:08:45 UTC&lt;/p&gt;
&lt;p&gt;We are facing an issue in the LON2 region, that is affecting certain customer workloads. We are working with our provider to restore services back.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Plannned Maintenancein LON1 2025-09-10</title>
          <link>https://status.civo.com/issues/2025-09-14-planned_maintenance_in_lon1/</link>
          <pubDate>Wed, 10 Sep 2025 21:00:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-09-14-planned_maintenance_in_lon1/</guid>
          <category>2025-09-10 23:00:00</category>
          <description>&lt;h2 id=&#34;were-performing-scheduled-maintenance-in-the-lon1-region-on-wednesday-10-september-from-2100-bst-to-improve-network-resiliency-although-we-dont-expect-any-customer-impact-theres-a-potential-1-hour-window-of-disruption-between-2100-and-2200-bst&#34;&gt;We&amp;rsquo;re performing scheduled maintenance in the LON1 region on Wednesday, 10 September, from 21:00 BST to improve network resiliency. Although we don&amp;rsquo;t expect any customer impact, there&amp;rsquo;s a potential 1-hour window of disruption between 21:00 and 22:00 BST.&lt;/h2&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Unexpected instance restarts</title>
          <link>https://status.civo.com/issues/2025-09-14-nyc1-storage-issue/</link>
          <pubDate>Thu, 14 Aug 2025 12:40:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-09-14-nyc1-storage-issue/</guid>
          <category>2025-08-14 13:20:00</category>
          <description>&lt;p&gt;2025-08-14 13:20:00 UTC&lt;/p&gt;
&lt;p&gt;All compute instances are now in a running state.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-08-14 12:00:00 UTC&lt;/p&gt;
&lt;p&gt;A small number of compute instances in the NYC1 region have experienced an unexpected restart. We are workking to restore all instances to a running state.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] GPU Compute instance outage LON2</title>
          <link>https://status.civo.com/issues/2025-07-30-gpu-nodes-offline_lon2/</link>
          <pubDate>Wed, 30 Jul 2025 10:25:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-07-30-gpu-nodes-offline_lon2/</guid>
          <category>2025-07-30 12:35:00</category>
          <description>&lt;p&gt;2025-07-30 12:46:00 UTC&lt;/p&gt;
&lt;p&gt;All services have been restored and are stable. The issue is now resolved.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-07-30 12:34:00 UTC&lt;/p&gt;
&lt;p&gt;All customer workload is now started. We will continue to monitor the region stability before closing the status.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-07-30 12:19:00 UTC&lt;/p&gt;
&lt;p&gt;We have begin a controlled power on of customer workload and will provide another update in 15 minutes.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-07-30 12:00:00 UTC&lt;/p&gt;
&lt;p&gt;The data center temperatures are back under control and we are working with the data center team to gradually power servers on.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-07-30 11:42:00 UTC&lt;/p&gt;
&lt;p&gt;The data center provider continue to work towards resolving the problem. We will provide a further update within the next 15 minutes.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-07-30 11:24:00 UTC&lt;/p&gt;
&lt;p&gt;The data center provider continue to work towards resolving the problem. We will provide a further update within the next 15 minutes.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-07-30 11:09:00 UTC&lt;/p&gt;
&lt;p&gt;We have been notified of a cooling issue at the LON2 datacenter. The data center provider is actively working to resolve the problem. We will provide a further update within the next 15 minutes.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-07-30 10:55:00 UTC&lt;/p&gt;
&lt;p&gt;We are still investigating the issue with the datacenter and will provide regular updates.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-07-30 10:25:00 UTC&lt;/p&gt;
&lt;p&gt;We are facing an issue in the LON2 region, that is affecting certain GPU compute instances. We are working to restore service.&lt;/p&gt;
&lt;hr&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Emergency Maintenancein LON2</title>
          <link>https://status.civo.com/issues/2025-07-07-emergency_maintenance_lon1/</link>
          <pubDate>Mon, 07 Jul 2025 22:00:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-07-07-emergency_maintenance_lon1/</guid>
          <category>2025-07-07 22:15:00</category>
          <description>&lt;h2 id=&#34;well-be-conducting-emergency-network-maintenance-in-the-lon2-region-on-monday-7-july-at-2200-bst-to-improve-network-resiliency-in-the-region-no-impact-to-customers-is-expected-but-were-posting-at-at-risk-window-of-1-hour-between-2200-and-2300-bst&#34;&gt;We&amp;rsquo;ll be conducting emergency network maintenance in the lon2 region on Monday 7 July at 22:00 BST to improve network resiliency in the region. No impact to customers is expected but we&amp;rsquo;re posting at at-risk window of 1 hour between 22:00 and 23:00 BST.&lt;/h2&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Network disruption FRA1</title>
          <link>https://status.civo.com/issues/2025-06-10-partial-disruption-fra1/</link>
          <pubDate>Tue, 10 Jun 2025 07:30:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-06-10-partial-disruption-fra1/</guid>
          <category>2025-06-10 09:50:00</category>
          <description>&lt;p&gt;2025-06-10 06:50:00 UTC&lt;/p&gt;
&lt;p&gt;We are facing an issue in the FRA1 region, that is affecting certain customer workloads. We&amp;rsquo;re investigating the cause and working to restore services.&lt;/p&gt;
&lt;hr&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Service disruption PHX1</title>
          <link>https://status.civo.com/issues/2025-04-10-disruption-phx1/</link>
          <pubDate>Thu, 10 Apr 2025 09:03:09 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-04-10-disruption-phx1/</guid>
          <category>2025-04-10 11:25:00</category>
          <description>&lt;p&gt;2025-04-10 11:58:23 UTC&lt;/p&gt;
&lt;p&gt;All customer workloads are now online.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-04-10 11:26:23 UTC&lt;/p&gt;
&lt;p&gt;The issue with the PHX1 region has been identified and resolved. Customer workloads are recovering and are coming back online.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-04-10 09:03:09 UTC&lt;/p&gt;
&lt;p&gt;We are facing an issue in the PHX1 region, that is affecting certain customer workloads. We are working with our provider to restore services back.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Civo website issues</title>
          <link>https://status.civo.com/issues/2025-04-01-website-issues/</link>
          <pubDate>Tue, 01 Apr 2025 09:30:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2025-04-01-website-issues/</guid>
          <category>2025-04-01 10:00:00</category>
          <description>&lt;p&gt;2025-04-01 09:56:00&lt;/p&gt;
&lt;p&gt;We are seeing improvement in the reachability and responsiveness of the Civo site and API and are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2025-04-01 09:30:00&lt;/p&gt;
&lt;p&gt;We are aware of issues accessing the Civo.com website, dashboard, and API, with timeouts occurring for some users. We are investigating the cause.&lt;/p&gt;
&lt;hr&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Civo website issues</title>
          <link>https://status.civo.com/issues/2024-11-19-website-issues/</link>
          <pubDate>Tue, 19 Nov 2024 12:00:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2024-11-19-website-issues/</guid>
          <category>2024-11-19 12:40:00</category>
          <description>&lt;p&gt;12:40 UTC&lt;/p&gt;
&lt;p&gt;We are seeing improvement in the reachability and responsiveness of the Civo site and API and are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2024-11-19 12:00 UTC&lt;/p&gt;
&lt;p&gt;We are aware of issues accessing the Civo.com website, dashboard, and API, with timeouts occurring for some users. We are investigating the cause.&lt;/p&gt;
&lt;hr&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Civo website issues</title>
          <link>https://status.civo.com/issues/2024-11-14-website-issues/</link>
          <pubDate>Thu, 14 Nov 2024 09:15:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2024-11-14-website-issues/</guid>
          <category>2024-11-14 09:30:00</category>
          <description>&lt;p&gt;09:30 UTC&lt;/p&gt;
&lt;p&gt;We are seeing improvement in the reachability and responsiveness of the Civo site and API and are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2024-11-14 09:15 UTC&lt;/p&gt;
&lt;p&gt;We are aware of issues accessing the Civo.com website, dashboard, and API, with timeouts occurring for some users. We are investigating the cause.&lt;/p&gt;
&lt;hr&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Civo website issues</title>
          <link>https://status.civo.com/issues/2024-10-21-website-issues/</link>
          <pubDate>Mon, 21 Oct 2024 14:40:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2024-10-21-website-issues/</guid>
          <category>2024-10-21 15:30:00</category>
          <description>&lt;p&gt;15:30 UTC&lt;/p&gt;
&lt;p&gt;We are seeing improvement in the reachability and responsiveness of the Civo site and API and are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;15:15 UTC&lt;/p&gt;
&lt;p&gt;We are continuing efforts to mitigate the intermittent issue with the timeouts on accessing the Civo website and API. We will next update here in 15 minutes at latest.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;14:54 UTC&lt;/p&gt;
&lt;p&gt;Currently running customer workloads in all Civo regions should be unaffected while we work to restore full functionality to the Civo website and API.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2024-10-21 14:40 UTC&lt;/p&gt;
&lt;p&gt;We are aware of issues accessing the Civo.com website, dashboard, and API, with timeouts occurring for some users. We are investigating the cause.&lt;/p&gt;
</description>
        </item>
      
        <item>
          <title>[Resolved] Service disruption PHX1</title>
          <link>https://status.civo.com/issues/2024-10-08-partial-disruption-phx1/</link>
          <pubDate>Tue, 08 Oct 2024 06:34:00 +0000</pubDate>
          <guid>https://status.civo.com/issues/2024-10-08-partial-disruption-phx1/</guid>
          <category>2024-10-10 04:30:00</category>
          <description>&lt;p&gt;2024-10-08 06:34:00 UTC&lt;/p&gt;
&lt;p&gt;We are facing an issue in the PHX1 region, that is affecting certain customer workloads. We have moved affected workloads and monitoring them.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;2024-10-08 08:05:00 UTC&lt;/p&gt;
&lt;p&gt;The majority of customer workloads have recovered and we are working to get the remaining ones back online.&lt;/p&gt;
</description>
        </item>
      
    </channel>
  </rss>

