<?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>FyfeWeb Status - Incident history</title>
    <link>https://status.fyfeweb.com</link>
    <description>FyfeWeb</description>
    <pubDate>Fri, 29 May 2026 00:00:00 +0000</pubDate>
    
<item>
  <title>[At Risk] Telehouse North &lt;&gt; Equinix LD8 Core Link Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Equinix LD8, London, Telehouse North, London, Core Network
    May 29, 00:00:00 GMT+0 - Identified - During the date and time below, one of our carriers will be upgrading equipment in Equinix LD8, London Docklands. Traffic will flow via alternative paths between THN and LD8, but the network should be considered &quot;at risk&quot; during this time. Traffic will be re-routed away from this link before the maintenance starts.

Start time: Friday 29 May 2026, 01:00 BST

End time: Friday 29 May 2026, 03:00 BST May 29, 00:00:01 GMT+0 - Identified - Maintenance is now in progress May 29, 02:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  During the date and time below, one of our carriers will be upgrading equipment in Equinix LD8, London Docklands. Traffic will flow via alternative paths between THN and LD8, but the network should be considered &quot;at risk&quot; during this time. Traffic will be re-routed away from this link before the maintenance starts.

Start time: Friday 29 May 2026, 01:00 BST

End time: Friday 29 May 2026, 03:00 BST.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00: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;May &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02: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;
]]>
  </content:encoded>
  <pubDate>Fri, 29 May 2026 00:00:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cmpn46g7803xspforjlc2butm</link>
  <guid>https://status.fyfeweb.com/maintenance/cmpn46g7803xspforjlc2butm</guid>
</item>

<item>
  <title>Upstream Carrier Issue (GTT)</title>
  <description>
    Type: Incident
    Duration: 3 hours and 24 minutes

    Affected Components: Telehouse North, London, , Reliance House, Newcastle, Interxion LON1, London, Equinix LD8, London, DC1, West Midlands, DC2, West Midlands, Core Network, 
Data Centre Facilities →
    Mar 23, 10:23:00 GMT+0 - Investigating - We are currently investigating this incident. Mar 23, 10:47:37 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the results. The issue was related to a fault with one of our upstream carriers, GTT, which has now been taken out of service temporarily until they resolve the issue.  Mar 23, 11:51:02 GMT+0 - Monitoring - BGP sessions with GTT remain shutdown whilst we await a resolution. Traffic is currently flowing via other carriers.  Mar 23, 13:47:02 GMT+0 - Resolved - This incident has been resolved. We have provided an RFO below:  
  
_We experienced a brief network service disruption today between 10:20 and 10:50 UTC, resulting in intermittent connectivity issues for some customers. Our initial assessment indicates the event aligned with a routing irregularity affecting connectivity between GTT their Corero-based protection platform in Benelux/Germany, although depending on the routing, other regions could have been impacted. At around 10:35, BGP sessions were shutdown towards GTT but prefixes took some time to withdraw, still causing connectivity issues for customers. At around 13:00, we were told the issue was resolved - so turned up our BGP sessions with them once again._   
  
FyfeWeb operates a diverse multi-homed network, with a diverse connectivity mix such as LINX, LONAP, NTT and Hurricane Electric. At all times, traffic flows via all carriers to ensure the best routing for our customers, and if there&#039;s maintenance / BGP session drop on a carrier, traffic automatically re-routes. In this case, the fault occurred within the providers network, resulting in any traffic traversing the GTT network for FyfeWeb would have experienced an issue.   
  
Due to the complex nature of the fault, our initial time spent troubleshooting was increased.   
  
We will be monitoring for any further issues. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 24 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:23:00&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;Mar &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:47:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the results. The issue was related to a fault with one of our upstream carriers, GTT, which has now been taken out of service temporarily until they resolve the issue. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:51:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  BGP sessions with GTT remain shutdown whilst we await a resolution. Traffic is currently flowing via other carriers. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:47:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. We have provided an RFO below:  
  
_We experienced a brief network service disruption today between 10:20 and 10:50 UTC, resulting in intermittent connectivity issues for some customers. Our initial assessment indicates the event aligned with a routing irregularity affecting connectivity between GTT their Corero-based protection platform in Benelux/Germany, although depending on the routing, other regions could have been impacted. At around 10:35, BGP sessions were shutdown towards GTT but prefixes took some time to withdraw, still causing connectivity issues for customers. At around 13:00, we were told the issue was resolved - so turned up our BGP sessions with them once again._   
  
FyfeWeb operates a diverse multi-homed network, with a diverse connectivity mix such as LINX, LONAP, NTT and Hurricane Electric. At all times, traffic flows via all carriers to ensure the best routing for our customers, and if there&#039;s maintenance / BGP session drop on a carrier, traffic automatically re-routes. In this case, the fault occurred within the providers network, resulting in any traffic traversing the GTT network for FyfeWeb would have experienced an issue.   
  
Due to the complex nature of the fault, our initial time spent troubleshooting was increased.   
  
We will be monitoring for any further issues..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 23 Mar 2026 10:23:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cmn31ez680004g9jgi05m3cl8</link>
  <guid>https://status.fyfeweb.com/incident/cmn31ez680004g9jgi05m3cl8</guid>
</item>

<item>
  <title>Network Issue - Newcastle</title>
  <description>
    Type: Incident
    Duration: 21 minutes

    Affected Components: Dedicated Servers, Reliance House, Newcastle, Network Services
    Feb 27, 00:07:24 GMT+0 - Investigating - We are currently experiencing a network issue affecting our Newcastle Data Centre, due to an upstream provider issue. Our team is actively investigating the situation, and further updates will follow as we work to resolve the issue with them.

**Details:**

**Location:** Newcastle Data Centre  
**Issue:** Network disruption  
**Cause:** Core router issue

Please be aware that during this time, services at the Newcastle Data Centre may have intermittent connectivity problems. We apologise for any inconvenience and appreciate your patience as we work to fix the issue.

Thank you for your understanding. Feb 27, 00:28:36 GMT+0 - Resolved - This incident has been resolved by reloading one of our core routers in Newcastle due to an unforeseen line card problem. This has now been resolved.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:07:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing a network issue affecting our Newcastle Data Centre, due to an upstream provider issue. Our team is actively investigating the situation, and further updates will follow as we work to resolve the issue with them.

**Details:**

**Location:** Newcastle Data Centre  
**Issue:** Network disruption  
**Cause:** Core router issue

Please be aware that during this time, services at the Newcastle Data Centre may have intermittent connectivity problems. We apologise for any inconvenience and appreciate your patience as we work to fix the issue.

Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:28:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved by reloading one of our core routers in Newcastle due to an unforeseen line card problem. This has now been resolved. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 27 Feb 2026 00:07:24 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cmm44uuym0cx8fnu1nr3w1ror</link>
  <guid>https://status.fyfeweb.com/incident/cmm44uuym0cx8fnu1nr3w1ror</guid>
</item>

<item>
  <title>NTT IP Transit Drop</title>
  <description>
    Type: Incident
    Duration: 8 hours and 35 minutes

    Affected Components: Network Services, Equinix LD8, London
    Jan 24, 06:32:45 GMT+0 - Monitoring - At around 4:30 AM NTT, one of our IP transit providers NTT dropped for around 10 minutes - this may have impacted some traffic for a few minutes whilst it was rerouted automatically to other carriers. Their NOC provided the following update at around 5 AM:

“Software bug/failure. Linecards failed on the device and restored before action was taken. We will investigate with the vendor regarding the event. No further impact is expected currently.”

We’ll monitor the situation over the next few hours.  Jan 24, 15:07:19 GMT+0 - Resolved - This incident has been resolved - we have not observed any further drops.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 8 hours and 35 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:32:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  At around 4:30 AM NTT, one of our IP transit providers NTT dropped for around 10 minutes - this may have impacted some traffic for a few minutes whilst it was rerouted automatically to other carriers. Their NOC provided the following update at around 5 AM:

“Software bug/failure. Linecards failed on the device and restored before action was taken. We will investigate with the vendor regarding the event. No further impact is expected currently.”

We’ll monitor the situation over the next few hours. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:07:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved - we have not observed any further drops. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 24 Jan 2026 06:32:45 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cmkrxngi70t0t109y7ntequd1</link>
  <guid>https://status.fyfeweb.com/incident/cmkrxngi70t0t109y7ntequd1</guid>
</item>

<item>
  <title>Emergency Maintenance - Telehouse North</title>
  <description>
    Type: Maintenance
    Duration: 23 hours and 58 minutes

    Affected Components: Network Services, Telehouse North, London, Dedicated Servers, DC1, West Midlands, DC2, West Midlands, Core Network
    Jan 22, 04:50:00 GMT+0 - Identified - In order to bring online some additional 100G capacity in Telehouse North, we&#039;ve got to complete an FPC restart. This may cause a brief drop in services connected to this router.  Jan 21, 04:51:37 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 23 hours and 58 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:50:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  In order to bring online some additional 100G capacity in Telehouse North, we&#039;ve got to complete an FPC restart. This may cause a brief drop in services connected to this router. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:51:37&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>Thu, 22 Jan 2026 04:50:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cmknjljuj06lixjng1e9jdvwy</link>
  <guid>https://status.fyfeweb.com/maintenance/cmknjljuj06lixjng1e9jdvwy</guid>
</item>

