<?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>DataCity Status - Incident history</title>
    <link>https://datacity.instatus.com</link>
    <description>DataCity</description>
    <pubDate>Wed, 15 Apr 2026 15:20:58 +0000</pubDate>
    
<item>
  <title>Internet Service</title>
  <description>
    Type: Incident
    Duration: 2 hours and 6 minutes

    Affected Components: Kitchener Datacenter, Kitchener Internet
    Apr 15, 15:20:58 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 15, 15:21:48 GMT+0 - Identified - Enova Power has 1000 customers in Doon with out power. Apr 15, 15:47:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 6 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:20:58&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;Apr &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:21:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Enova Power has 1000 customers in Doon with out power..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:47: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>Wed, 15 Apr 2026 15:20:58 +0000</pubDate>
  <link>https://datacity.instatus.com/incident/cmo076rb5000l4161tbg22fq9</link>
  <guid>https://datacity.instatus.com/incident/cmo076rb5000l4161tbg22fq9</guid>
</item>

<item>
  <title>Local Power Outage - Kitchener</title>
  <description>
    Type: Incident
    

    Affected Components: Kitchener Datacenter, Cloud Service Kitchener, Kitchener Internet, Cambridge Internet
    Apr 15, 14:45:00 GMT+0 - Identified - Enova is onsite restoring connection. Apr 15, 14:45:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Enova is onsite restoring connection..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:45: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, 15 Apr 2025 14:45:00 +0000</pubDate>
  <link>https://datacity.instatus.com/incident/cm9in9li30002gordfk4qxxlb</link>
  <guid>https://datacity.instatus.com/incident/cm9in9li30002gordfk4qxxlb</guid>
</item>

<item>
  <title>Rogers Outage</title>
  <description>
    Type: Incident
    Duration: 1 hour and 53 minutes

    Affected Components: Waterloo Datacenter, Kitchener Datacenter, Toronto Internet, Support SMS, Cloud Service Kitchener, Cloud Service Waterloo, Support Phone, Waterloo Internet Service, Kitchener Internet, Cambridge Internet
    Nov 3, 20:01:05 GMT+0 - Investigating - We are currently investigating this incident. Nov 3, 21:53:59 GMT+0 - Resolved - Rogers replaced a line card and this incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 53 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:01:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Nov &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:53:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Rogers replaced a line card and this incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 3 Nov 2024 20:01:05 +0000</pubDate>
  <link>https://datacity.instatus.com/incident/cm320p7ip003hn3fq409d7rfg</link>
  <guid>https://datacity.instatus.com/incident/cm320p7ip003hn3fq409d7rfg</guid>
</item>

<item>
  <title>Network Outage</title>
  <description>
    Type: Incident
    Duration: 1 day, 3 hours and 59 minutes

    Affected Components: Waterloo Datacenter, Kitchener Datacenter, Toronto Internet, Support SMS, Cloud Service Kitchener, Cloud Service Waterloo, Support Phone, Waterloo Internet Service, Kitchener Internet, Cambridge Internet
    Oct 2, 01:50:50 GMT+0 - Investigating - We are currently investigating this incident. Oct 3, 05:50:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 3 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:50:50&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating this incident..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Oct &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:50: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>Wed, 2 Oct 2024 01:50:50 +0000</pubDate>
  <link>https://datacity.instatus.com/incident/cm1r7nvpi0010x04fg1m12ma2</link>
  <guid>https://datacity.instatus.com/incident/cm1r7nvpi0010x04fg1m12ma2</guid>
</item>

<item>
  <title>Major Fiber Cut</title>
  <description>
    Type: Incident
    Duration: 11 hours and 7 minutes

    Affected Components: Waterloo Datacenter, Kitchener Datacenter, Toronto Internet, Support SMS, Cloud Service Kitchener, Cloud Service Waterloo, Support Phone, Waterloo Internet Service, Kitchener Internet, Cambridge Internet
    Aug 19, 10:13:00 GMT+0 - Identified - We are tracking a **major fiber cut** due to vandalism Around **2:50 AM EST**. Both Zayo and Rogers are cut. Here is the latest note from the Rogers Fiber tech who is at the scene. The Rogers fibre technician arrived on-site at the fault location near Hanlon rd and Stone Rd in Guelph. Teams found 5 fibre cables cut due to vandalism. The fibre crew is currently assessing the damages and working on a repair plan. 

