Secured Signing Outage History

Started Jun 25, 2026, 08:04 AM UTC· resolved Jun 25, 2026, 05:40 PM UTC

1. investigating Jun 25, 2026, 08:04 AM UTC

   Update - We are investigating an issue impacting outbound message delivery across all regions. Customers will experience delays in message processing and delivery, with message statuses remaining in "Enroute" for longer than expected. This issue is affecting outbound message sending across our platform. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available.

2. investigating Jun 25, 2026, 08:17 AM UTC

   An update has been posted We are still investigating an issue impacting outbound message delivery and engaging additional resources to help restore normal service as quickly as possible. Further updates will be provided as more information becomes available.

3. identified Jun 25, 2026, 08:57 AM UTC

   Update - Our SMS service partner identified an issue within the internal systems responsible for routing messages to downstream mobile network operators. Since approximately 14:30 AEST, messages within our platform have been intermittently becoming stuck in a router worker process, resulting in delays to outbound message delivery. While the issue is ongoing, small batches of queued messages are continuing to be processed and delivered approximately every few minutes. Customers may also observe duplicate message deliveries in some cases as a result of this issue. Our engineering teams are actively investigating the root cause and working to restore normal service as quickly as possible. Once the issue has been resolved, we expect queued messages to resume processing and be delivered automatically. We will provide further updates as more information becomes available.

4. identified Jun 25, 2026, 09:58 AM UTC

   Update - Our partner team investigation is ongoing, and we have not yet been able to definitively identify the root cause of the issue affecting outbound message delivery within the platform. To prevent further message backlog growth and reduce the risk of additional duplicate deliveries, we have implemented the following mitigation measures: Message submissions are being temporarily blocked and will return Failed responses. Message workers have been stopped to prevent further processing of impacted traffic. Queued messages are being redirected to a new queue for post-incident analysis and recovery efforts. Customers using SMPP may still be able to submit messages during this period. As a result, some message duplication may continue to occur until the incident is fully resolved. As part of our recovery strategy, messages queued from the start of the incident will not be automatically reprocessed. While some of these messages may already have been successfully delivered after experiencing delays, others may not have been sent. Customers should be aware that message reconciliation and potential resubmission may be required once service has been restored. Our engineering teams remain actively engaged in identifying the root cause and restoring normal service. We will continue to provide updates as new information becomes available.

5. monitoring Jun 25, 2026, 05:39 PM UTC

   A fix has been implemented, and we are monitoring the results.

6. monitoring Jun 25, 2026, 05:39 PM UTC

   A fix has been implemented and messaging services have recovered. We have completed validation testing and confirmed message sending and delivery are functioning as expected. Our teams will continue to closely monitor platform performance to ensure stability. We are not currently observing any further issues related to this incident.

7. resolved Jun 25, 2026, 05:40 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 15, 2025, 09:37 AM UTC· resolved Dec 15, 2025, 10:52 AM UTC

1. investigating Dec 15, 2025, 09:37 AM UTC

   We are currently investigating this issue.

2. investigating Dec 15, 2025, 10:19 AM UTC

   We are continuing to investigate this issue.

3. monitoring Dec 15, 2025, 10:49 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Dec 15, 2025, 10:52 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 29, 2025, 04:44 PM UTC· resolved Oct 29, 2025, 09:59 PM UTC

1. investigating Oct 29, 2025, 04:44 PM UTC

   Azure (Microsoft - Global Data Center provider) is experiencing DNS issues resulting in availability degradation of some services. Customers may experience issues accessing the Azure Portal. We have taken action that is expected to address the portal access issues here shortly. We are actively investigating the underlying issue and additional mitigation actions.

2. investigating Oct 29, 2025, 04:46 PM UTC

   We are continuing to investigate this issue.

3. investigating Oct 29, 2025, 05:24 PM UTC

   Azure is experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. This issue affecting our service,

4. investigating Oct 29, 2025, 06:55 PM UTC

   Azure team - We have initiated the deployment of our last known good configuration of Front Door, which is expected to complete A.S.A.P. We do not yet have an ETA for full mitigation, but we will provide another update once the deployment has completed.

5. identified Oct 29, 2025, 07:26 PM UTC

   The issue has been identified and a fix is being implemented.

6. identified Oct 29, 2025, 07:46 PM UTC

   Azure Notification We are actively working to recover affected nodes and anticipate full mitigation within the next four hours. Some customers may be able to log in; however, service delays are expected during this recovery period. We will provide further updates as soon as more information becomes available.

7. identified Oct 29, 2025, 08:35 PM UTC

   We are continuing to work on a fix for this issue.

8. identified Oct 29, 2025, 08:45 PM UTC

   We are continuing to work on a fix for this issue.

9. monitoring Oct 29, 2025, 09:32 PM UTC

   A fix has been implemented and we are monitoring the results.

10. resolved Oct 29, 2025, 09:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Sep 22, 2025, 11:16 PM UTC· resolved Sep 23, 2025, 03:59 AM UTC

1. investigating Sep 22, 2025, 11:16 PM UTC

   We are currently investigating an issue affecting some integrations like JobAdder, Bullhorn, Sharepoint and others, in New Zealand Region Only. This is related to Integration User Connection.

2. identified Sep 22, 2025, 11:18 PM UTC

   The issue has been identified and a fix is being implemented.

3. identified Sep 23, 2025, 01:55 AM UTC

   We are continuing to work on a fix for this issue.

4. identified Sep 23, 2025, 02:55 AM UTC

   We are continuing to work on a fix for this issue.

5. monitoring Sep 23, 2025, 03:43 AM UTC

   A fix has been implemented and we are monitoring the results.

6. resolved Sep 23, 2025, 03:59 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 03, 2025, 07:09 PM UTC· resolved Mar 03, 2025, 08:44 PM UTC

1. investigating Mar 03, 2025, 07:09 PM UTC

   We are currently investigating this issue.

2. investigating Mar 03, 2025, 07:11 PM UTC

   We are continuing to investigate this issue.

3. investigating Mar 03, 2025, 07:28 PM UTC

   We are continuing to investigate this issue.

4. investigating Mar 03, 2025, 08:00 PM UTC

   We are continuing to investigate this issue.

5. identified Mar 03, 2025, 08:16 PM UTC

   The issue has been identified and a fix is being implemented.

6. monitoring Mar 03, 2025, 08:41 PM UTC

   A fix has been implemented and we are monitoring the results.

7. resolved Mar 03, 2025, 08:44 PM UTC

   This incident has been resolved.

Read the full incident report →