<item>
  <title>Cloudflare Connectivity Issues</title>
  <description>
    Type: Incident
    Duration: 6 hours and 2 minutes

    Affected Components: Internal Infrastructure
    Nov 18, 14:58:54 GMT+0 - Monitoring - Cloudflare have stated that the issue has now been resolved. Our Client Portal was impacted by the issue, as well as our status page.

If you cannot access our portal still, and require any support, please email [support@fyfeweb.com](mailto:support@fyfeweb.com).

Apologies for any inconvenience caused. Nov 18, 11:55:35 GMT+0 - Identified - At the moment, websites that utilise Cloudflare may be unavailable due to issues with the Cloudflare network.

More information regarding the Cloudflare issue can be found on their status page here: &lt;https://www.cloudflarestatus.com/incidents/8gmgl950y3h7&gt; Nov 18, 17:58:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:58:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Cloudflare have stated that the issue has now been resolved. Our Client Portal was impacted by the issue, as well as our status page.

If you cannot access our portal still, and require any support, please email [support@fyfeweb.com](mailto:support@fyfeweb.com).

Apologies for any inconvenience caused..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:55:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  At the moment, websites that utilise Cloudflare may be unavailable due to issues with the Cloudflare network.

More information regarding the Cloudflare issue can be found on their status page here: &lt;https://www.cloudflarestatus.com/incidents/8gmgl950y3h7&gt;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:58:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 18 Nov 2025 11:55:35 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cmi4iojsm02d44o90a7idbvym</link>
  <guid>https://status.fyfeweb.com/incident/cmi4iojsm02d44o90a7idbvym</guid>
</item>

<item>
  <title>NTT IP Transit Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 3 hours

    Affected Components: Core Network
    Oct 29, 02:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 29, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Oct 29, 02:00:00 GMT+0 - Identified - NTT, one of our tier 1 carriers, will be performing software upgrades to a core router during this maintenance window in Equinix LD8, London Docklands. Traffic will automatically reroute via alternative paths during this time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02: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; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05: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; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  NTT, one of our tier 1 carriers, will be performing software upgrades to a core router during this maintenance window in Equinix LD8, London Docklands. Traffic will automatically reroute via alternative paths during this time..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 29 Oct 2025 02:00:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cmgqmzsz6012e52kixh00zs74</link>
  <guid>https://status.fyfeweb.com/maintenance/cmgqmzsz6012e52kixh00zs74</guid>
</item>

<item>
  <title>LONAP Peering Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 3 hours

    Affected Components: Core Network
    Oct 27, 23:30:00 GMT+0 - Identified - During the specified time below, LONAP will be moving all member 1GE/10GE and some 100GE ports to new switch hardware in Equinix LD8/Harbour Exchange. 

From: Mon 2025-10-27 23:30 UTC (23:30 UK)

To: Tue 2025-10-28 02:30 UTC (02:30 UK)

To minimise impact during the maintenance, LONAP will apply an ACL to gracefully close BGP sessions for affected ports (BGP Session Culling)   
  
The ACL will remain in place until we have verified the maintenance is successful. Traffic on the FyfeWeb network will reroute via alternative paths during this time. Oct 27, 23:30:01 GMT+0 - Identified - Maintenance is now in progress Oct 28, 02:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  During the specified time below, LONAP will be moving all member 1GE/10GE and some 100GE ports to new switch hardware in Equinix LD8/Harbour Exchange. 

From: Mon 2025-10-27 23:30 UTC (23:30 UK)

To: Tue 2025-10-28 02:30 UTC (02:30 UK)

To minimise impact during the maintenance, LONAP will apply an ACL to gracefully close BGP sessions for affected ports (BGP Session Culling)   
  
The ACL will remain in place until we have verified the maintenance is successful. Traffic on the FyfeWeb network will reroute via alternative paths during this time..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23: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; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02: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>Mon, 27 Oct 2025 23:30:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cmh0kux4k006dd72jbss1q651</link>
  <guid>https://status.fyfeweb.com/maintenance/cmh0kux4k006dd72jbss1q651</guid>
</item>

<item>
  <title>Network issue Wolverhampton</title>
  <description>
    Type: Incident
    Duration: 4 hours and 1 minute

    Affected Components: Hosted Virtual Machines, Web Hosting, VPS Hosting, DC1, West Midlands, DC2, West Midlands
    Oct 23, 17:51:25 GMT+0 - Identified - We have an ETA of around 60-90 minutes for full recovery, some services such as cPanel etc are recovered. Oct 23, 19:18:09 GMT+0 - Resolved - We have now seen full service recovery after swapping the affected device, this required a full reconfiguration due to various unexpected issues encountered along the way, which delayed the recovery process.

I would like to take this opportunity to apologise to you for any inconvenience caused this evening by the outage, as well as thanking you for your patience and support. These issues fall well below the standard of high quality service we want to provide, and for that we are truly sorry. Rest assured, throughout the incident we were working as quickly as possible to restore service.

We are continually investing in our network to increase reliability throughout, and will continue doing so. As always, if you have any issues please get in touch. Oct 23, 15:16:43 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 23, 15:25:15 GMT+0 - Identified - We have identified an issue with core1-dc2.wlv - one of our core routers. We are still working on a fix. Oct 23, 15:47:12 GMT+0 - Monitoring - The device has been rebooted and is now back online, apologies for any inconvenience caused. We are still monitoring for further issues, a replacement device has been sourced and will be swapped out if the issue occurs again. 

We&#039;re currently checking the logs on the device but at first glance it appears as if the device crashed.  Oct 23, 16:26:01 GMT+0 - Monitoring - We are still monitoring the device for any further issues. Oct 23, 17:10:42 GMT+0 - Investigating - The issue has re-occurred. We are going to perform a device swap, the new device is currently being prepared. Oct 23, 17:34:04 GMT+0 - Identified - We are continuing to work on a fix for this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:51:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have an ETA of around 60-90 minutes for full recovery, some services such as cPanel etc are recovered..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:18:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We have now seen full service recovery after swapping the affected device, this required a full reconfiguration due to various unexpected issues encountered along the way, which delayed the recovery process.

I would like to take this opportunity to apologise to you for any inconvenience caused this evening by the outage, as well as thanking you for your patience and support. These issues fall well below the standard of high quality service we want to provide, and for that we are truly sorry. Rest assured, throughout the incident we were working as quickly as possible to restore service.

We are continually investing in our network to increase reliability throughout, and will continue doing so. As always, if you have any issues please get in touch..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:16:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:25:15&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified an issue with core1-dc2.wlv - one of our core routers. We are still working on a fix..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:47:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The device has been rebooted and is now back online, apologies for any inconvenience caused. We are still monitoring for further issues, a replacement device has been sourced and will be swapped out if the issue occurs again. 

We&#039;re currently checking the logs on the device but at first glance it appears as if the device crashed. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:26:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are still monitoring the device for any further issues..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:10:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  The issue has re-occurred. We are going to perform a device swap, the new device is currently being prepared..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:34:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 23 Oct 2025 15:16:43 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cmh3kf2n9003flvugk36aotkd</link>
  <guid>https://status.fyfeweb.com/incident/cmh3kf2n9003flvugk36aotkd</guid>
</item>

<item>
  <title>Reliance House Power Works</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: Reliance House, Newcastle
    Oct 21, 22:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 22, 00:00:00 GMT+0 - Completed - Maintenance has completed successfully Oct 21, 22:00:00 GMT+0 - Identified - On the 21st October, we will be carrying out essential work to replace an isolator powering some plant equipment at our Reliance House data centre facility. Power should be considered at risk for the duration of this maintenance window. If you have any questions, please don&#039;t hesitate to contact us.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22: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; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00: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; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  On the 21st October, we will be carrying out essential work to replace an isolator powering some plant equipment at our Reliance House data centre facility. Power should be considered at risk for the duration of this maintenance window. If you have any questions, please don&#039;t hesitate to contact us. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 21 Oct 2025 22:00:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cmgtsz4sw00czx4py6kqa47q9</link>
  <guid>https://status.fyfeweb.com/maintenance/cmgtsz4sw00czx4py6kqa47q9</guid>
</item>

<item>
  <title>Core Router Issue</title>
  <description>
    Type: Incident
    Duration: 1 day, 17 hours and 48 minutes

    Affected Components: DC1, West Midlands, DC2, West Midlands
    Oct 4, 11:33:29 GMT+0 - Identified - A network engineer has been dispatched to the data centre and will perform remedial works between 10 PM and 11 PM this evening.  Oct 4, 23:13:59 GMT+0 - Identified - The faulty device is now being replaced. Services will drop.  Oct 4, 23:24:02 GMT+0 - Identified - The new device has been installed and is booting.  Oct 4, 21:51:29 GMT+0 - Identified - The work has been delayed due to issues with travel - the engineer is 30 minutes away from the data centre and will perform the device swap shortly. The device is currently still flapping up and down.  Oct 4, 22:30:39 GMT+0 - Identified - We are now preparing the new device, please stand by for further updates.  Oct 4, 23:30:13 GMT+0 - Monitoring - Services are now back online and we are monitoring for any further issues.  Oct 5, 21:59:36 GMT+0 - Resolved - This incident has been resolved, we have observed stability since performing the swap.  Oct 4, 08:27:24 GMT+0 - Identified - We have located a replacement device in stores and will organise a device replacement this evening. This will cause a drop to all services connected to this router, a time will be confirmed within the next 6-7 hours.  Oct 4, 04:11:17 GMT+0 - Identified - We have identified a potential hardware issue with one of our core routers in Wolverhampton, core0-dc2.wlv where the device is randomly rebooting due to an apparent hardware problem. We&#039;re currently organising the installation of a new replacement device and this will be swapped out over the weekend due to the reliability issues of the current device. 

