<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:tops-office.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://tops-office.instatus.com/history.atom"/>
  <title>TOPS Status - Incident history</title>
  <updated>2026-10-13T16:10:00.000+00:00</updated>
  <author>
    <name>TOPS</name>
  </author>
  
<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmv70o85p03xi1ml4aofzk2uj</id>
  <published>2026-10-13T16:10:00.000+00:00</published>
  <updated>2026-10-13T18:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmv70o85p03xi1ml4aofzk2uj"/>
  <title>Intermittent message delivery failures on TOC / webhook platform </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> TOPS Office Communicator (TOC), SMS/MMS</p>
    <p><small>Oct <var data-var='date'> 13</var>, <var data-var='time'>18:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 13</var>, <var data-var='time'>16:10:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Earlier today, some customers experienced intermittent failures when sending and receiving messages through the TOC webhook platform. 

The issue was triggered by a media transcoding error when processing certain MMS attachments, which caused message delivery and authentication to fail intermittently for affected accounts.

A fix has been identified, tested, and deployed. 

Media handling has also been improved to support a wider range of attachment formats going forward. 

Message delivery is fully restored — no action is required on your part. 

If you continue to see any issues, please contact support..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmqtukjwk007i2ip7sp0oaqjl</id>
  <published>2026-06-25T18:35:00.000+00:00</published>
  <updated>2026-06-25T18:35:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmqtukjwk007i2ip7sp0oaqjl"/>
  <title>Minor Incident - Routing Change</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> RingCentral, Zultys, TOPS Office Communicator (TOC)</p>
    <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>18:35:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  About 10 minutes ago we detected an internet routing change impacting traffic to our data centres. Some customers reported dropped calls, audio glitches, or phones ringing for several minutes. 

Traffic has already returned to normal and we are monitoring for any further issues..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmpwtqhoj01wupgjp13npziqw</id>
  <published>2026-06-02T15:45:00.000+00:00</published>
  <updated>2026-06-02T16:42:24.393+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmpwtqhoj01wupgjp13npziqw"/>
  <title>Outgoing Call Issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 57 minutes</p>
    <p><strong>Affected Components:</strong> TOPS Office Communicator (TOC), Outbound Call Routing (International), Zultys, Outbound Call Routing (North America)</p>
    <p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>16:42:24</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. We are continuing investigations with the upstream carrier into the root cause of the outage..</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>15:55:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are no longer seeing errors on outgoing calls..</p>
<p><small>Jun <var data-var='date'> 2</var>, <var data-var='time'>15:45:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are receiving errors from the upstream carrier when attempting to send outgoing calls. We are currently investigating..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmpvf6xc6007fp7qjzlr62z92</id>
  <published>2026-06-01T16:25:37.169+00:00</published>
  <updated>2026-06-01T22:08:08.487+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmpvf6xc6007fp7qjzlr62z92"/>
  <title>Minor Incident - SMS and Fax Failures</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 43 minutes</p>
    <p><strong>Affected Components:</strong> SMS/MMS, Advanced Faxing Services</p>
    <p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>22:08:08</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have not detected any further issues in the last few hours. This incident is now resolved. .</p>
<p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>19:11:40</var> GMT+0</small><br /><strong>Monitoring</strong> -
  All services are restored and working. We are monitoring for any further issues..</p>
<p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>18:22:16</var> GMT+0</small><br /><strong>Identified</strong> -
  We found an issue with one of our other servers that is causing both intermittent SMS and fax failures. We have identified the issue and we are working on a fix now. .</p>
<p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>16:47:38</var> GMT+0</small><br /><strong>Investigating</strong> -
  SMS service is down again. We are investigating further. .</p>
<p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>16:40:52</var> GMT+0</small><br /><strong>Monitoring</strong> -
  SMS functionality is restored. We are monitoring for any further issues. .</p>
