<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.securecall.cloud,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud"/>
  <link rel="self" type="application/atom+xml" href="https://status.securecall.cloud/history.atom"/>
  <title>SecureCall Status - Incident history</title>
  <updated>2025-10-20T08:36:11.030+00:00</updated>
  <author>
    <name>SecureCall</name>
  </author>
  
<entry>
  <id>tag:status.securecall.cloud,2005:Incident/cmgyvsh0003i3twbp9ics3tb4</id>
  <published>2025-10-20T08:36:11.030+00:00</published>
  <updated>2025-10-20T08:36:11.030+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/incident/cmgyvsh0003i3twbp9ics3tb4"/>
  <title>Service Disruption : SecureCall Services (US East Region)</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 48 minutes</p>
    <p><strong>Affected Components:</strong> Voice Services, Payment Services</p>
    <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>08:36:11</var> GMT+0</small><br /><strong>Identified</strong> -
  We’re currently experiencing service disruptions with SecureCall Services in US East Region due to an ongoing AWS outage impacting our infrastructure..</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>10:24:27</var> GMT+0</small><br /><strong>Resolved</strong> -
  AWS reports conditions have improved, and most services are now operational. SecureCall Services are also working normally, and we will continue to monitor for stability..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Maintenance/cmfd9dk7q0049i7tvfzzp15uh</id>
  <published>2025-09-10T01:00:00.000+00:00</published>
  <updated>2025-09-10T01:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/maintenance/cmfd9dk7q0049i7tvfzzp15uh"/>
  <title>Message Broker Updates - UK</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Payment Services, Voice Services</p>
    <p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>01:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be performing scheduled updates to SecureCall message broker service in the UK region to improve performance and reliability.

During this maintenance window, the SecureCall services in the region will be unavailable. .</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>03:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Incident/cmegdeh5i000n62k15mq3osr5</id>
  <published>2025-08-17T23:00:54.191+00:00</published>
  <updated>2025-08-17T23:00:54.191+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/incident/cmegdeh5i000n62k15mq3osr5"/>
  <title>Webex Calling - SecureCall Issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 38 minutes</p>
    <p><strong>Affected Components:</strong> Voice Services, Payment Services</p>
    <p><small>Aug <var data-var='date'> 17</var>, <var data-var='time'>23:00:54</var> GMT+0</small><br /><strong>Identified</strong> -
  We have been advised of intermittent failures and timeouts with the Webex Calling APIs, which are also impacting SecureCall functionality. The issue has been confirmed to be on Webex’s side, and their engineering teams are actively working to restore normal service..</p>
<p><small>Aug <var data-var='date'> 18</var>, <var data-var='time'>02:38:31</var> GMT+0</small><br /><strong>Resolved</strong> -
  Cisco has confirmed that this issue has been resolved. Further updates can be found at: &lt;https://status.webex.com/commercial/status?lang=en%5FUS&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Maintenance/cm8p7focp00epozlo2e8tbku2</id>
  <published>2025-04-10T08:00:00.000+00:00</published>
  <updated>2025-04-10T08:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/maintenance/cm8p7focp00epozlo2e8tbku2"/>
  <title>Voice Routing Platform Cutover</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> Voice Services</p>
    <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>08:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be performing a scheduled maintenance to cut over from our current voice routing platform to a new system. 

Our teams will be actively monitoring the transition to ensure minimal impact and a smooth migration. 

If you experience any issues after the maintenance, please reach out to our support team..</p>
<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>08:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Incident/cm72dt8pb000j30mt8wf2niwm</id>
  <published>2025-02-12T20:46:59.963+00:00</published>
  <updated>2025-02-12T20:46:59.963+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/incident/cm72dt8pb000j30mt8wf2niwm"/>
  <title>Issues with  Securing Webex Calls -APAC</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    
    <p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>20:46:59</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>21:07:08</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. Root Cause is being investigated .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Maintenance/cm6q1iohi00729efpze924mg4</id>
  <published>2025-02-07T09:00:00.000+00:00</published>
  <updated>2025-02-07T11:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/maintenance/cm6q1iohi00729efpze924mg4"/>
  <title>Upcoming SecureCall Web Component Deployment</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Payment Services</p>
    <p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We’re rolling out an update to the SecureCall Web Components, As part of this deployment, we have refactored the component to extract common SecureCall client API communication functions into a separate library. This change is seamless and will not impact the functionality of the Web Component.