We apologise for any inconvenience this is causing you.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 17 hours and 48 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:33:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  A network engineer has been dispatched to the data centre and will perform remedial works between 10 PM and 11 PM this evening. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:13:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The faulty device is now being replaced. Services will drop. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:24:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The new device has been installed and is booting. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:51:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The work has been delayed due to issues with travel - the engineer is 30 minutes away from the data centre and will perform the device swap shortly. The device is currently still flapping up and down. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:30:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are now preparing the new device, please stand by for further updates. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:30:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Services are now back online and we are monitoring for any further issues. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:59:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved, we have observed stability since performing the swap. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:27:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have located a replacement device in stores and will organise a device replacement this evening. This will cause a drop to all services connected to this router, a time will be confirmed within the next 6-7 hours. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:11:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified a potential hardware issue with one of our core routers in Wolverhampton, core0-dc2.wlv where the device is randomly rebooting due to an apparent hardware problem. We&#039;re currently organising the installation of a new replacement device and this will be swapped out over the weekend due to the reliability issues of the current device. 

We apologise for any inconvenience this is causing you. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 4 Oct 2025 04:11:17 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cmgbra4sv05athrwxr26x7nmr</link>
  <guid>https://status.fyfeweb.com/incident/cmgbra4sv05athrwxr26x7nmr</guid>
</item>

<item>
  <title>CP01: cPanel Hosting LiteSpeed Updates</title>
  <description>
    Type: Maintenance
    Duration: 1 minute

    Affected Components: Web Hosting
    Sep 17, 22:00:00 GMT+0 - Identified - During the specified time below, we will be performing updates to the LiteSpeed Web Server on our CP01 cPanel web hosting server. 

We don&#039;t expect any major impact, but the LiteSpeed service will be restarted, which may cause a brief blip in the reachability of websites.  Sep 17, 22:01:14 GMT+0 - Completed - Maintenance has completed successfully, the update has been installed.  Sep 17, 22:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 minute</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  During the specified time below, we will be performing updates to the LiteSpeed Web Server on our CP01 cPanel web hosting server. 

We don&#039;t expect any major impact, but the LiteSpeed service will be restarted, which may cause a brief blip in the reachability of websites. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:01:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully, the update has been installed. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22: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;
]]>
  </content:encoded>
  <pubDate>Wed, 17 Sep 2025 22:00:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cmfo86au8006shc8gv13mvsgn</link>
  <guid>https://status.fyfeweb.com/maintenance/cmfo86au8006shc8gv13mvsgn</guid>
</item>

<item>
  <title>DC1/DC2 Core Network Upgrades</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: DC1, West Midlands, DC2, West Midlands
    Sep 12, 23:00:00 GMT+0 - Identified - During this maintenance window, we will be performing upgrades to both core routers in our West Midlands data centres. 

Customers directly attached to these devices, which is limited to some Virtual Private Servers &amp; Dedicated servers, as well as web hosting services, will experience a brief drop of network connectivity for around 15 minutes. This work is being carried out by engineers when traffic levels are at their lowest. 

If you have any questions, please don&#039;t hesitate to get in touch. Sep 13, 00:00:00 GMT+0 - Completed - Maintenance has completed successfully Sep 12, 23:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </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;Sep &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  During this maintenance window, we will be performing upgrades to both core routers in our West Midlands data centres. 

Customers directly attached to these devices, which is limited to some Virtual Private Servers &amp; Dedicated servers, as well as web hosting services, will experience a brief drop of network connectivity for around 15 minutes. This work is being carried out by engineers when traffic levels are at their lowest. 

If you have any questions, please don&#039;t hesitate to get in touch..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 13&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00: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;Sep &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23: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;
]]>
  </content:encoded>
  <pubDate>Fri, 12 Sep 2025 23:00:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cmfb1tjrf000s4jilmuxqnmjv</link>
  <guid>https://status.fyfeweb.com/maintenance/cmfb1tjrf000s4jilmuxqnmjv</guid>
</item>

<item>
  <title>Network issue</title>
  <description>
    Type: Incident
    Duration: 1 hour and 18 minutes

    Affected Components: Core Network
    Aug 30, 19:16:17 GMT+0 - Identified - We are continuing to work on a fix for this incident. Aug 30, 19:05:58 GMT+0 - Investigating - We have identified a potential network issue and are looking into it. Aug 30, 20:24:10 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 18 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:16:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:05:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We have identified a potential network issue and are looking into it..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:24:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 30 Aug 2025 19:05:58 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cmeymtvr00014yqlck0ro0cfr</link>
  <guid>https://status.fyfeweb.com/incident/cmeymtvr00014yqlck0ro0cfr</guid>
</item>

<item>
  <title>Power Issues at Reliance House, Newcastle.</title>
  <description>
    Type: Incident
    Duration: 7 hours and 44 minutes

    Affected Components: Reliance House, Newcastle, Dedicated Servers
    Aug 22, 01:45:23 GMT+0 - Monitoring - We had an electrical issue impacting some cooling circuits within the data centre facility. Engineers have performing remedial works and are monitoring closely.  Aug 22, 01:41:13 GMT+0 - Monitoring - We have implemented a fix and are currently monitoring our systems, with engineers on-site.  Aug 22, 03:08:30 GMT+0 - Monitoring - We are still monitoring for further issues, but we have observed good stability so far. Another update will be provided within the next 6 hours, and then the incident will be marked as resolved.  Aug 22, 08:58:48 GMT+0 - Resolved - This incident has been resolved. Aug 22, 01:14:47 GMT+0 - Investigating - We are aware of, and are currently investigating, issues with power at our Reliance House facility in Newcastle. Our team are on-site and are actively working to restore services as quickly as possible.

We apologise for any inconvenience this may cause you and a full Reason for Outage Report shall be made available upon request at a later date.

Please note only **Dedicated Servers** and **Colocation** within **Reliance House only** are affected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:45:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We had an electrical issue impacting some cooling circuits within the data centre facility. Engineers have performing remedial works and are monitoring closely. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:41:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have implemented a fix and are currently monitoring our systems, with engineers on-site. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:08:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We are still monitoring for further issues, but we have observed good stability so far. Another update will be provided within the next 6 hours, and then the incident will be marked as resolved. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:58:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:14:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of, and are currently investigating, issues with power at our Reliance House facility in Newcastle. Our team are on-site and are actively working to restore services as quickly as possible.

We apologise for any inconvenience this may cause you and a full Reason for Outage Report shall be made available upon request at a later date.

Please note only **Dedicated Servers** and **Colocation** within **Reliance House only** are affected..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 22 Aug 2025 01:14:47 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cmem51izz0001hk97r7h5duux</link>
  <guid>https://status.fyfeweb.com/incident/cmem51izz0001hk97r7h5duux</guid>
</item>

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

    Affected Components: Reliance House, Newcastle
    Mar 7, 06:00:00 GMT+0 - Completed - Maintenance has completed successfully Mar 7, 05:00:01 GMT+0 - Identified - Maintenance is now in progress Mar 7, 05:00:00 GMT+0 - Identified - During this maintenance window, we will be introducing an additional core link on a router within our Newcastle (Reliance House) data centre facility.

We don&#039;t anticipate any outage, but the network should be considered &quot;at-risk&quot; whilst we&#039;re making several configuration changes to the device the link terminates on.

The maintenance is required to ensure the smooth operation of our network, and to provide further capacity and reliability enhancements.

If you have any questions, please don&#039;t hesitate to get in touch. 
  </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;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06: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;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05: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;Mar &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  During this maintenance window, we will be introducing an additional core link on a router within our Newcastle (Reliance House) data centre facility.

We don&#039;t anticipate any outage, but the network should be considered &quot;at-risk&quot; whilst we&#039;re making several configuration changes to the device the link terminates on.

The maintenance is required to ensure the smooth operation of our network, and to provide further capacity and reliability enhancements.

If you have any questions, please don&#039;t hesitate to get in touch..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 7 Mar 2025 05:00:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cm7wivrph001e11w61bkcn22x</link>
  <guid>https://status.fyfeweb.com/maintenance/cm7wivrph001e11w61bkcn22x</guid>
</item>

<item>
  <title>Upstream Transit Issue (GTT)</title>
  <description>
    Type: Incident
    Duration: 59 minutes

    Affected Components: Network Services
    Feb 28, 20:23:07 GMT+0 - Resolved - This incident has been resolved. Feb 28, 19:23:39 GMT+0 - Identified - We have identified an issue which seems to have impacted some services across our network for around 30-60 seconds, the issue is further upstream to our network and we have contacted the provider. We will update this status message again shortly with more information.  Feb 28, 19:41:25 GMT+0 - Monitoring - We suspect there has been a device outage on GTTs end, as traffic is no longer flowing via Telehouse North. The 2-3 minute outage experienced can be put down to any traffic flowing via THN to GTT being cut off in a non-graceful state, as well as BGP hold-timers expiring and route reconvergence. We&#039;ll be monitoring for the next 24 hours, and will post any further updates here.  
  </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;Feb &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:23:07&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:23:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified an issue which seems to have impacted some services across our network for around 30-60 seconds, the issue is further upstream to our network and we have contacted the provider. We will update this status message again shortly with more information. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:41:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We suspect there has been a device outage on GTTs end, as traffic is no longer flowing via Telehouse North. The 2-3 minute outage experienced can be put down to any traffic flowing via THN to GTT being cut off in a non-graceful state, as well as BGP hold-timers expiring and route reconvergence. We&#039;ll be monitoring for the next 24 hours, and will post any further updates here. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 28 Feb 2025 19:23:39 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cm7p5vqwa003hgjvjy7phbw5o</link>
  <guid>https://status.fyfeweb.com/incident/cm7p5vqwa003hgjvjy7phbw5o</guid>
