<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.televoips.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.televoips.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.televoips.com/history.atom"/>
  <title>TeleVoIPs Status Status - Incident history</title>
  <updated>2026-07-07T12:45:00.000+00:00</updated>
  <author>
    <name>TeleVoIPs Status</name>
  </author>
  
<entry>
  <id>tag:status.televoips.com,2005:Incident/cmraq5tie08c91an6rutmxztg</id>
  <published>2026-07-07T12:45:00.000+00:00</published>
  <updated>2026-07-07T12:45:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmraq5tie08c91an6rutmxztg"/>
  <title>Slow load times for the vFax portal and Manager portal fax integration</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 58 minutes</p>
    <p><strong>Affected Components:</strong> vFax Portal</p>
    <p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>12:45:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Jul <var data-var='date'> 7</var>, <var data-var='time'>20:43:23</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Maintenance/cmolucuhw0aqz113owdpcvrvh</id>
  <published>2026-05-06T03:00:00.000+00:00</published>
  <updated>2026-05-06T03:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/maintenance/cmolucuhw0aqz113owdpcvrvh"/>
  <title>Scheduled maintenance for V2 Voice Services</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 7 minutes</p>
    <p><strong>Affected Components:</strong> Manager Portal, API, ATL Core Server, TPA Core Server, AWS US East 1 Core Server, WebPhone, Endpoint Provisioning Server, Mobile App, Desktop Softphone, ATL Recording Server, TPA Recording Server, AWS US East 1 Recording Server</p>
    <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  This maintenance will take place on **Tuesday, May 5, between 11:00 PM and 12:00 AM**. There is no expected downtime, and your services should continue to operate normally throughout the maintenance window..</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>03:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>04:06:57</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio15011v0nph7rlz3xdn</id>
  <published>2026-01-22T19:30:00.000+00:00</published>
  <updated>2026-01-22T19:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio15011v0nph7rlz3xdn"/>
  <title>Inbound email outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Helpdesk</p>
    <p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Microsoft is reporting Degraded Performance sending and receiving email through Exchange Online. This is affecting our email helpdesk..</p>
<p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>13:00:45</var> GMT+0</small><br /><strong>Resolved</strong> -
  All systems are normal, this incident is resolved..</p>
<p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>07:30:54</var> GMT+0</small><br /><strong>Investigating</strong> -
  Inbound and Outbound email has returned to normal.
From Microsoft Jan 23, 2026, 1:27 AM EST: We’ve confirmed that the affected infrastructure has returned to a healthy state and is operating as expected. We’ll continue to closely monitor the remediation actions taken and make any necessary adjustments to maintain stability..</p>
<p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>21:53:07</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing emails start to trickle in. Microsoft&#039;s current status is still degraded. 
Microsoft: We&#039;re continuing to refine our load balancing configurations to remedy residual imbalances across the environment and further our ongoing recovery efforts..</p>
<p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>21:50:38</var> GMT+0</small><br /><strong>Investigating</strong> -
  From Microsoft: Current status: While we&#039;ve restored the affected infrastructure to a heathy state, further load balancing is required to mitigate persistent impact. We&#039;ve identified and are implementing additional actions to direct requests and traffic to additional healthy sections of infrastructure to achieve withstanding recovery.

During this time please call our support desk at 8136555100 option 2 until this is resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio15011q0nph63f5e8rf</id>
  <published>2025-10-20T11:36:00.000+00:00</published>
  <updated>2025-10-20T11:36:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio15011q0nph63f5e8rf"/>
  <title>AWS Outage Affecting SMS and MMS Delivery</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound SMS, Outbound SMS</p>
    <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>11:36:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are experiencing an outage on inbound and outbound SMS and MMS messaging due to a Global AWS outage..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>14:02:43</var> GMT+0</small><br /><strong>Investigating</strong> -
  The incident has been resolved.</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>23:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  AWS resolved the issues with their DNS and EC2 infrastructure. AWS&#039;s resolution post below.