Additionally, some error messages displayed during specific network outage conditions have been updated. These changes are purely cosmetic and do not affect service operations.

**Deployment Schedule**

The update will be deployed during the following maintenance window:

APAC: Thursday, 6 February 2025, 10:00 PM – Friday, 7 February, 12:00 AM (AEDT)

UK: Friday, 7 February 2025, 5:00 AM – 7:00 AM (AEDT)

US: Friday, 7 February 2025, 8:00 PM – 10:00 PM (AEDT)

If you have any questions, please reach out to our support team.</p>
<p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Maintenance/cm6q17nte008qh2vgy5mcxle7</id>
  <published>2025-02-06T18:00:00.000+00:00</published>
  <updated>2025-02-06T18:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/maintenance/cm6q17nte008qh2vgy5mcxle7"/>
  <title>Upcoming SecureCall Web Component Deployment</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Payment Services</p>
    <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We’re rolling out an update to the SecureCall Web Component As part of this deployment, we have refactored the component to extract common SecureCall client API communication functions into a separate library. This change is seamless and will not impact the functionality of the Web Component.

Additionally, some error messages displayed during specific network outage conditions have been updated. These changes are purely cosmetic and do not affect performance.

**Deployment Schedule**

The update will be deployed during the following maintenance window:

APAC: Thursday, 6 February 2025, 10:00 PM – Friday, 7 February, 12:00 AM (AEDT)

UK: Friday, 7 February 2025, 5:00 AM – 7:00 AM (AEDT)

US: Friday, 7 February 2025, 8:00 PM – 10:00 PM (AEDT)

If you have any questions, please reach out to our support team.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Maintenance/cm6q0ikql008xyaukesv55jlu</id>
  <published>2025-02-06T11:00:00.000+00:00</published>
  <updated>2025-02-06T13:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/maintenance/cm6q0ikql008xyaukesv55jlu"/>
  <title>Upcoming SecureCall Web Component Deployment</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Payment Services</p>
    <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We’re rolling out an update to the SecureCall Web Component As part of this deployment, we have refactored the component to extract common SecureCall client API communication functions into a separate library. This change is seamless and will not impact the functionality of the Web Component.

Additionally, some error messages displayed during specific network outage conditions have been updated. These changes are purely cosmetic and do not affect performance.

### **Deployment Schedule**

The update will be deployed during the following maintenance window:

###  APAC: Thursday, 6 February 2025, 10:00 PM – Friday, 7 February, 12:00 AM (AEDT)

 UK: Friday, 7 February 2025, 5:00 AM – 7:00 AM (AEDT)

 US: Friday, 7 February 2025, 8:00 PM – 10:00 PM (AEDT)

If you have any questions, please reach out to our support team.</p>
<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>11:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Incident/cm3tnltxd00etbi9ofmrq896h</id>
  <published>2024-11-23T04:12:05.483+00:00</published>
  <updated>2024-11-23T04:12:05.483+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/incident/cm3tnltxd00etbi9ofmrq896h"/>
  <title>Failure to Secure Calls using Webex Calling</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 hours and 14 minutes</p>
    <p><strong>Affected Components:</strong> Payment Services</p>
    <p><small>Nov <var data-var='date'> 23</var>, <var data-var='time'>04:12:05</var> GMT+0</small><br /><strong>Identified</strong> -
  We have identified an issue with Webex Calling where calls are unable to be secured. Our team is currently investigating this in collaboration with our carrier partners..</p>
<p><small>Nov <var data-var='date'> 23</var>, <var data-var='time'>05:01:16</var> GMT+0</small><br /><strong>Identified</strong> -
  The issue has been identified as an intermittent request timeout from Cisco Calling APIs within the Cisco Webex platform..</p>
