<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.primevox.net,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.primevox.net"/>
  <link rel="self" type="application/atom+xml" href="https://status.primevox.net/history.atom"/>
  <title>Primevox Communications Status - Incident history</title>
  <updated>2026-08-27T17:00:00.000+00:00</updated>
  <author>
    <name>Primevox Communications</name>
  </author>
  
<entry>
  <id>tag:status.primevox.net,2005:Incident/cmtbtk2p00mpz0ylgx4a3pibe</id>
  <published>2026-08-27T17:00:00.000+00:00</published>
  <updated>2026-08-27T17:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cmtbtk2p00mpz0ylgx4a3pibe"/>
  <title>Inter-Data Center Packet Loss</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 34 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Calling, Outbound Calling, AnswerCARE &amp; Voicemail</p>
    <p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating intermittent packet loss affecting network traffic between some of our data centers. This may result in intermittent connectivity issues or degraded call quality for some customers.

Services remain operational, and we will provide another update as soon as we have more information..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>17:53:04</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the cause of the intermittent packet loss as an issue with the fiber carrier serving our Dallas data center.

Our team is working with the carrier to resolve the issue and restore normal network connectivity between our data centers. Services remain operational, but some customers may continue to experience intermittent connectivity or degraded call quality while the issue is being addressed..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>20:19:04</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our fiber carrier has implemented a fix for the issue affecting connectivity between our data centers.

Our team is monitoring the network closely to confirm the fix has fully resolved the intermittent packet loss..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>20:34:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cmst02xhl098u0yo5sui4uxzr</id>
  <published>2026-08-14T13:15:00.000+00:00</published>
  <updated>2026-08-14T13:15:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cmst02xhl098u0yo5sui4uxzr"/>
  <title>Upstream Carrier Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> Inbound Calling</p>
    <p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>13:15:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating reports of customers not receiving inbound calls. Our team has confirmed the issue and is actively working to identify the root cause. We&#039;ll provide an update as soon as we know more..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>13:44:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;ve identified the issue: one of our partner carriers is experiencing a partial outage causing SIP calls not to be delivered to our network as expected. We are working directly with the carrier to resolve this and have begun rerouting traffic to minimize impact while a permanent fix is put in place..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>13:55:35</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been implemented in coordination with our partner carrier, and inbound calling has been restored. We are closely monitoring call traffic to confirm the issue is fully resolved and stable..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>14:15:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. Inbound calling is functioning normally, and we&#039;ve confirmed stability with our partner carrier. We apologize for any disruption this caused and appreciate your patience..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cmp4ow77v00n0p5m3lcdsqdo1</id>
  <published>2026-05-13T18:29:00.000+00:00</published>
  <updated>2026-05-13T18:29:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cmp4ow77v00n0p5m3lcdsqdo1"/>
  <title>Localized System Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 58 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Calling, Outbound Calling, AnswerCARE &amp; Voicemail</p>
    <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>18:29:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Major packet loss within our Phoenix datacenter caused service disruption for a portion of customers on our green platform. Our purple platform was not impacted.

As designed, our systems automatically began moving affected customer phone systems to another datacenter to minimize impact. While the migration process initially reported as successful, we later identified that a limited number of systems did not fully transition due to instability within the affected server environment causing a disruption to service for those customers..</p>
<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>19:27:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our development team manually identified the remaining affected PBX systems and migrated them to healthy datacenters, restoring service availability for impacted customers.

The upstream network carrier later repaired the affected infrastructure responsible for the packet loss condition within the Phoenix datacenter, fully stabilizing network connectivity..</p>
<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>23:28:24</var> GMT+0</small><br /><strong>Postmortem</strong> -
  ### **Permanent Corrective Actions**

We have already begun deploying upgraded routing infrastructure across our datacenters to further improve resiliency and failover performance. The updated architecture includes:

• Dedicated IP address space owned and managed directly by our organization  
• Multi-carrier BGP routing to provide additional carrier redundancy  
• Enhanced inter-datacenter traffic failover capabilities

These improvements significantly reduce reliance on any single upstream network carrier and strengthen platform resiliency during carrier congestion or outage scenarios.

Our purple platform already operates on this architecture, which is why it remained fully operational throughout this incident.  