Oct 20 3:53 PM PDT Between 11:49 PM PDT on October 19 and 2:24 AM PDT on October 20, we experienced increased error rates and latencies for AWS Services in the US-EAST-1 Region. Additionally, services or features that rely on US-EAST-1 endpoints such as IAM and DynamoDB Global Tables also experienced issues during this time. At 12:26 AM on October 20, we identified the trigger of the event as DNS resolution issues for the regional DynamoDB service endpoints. After resolving the DynamoDB DNS issue at 2:24 AM, services began recovering but we had a subsequent impairment in the internal subsystem of EC2 that is responsible for launching EC2 instances due to its dependency on DynamoDB. As we continued to work through EC2 instance launch impairments, Network Load Balancer health checks also became impaired, resulting in network connectivity issues in multiple services such as Lambda, DynamoDB, and CloudWatch. We recovered the Network Load Balancer health checks at 9:38 AM. As part of the recovery effort, we temporarily throttled some operations such as EC2 instance launches, processing of SQS queues via Lambda Event Source Mappings, and asynchronous Lambda invocations. Over time we reduced throttling of operations and worked in parallel to resolve network connectivity issues until the services fully recovered. By 3:01 PM, all AWS services returned to normal operations. Some services such as AWS Config, Redshift, and Connect continue to have a backlog of messages that they will finish processing over the next few hours..</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>11:37:48</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing successful delivery of SMS and MMS messaginges. We will continue to monitor..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio15011m0nph8cxiatpx</id>
  <published>2025-07-22T18:23:00.000+00:00</published>
  <updated>2025-07-22T18:23:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio15011m0nph8cxiatpx"/>
  <title>TeleVoIPs Outbound SMS</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Outbound SMS, SMS API</p>
    <p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>18:23:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating an issue with outbound SMS messages.</p>
<p><small>Jul <var data-var='date'> 23</var>, <var data-var='time'>11:34:32</var> GMT+0</small><br /><strong>Resolved</strong> -
  Resolved.</p>
<p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>19:24:54</var> GMT+0</small><br /><strong>Investigating</strong> -
  Outbound SMS operation has returned to normal, we will continue to monitor..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Maintenance/cmmkzio5o01230nph2gjtgx8f</id>
  <published>2024-09-22T00:00:00.000+00:00</published>
  <updated>2024-09-22T00:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/maintenance/cmmkzio5o01230nph2gjtgx8f"/>
  <title>Scheduled Maintenance of our Client Portal and API</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> Client Portal, Call Detail Redords API, Inbound SMS, SMS API, Outbound SMS, New Number Ordering, Desktop Softphone, Mobile App, Mobile App, Desktop Softphone</p>
    <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are scheduling maintenance of our Client Portal and API on September 21, 2024 from 8pm to 11:59pm Eastern. During the maintenance window access to our Client Portal and mobile/desktop app login may be unreachable or delayed. Outbound and Inbound SMS will be delayed as too will all CDR records and Portal CDR reports..</p>
<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>02:57:08</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is complete. All services are operational.</p>
<p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>18:09:26</var> GMT+0</small><br /><strong>Identified</strong> -
  From Jason: 
During the maintenance window access to our online Portal (not NS manager) and mobile/desktop app login may be unreachable or delayed. Outbound and Inbound SMS will be delayed as too will all CDR records and Portal CDR reports. Below is a detailed list, not all of which applies to our customers.

 

Possibly unreachable for a short period:

Portal
Mobile App login and SMS outbound
Desktop App login and SMS outbound
Mobile callback
Client access to API
Onboarding and Migration
 

Delayed during the window:

CDR records and reports
SMS outbound and inbound for all devices
Portal webhooks
NetSapiens replication to Portal
Vendor API processing (Bandwidth, HubSpot, Freshdesk, etc.).</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio15011i0nphb6qifv7o</id>
  <published>2023-06-13T19:08:00.000+00:00</published>
  <updated>2023-06-13T19:08:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio15011i0nphb6qifv7o"/>
  <title>AWS Multiple services Operational issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound SMS, Outbound SMS, New Number Ordering, Call Detail Redords API, SMS API, Mobile App</p>
    <p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>19:08:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are monitoring AWS issues that are impacting several of our services. Mainly SMS, some API calls and new mobile app registrations..</p>
<p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>21:45:08</var> GMT+0</small><br /><strong>Resolved</strong> -
  We are now seeing all services back up and operational with AWS Services. All functions and services have been restored. Please test and let us know if you encounter any and all issues. You will receive all messages that were sent during this outage as the backlog has caught up and sent all messages through the system. If you have cause to believe you have missed SMS texts please provide an approximate date/time and number that you believe sent them..</p>