<p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>16:25:37</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an incident involving SMS messaging failures..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmppveaho00mtp6udmn0kjee6</id>
  <published>2026-05-28T19:12:37.792+00:00</published>
  <updated>2026-05-28T23:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmppveaho00mtp6udmn0kjee6"/>
  <title>Minor Incident - Some Systems Unreachable</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> Transcription (Speech to Text), Outbound Call Routing (International), Toll-free Call Routing, RingCentral, Voicemail to Email, SMS/MMS, Zultys, Outbound Call Routing (North America), Inbound Call Routing, Text to Speech, Advanced Faxing Services, Advanced IVR/AA Services</p>
    <p><small>May <var data-var='date'> 28</var>, <var data-var='time'>23:30:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  We are still waiting for detailed analysis from data centre team. We will post it here when received. .</p>
<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>19:14:59</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Failover routing has kicked in and all systems are back online. We are still investigating the root cause..</p>
<p><small>May <var data-var='date'> 28</var>, <var data-var='time'>19:12:37</var> GMT+0</small><br /><strong>Investigating</strong> -
  We just detected a network incident impacting traffic at one of our data centres. A small number of customers are currently offline. We are investigating with high priority..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmponf23u08kup2gfkuewiqlv</id>
  <published>2026-05-27T22:41:34.568+00:00</published>
  <updated>2026-05-27T22:41:34.568+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmponf23u08kup2gfkuewiqlv"/>
  <title>Minor Incident - Fax Failures</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Advanced Faxing Services, Zultys</p>
    <p><small>May <var data-var='date'> 27</var>, <var data-var='time'>22:41:34</var> GMT+0</small><br /><strong>Resolved</strong> -
  We detected a large number of fax failures over the past 90 minutes. We found our fax server had encountered an error. The problem is now resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmpftb1120274nsv7fcathrt0</id>
  <published>2026-05-21T18:16:23.934+00:00</published>
  <updated>2026-05-21T20:51:27.929+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmpftb1120274nsv7fcathrt0"/>
  <title>SMS/MMS Deliverability</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 35 minutes</p>
    <p><strong>Affected Components:</strong> SMS/MMS</p>
    <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>20:51:27</var> GMT+0</small><br /><strong>Resolved</strong> -
  Messaging services are fully restored. The intermittent failures experienced between \~10:40 AM and \~11:22 AM PST, May 21st 2026, have cleared up. We confirm that stable message delivery has resumed. Continuous monitoring is in place..</p>
<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>20:51:26</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We are pleased to report that we are seeing a significant reduction in message failure instances from our carrier network. Our services are showing signs of stabilization, but full stability has not yet been confirmed across all channels.

Our technical team continues to monitor the connection status and works closely with the carrier for continuous improvements.

**Please continue to report any issues.** If you encounter any further message failures or unusual behavior, please notify us immediately and provide the unique Log ID generated by your system reference..</p>
<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>18:16:23</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently experiencing intermittent message failures. These disruptions appear to be related to a connectivity issue on our carrier&#039;s end. Our engineering team has escalated this incident immediately and is working closely with the provider for resolution.

We will post updates as soon as we receive more information. _Please note: If a message fails, our system will generate a Log ID that you can provide to support._.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmoiumzrv00qy5vlulzqgucd6</id>
  <published>2026-04-28T16:37:23.834+00:00</published>
  <updated>2026-04-28T23:08:15.937+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmoiumzrv00qy5vlulzqgucd6"/>
  <title>Minor Incident - No Audio on Some Calls</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> Zultys</p>
    <p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>23:08:15</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have not detected any further issues since 2:42pm. This incident is now resolved. .</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>21:42:13</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Telus reports they have fixed the problem and our tests are now successful. We will continue to monitor for any further problems..</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>20:42:20</var> GMT+0</small><br /><strong>Identified</strong> -
  Telus has now posted the incident on their website:  

&quot;We are experiencing 1-way audio and DTMF issues with inbound calls routing via TELUS&#039; Western Voice Core infrastructure. Our Network Integrity team is investigating the issue with priority.&quot;.</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>19:30:52</var> GMT+0</small><br /><strong>Identified</strong> -
  Telus has now identified the issue and repair teams are actively working to resolve it. .</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>18:32:59</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work with Telus on a fix for this Mobility network issue. .</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>17:09:44</var> GMT+0</small><br /><strong>Identified</strong> -
  Update: We have confirmed the issue is with Telus Mobility. Some inbound calls from Telus Mobility cellphones are not passing audio to our network. 