</item>

<item>
  <title>Network Issue - Newcastle DC</title>
  <description>
    Type: Incident
    Duration: 3 hours and 15 minutes

    Affected Components: Reliance House, Newcastle
    Feb 20, 14:02:54 GMT+0 - Investigating - We are aware of an issue impacting connectivity at our Newcastle data centre. We believe this may potentially be a failure of a core device. We have engineers on-site investigating this as a matter of urgency. We will provide another update shortly. Feb 20, 14:24:08 GMT+0 - Identified - We have located the issue, there was a failed SFP module on a core device. This has since been replaced, and has restored service.  Feb 20, 17:17:54 GMT+0 - Resolved - This incident has been resolved, and the root cause identified. Please get in touch should you have any questions, and apologies for any inconvenience this may have caused.  
  </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>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:02:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of an issue impacting connectivity at our Newcastle data centre. We believe this may potentially be a failure of a core device. We have engineers on-site investigating this as a matter of urgency. We will provide another update shortly..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:24:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have located the issue, there was a failed SFP module on a core device. This has since been replaced, and has restored service. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:17:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved, and the root cause identified. Please get in touch should you have any questions, and apologies for any inconvenience this may have caused. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 20 Feb 2025 14:02:54 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cm7dewfya000sstwtf74frrqs</link>
  <guid>https://status.fyfeweb.com/incident/cm7dewfya000sstwtf74frrqs</guid>
</item>

<item>
  <title>Network Issue Newcastle</title>
  <description>
    Type: Incident
    Duration: 52 minutes

    Affected Components: Reliance House, Newcastle
    Feb 3, 09:53:27 GMT+0 - Identified - We identified a core link to London failed, this has since failed over to another link.  Feb 3, 10:10:09 GMT+0 - Monitoring - The core link is now back online, but is flapping up and down, we&#039;re currently in the process of disabling this link until the issue is resolved.  Feb 3, 10:45:55 GMT+0 - Resolved - We&#039;ve implemented some fixes to the configuration of our routing between Newcastle and London, this has been tested and confirmed to be working now. The core link that was flapping has been taken out of service until we&#039;re happy it&#039;s not going down repeatedly again. We apologise for any issues this may have caused you this morning.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 52 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:53:27&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We identified a core link to London failed, this has since failed over to another link. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:10:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The core link is now back online, but is flapping up and down, we&#039;re currently in the process of disabling this link until the issue is resolved. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:45:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We&#039;ve implemented some fixes to the configuration of our routing between Newcastle and London, this has been tested and confirmed to be working now. The core link that was flapping has been taken out of service until we&#039;re happy it&#039;s not going down repeatedly again. We apologise for any issues this may have caused you this morning. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 3 Feb 2025 09:53:27 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cm6ovi5ss0006ojpzx4935r1n</link>
  <guid>https://status.fyfeweb.com/incident/cm6ovi5ss0006ojpzx4935r1n</guid>
</item>

<item>
  <title>Emergency Maintenance - Core Links, Newcastle</title>
  <description>
    Type: Incident
    Duration: 25 minutes

    Affected Components: Reliance House, Newcastle
    Jan 18, 17:59:58 GMT+0 - Resolved - This incident has been resolved. Jan 18, 17:35:19 GMT+0 - Identified - We&#039;re having to swap some core links around in our data centre in Newcastle. This may cause a brief outage of around 5 minutes whilst routes reconverge within the network. We apologise for any inconvenience this may cause.  Jan 18, 17:49:59 GMT+0 - Monitoring - We&#039;ve swapped the relevant core links around, and services should be recovering now.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 25 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;17:59:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&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;17:35:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re having to swap some core links around in our data centre in Newcastle. This may cause a brief outage of around 5 minutes whilst routes reconverge within the network. We apologise for any inconvenience this may cause. .&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;17:49:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We&#039;ve swapped the relevant core links around, and services should be recovering now. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 18 Jan 2025 17:35:19 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cm62gyhwx0006q1pa6by3l0rb</link>
  <guid>https://status.fyfeweb.com/incident/cm62gyhwx0006q1pa6by3l0rb</guid>
</item>

<item>
  <title>Cloud03 VPS Node Issues</title>
  <description>
    Type: Incident
    Duration: 30 minutes

    
    Jan 4, 19:56:51 GMT+0 - Investigating - We are currently investigating an incident regarding our Cloud03 VPS node becoming unresponsive. This may cause issues with your VPS, if it&#039;s located on this node. We hope to have an update ASAP.  Jan 4, 20:06:20 GMT+0 - Identified - We&#039;ve performed a hard reboot of the server, and are currently monitoring the startup process for any errors.  Jan 4, 20:15:58 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jan 4, 20:27:16 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:56:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident regarding our Cloud03 VPS node becoming unresponsive. This may cause issues with your VPS, if it&#039;s located on this node. We hope to have an update ASAP. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:06:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;ve performed a hard reboot of the server, and are currently monitoring the startup process for any errors. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:15:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:27:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 4 Jan 2025 19:56:51 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cm5ilul88006414fzv1yydvtw</link>
  <guid>https://status.fyfeweb.com/incident/cm5ilul88006414fzv1yydvtw</guid>
</item>

<item>
  <title>Network Maintenance - Core Switch (DC2 WLV)</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 52 minutes

    Affected Components: Internal Infrastructure, Hosted Virtual Machines, Dedicated Servers, DC2, West Midlands
    Dec 6, 00:33:51 GMT+0 - Identified - We&#039;ve swapped all ports to the new device, we are currently checking for any issues.  Dec 5, 23:00:00 GMT+0 - Identified - During this maintenance window, we will be performing upgrades to one of our core switches in our DC2 data centre, West Midlands.

Customers directly attached to this device, which is limited to some Virtual Private Servers &amp; Dedicated servers, will experience a brief drop of network connectivity for around 10 minutes.

If you have any questions, please don&#039;t hesitate to get in touch. Nov 24, 13:38:14 GMT+0 - Identified - Please note that the window for the maintenance is from 11 PM to 12 AM - not 11 AM.  Dec 5, 23:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 6, 00:51:33 GMT+0 - Completed - This has been completed, please get in touch if you have any issues.  Dec 5, 23:06:45 GMT+0 - Identified - We are currently preparing to move customer access ports over to the new switch. There will be a drop in connectivity when this is done. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 52 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:33:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;ve swapped all ports to the new device, we are currently checking for any issues. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  During this maintenance window, we will be performing upgrades to one of our core switches in our DC2 data centre, West Midlands.

Customers directly attached to this device, which is limited to some Virtual Private Servers &amp; Dedicated servers, will experience a brief drop of network connectivity for around 10 minutes.

If you have any questions, please don&#039;t hesitate to get in touch..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:38:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Please note that the window for the maintenance is from 11 PM to 12 AM - not 11 AM. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23: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; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:51:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  This has been completed, please get in touch if you have any issues. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:06:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are currently preparing to move customer access ports over to the new switch. There will be a drop in connectivity when this is done..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 5 Dec 2024 23:00:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cm3vmxb6p00a0xc8hyfohvvgy</link>
  <guid>https://status.fyfeweb.com/maintenance/cm3vmxb6p00a0xc8hyfohvvgy</guid>
</item>

<item>
  <title>Emergency Maintenance - Hypervisor 3, Midlands</title>
  <description>
    Type: Maintenance
    Duration: 15 minutes

    Affected Components: Hosted Virtual Machines
    Nov 4, 14:57:20 GMT+0 - Identified - We are currently performaing emergency maintenance on one of our hypervisor nodes, this may cause issues with some VDS services. Nov 4, 15:26:08 GMT+0 - Completed - This has been conmpleted and all servers are now back online. Nov 4, 15:10:42 GMT+0 - Identified - The faulty part has now been replaced, and the server is currently powering back up. 
  </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;Nov &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:57:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are currently performaing emergency maintenance on one of our hypervisor nodes, this may cause issues with some VDS services..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:26:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  This has been conmpleted and all servers are now back online..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:10:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The faulty part has now been replaced, and the server is currently powering back up..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 4 Nov 2024 14:57:20 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cm335bwrl001hezbk6eu38tpy</link>
  <guid>https://status.fyfeweb.com/maintenance/cm335bwrl001hezbk6eu38tpy</guid>
</item>

<item>
  <title>Essential Maintenance: Core Router Upgrade in DC1, West Midlands</title>
  <description>
    Type: Maintenance
    Duration: 9 hours and 46 minutes

    Affected Components: Hosted Virtual Machines, Dedicated Servers, DC1, West Midlands
    Oct 8, 15:32:23 GMT+0 - Identified - Update 08/10/2024:

We have implemented an additional dark fibre connection between two of our core routers, therefore this maintenance event should be non-service impacting. 