### **Preventive Improvements**

In addition to the infrastructure upgrades already underway, we are implementing several operational improvements designed to strengthen automated failover validation and incident detection, including:

• Enhanced verification of PBX evacuation completion status  
• Improved detection of partially completed failover events  
• Additional safeguards for system failover during severe packet loss conditions  
• Expanded monitoring and alerting for evacuation inconsistencies and failover anomalies.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cmneww2t300nwtz2d8kfd7wad</id>
  <published>2026-03-31T17:49:34.434+00:00</published>
  <updated>2026-04-02T09:10:21.576+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cmneww2t300nwtz2d8kfd7wad"/>
  <title>Voicemail Transcription and Voicemail-to-Email Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 15 hours and 21 minutes</p>
    <p><strong>Affected Components:</strong> AnswerCARE &amp; Voicemail</p>
    <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>09:10:21</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>17:49:34</var> GMT+0</small><br /><strong>Investigating</strong> -
  We’re currently investigating reports of voicemail transcriptions not being generated as expected and voicemail emails not being sent. Our team is actively working to identify the root cause and restore normal functionality..</p>
<p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>19:11:58</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>19:11:17</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cmltodfyz0405i9u2cklr063t</id>
  <published>2026-02-19T16:28:15.689+00:00</published>
  <updated>2026-02-19T16:28:15.689+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cmltodfyz0405i9u2cklr063t"/>
  <title>Voicemail Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> AnswerCARE &amp; Voicemail</p>
    <p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>16:28:15</var> GMT+0</small><br /><strong>Identified</strong> -
  We are currently experiencing a voicemail service disruption due to packet loss between data centers. Our team is actively working to restore voicemail services as quickly as possible. We will provide updates as progress is made..</p>
<p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>16:31:27</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The voicemail service disruption caused by packet loss between data centers has been resolved. Services are fully restored at this time.

We are actively monitoring the system to ensure continued stability. Please contact support if you experience any further issues..</p>
<p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>19:22:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cmixlvc400j6ykm58oxnzbsvz</id>
  <published>2025-12-08T20:30:09.677+00:00</published>
  <updated>2025-12-08T20:30:09.677+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cmixlvc400j6ykm58oxnzbsvz"/>
  <title>Users Unable to Log Into Web Portal</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 35 minutes</p>
    <p><strong>Affected Components:</strong> PBX Admin &amp; User Portal</p>
    <p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>20:30:09</var> GMT+0</small><br /><strong>Identified</strong> -
   We have identified an issue with our web portal. Our engineering team is actively working to resolve this as quickly as possible. .</p>
<p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>21:00:27</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Access to our web portal has been fully restored. Our engineering team has implemented a fix and services are operating as expected. We are continuing to monitor the portal to ensure stability.

An internal investigation is underway to determine the underlying cause and to prevent future occurrences. We will provide additional updates if necessary.

Thank you for your patience. If you continue to experience any issues, please contact our support team..</p>
<p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>22:05:39</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cmebvdz8x000c7pl512x30lys</id>
  <published>2025-08-14T20:46:50.926+00:00</published>
  <updated>2025-08-14T20:46:50.926+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cmebvdz8x000c7pl512x30lys"/>
  <title>NYC Data Center Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 2 minutes</p>
    <p><strong>Affected Components:</strong> Call History API, AnswerCARE &amp; Voicemail</p>
    <p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>20:46:50</var> GMT+0</small><br /><strong>Identified</strong> -
  We are currently experiencing a partial outage in our NYC data center (one of our five data centers). This is impacting Call History reporting and web portal access for customers served from this location. Our engineering team is actively working with the data center to restore services as quickly as possible. All other call services remain fully operational, and customers in other regions are not affected. We will provide updates as soon as more information becomes available..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>20:52:11</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The earlier issue affecting Call History reporting and web portal access for customers in our NYC data center has been resolved. All services are now operating normally, and we continue to monitor for stability..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>21:48:23</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cmdoxb15k004zfn8qzvhkb67s</id>
  <published>2025-07-29T19:21:50.558+00:00</published>
  <updated>2025-07-29T19:21:50.558+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cmdoxb15k004zfn8qzvhkb67s"/>
  <title>Packet Loss in Raleigh, NC Datacenter</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 minutes</p>
    <p><strong>Affected Components:</strong> eFax API, SMS/MMS Messaging API, Inbound Calling, Outbound Calling, Click-to-Call API, Call History API, PBX Admin &amp; User Portal, , 