We are continuing to work with Telus on a fix..</p>
<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>16:37:23</var> GMT+0</small><br /><strong>Investigating</strong> -
  Problem: We are investigating reports of no audio on some inbound calls.

Evidence currently points to an issue on the Telus Mobility network.

We have escalated this issue to Telus..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmocf66zm00a38apum1svx3xw</id>
  <published>2026-04-24T04:37:43.067+00:00</published>
  <updated>2026-04-24T04:37:43.067+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmocf66zm00a38apum1svx3xw"/>
  <title>SMS Service</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> SMS/MMS</p>
    <p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>04:37:43</var> GMT+0</small><br /><strong>Resolved</strong> -
  We identified and resolved an issue with our SMS delivery pipeline earlier today. Enhanced safeguards and logging have been deployed. We are actively monitoring and no further impact is expected..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmnf58ztx01l2v4ysko86jymq</id>
  <published>2026-03-31T21:43:33.989+00:00</published>
  <updated>2026-03-31T21:43:33.989+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmnf58ztx01l2v4ysko86jymq"/>
  <title>Critical Backup Infrastructure Update</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> SMS/MMS</p>
    <p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>21:43:33</var> GMT+0</small><br /><strong>Resolved</strong> -
  An incident occurred today between approximately 10:00 AM and 12:00 PM PST that has now been fully resolved.

During this window, a critical change to our backup infrastructure caused intermittent connectivity issues for texting clients. Affected clients experienced delayed reconnections, which resulted in some users being temporarily unable to send or receive messages. Other users may have experienced degraded performance but maintained partial functionality.

The root cause has been identified and addressed. All SMS services are now operating normally. We will continue to monitor the situation to ensure stability.

We apologize for any disruption this may have caused..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cml9rj0xv01xdpy7kn1lszh33</id>
  <published>2026-02-05T18:01:11.891+00:00</published>
  <updated>2026-02-05T19:16:48.680+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cml9rj0xv01xdpy7kn1lszh33"/>
  <title>Telus Fiber - Kamloops</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 16 minutes</p>
    
    <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>19:16:48</var> GMT+0</small><br /><strong>Resolved</strong> -
  Telus is reporting the outage has been resolved..</p>
<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>18:01:11</var> GMT+0</small><br /><strong>Monitoring</strong> -
  There is an active Telus Fiber outage occurring in Kamloops affecting the internet of Telus Fiber customers.   
  
More information can be found on the Telus Service Status page: &lt;https://www.telus.com/en/bc/outages?linktype=ge-footer&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmhf9tsdo01fsroq534avnkda</id>
  <published>2025-10-31T19:40:00.000+00:00</published>
  <updated>2025-11-01T00:24:28.802+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmhf9tsdo01fsroq534avnkda"/>
  <title>Network Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> , Inbound Call Routing, Outbound Call Routing (International), Toll-free Call Routing, Zultys, Outbound Call Routing (North America), 
Voice Services →</p>
    <p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>00:24:28</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has now been resolved. We will continue to monitor throughout the weekend for any further problems. .</p>
<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>23:53:21</var> GMT+0</small><br /><strong>Identified</strong> -
  Data centre and Rogers engineers are still working on this.

We found a technical &quot;work-around&quot; to restore service to many customer systems throughout the afternoon. 

We are continuing to monitor this issue and will update when new information is available..</p>
<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>21:34:07</var> GMT+0</small><br /><strong>Identified</strong> -
  Data Centre engineers are working directly with Rogers to resolve the issue as soon as possible.