However, the network in this facility should still be considered &quot;at risk&quot; during this period.  Oct 22, 22:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 23, 07:46:05 GMT+0 - Completed - Maintenance was completed last night with no issues, checks were completed to ensure everything was working as it should. Please let us know if you have any problems today.  Oct 22, 22:00:00 GMT+0 - Identified - During this maintenance window, we will be performing both software and hardware upgrades to router core1-dc1, located in DC1, West Midlands.

This maintenance requires a full power down of the device in order to install new control boards and redundant routing engines.

Customers in this facility, which includes cPanel Web Hosting and some dedicated servers and colocation, will not experience any loss of service due to the resilient nature of our core network - but services should be considered &quot;at-risk&quot; during this period. 

If you have any questions, please don&#039;t hesitate to get in touch. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 9 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 8&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:32:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Update 08/10/2024:

We have implemented an additional dark fibre connection between two of our core routers, therefore this maintenance event should be non-service impacting. 

However, the network in this facility should still be considered &quot;at risk&quot; during this period. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22: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; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:46:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance was completed last night with no issues, checks were completed to ensure everything was working as it should. Please let us know if you have any problems today. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  During this maintenance window, we will be performing both software and hardware upgrades to router core1-dc1, located in DC1, West Midlands.

This maintenance requires a full power down of the device in order to install new control boards and redundant routing engines.

Customers in this facility, which includes cPanel Web Hosting and some dedicated servers and colocation, will not experience any loss of service due to the resilient nature of our core network - but services should be considered &quot;at-risk&quot; during this period. 

If you have any questions, please don&#039;t hesitate to get in touch..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 22 Oct 2024 22:00:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cm1hpda4n00014aipw2ija2oa</link>
  <guid>https://status.fyfeweb.com/maintenance/cm1hpda4n00014aipw2ija2oa</guid>
</item>

<item>
  <title>Network Maintenance: Reliance House </title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Hosted Virtual Machines, Reliance House, Newcastle, Dedicated Servers
    Aug 30, 05:00:00 GMT+0 - Completed - Maintenance has completed successfully Aug 30, 04:00:00 GMT+0 - Identified - In response to a minor network issue experienced late last week, we are undertaking some essential maintenance on one of our core devices in Reliance House, Newcastle.

At 5AM (UK time) on Friday 30th August 2024, customers situated in Reliance House (Newcastle DC1) will notice a very brief period of network downtime of approximately 10 minutes (within the scheduled time) whilst we re-configure a core network device. The actual duration of downtime is expected to be much less.

This maintenance is essential in order to proactively prevent further issues of this nature from re-occurring. Aug 30, 04:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </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;Aug &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05: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;Aug &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  In response to a minor network issue experienced late last week, we are undertaking some essential maintenance on one of our core devices in Reliance House, Newcastle.

At 5AM (UK time) on Friday 30th August 2024, customers situated in Reliance House (Newcastle DC1) will notice a very brief period of network downtime of approximately 10 minutes (within the scheduled time) whilst we re-configure a core network device. The actual duration of downtime is expected to be much less.

This maintenance is essential in order to proactively prevent further issues of this nature from re-occurring..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04: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;
]]>
  </content:encoded>
  <pubDate>Fri, 30 Aug 2024 04:00:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cm0e6pxzg007aycpu6bse53if</link>
  <guid>https://status.fyfeweb.com/maintenance/cm0e6pxzg007aycpu6bse53if</guid>
</item>

<item>
  <title>Connectivity issues at Reliance House, Newcastle.</title>
  <description>
    Type: Incident
    Duration: 9 days, 23 hours and 36 minutes

    Affected Components: Internal Infrastructure, Network Services, Reliance House, Newcastle, Dedicated Servers
    Aug 25, 19:51:49 GMT+0 - Investigating - We are aware of a incident affecting connectivity in our Newcastle Reliance House Facility. Aug 25, 20:08:58 GMT+0 - Monitoring - It appears that an unexpected reboot of a core device is the cause of approximately 5 mins of downtime.

We’re monitoring this closely and will plan maintenance imminently to ensure that further issues are prevented. Aug 25, 22:55:04 GMT+0 - Resolved - We haven&#039;t seen any further issues since one of our core routers rebooted unexpectedly. 

We believe the issue was related to a bug within the software running on the device, triggering an unexpected reboot.   
  
We will be performing further emergency maintenance in the coming days in order to ensure stability across services connected to this device.  Sep 4, 17:02:30 GMT+0 - Identified - We have seen a repeat of this incident - we are going to replace this device now. Only directly connected customers to this device will be impacted at the moment. Sep 4, 18:00:32 GMT+0 - Identified - We are continuing to work on a fix for this incident - we&#039;re on-site and building a replacement device, there will be another brief 5 min drop when we replace the device.  Sep 4, 18:24:54 GMT+0 - Monitoring - We have identified a faulty optic within the FPC of the device, instead of swapping the whole device we&#039;re going to swap the optic and monitor from there.  Sep 4, 19:27:32 GMT+0 - Resolved - We have completed the replacement and normal service has since resumed. 

Apologies for any inconvenience caused this evening.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 days, 23 hours and 36 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:51:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of a incident affecting connectivity in our Newcastle Reliance House Facility..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:08:58&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  It appears that an unexpected reboot of a core device is the cause of approximately 5 mins of downtime.

We’re monitoring this closely and will plan maintenance imminently to ensure that further issues are prevented..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:55:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We haven&#039;t seen any further issues since one of our core routers rebooted unexpectedly. 

We believe the issue was related to a bug within the software running on the device, triggering an unexpected reboot.   
  
We will be performing further emergency maintenance in the coming days in order to ensure stability across services connected to this device. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:02:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have seen a repeat of this incident - we are going to replace this device now. Only directly connected customers to this device will be impacted at the moment..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:00:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are continuing to work on a fix for this incident - we&#039;re on-site and building a replacement device, there will be another brief 5 min drop when we replace the device. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:24:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have identified a faulty optic within the FPC of the device, instead of swapping the whole device we&#039;re going to swap the optic and monitor from there. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:27:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We have completed the replacement and normal service has since resumed. 

Apologies for any inconvenience caused this evening. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 25 Aug 2024 19:51:49 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cm09zjod6005v586ie5g14ii9</link>
  <guid>https://status.fyfeweb.com/incident/cm09zjod6005v586ie5g14ii9</guid>
</item>

<item>
  <title>CP01 - cPanel Server - LiteSpeed Web Server Outage</title>
  <description>
    Type: Incident
    Duration: 7 minutes

    
    Aug 16, 21:50:54 GMT+0 - Investigating - We have detected an issue with one of our cPanel servers, CP01\. We&#039;re currently looking into the root cause of the issue. During this time, some customer websites may be offline. Aug 16, 21:53:33 GMT+0 - Identified - We have switched the web server to Apache whilst we figure out the root cause of the issue. Websites are back online, but may run slower than usual. Aug 16, 21:57:51 GMT+0 - Resolved - This incident has been resolved. We found there was a LiteSpeed update that failed to apply automatically, causing the web server process to become &quot;stuck&quot; - it has now been successfully updated, so we&#039;re closing this issue off.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:50:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We have detected an issue with one of our cPanel servers, CP01\. We&#039;re currently looking into the root cause of the issue. During this time, some customer websites may be offline..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:53:33&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have switched the web server to Apache whilst we figure out the root cause of the issue. Websites are back online, but may run slower than usual..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:57:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved. We found there was a LiteSpeed update that failed to apply automatically, causing the web server process to become &quot;stuck&quot; - it has now been successfully updated, so we&#039;re closing this issue off. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 16 Aug 2024 21:50:54 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/clzx8u5nv001cdiqim6o3td7e</link>
  <guid>https://status.fyfeweb.com/incident/clzx8u5nv001cdiqim6o3td7e</guid>
</item>

<item>
  <title>Plesk Hosting Migrations</title>
  <description>
    Type: Maintenance
    Duration: 1 day

    
    Jul 30, 17:00:01 GMT+0 - Identified - Maintenance is now in progress Jul 30, 17:00:00 GMT+0 - Identified - Over the next few days, we will be migrating customers from some of our Plesk servers to our new whitelabel Plesk reseller hosting platform.

Customers on our existing CentOS Plesk servers will be moved to various new servers running CloudLinux, which delivers the very best security, reliability and performance. The new servers also feature newer hardware, such as newer CPUs, better SSDs and the latest generation memory.