<p><small>Jun <var data-var='date'> 13</var>, <var data-var='time'>19:41:19</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are continuing to experience increased error rates and latencies for multiple AWS Services. The root cause has been identified as an issue with AWS Lambda, and are actively working toward resolution.  We are actively working on full mitigation and will continue to provide regular updates..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio15011g0nphgp5ddjbf</id>
  <published>2023-05-11T12:30:00.000+00:00</published>
  <updated>2023-05-11T12:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio15011g0nphgp5ddjbf"/>
  <title>Verizon Wireless network outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound Voice Services</p>
    <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  There was an outage within the Verizon Wireless network causing some inbound calls to drop at roughly the five minute point.

We received word from Verizon that this issue was resolved at 3:02 ET today. All traffic was removed from their faulty routes..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio15011b0nph3ettd03h</id>
  <published>2023-03-07T13:00:00.000+00:00</published>
  <updated>2023-03-07T13:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio15011b0nph3ettd03h"/>
  <title>Mobile App and Desktop Softphone connection issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Desktop Softphone, Mobile App</p>
    <p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing reports of connection issues with our Mobile App and Desktop Softphone. Most are able to log in but cannot make or receive calls. Development and tech support are working on isolating the issue..</p>
<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>16:00:33</var> GMT+0</small><br /><strong>Resolved</strong> -
  The Mobile App and Desktop Softphone are back to normal and working. There was a port issue with these devices and a patch needed to be deployed to resolve it. If you are still experiencing issues with not being able to make or take calls from your Mobile app or Desktop Softphone, please reset the app and log back in to receive the updated patch..</p>
<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>14:40:53</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have deployed a patch to resolve the issues with the Mobile App and Desktop Softphone. We are starting to see these devices register correctly now. We will be monitoring the progress of the apps..</p>
<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>14:15:37</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are working and close to identifying the issue. We will be deploying a patch shortly to resolve..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio1501150nph33938g4c</id>
  <published>2022-12-09T16:30:00.000+00:00</published>
  <updated>2022-12-09T16:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio1501150nph33938g4c"/>
  <title>Inbound SMS delivery issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound SMS</p>
    <p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are receiving reports of inbound SMS messages not being delivered, we are investigating this issue now. More details to come..</p>
<p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>20:44:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have continued to monitor inbound SMS messages and all are being delivered successfully. We have also seen the previously failed messages be delivered as well. We will be closing this incident and marking it as resolved..</p>
<p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>17:05:38</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing SMS messages being delivered successfully now. Messages that were not delivered will be retried over the next few hours. Will will keep this status open for now while we monitor the service.</p>
<p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>16:55:51</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have identified the issue and are deploying a fix..</p>
<p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>16:35:42</var> GMT+0</small><br /><strong>Investigating</strong> -
  Engineers are currently looking into the issue.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Maintenance/cmmkzio5o01210nph2ao94n5k</id>
  <published>2022-08-29T01:30:00.000+00:00</published>
  <updated>2022-08-29T01:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/maintenance/cmmkzio5o01210nph2ao94n5k"/>
  <title>Firewall Work</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> Inbound Voice Services, Outbound Voice Services, 911 Services</p>
    <p><small>Aug <var data-var='date'> 29</var>, <var data-var='time'>01:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Hello,

UPDATE: We will be moving the window up to 9:30 PM - 10:30 PM tonight.

Please be aware that we will be performing emergency firewall maintenance on August 29 from 12am-1am. This is necessary due to the issues we experienced earlier today.

As a result, you may experience intermittent downtime during this window.  This includes all inbound and outbound calling.

We will advise when the maintenance is complete via our status page at status.televoips.com.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio1501100npha283gayt</id>
  <published>2022-08-28T13:25:00.000+00:00</published>
  <updated>2022-08-28T13:25:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio1501100npha283gayt"/>
  <title>Phone Service Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound Voice Services, Outbound Voice Services, 911 Services</p>
    <p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>13:25:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigation an outage at one of our datacenters.</p>