**Technician ETA: on-siteEstimated Time To Restore: N/A Next update: 8:30 AM ET or sooner should a major change in status occur** Aug 19, 12:31:52 GMT+0 - Identified - Rogers fibre team is waiting for the aerial crew to arrive onsite. They need to do a deeper dive to see how far the damage extends. Teams continue to work to access the damage and are preparing an action plan.

**Technician ETA: Onroute** 

**Estimated Time To Restore: N/A**

**Next update: 11:00 AM ET or sooner should a major change occur.**  Aug 19, 15:16:38 GMT+0 - Identified - Rogers fibre crew has started preparations on the North end of the cable where the first cut was identified. Teams are also concurrently delasing and removing some of the old cut pieces of cable to place the new one.   
The amount of work for repairs is extensive, requiring about 500 metres of replacement cable as well as 4 new fibre optic splice closures (FOSCs) to be built and installed. No ETR is available at this time. 

**Technician ETA: on-site**

**Estimated Time To Restore: N/A** 

**Next update: 1:30 PM ET or sooner should a major change in status occur** Aug 19, 17:56:52 GMT+0 - Identified - Rogers fibre crew have completed assessments and all damaged and cut fibre cables have been accounted for. In total roughly 500 metres of replacement fibre optic cable needs to be replaced and 5 new FOSCs installed for the restoration. Teams have begun preparations for splicing on one end of the cable and about to start on the other end. Teams are also preparing for a crew change over as the current crew have been on-site since early this morning and are exhausted. An initial ETR for full restoration was provided for August 20th at 12:00 PM, however circuits are expected to recover sooner once splicing begins. An updated ETR will be provided as repairs and splicing progresses. 

**Technician ETA: on-site**

**Estimated Time To Restore: August 20th at 12:00 PM**

**Next update: 4:00 PM ET or sooner should a major change in status occur** Aug 19, 20:26:19 GMT+0 - Identified - Splicing have begun on the north end of the cable, however services are not expected to recover until splicing on the south end beings.  
Preparations are underway on both ends of the cable. Additionally crews are changing over to an evening crew to relieve the existing crew and handing off. Teams expect to start seeing some circuits recover around 6PM - 7PM.

**Technician ETA: on-site**

**Estimated Time To Restore: Gradual recovery starting around 6PM with a full Restoration on Aug 20th at 12:00 PM** 

**Next update: 6:30 PM ET or sooner should a major change in status occur** Aug 19, 22:48:06 GMT+0 - Resolved - Rogers fibre crew has advised that teams have spliced most of the fibre cables on the north end. On the South end the 288 count is completed preparations and expected to start splicing shortly. Additionally there is a middle section of the cable which is also being prepped and expected to start splicing shortly. Circuits should begin to recover once splicing on the centre portion and south end begins.   
Currently there are no changes to the ETR. 

**Technician ETA: on-site**

**Estimated Time To Restore: August 20th at 12:00 PM ET**

**Next update: 9:00 PM ET or sooner should a major change in status occur** 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 7 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:13:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are tracking a **major fiber cut** due to vandalism Around **2:50 AM EST**. Both Zayo and Rogers are cut. Here is the latest note from the Rogers Fiber tech who is at the scene. The Rogers fibre technician arrived on-site at the fault location near Hanlon rd and Stone Rd in Guelph. Teams found 5 fibre cables cut due to vandalism. The fibre crew is currently assessing the damages and working on a repair plan. 

**Technician ETA: on-siteEstimated Time To Restore: N/A Next update: 8:30 AM ET or sooner should a major change in status occur**.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:31:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Rogers fibre team is waiting for the aerial crew to arrive onsite. They need to do a deeper dive to see how far the damage extends. Teams continue to work to access the damage and are preparing an action plan.