Impacted customers can use the Mobile ZAC application on their cellphone with wifi turned off to receive calls, if the cellphone provider is not Rogers..</p>
<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>20:43:20</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified an issue between Shaw/Rogers internet clients and one of our data centres. Engineers are working to resolve the issue as soon as possible. .</p>
<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>19:40:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an incident at one of our data centers causing a phone service disruption to a significant number of customers..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmgllcxwm05yf96zl5h131xh7</id>
  <published>2025-10-10T20:30:00.000+00:00</published>
  <updated>2025-10-11T01:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmgllcxwm05yf96zl5h131xh7"/>
  <title>Call Quality Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> Zultys</p>
    <p><small>Oct <var data-var='date'> 11</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our server issue has been fixed and all calls are operational. We are continuing to monitor the failing Telus server, but this should have no impact on service over the weekend. .</p>
<p><small>Oct <var data-var='date'> 11</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We found some &quot;stuck&quot; calls between the degraded Telus server and one of our servers. We rebooted our server to clear them. Our server did not boot up properly and some customers reported being unable to call out for about 10 minutes just before 5:00pm. We moved calls to our redundant server. .</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  More and more reports came in throughout the afternoon. We discovered a problem with one of Telus redundant call routing servers. We disabled this server and immediately noticed an improvement. .</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>20:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We began to receive some reports of call quality issues around 1:30pm. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmgl64buk023h7otnaigxxh28</id>
  <published>2025-10-10T17:50:00.000+00:00</published>
  <updated>2025-10-10T20:34:26.575+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmgl64buk023h7otnaigxxh28"/>
  <title>Network Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> Zultys</p>
    <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>20:34:26</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have detected no further issues. .</p>
<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>17:50:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  At 10:50am we detected one of our data centres went fully offline. It came back at 10:53, went down at 10:55, and came back at 10:58\. We believe there was a network problem that caused a hard failover scenario. We are monitoring for further issues and have opened a case with our data centre support. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmfmsjsfq000kt1lb2c88k1ii</id>
  <published>2025-09-16T16:30:00.000+00:00</published>
  <updated>2025-09-16T17:33:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmfmsjsfq000kt1lb2c88k1ii"/>
  <title>Inbound calls - endless ringing/failure to establish</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 3 minutes</p>
    <p><strong>Affected Components:</strong> Zultys, Inbound Call Routing</p>
    <p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>17:33:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.

Problem: Customers reported inbound and outbound calls ringing forever, failing to connect, or getting a busy signal.

Cause: This outage was caused by a software glitch in one of our maintenance tools that created a cascading failure beginning at approximately 9:30am. Once we determined the cause we were able to resolve it at 9:48am.

Corrective Action: we will be patching and testing the maintenance tool offline before putting it back into service..</p>
<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>16:48:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We believe the issue has been resolved at this time but will continue to monitor. Please report any incoming call issues to our \[dispatch@topsoffice.ca\](mailto:dispatch@topsoffice.ca) email..</p>
<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We&#039;ve detected a widespread problem with call routing affecting incoming calls. We believe the issue has been resolved at this time but will continue to monitor. Please report any incoming call issues to our \[dispatch@topsoffice.ca\](mailto:dispatch@topsoffice.ca) email..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmebv7tdq000hcop3qkbgah5s</id>
  <published>2025-08-14T20:42:02.972+00:00</published>
  <updated>2025-08-14T20:56:33.944+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmebv7tdq000hcop3qkbgah5s"/>
  <title>Minor Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Call Routing, Outbound Call Routing (North America), Outbound Call Routing (International), , Toll-free Call Routing, Zultys, 
Voice Services →</p>
    <p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>20:56:33</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>20:42:02</var> GMT+0</small><br /><strong>Investigating</strong> -
  Problem: Our automated monitoring has detected a network issue affecting one of our three data centres. The impact is limited, and only a small portion of customers are affected. The issue began at approximately 12:20 PM PST and is ongoing. We are actively investigating to determine the cause and will provide further updates as more information becomes available..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cmdp1slb40035y1v4qab5wem5</id>
  <published>2025-07-29T21:27:28.138+00:00</published>
  <updated>2025-07-29T23:23:43.724+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cmdp1slb40035y1v4qab5wem5"/>
  <title>Minor Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 56 minutes</p>
    
    <p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>23:23:43</var> GMT+0</small><br /><strong>Resolved</strong> -
  Status: resolved