<p><small>Aug <var data-var='date'> 29</var>, <var data-var='time'>02:45:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>14:47:39</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have implemented a fix and are monitoring the firewalls. All services are up and running..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>13:45:49</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have identified the issue to be at our firewalls in one of our datacenters. Working on a resolution..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio15010v0nphe7yhh9gf</id>
  <published>2022-08-28T04:30:00.000+00:00</published>
  <updated>2022-08-28T04:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio15010v0nphe7yhh9gf"/>
  <title>Phone service outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound Voice Services, Outbound Voice Services, 911 Services</p>
    <p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>04:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigation an outage at one of our datacenters.</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>10:25:10</var> GMT+0</small><br /><strong>Resolved</strong> -
  The incident has been resolved.</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>09:40:04</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have implemented a fix and are monitoring the firewalls. all services are up and running..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>09:14:51</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have identified the issue to be at our firewalls in one of our datacenters. Working on a resolution..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio15010r0nphfl523hwq</id>
  <published>2022-02-16T15:15:00.000+00:00</published>
  <updated>2022-02-16T15:15:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio15010r0nphfl523hwq"/>
  <title>Level3 internet outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound Voice Services, Outbound Voice Services</p>
    <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>15:15:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing connectivity issues over Level3 network connections..</p>
<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>17:38:17</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have not seen any further issues after making the routing changes. We are considering this issue resolved..</p>
<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>15:25:55</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have bypassed the Level3 routes are starting to see connections normalize. Will will keep monitoring all connections..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio15010m0nph9k600pkm</id>
  <published>2021-12-07T17:30:00.000+00:00</published>
  <updated>2021-12-07T17:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio15010m0nph9k600pkm"/>
  <title>Some services affected by Amazon AWS outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound SMS, New Number Ordering, Helpdesk, Call Detail Redords API, SMS API</p>
    <p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  Some TeleVoIPs services are experiencing issues due to Amazon&#039;s AWS US-EAST-1 Region outage. The most recent AWS update is: &quot;The root cause of this issue is an impairment of several network devices in the US-EAST-1 Region. We are pursuing multiple mitigation paths in parallel, and have seen some signs of recovery, but we do not have an ETA for full recovery at this time.&quot; Inbound SMS is currently delayed and several APIs are being affected. Our support ticket system is currently unable receive new inbound support email requests. TeleVoIPs has employed our failover system so support email replies are currently delayed. Please do not hesitate to call support at 8136555100 option 2 if you have an urgent issue..</p>
<p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>14:38:40</var> GMT+0</small><br /><strong>Resolved</strong> -
  Amazon AWS is reporting all systems normal and consider the issue resolved. We have seen all connections return to normal overnight and are considering this issue resolved as well..</p>
<p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>22:58:28</var> GMT+0</small><br /><strong>Investigating</strong> -
  Amazon is reporting all there services coming back up to full capacity. We are monitoring and have seen our integrations return to normal. We will continue to monitor overnight and update the status in the morning..</p>
<p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>22:56:02</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are starting to see services normalize with AWS. Their latest update indicates they are getting closer to being fully operational. &quot;We have mitigated the underlying issue that caused some network devices in the US-EAST-1 Region to be impaired. We are seeing improvement in availability across most AWS services. All services are now independently working through service-by-service recovery. We continue to work toward full recovery for all impacted AWS Services and API operations.&quot;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio14010h0nph8b39efde</id>
  <published>2021-10-01T15:42:00.000+00:00</published>
  <updated>2021-10-01T15:42:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio14010h0nph8b39efde"/>
  <title>View my fax portal incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> vFax Portal, Fax email notifications</p>
    <p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>15:42:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating issues with the viewmyfax.com Portal. the site may be inaccessible for some customers..</p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>18:16:55</var> GMT+0</small><br /><strong>Resolved</strong> -
  All issues have been resolved with the vfax portal and all other vFax services. If anyone continues to have any issues please contact support to let us know..</p>
<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>19:22:20</var> GMT+0</small><br /><strong>Investigating</strong> -
  The issue has been identified and a fix is being implemented. You may see some services restored..</p>
<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>16:51:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating issues with our vFax service. This is affecting the viewmyfax.com portal, email to fax and fax email notifications. We are working to resolve this issue. We will update this incident when we have more information..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio1401090nph51c9hhcd</id>
  <published>2021-09-29T13:55:00.000+00:00</published>
  <updated>2021-09-29T13:55:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio1401090nph51c9hhcd"/>
  <title>Voice and 911 Intermittent Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound Voice Services, 911 Services, Inbound SMS, Outbound SMS</p>
    <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>13:55:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are starting to see instability in our upstream carrier&#039;s connections. We are monitoring the issues and it is possible voice and 911 calls could be impacted intermittently..</p>