<p><small>Nov <var data-var='date'> 23</var>, <var data-var='time'>06:52:39</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We have implemented a workaround and are currently monitoring the result..</p>
<p><small>Nov <var data-var='date'> 23</var>, <var data-var='time'>22:26:28</var> GMT+0</small><br /><strong>Resolved</strong> -
  Cisco has confirmed that there was an incident impacting Australia&#039;s Calling Data Centers, which caused slower response times. The issue has been resolved now.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Incident/cm3pn0emq00017gop00gafh9k</id>
  <published>2024-11-20T08:44:20.664+00:00</published>
  <updated>2024-11-20T09:45:17.516+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/incident/cm3pn0emq00017gop00gafh9k"/>
  <title>APAC - Service Degradation</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 1 minute</p>
    <p><strong>Affected Components:</strong> Voice Services</p>
    <p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>09:45:17</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Nov <var data-var='date'> 20</var>, <var data-var='time'>08:44:20</var> GMT+0</small><br /><strong>Identified</strong> -
  Customers in the APAC region may experience service degradation with Secure Call Services due to an issue with the core voice switching platform..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Incident/cm2nuwpxa000kroismffjyy6n</id>
  <published>2024-10-24T18:09:00.000+00:00</published>
  <updated>2024-10-24T18:09:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/incident/cm2nuwpxa000kroismffjyy6n"/>
  <title>Change to Web component may affect your SecureCall integration</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 2 minutes</p>
    <p><strong>Affected Components:</strong> Payment Services</p>
    <p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>18:09:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  A recent change in our web component may affect your SecureCall integration. This change could potentially cause a break in the integration, leading to issues with functionality..</p>
<p><small>Oct <var data-var='date'> 24</var>, <var data-var='time'>22:11:02</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. Change was rolled back.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Maintenance/clxu00voz53138bbmxifahbecm</id>
  <published>2024-06-26T18:00:00.000+00:00</published>
  <updated>2024-06-26T18:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/maintenance/clxu00voz53138bbmxifahbecm"/>
  <title>Updates to Message Broker UK/EU</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Payment Services</p>
    <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>18:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled maintenance to Message Broker, Payment services will be unavailable during this time..</p>
<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Maintenance/clxtzue0f47265bjmxydvd8dqn</id>
  <published>2024-06-26T09:00:00.000+00:00</published>
  <updated>2024-06-26T11:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/maintenance/clxtzue0f47265bjmxydvd8dqn"/>
  <title>Updates to Message Broker AU/US</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> Payment Services</p>
    <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled maintenance to Message Broker, Payment services will be unavailable during this time..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Incident/cltgfltm194134bblrd9r9pq8l</id>
  <published>2024-03-06T22:30:00.000+00:00</published>
  <updated>2024-03-06T22:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/incident/cltgfltm194134bblrd9r9pq8l"/>
  <title>APAC - Payment and Voice Services Impacted </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 24 minutes</p>
    <p><strong>Affected Components:</strong> Payment Services, Voice Services</p>
    <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>22:30:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We identified an issue with payment and voice services in APAC region. Teams are working on a fix for this event..</p>
<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>23:54:14</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Incident/clsju1rez8719beojzqnzhdhk</id>
  <published>2024-02-09T09:53:00.000+00:00</published>
  <updated>2024-02-09T09:53:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/incident/clsju1rez8719beojzqnzhdhk"/>
  <title>Payment Services not able to connect to database </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 hours and 53 minutes</p>
    <p><strong>Affected Components:</strong> Payment Services</p>
    <p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>09:53:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  .</p>
<p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.securecall.cloud,2005:Maintenance/clq3r5er226990btoim58lvgxb</id>
  <published>2023-12-14T06:00:00.000+00:00</published>
  <updated>2023-12-14T06:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.securecall.cloud/maintenance/clq3r5er226990btoim58lvgxb"/>
  <title>User Interface update at https://client.securecall.cloud/</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day and 33 minutes</p>
    <p><strong>Affected Components:</strong> Payment Services, Voice Services</p>
    <p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>06:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Dec <var data-var='date'> 15</var>, <var data-var='time'>06:32:48</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Dec <var data-var='date'> 14</var>, <var data-var='time'>06:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  **Planned Works:** SecureCall is receiving a new look and feel in its user interface. The new interface will be deployed for those SecureCall customers who use the ‘stand-alone’ web user interface to take customer payments-by-phone. No functional differences have been made. A new user guide is available for staff to familiarise themselves. This update does not affect those customers who have embedded the
SecureCall client within their own applications.

**BroadSource Change Record:** CR25

**Supporting Material:** A new User guide can be found at [https://www.broadsource.com.au/securecall/client-user-guide/](url)
.</p>

        ]]>
  </content>
</entry>

</feed>