The new servers will be located on our [**websiteserver.uk**](http://websiteserver.uk) domain as opposed to our own, which is great for resellers of the service.

We will reach out to affected customers via email with the new server IP addresses, and new nameservers if they wish to use those, as well as a time we&#039;ll be carrying out the migration work.

Customers should not need to do anything during and after the migration if you use our existing Plesk nameservers, your website will seamlessly point to the new servers without requiring any action. Jul 31, 17:00:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day</p>
    
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 30&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;Jul &lt;var data-var=&#039;date&#039;&gt; 30&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; -
  Over the next few days, we will be migrating customers from some of our Plesk servers to our new whitelabel Plesk reseller hosting platform.

Customers on our existing CentOS Plesk servers will be moved to various new servers running CloudLinux, which delivers the very best security, reliability and performance. The new servers also feature newer hardware, such as newer CPUs, better SSDs and the latest generation memory.

The new servers will be located on our [**websiteserver.uk**](http://websiteserver.uk) domain as opposed to our own, which is great for resellers of the service.

We will reach out to affected customers via email with the new server IP addresses, and new nameservers if they wish to use those, as well as a time we&#039;ll be carrying out the migration work.

Customers should not need to do anything during and after the migration if you use our existing Plesk nameservers, your website will seamlessly point to the new servers without requiring any action..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 31&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;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 30 Jul 2024 17:00:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/clz663uhz330576heoddipcwkxk</link>
  <guid>https://status.fyfeweb.com/maintenance/clz663uhz330576heoddipcwkxk</guid>
</item>

<item>
  <title>FyfeWeb Portal Maintenance</title>
  <description>
    Type: Incident
    Duration: 14 minutes

    
    Jul 27, 16:05:37 GMT+0 - Identified - We are currently applying some upgrades to our client portal. Whilst we carry out the work, we expect this to be offline for the next 15-20 minutes. Jul 27, 16:19:35 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 14 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:05:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are currently applying some upgrades to our client portal. Whilst we carry out the work, we expect this to be offline for the next 15-20 minutes..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:19:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 27 Jul 2024 16:05:37 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/clz4bp2n252557i7oddqh1sgzv</link>
  <guid>https://status.fyfeweb.com/incident/clz4bp2n252557i7oddqh1sgzv</guid>
</item>

<item>
  <title>Network Interruption at Reliance House</title>
  <description>
    Type: Incident
    Duration: 1 hour and 20 minutes

    Affected Components: Internal Infrastructure, Hosted Virtual Machines, Reliance House, Newcastle, Dedicated Servers
    Jul 21, 19:24:02 GMT+0 - Investigating - We are aware of some potential disruption affecting backhaul to our Reliance House Facility. We are currently investigating this incident. Jul 21, 19:54:55 GMT+0 - Identified - We&#039;ve identified the issue with one of our backhaul carriers in this data centre. Services seem stable for now, but we&#039;re still monitoring for further issues.  Jul 21, 20:44:04 GMT+0 - Resolved - We have been notified that the incident has been resolved, we&#039;ve been told it was related to a core network link between Newcastle and London experiencing some packet loss.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 20 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:24:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are aware of some potential disruption affecting backhaul to our Reliance House Facility. We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:54:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;ve identified the issue with one of our backhaul carriers in this data centre. Services seem stable for now, but we&#039;re still monitoring for further issues. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:44:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We have been notified that the incident has been resolved, we&#039;ve been told it was related to a core network link between Newcastle and London experiencing some packet loss. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 21 Jul 2024 19:24:02 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/clyvy55wz16791wxn1lwzihnd2</link>
  <guid>https://status.fyfeweb.com/incident/clyvy55wz16791wxn1lwzihnd2</guid>
</item>

<item>
  <title>Network Edge - Rack Move - Equinix LD8, London</title>
  <description>
    Type: Maintenance
    Duration: 2 hours and 57 minutes

    Affected Components: Network Services, Equinix LD8, London, Reliance House, Newcastle, Dedicated Servers
    Jul 14, 00:00:00 GMT+0 - Identified - At FyfeWeb, we&#039;re always looking at ways in which we can improve our services and network infrastructure. That&#039;s why on Sunday 14th July at around 1 AM, we&#039;ll be moving into a brand new cabinet in Equinix LD8\. The reasons for the move are to improve service availability, add additional redundancy into the network and also have higher power density within this particular data centre for future upgrades we have planned.

This is a very rare event, the last time we moved some of our edge network infrastructure was in 2020, around four years ago now (interestingly enough, also in June!) so we&#039;re not expecting anything like this to happen in the near future anyway.

This will cause service disruption in the following data centres for around one hour, which is why we&#039;re doing the work after midnight:

* Equinix LD8, London
* Stellium, Newcastle upon Tyne
* Reliance House, Newcastle upon Tyne

We&#039;ll be working late into the night to ensure all work gets completed as quickly as possible, and to ensure minimum disruption to your services.

This work will predominantly effect customer dedicated servers and colocation services. Our VPS and cPanel hosting will not be affected.

We&#039;re also giving over one months notice to ensure you&#039;re aware of the scope of work being carried out. Please do get in touch if you have any further questions.

Kind regards,

Jaden Jun 26, 11:20:36 GMT+0 - Identified - Due to engineer availability at Equinix, we have had to postpone this maintenance and change it to Sunday 14th July at around 1 AM. 

We apologise for any inconvenience caused by this.

Please contact us should you have any further questions.  Jul 14, 02:56:46 GMT+0 - Completed - All services are back up and running.  Jul 14, 00:04:51 GMT+0 - Identified - We are beginning to move the equipment within this rack. Service disruption will occur imminently.  Jul 14, 01:50:59 GMT+0 - Identified - Our cross connects have been re-patched and the ports are now online. We&#039;re still finishing some final works, however the data centres are now back online. Thank you for your patience so far.  Jul 14, 01:33:35 GMT+0 - Identified - We have now moved the equipment to the new rack. Devices are booting up, and we will begin to re-patch our cross connects.  Jul 14, 00:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 57 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  At FyfeWeb, we&#039;re always looking at ways in which we can improve our services and network infrastructure. That&#039;s why on Sunday 14th July at around 1 AM, we&#039;ll be moving into a brand new cabinet in Equinix LD8\. The reasons for the move are to improve service availability, add additional redundancy into the network and also have higher power density within this particular data centre for future upgrades we have planned.

This is a very rare event, the last time we moved some of our edge network infrastructure was in 2020, around four years ago now (interestingly enough, also in June!) so we&#039;re not expecting anything like this to happen in the near future anyway.

This will cause service disruption in the following data centres for around one hour, which is why we&#039;re doing the work after midnight:

* Equinix LD8, London
* Stellium, Newcastle upon Tyne
* Reliance House, Newcastle upon Tyne

We&#039;ll be working late into the night to ensure all work gets completed as quickly as possible, and to ensure minimum disruption to your services.

This work will predominantly effect customer dedicated servers and colocation services. Our VPS and cPanel hosting will not be affected.

We&#039;re also giving over one months notice to ensure you&#039;re aware of the scope of work being carried out. Please do get in touch if you have any further questions.

Kind regards,

Jaden.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:20:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Due to engineer availability at Equinix, we have had to postpone this maintenance and change it to Sunday 14th July at around 1 AM. 

We apologise for any inconvenience caused by this.

Please contact us should you have any further questions. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:56:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  All services are back up and running. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:04:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are beginning to move the equipment within this rack. Service disruption will occur imminently. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:50:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our cross connects have been re-patched and the ports are now online. We&#039;re still finishing some final works, however the data centres are now back online. Thank you for your patience so far. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:33:35&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have now moved the equipment to the new rack. Devices are booting up, and we will begin to re-patch our cross connects. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00: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;
]]>
  </content:encoded>
  <pubDate>Sun, 14 Jul 2024 00:00:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/clwaikei558198bioqbzkzn98o</link>
  <guid>https://status.fyfeweb.com/maintenance/clwaikei558198bioqbzkzn98o</guid>
</item>

<item>
  <title>Network Interruption - West Midlands DC1</title>
  <description>
    Type: Incident
    Duration: 2 hours and 17 minutes

    Affected Components: Dedicated Servers, DC1, West Midlands
    Jun 21, 14:40:56 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jun 21, 14:24:21 GMT+0 - Investigating - We are currently investigating a network issue in our West Midlands data centre - this is causing issues with some managed dedicated servers, colocation and cPanel Web Hosting. Jun 21, 14:33:57 GMT+0 - Investigating - We are still investigating the incident - the issue appears to be related to connectivity with an upstream provider within this facility from our core router. We are currently in contact with the provider in question. There is no ETA at this time, but we&#039;re trying to get this resovled as quickly as possible. Jun 21, 14:57:32 GMT+0 - Monitoring - ### **Root Cause Analysis**

### 

We identified an issue with the primary routing-engine in core1-dc1, the core router in DC1\. 

We have manually switched mastership to the backup routing-engine without graceful-switchover which has caused all protocols to flap and re-converge on this router.

Services have now recovered and the router is stable, however if you are still experiencing issues please get in touch. Jun 21, 16:41:47 GMT+0 - Resolved - Services have remained stable since the previous update.

Separate to this incident, this router is due to be upgraded with newer routing-engines. This work will now be prioritised and will be scheduled as a new maintenance window, to be announced in due course. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:40:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We implemented a fix and are currently monitoring the result..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:24:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating a network issue in our West Midlands data centre - this is causing issues with some managed dedicated servers, colocation and cPanel Web Hosting..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:33:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are still investigating the incident - the issue appears to be related to connectivity with an upstream provider within this facility from our core router. We are currently in contact with the provider in question. There is no ETA at this time, but we&#039;re trying to get this resovled as quickly as possible..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:57:32&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  ### **Root Cause Analysis**

### 

We identified an issue with the primary routing-engine in core1-dc1, the core router in DC1\. 

We have manually switched mastership to the backup routing-engine without graceful-switchover which has caused all protocols to flap and re-converge on this router.

Services have now recovered and the router is stable, however if you are still experiencing issues please get in touch..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:41:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Services have remained stable since the previous update.

Separate to this incident, this router is due to be upgraded with newer routing-engines. This work will now be prioritised and will be scheduled as a new maintenance window, to be announced in due course..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 21 Jun 2024 14:24:21 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/clxos85rx35276z3om03rz5pf2</link>
  <guid>https://status.fyfeweb.com/incident/clxos85rx35276z3om03rz5pf2</guid>
</item>