<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>19:20:10</var> GMT+0</small><br /><strong>Resolved</strong> -
  We have continued to observe normal network behavior and inbound call performance. At this time the upstream carrier is continuing to report stability and is monitoring. TeleVoIPs is considering the incident resolved and will reopen a new incident provided issues reoccur at the upstream carrier level..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>18:06:39</var> GMT+0</small><br /><strong>Investigating</strong> -
  We continue to observe network stability from our carrier and will continue to monitor..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>14:03:01</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have been observing normal inbound call performance since yesterday evening. We continue to monitor this incident and will post updates here.  Outbound calling continues to be unaffected..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>23:22:42</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing inbound call failures at this time due to the upstream carrier. It is currently being investigated and all teams are engaged..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>19:18:49</var> GMT+0</small><br /><strong>Investigating</strong> -
  Our upstream carrier has worked with Verizon Wireless to address inbound call issues. At this time we are seeing expected call behavior and we will continue to monitor..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>15:21:05</var> GMT+0</small><br /><strong>Investigating</strong> -
  We continue to see intermittent issues with inbound calls due to the upstream carrier. Most issues are limited to inbound calls from primarily Verizon Wireless / Verizon subscribers. Outbound calling is not impacted. We will continue to provide more information as we receive it..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio1401010nphau80ba4y</id>
  <published>2021-09-28T13:31:00.000+00:00</published>
  <updated>2021-09-28T13:31:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio1401010nphau80ba4y"/>
  <title>Voice and 911 Intermittent Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound Voice Services, 911 Services</p>
    <p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>13:31:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating the issue currently.</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>11:17:08</var> GMT+0</small><br /><strong>Resolved</strong> -
  After observing continued network stability, our carrier is considering this incident resolved. Their teams continue to monitor their network for possible threats. We will be marking this incident as resolved and open a new one if required..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>01:59:07</var> GMT+0</small><br /><strong>Investigating</strong> -
  We will continue to leave this incident open while we monitor the situation. At this time the majority of calls are processing as expected. Incoming calls may in some cases experience one-way audio, or Verizon numbers may have issues calling in intermittently, however this the minority. We will continue to provide updates as we receive them..</p>
<p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>18:26:46</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have not received a current update from our carrier, however we have seen our connections stabilized and calls are processing normally at this time..</p>
<p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>16:22:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  TeleVoIPs continues to see intermittent issues with inbound calls, however it does not appear to be consistent nor have the same severity as yesterday. We will continue to monitor and provide updates here..</p>
<p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>14:33:15</var> GMT+0</small><br /><strong>Investigating</strong> -
  Current Status &amp; Action Plan
Our upstream carrier continues to fight against an attack on their network which may intermittently impact your services. Their teams are actively adapting their mitigation efforts to defend the network, and operations and engineering teams are responding in real-time. We will continue to provide updates here..</p>
<p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>13:44:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are starting to see instability in our upstream carrier&#039;s connections. We are monitoring the issues and it is possible voice and 911 calls could be impacted intermittently..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio1400zu0nphf9bsfttx</id>
  <published>2021-09-27T13:12:00.000+00:00</published>
  <updated>2021-09-27T13:12:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio1400zu0nphf9bsfttx"/>
  <title>Voice Intermittent Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound Voice Services, Outbound Voice Services, 911 Services, Inbound SMS, Outbound SMS, New Number Ordering, Number Porting, Inbound Calling - Caller ID Lookup (CNAM)</p>
    <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>13:12:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  This incident affects: Outbound Calling Services and Inbound Calling Services.</p>
<p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>12:01:38</var> GMT+0</small><br /><strong>Resolved</strong> -
  The upstream carrier is currently considering this issue resolved. TeleVoIPs will continue to monitor the situation and post updates to our status page where needed. We will be marking this incident as resolved and open a new one if required. 

If you are not subscribed to this status page we highly suggest subscribing to receive the latest on any updates or issues..</p>
<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>22:58:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We have observed continued stability over the last hour. We are waiting on additional updates from our upstream inbound carrier and will continue to monitor all services. While we wait for these updates, we wanted to take the time to provide as much details as we have available. 