Web Portal &amp; APIs →</p>
    <p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>19:21:50</var> GMT+0</small><br /><strong>Identified</strong> -
  Hello, we are currently observing some significant packet loss in our Raleigh, NC datacenter. We&#039;ve engaged our fiber carriers to determine the cause and fix it as soon as possible.  
  
In the meantime, call quality for some customers may be affected, and accessing the web portal/fax portal may experience delays..</p>
<p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>19:29:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  Re-routing around the outage was successful, we are seeing everything return to normal. If you are still encountering any issues, please send an email to support@primevox.net.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cm9adkpdb000dzdjx4z134crj</id>
  <published>2025-04-09T20:21:53.505+00:00</published>
  <updated>2025-04-10T13:36:32.098+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cm9adkpdb000dzdjx4z134crj"/>
  <title>Outbound SMS Messaging Failures</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 17 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> Outbound Messaging</p>
    <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>13:36:32</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved, all outbound SMS/MMS messaging is functional..</p>
<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>20:21:53</var> GMT+0</small><br /><strong>Identified</strong> -
  SMS providers and carriers nationwide have identified an issue affecting the delivery of outbound SMS messaging traffic. At this time, inbound SMS messaging traffic remains unaffected. We will provide updates on this page as soon as the issue with outbound SMS traffic is resolved..</p>
<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>03:10:32</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The stream carrier responsible for the SMS/MMS delivery issues has identified the root cause and implemented a fix. At this time, SMS/MMS messages appear to be sending successfully. We will continue to actively monitor the situation to ensure continued stability..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Maintenance/cm3dkr6tu004s14hh268zaoeg</id>
  <published>2024-11-17T04:00:00.000+00:00</published>
  <updated>2024-11-17T04:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/maintenance/cm3dkr6tu004s14hh268zaoeg"/>
  <title>Adding SIP Servers to Accommodate Growth </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> Inbound Calling, Outbound Calling</p>
    <p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>04:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Nov <var data-var='date'> 17</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Our development team will be adding additional SIP servers to our infrastructure to accommodate customer growth.  
  
This is planned as a no-downtime operation, so service should remain uninterrupted.

  
**Important:** If you or your customers use a managed firewall that requires whitelisting for VoIP traffic, please contact [support@primevox.net](mailto:support@primevox.net) to request a list of the new IP addresses associated with these upgrades..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cm3g4k5gv0002mamjxpjp8gft</id>
  <published>2024-11-13T16:57:53.997+00:00</published>
  <updated>2024-11-13T16:57:53.997+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cm3g4k5gv0002mamjxpjp8gft"/>
  <title>Upstream carrier issues affecting outbound messaging</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 27 minutes</p>
    <p><strong>Affected Components:</strong> Outbound Messaging</p>
    <p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>16:57:53</var> GMT+0</small><br /><strong>Identified</strong> -
  Our team has been notified of an issue with an upstream carrier impacting outbound messaging. The carrier is actively working on a resolution, and we will provide updates as soon as they become available..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>17:25:08</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Our team has been notified that the issue with the upstream carrier impacting outbound messaging has been resolved. We are currently monitoring messaging traffic for any additional problems..</p>
<p><small>Nov <var data-var='date'> 13</var>, <var data-var='time'>18:25:08</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cm2lxeppf001y3oh16fz546uq</id>
  <published>2024-10-23T13:44:38.123+00:00</published>
  <updated>2024-10-23T13:44:38.123+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cm2lxeppf001y3oh16fz546uq"/>
  <title>Multi-Region Internet Stability Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 20 minutes</p>
    <p><strong>Affected Components:</strong> eFax API, Outbound Messaging, Inbound Messaging, Click-to-Call API, SMS/MMS Messaging API, Call History API, Inbound Calling, Outbound Calling, PBX Admin &amp; User Portal, AnswerCARE &amp; Voicemail</p>
    <p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>13:44:38</var> GMT+0</small><br /><strong>Identified</strong> -
  We are observing some major packet loss across multiple internet carriers, which may be impacting voice quality and web portal access.

  