Update: We have confirmation the problem was caused by one of the internet providers to the data centre. We do not expect any further issues. .</p>
<p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>21:27:28</var> GMT+0</small><br /><strong>Investigating</strong> -
  Status: investigating 

Problem: Our automated monitoring detected two brief network outages at one of our data centres. The first occurred at 13:52 PDT and lasted for \~2 minutes. The second occurred at 14:02 PDT and lasted \~2 minutes. The network is operational now and no further issues have been detected. We are investigating further to determine the cause. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Maintenance/cmbharytd002aqaoj08lty8zo</id>
  <published>2025-06-05T02:00:00.000+00:00</published>
  <updated>2025-06-05T04:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/maintenance/cmbharytd002aqaoj08lty8zo"/>
  <title>Scheduled Software Updates</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Zultys</p>
    <p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>02:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 5</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be performing scheduled software updates during the following times:

**June 3rd - 7:00pm-9:00pm**

**June 4th - 7:00pm-9:00pm**

If you received an email on May 23rd, your phones and phone applications may go offline for up to 30 minutes during one of these windows..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Maintenance/cmbhapu0a00144q8ko5840w74</id>
  <published>2025-06-04T02:00:00.000+00:00</published>
  <updated>2025-06-04T04:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/maintenance/cmbhapu0a00144q8ko5840w74"/>
  <title>Scheduled Software Updates</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Zultys</p>
    <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>02:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be performing scheduled software updates during the following times:

**June 3rd - 7:00pm-9:00pm**

**June 4th - 7:00pm-9:00pm**

If you received an email on May 23rd, your phones and phone applications may go offline for up to 30 minutes during one of these windows. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cm9spyz2v004v24y3p05woucb</id>
  <published>2025-04-22T16:15:00.000+00:00</published>
  <updated>2025-04-22T18:45:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cm9spyz2v004v24y3p05woucb"/>
  <title>Minor Incident - Dropped Calls</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> Toll-free Call Routing, Outbound Call Routing (International), Zultys, Inbound Call Routing, Outbound Call Routing (North America)</p>
    <p><small>Apr <var data-var='date'> 22</var>, <var data-var='time'>18:45:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Update: We have monitored traffic flows since we performed the rollback and confirmed the problem is resolved..</p>
<p><small>Apr <var data-var='date'> 22</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Update: our software vendor identified a bug that was causing the high CPU usage and advised us to roll the software back. We completed the software rollback and initial observations appear the problem is resolved. .</p>
<p><small>Apr <var data-var='date'> 22</var>, <var data-var='time'>16:35:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Update: We have identified high CPU usage on one of our core routing servers. We are rerouting traffic through our redundant server now. .</p>
<p><small>Apr <var data-var='date'> 22</var>, <var data-var='time'>16:15:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Problem: several customers are reporting dropped calls or loss of audio during a call.

Scope: We think the problem is only affecting a small portion of customers - under 10%.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cm9lsg6hv001eft9anvxtvhm4</id>
  <published>2025-04-17T19:17:00.000+00:00</published>
  <updated>2025-04-17T21:26:07.358+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cm9lsg6hv001eft9anvxtvhm4"/>
  <title>Minor Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 9 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Call Routing, Toll-free Call Routing, Outbound Call Routing (International), Outbound Call Routing (North America)</p>
    <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>21:26:07</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>19:17:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Status: identified

Problem: We had a minor problem with a virtual machine host in our data center that caused 9 systems to go offline, move to a different machine, and reboot. This outage lasted about 10 minutes and all customer systems are fully functional now.

