Secured Signing Outage History
Secured Signing is up right nowSecured Signing had 5 outages in the last 2 years totaling 22h 23m of downtime, averaging 0.2 incidents per month.
There were 5 Secured Signing outages since March 3, 2025 totaling 22h 23m of downtime. Each is summarised below. Incident details, duration, and resolution information.
UK Region Only - Azure Front Door network issue
Timeline · 4 updates
- investigating Dec 15, 2025, 09:37 AM UTC
We are currently investigating this issue.
- investigating Dec 15, 2025, 10:19 AM UTC
We are continuing to investigate this issue.
- monitoring Dec 15, 2025, 10:49 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 15, 2025, 10:52 AM UTC
This incident has been resolved.
Secured signing all Regions - Azure Access Issues- DNS
Timeline · 10 updates
[NZ Region] Integration User Connection
Timeline · 6 updates
- 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.
- identified Sep 22, 2025, 11:18 PM UTC
The issue has been identified and a fix is being implemented.
- identified Sep 23, 2025, 01:55 AM UTC
We are continuing to work on a fix for this issue.
- identified Sep 23, 2025, 02:55 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Sep 23, 2025, 03:43 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 23, 2025, 03:59 AM UTC
This incident has been resolved.
Secured Signing Website US Region upload files is not working well
Timeline · 7 updates
- investigating Mar 03, 2025, 07:09 PM UTC
We are currently investigating this issue.
- investigating Mar 03, 2025, 07:11 PM UTC
We are continuing to investigate this issue.
- investigating Mar 03, 2025, 07:28 PM UTC
We are continuing to investigate this issue.
- investigating Mar 03, 2025, 08:00 PM UTC
We are continuing to investigate this issue.
- identified Mar 03, 2025, 08:16 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Mar 03, 2025, 08:41 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 03, 2025, 08:44 PM UTC
This incident has been resolved.