All teams are engaged and working on the issue to get it resolved ASAP..</p>
<p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>14:06:45</var> GMT+0</small><br /><strong>Identified</strong> -
  Public internet disruptions have been resolved, so voice quality and portal access is back to normal.

Viewing Call History (CDR Events) via the web portal and API is still impacted, and will be resolved as quickly as possible. For now, call history will not be viewable temporarily..</p>
<p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>15:05:06</var> GMT+0</small><br /><strong>Resolved</strong> -
  Call history viewing and APIs are now functional. At this time, all services are back to normal..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Maintenance/cm2akddlz000gxyynh4bgfsg0</id>
  <published>2024-10-19T13:30:00.000+00:00</published>
  <updated>2024-10-19T13:30:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/maintenance/cm2akddlz000gxyynh4bgfsg0"/>
  <title>Web Portal, eFax, Messaging &amp; API Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> eFax API, Outbound Messaging, Inbound Messaging, Click-to-Call API, SMS/MMS Messaging API, Call History API, PBX Admin &amp; User Portal</p>
    <p><small>Oct <var data-var='date'> 19</var>, <var data-var='time'>13:30:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Oct <var data-var='date'> 19</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Oct <var data-var='date'> 19</var>, <var data-var='time'>13:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  This Saturday, October 19 at 8:30am Central Time to 12:30pm Central Time, our Dallas datacenter will be upgraded.

  
During this time window, the Web Portal and APIs **may go offline** for some of the maintenance window. This includes features like Digital Faxing, Messaging, and phone system PBX management/reporting.

This maintenance window **will not** affect phones, apps, or voice traffic - phone calls and phone systems will continue to operate normally..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Maintenance/cm1bc9ng2000110ni6geaxrkg</id>
  <published>2024-09-25T04:00:00.000+00:00</published>
  <updated>2024-09-25T06:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/maintenance/cm1bc9ng2000110ni6geaxrkg"/>
  <title>System 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 Calling, Outbound Calling</p>
    <p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>04:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be performing scheduled maintenance to increase server capacity and enhance system performance. We expect little to no downtime; however, there may be brief interruptions as phones fail over between data centers.

We appreciate your patience and understanding as we work to improve our network and your experience..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cm0wnc4ep000sot4jaijar24d</id>
  <published>2024-09-10T16:28:44.265+00:00</published>
  <updated>2024-09-10T16:28:44.265+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cm0wnc4ep000sot4jaijar24d"/>
  <title>Voicemail Emails Are Not Being Sent</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 49 minutes</p>
    <p><strong>Affected Components:</strong> AnswerCARE &amp; Voicemail</p>
    <p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>16:28:44</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified an issue where voicemail emails are not being sent. This issue does not affect AnswerCARE.

An immediate solution is to Apply Changes on the affected PBX. Otherwise, a system-wide update will be implemented tonight after hours..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>17:17:20</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. All voicemail-to-email notifications should be functioning properly..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/clwnk4fo8251187aqoaiipeg85l</id>
  <published>2024-05-26T13:10:01.866+00:00</published>
  <updated>2024-05-26T13:10:01.866+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/clwnk4fo8251187aqoaiipeg85l"/>
  <title>Dallas Datacenter Power Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> eFax API, Outbound Messaging, Inbound Messaging, Click-to-Call API, SMS/MMS Messaging API, Call History API, PBX Admin &amp; User Portal</p>
    <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>13:10:01</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified a power issue in our Dallas datacenter, and an on-site technician is currently working on the issue. This is affecting the web portal and APIs, which includes digital faxing and SMS/MMS messaging..</p>
<p><small>May <var data-var='date'> 26</var>, <var data-var='time'>15:20:04</var> GMT+0</small><br /><strong>Resolved</strong> -
  Power to Dallas has been restored, and web portal access is functional. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/clur2rp8114718xopj9sptffv</id>
  <published>2024-04-08T14:55:54.043+00:00</published>
  <updated>2024-04-08T14:55:54.043+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/clur2rp8114718xopj9sptffv"/>
  <title>Custom Voicemail Greetings Playback Issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 17 hours and 5 minutes</p>
    <p><strong>Affected Components:</strong> AnswerCARE &amp; Voicemail</p>
    <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>14:55:54</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;ve identified an issue with custom voicemail greetings playback and our development team is currently working on a fix..</p>
