tag:amscomp.statuspage.io,2005:/historyamscomp Status - Incident History2024-03-28T06:09:09-07:00amscomptag:amscomp.statuspage.io,2005:Incident/194412492024-03-22T13:18:37-07:002024-03-22T13:18:37-07:00Origination/Termination Issues: Various<p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>13:18</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Dec <var data-var='date'>14</var>, <var data-var='time'>12:08</var> PST</small><br><strong>Monitoring</strong> - Service provider reports that services are stable as of 14:07 ET, and they are still investigating further.</p><p><small>Dec <var data-var='date'>14</var>, <var data-var='time'>11:12</var> PST</small><br><strong>Investigating</strong> - We are investigating reports of Origination issues in Various Regions<br /><br />Please stand by for updates. We thank you for your patience and apologize for the inconvenience.</p>tag:amscomp.statuspage.io,2005:Incident/178160492023-07-21T09:24:54-07:002023-07-21T09:24:54-07:00Outbound COUNTERPOINT email issues<p><small>Jul <var data-var='date'>21</var>, <var data-var='time'>09:24</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>08:16</var> PDT</small><br><strong>Update</strong> - Monitoring over the past day show that emails to hotmail addresses are also now flowing properly, with no reported bounce-back emails since early yesterday morning.</p><p><small>Jul <var data-var='date'>11</var>, <var data-var='time'>15:53</var> PDT</small><br><strong>Update</strong> - There have been a couple of additional reports of hotmail addresses bouncing, but these seem to have been intermittent, and a subsequent resend of the invoice proved to go through without issue.<br /><br />We are still monitoring the services.</p><p><small>Jul <var data-var='date'>10</var>, <var data-var='time'>14:49</var> PDT</small><br><strong>Monitoring</strong> - We have been notified that a fix is in place, and that outbound emails are being delivered to GMail inboxes without issue.<br /><br />During a number of tests on our end, we can confirm successful receipt of COUNTERPOINT system emails.<br /><br />We will continue monitor emails and to work with the service provider as needed</p><p><small>Jul <var data-var='date'>10</var>, <var data-var='time'>10:53</var> PDT</small><br><strong>Update</strong> - Update from our email service provider:<br /><br />"We continue to develop, test and deploy improvements to improve the delivery rate to Gmail and Google WorkSpace users’ inboxes.<br /> <br />We continue to work with Google to help solve this and with Microsoft on the root cause of this issue.<br /> <br />As mentioned in our last update, Google Tech Support has recently identified a vulnerability in Microsoft SPF checking, which has allowed for a new type of spam and phishing attack. It is important to note that this affects the delivery of emails to both Google Workspace and Gmail platforms. Any downstream processing services associated with these platforms automatically become tagged and implicated. Our team is actively working to address this issue and mitigate its impact on our customers. We will provide further updates as we make progress in resolving this matter.<br />Kind Regards"</p><p><small>Jul <var data-var='date'>10</var>, <var data-var='time'>10:00</var> PDT</small><br><strong>Update</strong> - The issue has been identified by our Email service provider:<br /><br />"Spammers managed to leverage the Office 365 developer network as a source to create a spam wave delivered via multiple downstream providers to attack Gmail accounts over the last few days. Some of these emails were passed through VIPRE systems to send out targeted emails towards Gmail addresses. Some of these emails passed through the VIPRE Email Security solution, resulting in a significant increase in traffic which initially impacted mail processing times. Consequently, Gmail also implemented defensive measures, classifying a number of these sources as spam to ensure they protected their users.<br /> <br />Google Tech Support has identified a vulnerability in Microsoft SPF checking, which allowed a new type of spam and phishing attack. Unfortunately, any downstream processing services that are in that email get automatically tagged and implicated, even though the issue is an SPF check weakness being exploited on the Office 365 platform."</p><p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>13:00</var> PDT</small><br><strong>Identified</strong> - A fix has been implemented for Microsoft addresses, which should now be receiving emails without issue. <br /><br />Gmail addresses are still assigning emails to SPAM</p><p><small>Jul <var data-var='date'> 5</var>, <var data-var='time'>10:19</var> PDT</small><br><strong>Investigating</strong> - We have received reports of COUNTERPOINT system generated emails that are sent out through eforms being bounced back from Microsoft (outlook.com, hotmail.com, live.ca) addresses and being classified as SPAM in GMail accounts.</p>tag:amscomp.statuspage.io,2005:Incident/168554132023-04-19T13:21:32-07:002023-04-19T13:21:32-07:00Call Audio Problems<p><small>Apr <var data-var='date'>19</var>, <var data-var='time'>13:21</var> PDT</small><br><strong>Resolved</strong> - This appears to have been resolved and there have been no additional reports of call problems over the past 24 hours.</p><p><small>Apr <var data-var='date'>18</var>, <var data-var='time'>12:07</var> PDT</small><br><strong>Monitoring</strong> - As of 10:30 AM (PT) we have begun seeing successful incoming calls from Shaw customers. We have processed test calls to confirm and are continuing to monitor</p><p><small>Apr <var data-var='date'>14</var>, <var data-var='time'>09:57</var> PDT</small><br><strong>Identified</strong> - We have identified an issue with the interconnect between Shaw VoIP and our carrier. This problem is limited to incoming calls from Shaw voice users in the Abbotsford/Mission/Chilliwack area.<br /><br />We are working with our carrier to connect with Shaw and try to resolve the problem.</p><p><small>Apr <var data-var='date'>13</var>, <var data-var='time'>12:42</var> PDT</small><br><strong>Investigating</strong> - We have received numerous reports of intermittent inbound call audio problems in the Abbotsford/Mission/Chilliwack region.<br /><br />We are currently working with our service provider to determine the cause</p>tag:amscomp.statuspage.io,2005:Incident/159364412023-01-25T16:56:47-08:002023-01-25T16:56:47-08:00Inbound Calling Issues<p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>16:56</var> PST</small><br><strong>Resolved</strong> - The transit provider has indicated the issue is now resolved. Please test any numbers that had problems and let us know via support@amscomp.com if any issues persist</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>15:15</var> PST</small><br><strong>Update</strong> - Our service provider has identified the common transit carrier through which they are receiving call completion issue reports and they are investigating on their side. We will update you shortly once we have an update.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>14:54</var> PST</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>14:54</var> PST</small><br><strong>Identified</strong> - Service provider has identified a call completion issue from some of their carriers and is currently working on a solution.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>14:40</var> PST</small><br><strong>Investigating</strong> - We are currently investigating reports from multiple customers of inbound call failures.<br /><br />We have reached out to the service provider and will provide updates as they are received.</p>tag:amscomp.statuspage.io,2005:Incident/127690082022-11-09T15:27:04-08:002022-11-14T15:28:54-08:00DNS Service Issues<p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>15:27</var> PST</small><br><strong>Resolved</strong> - After monitoring the issue , we no longer see any dropped DNS requests</p><p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>14:15</var> PST</small><br><strong>Update</strong> - We are continuing to monitor this issue.</p><p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>14:06</var> PST</small><br><strong>Update</strong> - Our DNS provider has told us that the issue has been resolved</p><p><small>Nov <var data-var='date'> 9</var>, <var data-var='time'>12:06</var> PST</small><br><strong>Investigating</strong> - Our domain service provider is having DNS service issues. They have informed us that, since it is affecting all customers, it is their highest priority</p>tag:amscomp.statuspage.io,2005:Incident/108927492022-08-31T09:13:45-07:002022-08-31T09:13:45-07:00Network issue investigating<p><small>Aug <var data-var='date'>31</var>, <var data-var='time'>09:13</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'>23</var>, <var data-var='time'>11:37</var> PDT</small><br><strong>Monitoring</strong> - Service provider reports that all services have been restored and they are monitoring for stability.</p><p><small>Aug <var data-var='date'>23</var>, <var data-var='time'>10:29</var> PDT</small><br><strong>Update</strong> - Service provider indicates that they have managed to restore some services,</p><p><small>Aug <var data-var='date'>23</var>, <var data-var='time'>09:57</var> PDT</small><br><strong>Investigating</strong> - Service provider is currently experiencing a network issue. They have network engineers investigating and will provide updates as they become available.</p>tag:amscomp.statuspage.io,2005:Incident/106423362022-07-20T09:45:16-07:002022-07-20T09:45:16-07:00Investigating partial outage in Hamilton Region<p><small>Jul <var data-var='date'>20</var>, <var data-var='time'>09:45</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>23:09</var> PDT</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>19:15</var> PDT</small><br><strong>Monitoring</strong> - We are seeing call flow at this time, a cause has not been provided at this time, we will update this notice once we hear from the ILEC regarding the cause of the outage.</p><p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>12:47</var> PDT</small><br><strong>Investigating</strong> - We have engaged the ILEC to investigate an outage in the Hamilton ON region.</p>tag:amscomp.statuspage.io,2005:Incident/106274932022-07-18T13:52:36-07:002022-07-18T13:52:36-07:00Hosted services connectivity problems<p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>13:52</var> PDT</small><br><strong>Resolved</strong> - Technician arrived on site and discovered a faulty piece of hardware. This item was replaced and tested upon replacement to confirm that service has been fully restored.</p><p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>13:17</var> PDT</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>11:59</var> PDT</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>11:57</var> PDT</small><br><strong>Identified</strong> - We have identified an issue with one of our managed fiber circuits. We have spoken with Telus to troubleshoot the issue, but they have determined that a technician will need to be dispatched. <br /><br />We are currently waiting for the technician to arrive.</p><p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>10:37</var> PDT</small><br><strong>Investigating</strong> - We are currently investigating reports of connectivity failures on AMS hosted services.</p>tag:amscomp.statuspage.io,2005:Incident/105674272022-07-14T06:15:45-07:002022-07-14T06:15:45-07:00Internal Network Upgrade<p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>06:15</var> PDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jul <var data-var='date'>14</var>, <var data-var='time'>06:01</var> PDT</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jul <var data-var='date'>13</var>, <var data-var='time'>09:24</var> PDT</small><br><strong>Scheduled</strong> - As a follow-up to last weekend’s hosted system network and power infrastructure upgrades, we will be completing the upgrade of our internal data network to fibre optics.<br /><br />Details of Changes<br /><br />In order to provide our hosted customers with the most performant data network connections, we will be upgrading our internal hosted services network to fibre optics. As a result, we will bringing our network down momentarily to complete this update.<br /><br />Affected Systems<br /><br />Hosted COUNTERPOINTautoecat.comjdispatch.cacounterpoint.cloud<br /><br />Timeline<br /><br />Thursday July 13, beginning at 6:00am and taking approximately 15 minutes.<br /><br />What to do if you encounter issues<br /><br />We are making every effort to keep any working-hour downtime to zero. However, during this maintenance window, the affected systems will be unavailable, and running COUNTERPOINT connections will be disconnected. We apologize for any inconvenience this may cause. If you encounter issues outside the maintenance window, and outside regular hours, please contact our support team via our after hours number.<br /><br />If you have any questions or comments regarding this maintenance please feel free to contact us at our support email, support@amscomp.com</p>tag:amscomp.statuspage.io,2005:Incident/105039342022-07-10T08:01:49-07:002022-07-10T08:01:49-07:00Network & Infrastructure Upgrades<p><small>Jul <var data-var='date'>10</var>, <var data-var='time'>08:01</var> PDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jul <var data-var='date'>10</var>, <var data-var='time'>05:01</var> PDT</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>09:11</var> PDT</small><br><strong>Scheduled</strong> - A maintenance window has been scheduled to perform network and infrastructure upgrades at our facility. These upgrades are a part of our on-going efforts to provide our hosted service customers with a resilient network. <br /><br />Timeline - Sunday July 10, beginning at 5:00am and takin approximately 2 hours.<br /><br />We are making every effort to keep any working hour downtime at zero. During this maintenance window, hosted COUNTERPOINT and PBX systems will be unavailable. We apologize for any inconvenience this may cause. <br /><br />If you have any questions or comments regarding this migration please feel free to contact us at our support email, support@amscomp.com<br /><br />Thank you for your continued support,<br /><br />Your AMS Support Team</p>tag:amscomp.statuspage.io,2005:Incident/98806202022-04-29T10:10:00-07:002022-05-09T09:21:36-07:00Investigating upstream issue<p><small>Apr <var data-var='date'>29</var>, <var data-var='time'>10:10</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Apr <var data-var='date'>29</var>, <var data-var='time'>10:05</var> PDT</small><br><strong>Update</strong> - Call flow appears to be normal now after observing it for some time, we are awaiting a response from the upstream carrier in question.</p><p><small>Apr <var data-var='date'>29</var>, <var data-var='time'>08:57</var> PDT</small><br><strong>Investigating</strong> - We are currently investigating an issue with an upstream carrier who may be experiencing issues. Please stand by for updates.</p>tag:amscomp.statuspage.io,2005:Incident/98499162022-04-25T12:26:35-07:002022-04-25T12:27:36-07:00Reports of inbound issues<p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>12:26</var> PDT</small><br><strong>Resolved</strong> - This incident is being marked resolved now as the carrier has been monitoring the service for a number of hours with no further reports of problems.</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>08:02</var> PDT</small><br><strong>Monitoring</strong> - The carrier has completed the required fix, are monitoring the network for behaviour and will provide an RFO after all investigations are complete.</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>07:43</var> PDT</small><br><strong>Update</strong> - Carrier currently has an ETR of 11 AM ET, 8 AM PT. please stand by for further updates.</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>07:41</var> PDT</small><br><strong>Identified</strong> - The carrier has identified the root cause of the issue and is currently working on a fix. We will continue to monitor for changes in call status.</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>07:37</var> PDT</small><br><strong>Update</strong> - We are seeing some calls flowing in, but are still awaiting further updates from the carrier and apologize for the continued outage.</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>07:00</var> PDT</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>06:47</var> PDT</small><br><strong>Update</strong> - The carrier is continuing to investigate and has enlisted one of their vendors to identify the issue.</p><p><small>Apr <var data-var='date'>25</var>, <var data-var='time'>05:59</var> PDT</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:amscomp.statuspage.io,2005:Incident/97847942022-04-14T14:52:50-07:002022-04-14T15:20:41-07:00Partial Connectivity Issue Upstream<p><small>Apr <var data-var='date'>14</var>, <var data-var='time'>14:52</var> PDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Apr <var data-var='date'>14</var>, <var data-var='time'>14:52</var> PDT</small><br><strong>Update</strong> - The issue appears to have been rectified. The carrier is still investigating for more details about the source of the issue.</p><p><small>Apr <var data-var='date'>14</var>, <var data-var='time'>13:11</var> PDT</small><br><strong>Update</strong> - Our primary carrier has narrowed down the outage to a specific carrier and are in contact with them to get updates.</p><p><small>Apr <var data-var='date'>14</var>, <var data-var='time'>12:48</var> PDT</small><br><strong>Investigating</strong> - We are currently investigating a possible upstream network outage.<br />More updates to come as we receive information.</p>tag:amscomp.statuspage.io,2005:Incident/96525912022-03-28T19:15:00-07:002022-03-29T08:53:33-07:00CLEC outage affecting call routing in Quebec<p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>19:15</var> PDT</small><br><strong>Resolved</strong> - We have confirmation that all services are back online as of 19:00 ET</p><p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>15:13</var> PDT</small><br><strong>Identified</strong> - An ETR of 2 hours has been provided as of 16:55 GMT-4 (EASTERN TIME)</p><p><small>Mar <var data-var='date'>28</var>, <var data-var='time'>15:12</var> PDT</small><br><strong>Investigating</strong> - We have been advised by a large CLEC in Quebec that they are experiencing a major outage. As a result we are seeing call routing problems. We will update you with details as they become available.</p>tag:amscomp.statuspage.io,2005:Incident/95564592022-03-18T08:41:45-07:002022-03-18T08:41:45-07:00Partial Outage in the Hamilton, ON Region<p><small>Mar <var data-var='date'>18</var>, <var data-var='time'>08:41</var> PDT</small><br><strong>Resolved</strong> - The ILEC has confirmed the circuits are online and stable as of March 17 2022 17:00-17:30 local time in Hamilton Ontario.<br />The cause was a water leak at the Hamilton Hunter - Central Office which disabled a Alcatel 1633 transport equipment causing outages across multiple carriers and lines.</p><p><small>Mar <var data-var='date'>17</var>, <var data-var='time'>04:22</var> PDT</small><br><strong>Update</strong> - Update From Carrier:<br /><br />We are presently in the process of carrying out some emergency maintenance on a part of our transport facilities equipment. This has affect T1s of a few of our customers. Our teams are working incessantly to restore normal service as soon as possible.</p><p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>12:48</var> PDT</small><br><strong>Identified</strong> - We requested an update from the ILEC and they have indicated work is underway to repair the transport equipment.</p><p><small>Mar <var data-var='date'>16</var>, <var data-var='time'>05:54</var> PDT</small><br><strong>Investigating</strong> - Our carrier is with the local ILEC on a transport issue causing a partial service outage in Hamilton Ontario. The ILEC is investigating the issue and implementing a repair. We will provide an update as soon as new information becomes available.</p>tag:amscomp.statuspage.io,2005:Incident/92837482022-02-10T08:56:00-08:002022-02-10T08:56:00-08:00Carrier Partner Outage<p><small>Feb <var data-var='date'>10</var>, <var data-var='time'>08:56</var> PST</small><br><strong>Resolved</strong> - Our vendor found an issue with the software, Vendor has completed a roll back. Currently they are collecting all necessary logs to find root cause of the issue.</p><p><small>Feb <var data-var='date'>10</var>, <var data-var='time'>07:07</var> PST</small><br><strong>Identified</strong> - We have been informed that a large carrier partner/CLEC is experiencing an outage. As a result of this, calls destined to their network will fail. Calls originating from their network will also fail.</p>tag:amscomp.statuspage.io,2005:Incident/90750012022-01-13T13:00:01-08:002022-01-13T13:00:01-08:00Loss of Connectivity to Fredericton, New Brunswick<p><small>Jan <var data-var='date'>13</var>, <var data-var='time'>13:00</var> PST</small><br><strong>Resolved</strong> - Connectivity is now restored to Fredericton, New Brunswick. All impacted services are back to normal operation.<br /><br />The issue was caused by a power outage at the Datacenter in Fredericton, which was eventually resolved by our colo partner.</p><p><small>Jan <var data-var='date'>13</var>, <var data-var='time'>12:59</var> PST</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Jan <var data-var='date'>13</var>, <var data-var='time'>10:03</var> PST</small><br><strong>Identified</strong> - The carrier's colo partners have dispatched technicians to fix the outage.<br /><br />They unfortunately do not have an accurate ETR yet, but be rest assured that the issue would be fixed within the shortest possible time.</p><p><small>Jan <var data-var='date'>13</var>, <var data-var='time'>07:30</var> PST</small><br><strong>Investigating</strong> - One of our carriers is currently experiencing loss of connectivity to their network elements in Federicton, New Brunswick. This is currently impacting calls to/from PSTN in New Brunswick.<br /><br />Unfortunately, they do not have an accurate Estimated Time of Recovery yet, but investigations are ongoing and they hope to resolve the issue within the shortest possible time.</p>tag:amscomp.statuspage.io,2005:Incident/90649972022-01-13T03:00:30-08:002022-01-13T03:00:30-08:00Network Maintenance<p><small>Jan <var data-var='date'>13</var>, <var data-var='time'>03:00</var> PST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>13</var>, <var data-var='time'>02:01</var> PST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>09:06</var> PST</small><br><strong>Scheduled</strong> - As part of one of our Carrier's on-going efforts to provide customers access to a resilient telecom network; they are making some changes to their SIP network. Part of the work involved requires a software update to their public facing session border controller (SBC) cluster.<br /><br />Details of Changes<br /><br />Beginning January 13, 2022 [05:00 ET/UTC-5] the carrier will initiate the software update working alongside engineers from their SBC vendor.<br /><br />The software update is expected to last 40-60 minutes.<br /><br />At this point the backup cluster will be updated. This process does not have any effect on network operation for customers. Once our backup cluster is updated, the entire system will be synced back to operate in a geo-redundant SBC cluster pair.<br /><br />Benefits achieved<br /><br />This change will allow the carrier:<br /><br />- Better control of infrastructure management<br />- Provide new features to end users<br />- Create a pathway for further service enhancements in the future<br />- Secure their network with enhanced security features provided by the new software update<br />- Faster processing for call records and diagnostic tools</p>tag:amscomp.statuspage.io,2005:Incident/90649492022-01-12T04:45:31-08:002022-01-12T09:23:25-08:00Toronto Inbound Outage<p><small>Jan <var data-var='date'>12</var>, <var data-var='time'>04:45</var> PST</small><br><strong>Resolved</strong> - We are considering this issue closed at this point. The ILEC has restored their host switches serving the Toronto rate centre.</p><p><small>Jan <var data-var='date'>11</var>, <var data-var='time'>21:30</var> PST</small><br><strong>Update</strong> - The ILEC has indicated to us that they are working on a solution to this issue which is related to water damaged equipment.</p><p><small>Jan <var data-var='date'>11</var>, <var data-var='time'>18:45</var> PST</small><br><strong>Identified</strong> - One of our carriers is currently experiencing a partial inbound outage in the Toronto region.</p>tag:amscomp.statuspage.io,2005:Incident/90313262022-01-07T23:36:57-08:002022-01-07T23:37:36-08:00autoecat update<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>23:36</var> PST</small><br><strong>Completed</strong> - Update is complete and new functionality is live. More details on the update can be found in the autoecat release notes.<br /><br />https://docs.amscomp.com/books/autoecatcom/page/january-2022-release-20220107</p><p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>23:30</var> PST</small><br><strong>Verifying</strong> - Currently verifying site functionality to confirm no critical errors are occurring</p><p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>23:07</var> PST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>23:00</var> PST</small><br><strong>Scheduled</strong> - We will be processing a minor update during this time. There is no downtime expected as a result.</p>tag:amscomp.statuspage.io,2005:Incident/89156472021-12-22T21:47:31-08:002021-12-22T21:47:31-08:00autoecat update<p><small>Dec <var data-var='date'>22</var>, <var data-var='time'>21:47</var> PST</small><br><strong>Completed</strong> - Updates and QA testing has now been completed. Thank you for your patience, and we apologize for any inconvenience you may have experienced</p><p><small>Dec <var data-var='date'>22</var>, <var data-var='time'>20:00</var> PST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Dec <var data-var='date'>22</var>, <var data-var='time'>12:40</var> PST</small><br><strong>Scheduled</strong> - We will be releasing a number of updates this evening. During this time, browsing may be interrupted. We will work to ensure any downtime is at a minimum</p>tag:amscomp.statuspage.io,2005:Incident/89145182021-12-22T16:29:10-08:002021-12-22T16:34:45-08:00Intermittent Connectivity Issues<p><small>Dec <var data-var='date'>22</var>, <var data-var='time'>16:29</var> PST</small><br><strong>Resolved</strong> - We have not received additional reports of this issue since implementing our patch. We have since updated the work-around with a potentially longer term solution. If you experience a browsing issue with the website, please report it to support@amscomp.com</p><p><small>Dec <var data-var='date'>22</var>, <var data-var='time'>10:39</var> PST</small><br><strong>Monitoring</strong> - We have implemented a fix to try and address the intermittent Shaw DNS outages and users should begin seeing more stable browsing. We will continue to monitor throughout the afternoon.</p><p><small>Dec <var data-var='date'>22</var>, <var data-var='time'>10:38</var> PST</small><br><strong>Identified</strong> - It appears that there is an issue with a Shaw DNS service and, as a result, some Shaw users are experiencing intermittent 'Page cannot be reached' errors.</p><p><small>Dec <var data-var='date'>22</var>, <var data-var='time'>09:44</var> PST</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Dec <var data-var='date'>22</var>, <var data-var='time'>08:42</var> PST</small><br><strong>Investigating</strong> - We have received reports of intermittent connectivity issues with autoecat. At this time, our monitors indicate that the site is fully operational, but we are investigating if there may be an upstream issue</p>tag:amscomp.statuspage.io,2005:Incident/87445132021-12-03T08:40:48-08:002021-12-03T08:40:48-08:00IP Transit Issues with Telus<p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>08:40</var> PST</small><br><strong>Resolved</strong> - Telus has confirmed this issue resolved. Please contact support@amscomp.com if you encounter further issues.</p><p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>16:00</var> PST</small><br><strong>Monitoring</strong> - Calls appear to be routing normally now. We will update you again once we have confirmation of resolution from Telus.</p><p><small>Dec <var data-var='date'> 2</var>, <var data-var='time'>11:51</var> PST</small><br><strong>Investigating</strong> - Our carrier reports that they are investigating problems with Telus IP trunking. This may affect inbound calling and audio on some inbound calls. We have reached out to for confirmation of network problems and will update the status as information comes in.</p>tag:amscomp.statuspage.io,2005:Incident/86822132021-11-25T09:05:37-08:002021-11-25T09:05:37-08:00Reports of inbound call failures<p><small>Nov <var data-var='date'>25</var>, <var data-var='time'>09:05</var> PST</small><br><strong>Resolved</strong> - We have monitored the issues through the evening and are still seeing good traffic flow from all of our carriers. It appears that this issue was related to specific caller's carriers.<br /><br />If any more problems are noticed, please email support@amscomp.com</p><p><small>Nov <var data-var='date'>24</var>, <var data-var='time'>17:01</var> PST</small><br><strong>Monitoring</strong> - We continue to monitor our services, but all traffic appears to be flowing properly within our network. At this time, we do not see issue with any of our carriers, and reported incidents seem to be localized to specific inbound callers.<br /><br />We will continue to monitor the situation and ask that any further issues be reported to support@amscomp.com</p><p><small>Nov <var data-var='date'>24</var>, <var data-var='time'>12:14</var> PST</small><br><strong>Update</strong> - We are continuing to monitor this situation, but at this time can confirm that we are not experiencing any issues with our carriers. <br /><br />We are beginning to investigate the reports to confirm if it is possible that another carrier is experiencing issues that may be originating from the callers end.</p><p><small>Nov <var data-var='date'>24</var>, <var data-var='time'>10:14</var> PST</small><br><strong>Investigating</strong> - We are receiving reports of intermittent inbound call failures. We have reached out to our carrier and are currently investigating the cause.</p>tag:amscomp.statuspage.io,2005:Incident/85846852021-11-18T16:25:56-08:002021-11-18T16:27:54-08:00Inbound call failures<p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>16:25</var> PST</small><br><strong>Resolved</strong> - At this time, all call services appear to be functioning at full capacity. If you experience any additional problems, please email us at support@amscomp.com</p><p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>11:53</var> PST</small><br><strong>Monitoring</strong> - Current ongoing issues are still related to fibre cuts on lines managed by an outside telco. As a work-around, we have routed calls originally managed by the affected carrier off to another carrier. If you are experiencing inbound call failures, please email us at support@amscomp.com</p><p><small>Nov <var data-var='date'>18</var>, <var data-var='time'>11:53</var> PST</small><br><strong>Investigating</strong> - We have received reports of inbound call failures returning. We are currently in contact with our carriers to determine the cause.</p>