**Technician ETA: Onroute** 

**Estimated Time To Restore: N/A**

**Next update: 11:00 AM ET or sooner should a major change occur.** .&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:16:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Rogers fibre crew has started preparations on the North end of the cable where the first cut was identified. Teams are also concurrently delasing and removing some of the old cut pieces of cable to place the new one.   
The amount of work for repairs is extensive, requiring about 500 metres of replacement cable as well as 4 new fibre optic splice closures (FOSCs) to be built and installed. No ETR is available at this time. 

**Technician ETA: on-site**

**Estimated Time To Restore: N/A** 

**Next update: 1:30 PM ET or sooner should a major change in status occur**.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;17:56:52&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Rogers fibre crew have completed assessments and all damaged and cut fibre cables have been accounted for. In total roughly 500 metres of replacement fibre optic cable needs to be replaced and 5 new FOSCs installed for the restoration. Teams have begun preparations for splicing on one end of the cable and about to start on the other end. Teams are also preparing for a crew change over as the current crew have been on-site since early this morning and are exhausted. An initial ETR for full restoration was provided for August 20th at 12:00 PM, however circuits are expected to recover sooner once splicing begins. An updated ETR will be provided as repairs and splicing progresses. 

**Technician ETA: on-site**

**Estimated Time To Restore: August 20th at 12:00 PM**

**Next update: 4:00 PM ET or sooner should a major change in status occur**.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:26:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Splicing have begun on the north end of the cable, however services are not expected to recover until splicing on the south end beings.  
Preparations are underway on both ends of the cable. Additionally crews are changing over to an evening crew to relieve the existing crew and handing off. Teams expect to start seeing some circuits recover around 6PM - 7PM.

**Technician ETA: on-site**

**Estimated Time To Restore: Gradual recovery starting around 6PM with a full Restoration on Aug 20th at 12:00 PM** 

**Next update: 6:30 PM ET or sooner should a major change in status occur**.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:48:06&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Rogers fibre crew has advised that teams have spliced most of the fibre cables on the north end. On the South end the 288 count is completed preparations and expected to start splicing shortly. Additionally there is a middle section of the cable which is also being prepped and expected to start splicing shortly. Circuits should begin to recover once splicing on the centre portion and south end begins.   
Currently there are no changes to the ETR. 

**Technician ETA: on-site**

**Estimated Time To Restore: August 20th at 12:00 PM ET**

**Next update: 9:00 PM ET or sooner should a major change in status occur**.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 19 Aug 2024 10:13:00 +0000</pubDate>
  <link>https://datacity.instatus.com/incident/cm00xbguk001eb2x0zzyxzft7</link>
  <guid>https://datacity.instatus.com/incident/cm00xbguk001eb2x0zzyxzft7</guid>
</item>

<item>
  <title>Network Connectivity Issues.</title>
  <description>
    Type: Incident
    

    Affected Components: Kitchener Datacenter, Cloud Service Kitchener, Kitchener Internet, Cambridge Internet
    Aug 5, 22:39:00 GMT+0 - Resolved - This incident has been resolved. Aug 5, 19:39:00 GMT+0 - Resolved - We are currently working on a network issue due to equipment failure.

The device is being repaired.. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:39: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;
&lt;p&gt;&lt;small&gt;Aug &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:39:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We are currently working on a network issue due to equipment failure.

The device is being repaired...&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 5 Aug 2024 19:39:00 +0000</pubDate>
  <link>https://datacity.instatus.com/incident/clzhfg6ix177206hzo6r1dctn58</link>
  <guid>https://datacity.instatus.com/incident/clzhfg6ix177206hzo6r1dctn58</guid>
</item>

<item>
  <title>Degraded Internet Due to heavy Rain.</title>
  <description>
    Type: Incident
    Duration: 1 day

    Affected Components: Kitchener Internet, Cambridge Internet
    Jul 16, 14:41:16 GMT+0 - Investigating - We are currently investigating this incident. Jul 17, 14:41:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:41:16&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;Jul &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:41: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, 16 Jul 2024 14:41:16 +0000</pubDate>
  <link>https://datacity.instatus.com/incident/clyoizk8z356800h2n4batsc1zh</link>
  <guid>https://datacity.instatus.com/incident/clyoizk8z356800h2n4batsc1zh</guid>