Our primary upstream carrier for inbound calling and inbound and outbound messaging on the PSTN is currently experiencing an attack on its network. Many if not most of the United States largest VoIP and cellular providers utilize this upstream carrier to provide connections for voice inbound and outbound.

Due to the way that telephone numbers work, we cannot set up a failover in the event that our main upstream carrier experiences an attack. We selected our upstream carrier based on multiple decades of great service and uptime, this is also why many other VoIP and cellular providers have chosen them.

Outbound calling can support failover and all of TeleVoIPs’ outbound calling traffic has been migrated away from this upstream carrier who is experiencing the attack. As the attack is ongoing there may be periods of poor audio quality inbound, or inbound call failures.

If you are experiencing an issue inbound or outbound do not hesitate to reach out, we are here to help, we are still looking through all poor audio or call issues to determine cause and resolve where possible. In the event that the issue is caused by this upstream carrier attack we will inform you.

We are working closely with our carrier and we do have the confidence that they have the ability to mitigate the ongoing distributed denial of service attack. However, in the event that the attack on this major carrier appears to extend in time, we are prepared to protect you and your business and will engage additional inbound carriers if needed.  

TeleVoIPs is currently having no issues with its own network, or extension to extension calling; Furthermore some TeleVoIPs customers do not rely on this upstream carrier for service and will be unaffected by this attack.

If you are having trouble reaching TeleVoIPs support through our main line you may dial our alternative support line: 813-378-3099

We will continue to provide updates at http://status.televoips.com in order to be as transparent as possible regarding the current issue affecting VoIP providers nationally.

NOTICE: In the event of an emergency where 911 needs to be reached please utilize cellular networks where possible..</p>
<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>18:48:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are still working with our carrier to resolve the issues. We have been made aware that new number ordering and number porting are also being affected at this time..</p>
<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>16:06:42</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are seeing issues with DTMF being passed through the call. We continue to work on the issues and will keep posting updates..</p>
<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>13:13:56</var> GMT+0</small><br /><strong>Investigating</strong> -
  TeleVoIPs teams are investigating an incident impacting our V2 Voice services. Customers may notice intermittent service disruptions..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio1400zl0nph23vzf8j5</id>
  <published>2021-09-26T15:30:00.000+00:00</published>
  <updated>2021-09-26T15:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio1400zl0nph23vzf8j5"/>
  <title>Voice, 911 and Messaging</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound Voice Services, Outbound Voice Services, 911 Services, Inbound SMS, Outbound SMS</p>
    <p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>15:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating an incident with our carrier impacting Voice (including 911 servce) and Messaging Services. We believe this may be stemming from yesterday&#039;s incident. Calls and Messages may experience unexpected failures. All teams are actively engaged and we will update you as our carrier continues to provide updates..</p>
<p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>00:50:08</var> GMT+0</small><br /><strong>Resolved</strong> -
  After continued monitoring with standard network behavior, TeleVoIPs considers this incident resolved..</p>
<p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>17:00:57</var> GMT+0</small><br /><strong>Investigating</strong> -
  Teams have identified the cause of this incident and continue to work towards a resolution. All teams are actively engaged..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.televoips.com,2005:Incident/cmmkzio1400zp0nphgal768hr</id>
  <published>2021-09-25T19:30:00.000+00:00</published>
  <updated>2021-09-25T19:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.televoips.com/incident/cmmkzio1400zp0nphgal768hr"/>
  <title>Voice and Messaging Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> Inbound Voice Services, Outbound Voice Services, 911 Services, Inbound SMS, Outbound SMS</p>
    <p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We Are investigating an incident impacting Voice and Messaging Services. Calls and Messages may experience unexpected failures. All teams are actively engaged..</p>
<p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>23:45:50</var> GMT+0</small><br /><strong>Resolved</strong> -
  With continued network stability, we consider this incident resolved..</p>
<p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>22:42:55</var> GMT+0</small><br /><strong>Investigating</strong> -
  We continue to see portal and network improvements. At this time, messaging traffic is processing as expected. We continue to work to resolve other impacted services..</p>
<p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>20:30:48</var> GMT+0</small><br /><strong>Investigating</strong> -
  TeleVoIps teams continue to investigate Voice and Messaging Failures. 911 calls are experiencing failures.

Customers may also experience portal and portal API time-outs, slowness, or unresponsiveness.

All teams are working towards a resolution at this time..</p>

        ]]>
  </content>
</entry>

</feed>