<item>
  <title>Network Issue - Reliance House, Newcastle</title>
  <description>
    Type: Incident
    Duration: 3 days, 13 hours and 41 minutes

    Affected Components: Network Services, Dedicated Servers, Reliance House, Newcastle
    Apr 22, 18:36:05 GMT+0 - Identified - We have identified that the issue is related to a faulty SFP module on one of our core network links from Newcastle back to Equinix LD8 in London, most traffic passing through this link is being dropped at present, we&#039;re working to replace the module now.  Apr 22, 18:43:14 GMT+0 - Monitoring - We have replaced the optic with a new one, and normal service has resumed.  Apr 22, 19:58:36 GMT+0 - Resolved - This incident has been resolved, with director involvement. If you require an RFO, please do get in touch. We apologise for any inconvenience caused by this outage.  Apr 22, 18:32:56 GMT+0 - Investigating - We are currently experiencing a network issue affecting our Reliance House data centre in Newcastle, our network team is actively investigating the situation.

**Location:** Reliance House, Newcastle  
**Issue:** Network disruption and packet loss

Please be aware that during this time, services hosted in this facility may have intermittent connectivity problems. We apologise for any inconvenience and appreciate your patience as we work to fix the issue.

Thank you for your understanding. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 13 hours and 41 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:36:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We have identified that the issue is related to a faulty SFP module on one of our core network links from Newcastle back to Equinix LD8 in London, most traffic passing through this link is being dropped at present, we&#039;re working to replace the module now. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:43:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We have replaced the optic with a new one, and normal service has resumed. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:58:36&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved, with director involvement. If you require an RFO, please do get in touch. We apologise for any inconvenience caused by this outage. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:32:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing a network issue affecting our Reliance House data centre in Newcastle, our network team is actively investigating the situation.

**Location:** Reliance House, Newcastle  
**Issue:** Network disruption and packet loss

Please be aware that during this time, services hosted in this facility may have intermittent connectivity problems. We apologise for any inconvenience and appreciate your patience as we work to fix the issue.

Thank you for your understanding..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 22 Apr 2024 18:32:56 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/clvbaoqk327181bcodum47c0od</link>
  <guid>https://status.fyfeweb.com/incident/clvbaoqk327181bcodum47c0od</guid>
</item>

<item>
  <title>Network Issue - West Midlands DC2</title>
  <description>
    Type: Incident
    Duration: 4 days, 11 hours and 54 minutes

    Affected Components: Hosted Virtual Machines, Network Services, Dedicated Servers, DC2, West Midlands
    Feb 12, 10:05:05 GMT+0 - Investigating - We&#039;re currently investigating an issue with packet loss in one of our data centres. At the moment, this appears to be isolated to an issue with an upstream provider and not on our network. We&#039;ll keep this incident updated throughout.

This will cause issues with some VPS services, as well as some customer dedicated servers and colocation. Feb 12, 10:13:25 GMT+0 - Identified - We are still seeing services flap, this has been raised to director-level with the upstream provider.

They have confirmed they&#039;re currently investigating the root cause of the incident. Feb 12, 10:26:41 GMT+0 - Monitoring - After around 5 minutes of service interruption in total, we are seeing services return to normal. Please raise a ticket if you&#039;re experiencing any issues. Feb 12, 11:16:00 GMT+0 - Monitoring - Service has remained stable for some time. Initial investigations indicate an issue with 2 wavelengths from Wolverhampton to London, causing a number of protocols to flap, interrupting traffic. We took action to disable those wavelengths which stabilised traffic. We will be reintroducing those wavelengths during a planned window late one evening to be able to monitor traffic as they&#039;re reintroduced. Feb 16, 21:59:00 GMT+0 - Resolved - This incident is now resolved and the wavelengths in question have been reintroduced to our network. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 11 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:05:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We&#039;re currently investigating an issue with packet loss in one of our data centres. At the moment, this appears to be isolated to an issue with an upstream provider and not on our network. We&#039;ll keep this incident updated throughout.

This will cause issues with some VPS services, as well as some customer dedicated servers and colocation..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:13:25&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are still seeing services flap, this has been raised to director-level with the upstream provider.

They have confirmed they&#039;re currently investigating the root cause of the incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:26:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  After around 5 minutes of service interruption in total, we are seeing services return to normal. Please raise a ticket if you&#039;re experiencing any issues..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 12&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:16:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  Service has remained stable for some time. Initial investigations indicate an issue with 2 wavelengths from Wolverhampton to London, causing a number of protocols to flap, interrupting traffic. We took action to disable those wavelengths which stabilised traffic. We will be reintroducing those wavelengths during a planned window late one evening to be able to monitor traffic as they&#039;re reintroduced..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:59:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident is now resolved and the wavelengths in question have been reintroduced to our network..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 12 Feb 2024 10:05:05 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/clsirq0tp508704bbofoa8i1l48</link>
  <guid>https://status.fyfeweb.com/incident/clsirq0tp508704bbofoa8i1l48</guid>
</item>

<item>
  <title>Emergency Reboot: CP01 cPanel Server</title>
  <description>
    Type: Incident
    Duration: 10 minutes

    
    Feb 4, 01:16:39 GMT+0 - Investigating - After recent investigations into some unexpected blips on one of our cPanel servers, we need to carry out an emergency reboot in order to apply some kernel changes. This is being done at around 1:20 AM on a Saturday, so hopefully you shouldn&#039;t notice anything. Thank you for your patience.  Feb 4, 01:20:57 GMT+0 - Identified - The reboot has commenced - this may take up to 20 minutes to complete.  Feb 4, 01:26:12 GMT+0 - Resolved - The reboot has been completed successfully with only \~3 minutes of downtime. Thank you for your patience.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 minutes</p>
    
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:16:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  After recent investigations into some unexpected blips on one of our cPanel servers, we need to carry out an emergency reboot in order to apply some kernel changes. This is being done at around 1:20 AM on a Saturday, so hopefully you shouldn&#039;t notice anything. Thank you for your patience. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:20:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The reboot has commenced - this may take up to 20 minutes to complete. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:26:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  The reboot has been completed successfully with only \~3 minutes of downtime. Thank you for your patience. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 4 Feb 2024 01:16:39 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cls6tbm7g411494b2om9qpjmjh2</link>
  <guid>https://status.fyfeweb.com/incident/cls6tbm7g411494b2om9qpjmjh2</guid>
</item>

<item>
  <title>Network Issues - Stellium</title>
  <description>
    Type: Incident
    Duration: 12 hours and 25 minutes

    Affected Components: Network Services, Dedicated Servers, Reliance House, Newcastle
    Jan 18, 22:37:57 GMT+0 - Investigating - We are currently experiencing a network issue affecting our PoP at Stellium in Newcastle, due to an issue with backhaul to London. Our team is actively investigating the situation, and further updates will follow as we work to resolve the issue with them.

**Details:**

**Location:** Stellium Data Centre, Newcastle
**Issue:** Network disruption
**Cause:** Backhaul connectivity issue

Please be aware that during this time, services at this site may have intermittent connectivity problems. We apologise for any inconvenience and appreciate your patience as we work to fix the issue.

Thank you for your understanding. Jan 18, 22:48:37 GMT+0 - Monitoring - We&#039;ve spoken to the carrier we use for our circuits back to London and they&#039;re currently aware of an issue on their network. However, service resumed after around 10 minutes of disruption. We&#039;re currently speaking to their engineers to find out what&#039;s happened.   Jan 18, 23:45:21 GMT+0 - Monitoring - To summerise, a change was done on one of the core backbone links at Stellium, there was an issue with this, and the change was rolled back. The change has since been reimplemented successfully. 

This is related to the installation of a new 100Gb wavelength between London and Newcastle. 

We&#039;ll keep this incident open overnight, and will confirm closure tomorrow morning - however it seems like the issue should not re-occur.  Jan 19, 11:03:20 GMT+0 - Resolved - We&#039;ve seen no further drops - this incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 hours and 25 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;22:37:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing a network issue affecting our PoP at Stellium in Newcastle, due to an issue with backhaul to London. Our team is actively investigating the situation, and further updates will follow as we work to resolve the issue with them.

**Details:**

**Location:** Stellium Data Centre, Newcastle
**Issue:** Network disruption
**Cause:** Backhaul connectivity issue

Please be aware that during this time, services at this site may have intermittent connectivity problems. We apologise for any inconvenience and appreciate your patience as we work to fix the issue.

Thank you for your understanding..&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;22:48:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We&#039;ve spoken to the carrier we use for our circuits back to London and they&#039;re currently aware of an issue on their network. However, service resumed after around 10 minutes of disruption. We&#039;re currently speaking to their engineers to find out what&#039;s happened.  .&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;23:45:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  To summerise, a change was done on one of the core backbone links at Stellium, there was an issue with this, and the change was rolled back. The change has since been reimplemented successfully. 

This is related to the installation of a new 100Gb wavelength between London and Newcastle. 

We&#039;ll keep this incident open overnight, and will confirm closure tomorrow morning - however it seems like the issue should not re-occur. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:03:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We&#039;ve seen no further drops - this incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 18 Jan 2024 22:37:57 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/clrjslx4i21175bfo5kr4aef4m</link>
  <guid>https://status.fyfeweb.com/incident/clrjslx4i21175bfo5kr4aef4m</guid>
</item>

<item>
  <title>Newcastle DC1 Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 2 hours and 14 minutes

    Affected Components: Reliance House, Newcastle
    Dec 24, 00:44:30 GMT+0 - Completed - Maintenance and checks have been completed successfully. Dec 23, 22:30:01 GMT+0 - Identified - Maintenance is now in progress Dec 23, 22:30:00 GMT+0 - Identified - We are undertaking some maintenance in our Newcastle DC1 facility between 22:30 on 23/12/2023 and 01:00 on 24/12/23.