<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>18:53:20</var> GMT+0</small><br /><strong>Identified</strong> -
  Our development team has created a solution for the custom voicemail playback issue. However, to avoid any service interruptions, its implementation has been scheduled for 11:00 PM ET tonight..</p>
<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>08:00:49</var> GMT+0</small><br /><strong>Resolved</strong> -
  Voicemail greeting playback has been fixed, and voicemail functionality is fully restored.

We apologize for this inconvenience, and testing measures have been created to ensure a similar voicemail failure cannot occur in the future..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cls4ull7g120550b2oh3hsm1bop</id>
  <published>2024-02-02T16:16:51.712+00:00</published>
  <updated>2024-02-02T16:16:51.712+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cls4ull7g120550b2oh3hsm1bop"/>
  <title>Intermittent Quality Issues in NYC</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Calling, Outbound Calling</p>
    <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>16:16:51</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified some internet congestion in our NYC datacenter, which can cause quality issues for a handful of customers. We are currently working with our fiber optic teams to restore normal connectivity.  
  
Customers located in this datacenter have already been moved to an alternative datacenter to help mitigate this issue.

The Realtime Dashboard (and Realtime Queue Analytics) may show inconsistent or absent behavior. This is expected..</p>
<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>19:48:08</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>17:19:08</var> GMT+0</small><br /><strong>Monitoring</strong> -
  The fiber optic outage (it was a national outage by backbone provider Cogent, affecting many websites and services) is largely repaired and appears to be resolved.

We will continue to monitor closely.

There may still be occasional call quality issues, but these should be very few and far between.

Thank you for your patience..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/clrjoxjtn146572b8ok0f3aywfa</id>
  <published>2024-01-18T20:55:02.348+00:00</published>
  <updated>2024-01-18T20:55:02.348+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/clrjoxjtn146572b8ok0f3aywfa"/>
  <title>NYC Datacenter Quality Concerns</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 21 hours and 51 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Calling, Outbound Calling</p>
    <p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>20:55:02</var> GMT+0</small><br /><strong>Identified</strong> -
  We are investigating some call quality issues in our New York datacenter, and will be moving all affected customers out of this datacenter shortly.

Affected customers may experience a temporary call drop as the failover takes place, but overall downtime will not exceed 10 seconds.

If any phone BLFs (light-up buttons) have issues synchronizing, simply reboot the affected phone..</p>
<p><small>Jan <var data-var='date'> 18</var>, <var data-var='time'>21:17:41</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Affected customers have been moved out of the problematic datacenter, and we are seeing call quality return to normal. We will continue to monitor actively for any changes.

If any BLFs (light-up buttons) on a phone are not working properly, simply reboot the phone to sync it back up with our servers.

Thank you for your patience and understanding!.</p>
<p><small>Jan <var data-var='date'> 19</var>, <var data-var='time'>18:46:17</var> GMT+0</small><br /><strong>Resolved</strong> -
  We were notified by our NYC datacenter that the impaired fiber line has been fixed around 4:00am Eastern Time this morning. Since then, we have observed full stability and quality..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/clri9vufh39738b1oibli5ycwb</id>
  <published>2024-01-17T21:06:02.075+00:00</published>
  <updated>2024-02-02T16:23:42.421+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/clri9vufh39738b1oibli5ycwb"/>
  <title>Cloud Softphone for Android: Outbound Calling Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 days, 19 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> Outbound Calling</p>
    <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>16:23:42</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. Updating the app from Google Play will fix it..</p>
<p><small>Jan <var data-var='date'> 17</var>, <var data-var='time'>21:06:02</var> GMT+0</small><br /><strong>Identified</strong> -
  After the recent release of Cloud Softphone&#039;s version 6.2.3 update on the Google Play Store, Android users have reported that they are unable to make outbound calls. Our development team identified that this version is causing communication issues with encrypted servers, such as Primevox&#039;s. Fortunately, Apple and desktop users (Mac/Windows) are unaffected.