One of our core routing servers was among the 9 systems and has been corrupted. We are rebuilding it. This may cause some faxes to fail and some calls may take longer to connect. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Maintenance/cm8jbsawa006sngx4di46pbdh</id>
  <published>2025-03-22T10:00:00.000+00:00</published>
  <updated>2025-03-22T12:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/maintenance/cm8jbsawa006sngx4di46pbdh"/>
  <title>Emergency Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Inbound Call Routing, Toll-free Call Routing, Zultys, Outbound Call Routing (International), Outbound Call Routing (North America)</p>
    <p><small>Mar <var data-var='date'> 22</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Mar <var data-var='date'> 22</var>, <var data-var='time'>10:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Mar <var data-var='date'> 22</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Data Center support staff will be performing emergency maintenance between the hours of 3:00am-5:00am Saturday March 22nd. During this time, some customers may experience service interruptions. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cm8iuncym009udmzav1g5ry3m</id>
  <published>2025-03-21T14:02:18.847+00:00</published>
  <updated>2025-03-24T18:15:33.851+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cm8iuncym009udmzav1g5ry3m"/>
  <title>Medium Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 4 hours and 13 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Call Routing, Toll-free Call Routing, Zultys, Outbound Call Routing (International), Outbound Call Routing (North America)</p>
    <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>18:15:33</var> GMT+0</small><br /><strong>Resolved</strong> -
  Update: We have received confirmation from our data center support that network maintenance performed by Rogers early in the morning on Saturday has resolved this issue. Our network diagnostics confirm increased stability since these changes. .</p>
<p><small>Mar <var data-var='date'> 21</var>, <var data-var='time'>14:11:31</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Update: Our systems appear to be fully operational. We are doing further diagnosis and waiting for more information from support teams about the cause of the problem..</p>
<p><small>Mar <var data-var='date'> 21</var>, <var data-var='time'>14:02:18</var> GMT+0</small><br /><strong>Identified</strong> -
  Status: identified

Problem: Automated network monitoring has detected problems with our systems overnight. We believe this may cause phones and apps may be unable to connect to the system, or experience phone calls with no audio

Scope: we believe this is impacting a subset of customers in one of our data centers

Cause: We think this is related to the problems we had on Monday night. 

Update: We are working with support engineers at Rogers and Telus to resolve the issue as quickly as possible.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cm8dtrxku0003glllq4wmvfm1</id>
  <published>2025-03-18T00:34:00.000+00:00</published>
  <updated>2025-03-24T18:15:04.586+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cm8dtrxku0003glllq4wmvfm1"/>
  <title>Medium Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 17 hours and 41 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Call Routing, Toll-free Call Routing, Zultys, Outbound Call Routing (International), Outbound Call Routing (North America)</p>
    <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>18:15:04</var> GMT+0</small><br /><strong>Resolved</strong> -
  Update: We have received confirmation from our data center support that network maintenance performed by Rogers early in the morning on Saturday has resolved this issue. Our network diagnostics confirm increased stability since these changes. .</p>
<p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>14:54:34</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Status: monitoring

Scope: we believe this impacted all customers in one of our data centers that have Telus internet on their premise - estimated about 20% of customers

Cause: there was a core networking &quot;BGP&quot; problem between Rogers and Telus. The source of this issue was identified to be a failing router in Rogers core network

Update: Rogers has implemented a fix and we are monitoring all networks for any further issues.</p>
<p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>02:52:13</var> GMT+0</small><br /><strong>Identified</strong> -
  Status: identified

Scope: we believe this is impacting 30% of our customers 

Problem: customers report intermittent connection issues with phones and apps, causing no audio on phone calls and unable to call out for 2-5 minute intervals

Cause: there is a core networking &quot;BGP&quot; problem between Rogers and Telus 

Update: we have opened tickets with all involved parties and made them the highest priority.</p>
<p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>00:34:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Status: investigating 

Scope: unknown

Problem: we are currently investigating a problem with one-way audio and login failures impacting several customers.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cm84onz5m00bm1pkvaa8o8kip</id>
  <published>2025-03-11T16:06:02.111+00:00</published>
  <updated>2025-03-11T18:24:33.728+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cm84onz5m00bm1pkvaa8o8kip"/>
  <title>Minor Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 19 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Call Routing, Toll-free Call Routing, Voicemail to Email, RingCentral, Transcription (Speech to Text), Text to Speech, Zultys, Outbound Call Routing (International), Outbound Call Routing (North America), Advanced IVR/AA Services</p>
    <p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>18:24:33</var> GMT+0</small><br /><strong>Resolved</strong> -
  Status: resolved

Update: the server has been rebuilt and is now processing calls