Affected customers have already been informed. Please get in contact if you have any questions. Dec 24, 00:16:00 GMT+0 - Identified - Maintenance in Newcastle DC1 is now complete. Your services should have now returned and we are performing checks.

Services remain &quot;at-risk&quot; and we will update once this is done.

If you have any issues, please don&#039;t hesitate to get in touch. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 14 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:44:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance and checks have been completed successfully..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22: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;Dec &lt;var data-var=&#039;date&#039;&gt; 23&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;Identified&lt;/strong&gt; -
  We are undertaking some maintenance in our Newcastle DC1 facility between 22:30 on 23/12/2023 and 01:00 on 24/12/23.

Affected customers have already been informed. Please get in contact if you have any questions..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:16:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance in Newcastle DC1 is now complete. Your services should have now returned and we are performing checks.

Services remain &quot;at-risk&quot; and we will update once this is done.

If you have any issues, please don&#039;t hesitate to get in touch..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 23 Dec 2023 22:30:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/clqimkxum613657sokk3914ooq</link>
  <guid>https://status.fyfeweb.com/maintenance/clqimkxum613657sokk3914ooq</guid>
</item>

<item>
  <title>Network Issue - Newcastle</title>
  <description>
    Type: Incident
    Duration: 3 hours and 1 minute

    Affected Components: Network Services, Dedicated Servers, Reliance House, Newcastle
    Sep 19, 20:37:01 GMT+0 - Resolved - This incident has been resolved. Sep 19, 17:36:30 GMT+0 - Investigating - We are currently experiencing a network issue affecting our Newcastle Data Centre, due to an upstream provider issue. Our team is actively investigating the situation, and further updates will follow as we work to resolve the issue with them.

**Details:**

**Location:** Newcastle Data Centre
**Issue:** Network disruption
**Cause:** Upstream provider connectivity issues

Please be aware that during this time, services at the Newcastle Data Centre may have intermittent connectivity problems. We apologise for any inconvenience and appreciate your patience as we work to fix the issue.

Thank you for your understanding. Sep 19, 17:51:13 GMT+0 - Monitoring - We&#039;ve implemented a fix and are currently monitoring the results. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:37:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:36:30&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently experiencing a network issue affecting our Newcastle Data Centre, due to an upstream provider issue. Our team is actively investigating the situation, and further updates will follow as we work to resolve the issue with them.

**Details:**

**Location:** Newcastle Data Centre
**Issue:** Network disruption
**Cause:** Upstream provider connectivity issues

Please be aware that during this time, services at the Newcastle Data Centre may have intermittent connectivity problems. We apologise for any inconvenience and appreciate your patience as we work to fix the issue.

Thank you for your understanding..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:51:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  We&#039;ve implemented a fix and are currently monitoring the results..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 19 Sep 2023 17:36:30 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/clmqlk5gw31323bvoj7femt5bn</link>
  <guid>https://status.fyfeweb.com/incident/clmqlk5gw31323bvoj7femt5bn</guid>
</item>

<item>
  <title>Transit Provider Emergency Maintenance</title>
  <description>
    Type: Maintenance
    Duration: 1 day, 22 hours and 48 minutes

    Affected Components: Network Services, Reliance House, Newcastle
    Aug 26, 16:16:13 GMT+0 - Identified - The provider has stated that they are still working on this, and are having to rebuild quite a lot of their network in London due to discovering some underlying issues. No impact is expected at the moment, but services are &quot;at-risk&quot; whilst the work is carried out.  Aug 28, 10:17:34 GMT+0 - Completed - The London network has now been fully rebuilt by the provider, and is now part of the new global network. Going forward, we don’t expect to see any further issues - but if we do, we’ll instigate our backup plans.  Aug 26, 11:30:01 GMT+0 - Identified - Maintenance is now in progress Aug 26, 13:19:16 GMT+0 - Identified - Maintenance is still in progress with this. Traffic has been re-routed via alternative paths, so no impact has been seen. We&#039;re extending this window by another hour, just to ensure we have enough time to get the &quot;all clear&quot; Aug 26, 11:30:00 GMT+0 - Identified - Our transit provider, Global Secure Layer, had network hardware shipped to London earlier this month which was found to be dead on arrival. The replacement units have arrived and completed all tests. These will be installed to complete the required upgrades for their EMEA network.

This maintenance window was created by them due to the issues they saw the other night - any occasional previous ~10-minute drops should be resolved going forward, once this work has been completed. FyfeWeb is in direct contact with the CEO/CTO at this time, ensuring we&#039;re constantly kept up to date with what&#039;s going on.

They expect outages to last less than 10 minutes during this maintenance window. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day, 22 hours and 48 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:16:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The provider has stated that they are still working on this, and are having to rebuild quite a lot of their network in London due to discovering some underlying issues. No impact is expected at the moment, but services are &quot;at-risk&quot; whilst the work is carried out. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:17:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The London network has now been fully rebuilt by the provider, and is now part of the new global network. Going forward, we don’t expect to see any further issues - but if we do, we’ll instigate our backup plans. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11: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;Aug &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:19:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is still in progress with this. Traffic has been re-routed via alternative paths, so no impact has been seen. We&#039;re extending this window by another hour, just to ensure we have enough time to get the &quot;all clear&quot;.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Our transit provider, Global Secure Layer, had network hardware shipped to London earlier this month which was found to be dead on arrival. The replacement units have arrived and completed all tests. These will be installed to complete the required upgrades for their EMEA network.

This maintenance window was created by them due to the issues they saw the other night - any occasional previous ~10-minute drops should be resolved going forward, once this work has been completed. FyfeWeb is in direct contact with the CEO/CTO at this time, ensuring we&#039;re constantly kept up to date with what&#039;s going on.

They expect outages to last less than 10 minutes during this maintenance window..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 26 Aug 2023 11:30:00 +0000</pubDate>
  <link>https://status.fyfeweb.com/maintenance/cllrx82ar49119b5os7cq1uj9t</link>
  <guid>https://status.fyfeweb.com/maintenance/cllrx82ar49119b5os7cq1uj9t</guid>
</item>

<item>
  <title>Network Issue - Newcastle</title>
  <description>
    Type: Incident
    Duration: 3 hours and 26 minutes

    Affected Components: Internal Infrastructure, Network Services
    Aug 25, 20:07:40 GMT+0 - Investigating - We are currently investigating this incident. Updates to follow. It looks as if this is an issue with GSL, one of our DDoS-protected IP transit providers.  Aug 25, 20:14:59 GMT+0 - Identified - Service has been restored - we&#039;re finding out what happened with the provider at the moment.  Aug 25, 20:22:16 GMT+0 - Monitoring - The provider has stated that they&#039;ve had a subsea cable failure which has caused the issue. Although the outage only lasted 11 minutes, we&#039;re wanting to improve reliability on this service. More information on this will follow in the coming days.  Aug 25, 23:33:12 GMT+0 - Resolved - As you may be aware, FyfeWeb runs its own 100Gbps+ IP network, spanning 6 UK-based data centres. In March this year, we had a project on to bring in an additional DDoS mitigation service from Global Secure Layer, who operate a global IP Transit network with inline DDoS Protection. When the project was completed in March, everything ran solid for about 3 months until we started to see some issues in July/August. I&#039;ve now escalated this to the CTO of GSL, and after a couple of hours discussing the issues, I know understand what&#039;s going on - and what&#039;s being done to fix it. Ultimately, GSL are building a new global network - with many sites now migrated over, London is ready to be migrated to the new network. I&#039;m being told that we should see around ~1 minute of traffic impact whilst this is carried out, and after that, there should be no further issues. However, that being said, we are still looking to add further resilience to this service as soon as possible. Thank you for your patience so far.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 26 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:07:40&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident. Updates to follow. It looks as if this is an issue with GSL, one of our DDoS-protected IP transit providers. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:14:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Service has been restored - we&#039;re finding out what happened with the provider at the moment. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:22:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt; -
  The provider has stated that they&#039;ve had a subsea cable failure which has caused the issue. Although the outage only lasted 11 minutes, we&#039;re wanting to improve reliability on this service. More information on this will follow in the coming days. .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:33:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  As you may be aware, FyfeWeb runs its own 100Gbps+ IP network, spanning 6 UK-based data centres. In March this year, we had a project on to bring in an additional DDoS mitigation service from Global Secure Layer, who operate a global IP Transit network with inline DDoS Protection. When the project was completed in March, everything ran solid for about 3 months until we started to see some issues in July/August. I&#039;ve now escalated this to the CTO of GSL, and after a couple of hours discussing the issues, I know understand what&#039;s going on - and what&#039;s being done to fix it. Ultimately, GSL are building a new global network - with many sites now migrated over, London is ready to be migrated to the new network. I&#039;m being told that we should see around ~1 minute of traffic impact whilst this is carried out, and after that, there should be no further issues. However, that being said, we are still looking to add further resilience to this service as soon as possible. Thank you for your patience so far. .&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 25 Aug 2023 20:07:40 +0000</pubDate>
  <link>https://status.fyfeweb.com/incident/cllr0y9ri54083cdormg4wwue7</link>
  <guid>https://status.fyfeweb.com/incident/cllr0y9ri54083cdormg4wwue7</guid>
</item>

  </channel>
  </rss>