We&#039;ve reported the issue to Acrobits, the developer of Cloud Softphone, and updates are on the way. For now, we kindly ask Android users to avoid updating the app and recommend disabling automatic app updates until a fix is implemented..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cloiwph8z22360bplh2lezc6uo</id>
  <published>2023-11-03T17:45:49.404+00:00</published>
  <updated>2023-11-03T17:54:25.582+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cloiwph8z22360bplh2lezc6uo"/>
  <title>Intermittent Voice Quality Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Calling, Outbound Calling, AnswerCARE &amp; Voicemail</p>
    <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>17:54:25</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. We have routed around the affected national fiber carrier..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>17:45:49</var> GMT+0</small><br /><strong>Investigating</strong> -
  There is a significant amount of internet congestion occurring between the East and West coasts, which may cause some customers to experience call quality issues.

We have reported this to our upstream fiber providers and a solution is being implemented..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/clo5suw8q43318bboidqyy4u7p</id>
  <published>2023-10-25T13:37:03.464+00:00</published>
  <updated>2023-10-25T13:37:03.464+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/clo5suw8q43318bboidqyy4u7p"/>
  <title>Intermittent Voice Quality Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> Inbound Calling, Outbound Calling</p>
    <p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>13:37:03</var> GMT+0</small><br /><strong>Investigating</strong> -
  There is a significant amount of internet congestion occurring between the East and West coasts, which may cause some customers to experience call quality issues.

We have reported this to our upstream fiber providers and a solution is being implemented..</p>
<p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>14:09:33</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified the internet provider responsible for the congestion and are actively implementing measures to reroute our voice traffic around this provider..</p>
<p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>14:48:57</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been implemented and we are currently monitoring the situation..</p>
<p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>19:38:21</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/clm88dbvd1102biode6wi4akv</id>
  <published>2023-09-06T21:07:25.131+00:00</published>
  <updated>2023-09-06T21:07:25.131+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/clm88dbvd1102biode6wi4akv"/>
  <title>Intermittent Voice Quality Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 hours and 3 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Calling, Outbound Calling</p>
    <p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>21:07:25</var> GMT+0</small><br /><strong>Investigating</strong> -
  There is a significant amount of internet congestion occurring between the East and West coasts, which may cause some customers to experience call quality issues.

We have reported this to our upstream fiber providers and a solution is being implemented..</p>
<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>03:10:14</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 6</var>, <var data-var='time'>21:29:20</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Internet congestion has been mitigated and everything appears to be stabilized.

We will continue monitoring closely should any issue arise..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cllv7xyny5140bqoe7y1tbist</id>
  <published>2023-08-28T16:30:00.000+00:00</published>
  <updated>2023-08-29T15:21:11.142+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cllv7xyny5140bqoe7y1tbist"/>
  <title>Intermittent Voice Quality Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 hours and 51 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Calling, Outbound Calling</p>
    <p><small>Aug <var data-var='date'> 29</var>, <var data-var='time'>15:21:11</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Due to some internet congestion between the West and East coasts, there may be occasional issues with call quality for a handful of customers.

The fiber providers involved in the congestion have been notified and are working on a fix now..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cll2k0iu353987b7n5rqe6akfb</id>
  <published>2023-08-07T18:00:00.000+00:00</published>
  <updated>2023-08-07T18:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cll2k0iu353987b7n5rqe6akfb"/>
  <title>Outbound Calling Incident</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> Outbound Calling</p>
    <p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  This incident is being opened retroactively. Outbound calls may not be completing for some users..</p>
<p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>18:15:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. 

A major upstream carrier experienced an incident causing some user&#039;s calls not to be connected. Traffic was re-routed to an alternative carrier allowing calls to being completed normally again..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/clkms3zk7158764ayokjukkbgeo</id>
  <published>2023-07-28T16:09:23.610+00:00</published>
  <updated>2023-07-28T16:47:34.704+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/clkms3zk7158764ayokjukkbgeo"/>
  <title>Intermittent Voice Quality Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 38 minutes</p>
    <p><strong>Affected Components:</strong> Inbound Calling, Outbound Calling</p>
    <p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>16:47:34</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>16:09:23</var> GMT+0</small><br /><strong>Identified</strong> -
  Due to some internet congestion along the East Coast, there may be intermittent voice quality issues for some customers.