Cause: the cause appears to be an issue with one of the server hosts in our data center. All machines were automatically migrated to a redundant host, however this migration caused the call routing server to crash.</p>
<p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>17:11:38</var> GMT+0</small><br /><strong>Identified</strong> -
  Status: identified 

Scope: some outbound faxes may fail; some customers may experience congestion on inbound or outbound calls

Problem: one of our call routing servers crashed and all traffic is currently being routed through our redundant server only

Update: we are rebuilding the server now.</p>
<p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>16:06:02</var> GMT+0</small><br /><strong>Investigating</strong> -
  Status: investigating 

Scope: some outbound faxes may fail; some customer systems may have experienced a brief service disruption

Problem: investigating.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Maintenance/cm6e26evb000castffeje8z79</id>
  <published>2025-01-26T20:00:00.000+00:00</published>
  <updated>2025-01-26T23:17:12.442+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/maintenance/cm6e26evb000castffeje8z79"/>
  <title>Low Risk Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> Zultys</p>
    <p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>23:17:12</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance completed.</p>
<p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>21:25:52</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing maintenance, but no further impact to customers is expected. .</p>
<p><small>Jan <var data-var='date'> 26</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are currently performing maintenance activities.

No impact is expected for most customers. A small number of customers may experience momentary app and/or phone call disconnects. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cm5h7i3o50034109bo1sjkal1</id>
  <published>2025-01-03T19:31:00.000+00:00</published>
  <updated>2025-01-03T21:31:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cm5h7i3o50034109bo1sjkal1"/>
  <title>Minor Incident - One-way audio</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 26 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Call Routing, Toll-free Call Routing, Zultys, Outbound Call Routing (International), Outbound Call Routing (North America)</p>
    <p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>21:31:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Status: Resolved

Update: We detected network connectivity issues between our data centers. We analyzed the impact and determined it to be no or very low impact to 99% of customers. We opened support tickets with appropriate channels. The problem is now resolved..</p>
<p><small>Jan <var data-var='date'> 3</var>, <var data-var='time'>19:31:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Status: investigating

Scope: minor

Problem: diagnostic tools have detected networking issues between our data centers; a few customers have reported one-way audio on some calls..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cm4bhcr4k003zhs99yawp3fir</id>
  <published>2024-12-05T15:00:00.000+00:00</published>
  <updated>2024-12-05T17:28:05.093+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cm4bhcr4k003zhs99yawp3fir"/>
  <title>Minor Incident - intermittent call failures</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 51 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Call Routing, Toll-free Call Routing, Zultys, Outbound Call Routing (International), Outbound Call Routing (North America)</p>
    <p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>17:28:05</var> GMT+0</small><br /><strong>Resolved</strong> -
  Update: The server has been repaired and all traffic is flowing normally

This incident is now resolved.</p>
<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Problem: Our monitoring systems detected a problem with one of our core servers early this morning

Status: Problem has been identified and repair is in progress

Impact: Estimated 10% of customers will experience intermittent call failures or dropped calls until resolved .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:tops-office.instatus.com,2005:Incident/cm2an6yyp000511ot9mfnyja5</id>
  <published>2024-10-15T15:43:00.000+00:00</published>
  <updated>2024-10-15T17:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://tops-office.instatus.com/incident/cm2an6yyp000511ot9mfnyja5"/>
  <title>Medium Incident - High Latency</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 17 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Call Routing, Toll-free Call Routing, Zultys, Outbound Call Routing (International), Outbound Call Routing (North America)</p>
    <p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Update: we are confident the problem is now resolved.

Cause: the root cause is still under investigation..</p>
<p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>16:34:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Update: we have implemented a manual failover to our redundant firewall. We are monitoring the issue but initial results appear the problem is resolved..</p>
<p><small>Oct <var data-var='date'> 15</var>, <var data-var='time'>15:43:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Problem: customers are reporting choppy audio on phone calls, or phones continuing to ring and unable to be answered

Status: investigating

Impact: estimated about 30% of customer base

Cause: diagnostic tools are reporting very high latency between our monitoring points and one of our data centers. We are investigating..</p>

        ]]>
  </content>
</entry>

</feed>