</item>

<item>
  <title>High Temperature Due to HVAC blower failure.</title>
  <description>
    Type: Incident
    Duration: 20 minutes

    Affected Components: Kitchener Datacenter
    Jun 15, 21:20:00 GMT+0 - Investigating - We are currently investigating this incident.

We will provide more details soon. Jun 15, 21:20:00 GMT+0 - Identified - We are back online, We will contact HVAC company to have things looked at. Jun 15, 21:40:00 GMT+0 - Resolved - This incident has been resolved.

It alerted to be power related.

We are following up with electrician this week 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:20: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.

We will provide more details soon..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are back online, We will contact HVAC company to have things looked at..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jun &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;21:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved.

It alerted to be power related.

We are following up with electrician this week.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 15 Jun 2024 21:20:00 +0000</pubDate>
  <link>https://datacity.instatus.com/incident/clxgn8v7744762bkofztcvyc6e</link>
  <guid>https://datacity.instatus.com/incident/clxgn8v7744762bkofztcvyc6e</guid>
</item>

<item>
  <title>Investing power issue in Cambridge.</title>
  <description>
    Type: Incident
    Duration: 41 minutes

    Affected Components: Kitchener Internet, Cambridge Internet
    May 22, 19:31:24 GMT+0 - Resolved - Resolved May 22, 18:50:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 41 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:31:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  Resolved.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:50: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;
]]>
  </content:encoded>
  <pubDate>Wed, 22 May 2024 18:50:00 +0000</pubDate>
  <link>https://datacity.instatus.com/incident/clwi6v8zd2676b3om0bngat50</link>
  <guid>https://datacity.instatus.com/incident/clwi6v8zd2676b3om0bngat50</guid>
</item>

<item>
  <title>Fiber Cut Waterloo</title>
  <description>
    Type: Incident
    Duration: 4 hours

    Affected Components: Support SMS, Support Phone, Waterloo Internet Service, Kitchener Internet
    Apr 3, 14:30:00 GMT+0 - Identified - We are currently working on a fiber issue in waterloo affecting some customers.

The team has been on site repairing the service and it should be back online soon. Apr 3, 18:30:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are currently working on a fiber issue in waterloo affecting some customers.

The team has been on site repairing the service and it should be back online soon..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;18:30: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>Wed, 3 Apr 2024 14:30:00 +0000</pubDate>
  <link>https://datacity.instatus.com/incident/clv43r493237880b5oo9btdhw35</link>
  <guid>https://datacity.instatus.com/incident/clv43r493237880b5oo9btdhw35</guid>
</item>

<item>
  <title>Network Outage</title>
  <description>
    Type: Incident
    Duration: 11 hours and 25 minutes

    Affected Components: Support SMS, Support Phone, Waterloo Internet Service, Kitchener Internet
    Mar 21, 14:35:00 GMT+0 - Identified - Earlier this morning, a truck collided with a post, causing damage to the fiber optic wire in Guelph that is responsible for hosting services for Rogers, Zayo, and Telus. As a result, a number of customers were affected and some may still be experiencing issues. Mar 22, 02:00:00 GMT+0 - Resolved - Issue Resolved 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 25 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 21&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Earlier this morning, a truck collided with a post, causing damage to the fiber optic wire in Guelph that is responsible for hosting services for Rogers, Zayo, and Telus. As a result, a number of customers were affected and some may still be experiencing issues..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 22&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;Resolved&lt;/strong&gt; -
  Issue Resolved.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 21 Mar 2024 14:35:00 +0000</pubDate>
  <link>https://datacity.instatus.com/incident/clv43lq2a225706b5oo1kk6t14e</link>
  <guid>https://datacity.instatus.com/incident/clv43lq2a225706b5oo1kk6t14e</guid>
</item>

  </channel>
  </rss>