All of our upstream fiber carriers have been notified of the issue, and are working on a resolution..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/clg1412tj1123514bboi6h5377mu</id>
  <published>2023-04-03T17:33:17.970+00:00</published>
  <updated>2023-04-03T17:33:17.970+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/clg1412tj1123514bboi6h5377mu"/>
  <title>Real-Time Reporting: Accuracy Issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours and 39 minutes</p>
    <p><strong>Affected Components:</strong> PBX Admin &amp; User Portal</p>
    <p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>17:33:17</var> GMT+0</small><br /><strong>Identified</strong> -
  An issue has been identified with our **Real-Time Latency** and **Extension Status Snapshot** reports. These reports are currently displaying online extensions as &quot;offline&quot;. This problem is isolated to reporting only, and the functionality of extensions showing as &quot;offline&quot; is not affected: they are functioning normally.

We have a pending fix that will be applied to these reports this evening..</p>
<p><small>Apr <var data-var='date'> 4</var>, <var data-var='time'>03:12:43</var> GMT+0</small><br /><strong>Resolved</strong> -
  Real-Time Latency and Extension Snapshot reports have been fixed, and should now be displaying correct online/offline extension status.

Thank you for your patience..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Maintenance/clerbs67011374hzof83rn02ti</id>
  <published>2023-03-03T04:00:00.000+00:00</published>
  <updated>2023-03-03T05:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/maintenance/clerbs67011374hzof83rn02ti"/>
  <title>Upgrades to Real-Time Data</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> PBX Admin &amp; User Portal</p>
    <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Tonight at 10:00pm Central Time, we will be publishing some upgrades to the following systems:
 - Real-Time Dashboards
 - Webhooks

During the upgrade, real-time dashboards such as Realtime Queues and Realtime Latency may experience delays or show inaccurate status.

After the upgrade, customers should not notice any changes with Webhook integrations, however if any issue is suspected with webhooks, please send an email to support@primevox.net and we will look into it.

If you do not utilize our APIs or Webhooks, you may ignore this notice..</p>
<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>04:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Incident/cl9osqxtq15502hjoe2xna67y7</id>
  <published>2022-10-25T22:46:01.119+00:00</published>
  <updated>2022-10-25T22:46:01.119+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/incident/cl9osqxtq15502hjoe2xna67y7"/>
  <title>Dallas Datacenter Outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 50 minutes</p>
    <p><strong>Affected Components:</strong> PBX Admin &amp; User Portal, SMS/MMS Messaging API, Call History API, Click-to-Call API, eFax API</p>
    <p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>22:46:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Our Dallas datacenter has experienced a loss of fiber link, impacting our web portal.

Phone systems and phones have failed over to alternative datacenters, however our eFax and web portal are unusable.

Our Dallas fiber carriers have been notified and we are working to get the web portal online as quickly as possible..</p>
<p><small>Oct <var data-var='date'> 26</var>, <var data-var='time'>00:36:28</var> GMT+0</small><br /><strong>Resolved</strong> -
  Our datacenter provider has confirmed connectivity in Dallas, so our Web Portal is back online. 

If you encounter any issues with phones, a simple reboot (unplug the power cable, and plug it back in) can help..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.primevox.net,2005:Maintenance/ckx3jb892164028eogi3flsi3o</id>
  <published>2021-12-12T17:45:00.000+00:00</published>
  <updated>2021-12-12T17:46:30.784+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.primevox.net/maintenance/ckx3jb892164028eogi3flsi3o"/>
  <title>Log4j Vulnerability Remediation</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 12 minutes</p>
    
    <p><small>Dec <var data-var='date'> 12</var>, <var data-var='time'>17:46:30</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress..</p>
<p><small>Dec <var data-var='date'> 12</var>, <var data-var='time'>17:56:33</var> GMT+0</small><br /><strong>Completed</strong> -
  Remediation of the log4j vulnerability has been completed..</p>
<p><small>Dec <var data-var='date'> 12</var>, <var data-var='time'>17:45:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified a single piece of software in our infrastructure that is susceptible to the newly discovered log4j 0-day vulnerability, and will be patching it shortly.

There is no expected impact to services..</p>

        ]]>
  </content>
</entry>

</feed>