Third-party Signature Platform (Dropbox Sign) is currently experiencing an issue.
- monitoring
An incident affecting Dropbox Sign is currently on-going. We will provide updates as they come.
- resolved
The incident with Dropbox Sign has been resolved.
38 recorded Ironclad incidents since January 2026, with official updates, affected components, duration and resolution information.
An incident affecting Dropbox Sign is currently on-going. We will provide updates as they come.
The incident with Dropbox Sign has been resolved.
Users with preferred language settings that is causing latency and long load times when users switch their preferred language to anything other than English (US). Our team is working to implement a fix to resolve the issue.
We have resolved the issue.
Ironclad is currently experiencing an issue with our Email sub-processor which can cause delays or failures in receiving inbound emails related to notifications, workflow activity feed, and email reminders.
We have identified the issue related to one of our Email Sub-Processors and are working to implement a fix.
We have resolved the issue with our Email Sub-Processor, and you should now see inbound emails deliver.
We have identified an issue with Mailgun which is currently affecting the Ironclad Platform. During this time there could be unexpected delays or failures in sending or receiving Notification Emails, Reminder Emails, and Signature Emails within the Ironclad Platform. As soon as this issue has been resolved we will report back.
We have taken steps to address the email errors and we are continuing to monitor for any further issues.
We have addressed the issue causing workflows to reach an error state and are actively working on resolving workflows impacted.
Ironclad is experiencing an issue where customers residing outside of the U.S. may experience latency and long load times. We are actively investigating this issue and identifying a resolution.
We have identified an issue with our preferred language settings that is causing latency and long load times when users switch their preferred language to anything other than English. Our team is working to implement a fix to resolve the issue.
Our team has deployed a fix and all users can now use their preferred language setting without experiencing latency or long load times.
Our team has deployed a fix and all users can now use their preferred language setting without experiencing latency or long load times.
Users may experience slightly longer load times and general latency when taking actions within the Ironclad platform. Our team is investigating this issue, which we believe may be related to a disruption at our cloud infrastructure provider, and is working to confirm the root cause.
The issue has been fully resolved. Our team identified the root cause as a disruption at our cloud infrastructure provider, which was causing longer load times and general latency across the Ironclad platform. Performance has returned to normal; all systems are now operating as expected. Thank you for your patience throughout this incident and please reach out if you continue to experience any issues.
Ironclad is experience technical issues at the moment. We are aware the platform is inaccessible and we are working as quickly as possible to address this.
We've successfully resolved this incident. We are fully back online.
Ironclad experienced a technical issue with rollout of our new Global Conditions feature. The team quickly disabled the feature to safely address and re-enable the feature. We'll post here once Global Conditions is re-enabled.
Our team is still working towards redeploying our Global Conditions feature. We'll update our statuspage once this is complete. All systems are fully online.
Thank you for patience. We've successfully rolled out our new Global Conditions feature across all Environments.
We are actively investigating this issue an issue with Public Workflows. Currently if someone attempts to submit a Public Workflow they will receive a Form Validation Error.
This issue has been resolved and all Public Workflows can be submitted as intended.
At the moment, Acrobat Services is experiencing technical difficulties which negatively impact's Ironclad's PDF -> DOCX conversion feature. We are monitoring their incident closely and will update our statuspage once Adobe's incident is resolved.
Adobe has resolved their incident. Ironclad's PDF -> DOCX conversion services are fully restored.
We are tracking a cross-customer performance issue with intermittent latency and loading failures across Production and Demo environments.
We continuing to investigate intermittent performance issues affecting some customers when using Ironclad. Our team is actively investigating the cause and working toward a resolution. We appreciate your patience and will provide another update as more information becomes available.
We are continuing to monitor and investigate the latency issues and will provide updates when available.
We have resolved the intermittent latency and loading failures across all environments
We are investigating elevated error rates affecting Smart Import contract recognition. Our team confirmed this is tied to an upstream OpenAI incident that has been acknowledged by their team. Smart Import request processing has partially recovered, but contract type extraction remains disabled while we validate service stability. We are actively monitoring the upstream service and will post another update once full functionality is restored.
As of 5pm, availability of OpenAI services has improved and we are continuing to monitor.
OpenAI has resolved the issue affecting Smart Import contract recognition. We will continue to monitor, but all impacted functionality has been restored.
Conversational Search is experiencing degraded performance. We are continuing to investigate.
Search is operating normally.
We are actively investigating an issue affecting entity and counterparty search on workflow launch forms in production. Some customers may see “no matching options” when selecting an entity for their counterparty, which prevents certain workflows from being launched.
We've confirmed that the issue is tied to bad logic underlying how the Entity picker displays options to select. We are working on a fix to address this bad logic and making it available on Production as soon as we can.
We have implemented a fix for the issue affecting entity and counterparty search on workflow launch forms in production. We are seeing recovery and are continuing to monitor closely to confirm stable performance across impacted workflows.
We have resolved the issue affecting entity and counterparty search on workflow launch forms in production. Customers will now be able to search for and select counterparties normally when launching impacted workflows. We will continue to review the incident internally.
We are investigating an issue affecting Clickwrap. Impacted customers may see workflow processing failures or errors during submission. Our team is actively investigating and we will share another update as soon as we have more information.
We have implemented mitigation and are seeing recovery in Clickwrap. We are monitoring the platform closely while additional background services are brought back online. During the incident, impacted customers may have experienced workflow processing failures or errors during submission.
The issue affecting Clickwrap has been mitigated and service has been restored. During the incident, impacted customers may have experienced workflow processing failures or errors during submission. We will continue to review the incident internally to confirm full stability.
We are currently investigating an issue affecting the Ironclad Salesforce Managed Package where users may experience failures with document and approval syncing. This includes documents not syncing to and from Salesforce and approvals not reflecting correctly within the Ironclad Approval object. Our engineering team is actively working to identify the root cause. We will provide updates here as more information becomes available. Thank you for your patience.
We are currently investigating an issue affecting the Ironclad Salesforce Managed Package where users may experience failures with document and approval syncing. This includes documents not syncing to and from Salesforce and approvals not reflecting correctly within the Ironclad Approval object. Our engineering team is actively working to identify the root cause. We will provide updates here as more information becomes available. Thank you for your patience.
A code fix to address the syncing issue between Ironclad and Salesforce affecting documents and approvals has been deployed. We are actively monitoring that the fix is performing as expected.
Our engineering team has confirmed that the code fix deployed to address the syncing issue between Ironclad and Salesforce is working as expected. Documents and approvals are now syncing successfully. This incident is resolved.
End users reported that they are unable to access records within Ironclad Repository. We identified the issue and implemented a fix and now all users can view records as intended.
End users reported that they are unable to access records within Ironclad Repository. We identified the issue and implemented a fix and now all users can view records as intended.
A fix has been implemented and the incident has been resolved. API requests are no longer receiving intermittent 502 error responses.
API requests are experiencing intermittent 502 server error responses.
We are investigating an issue affecting some customers in **NA1 production** where **bulk** **document download, dashboard export, and preview actions are failing**. We have identified elevated errors in the document service and are actively working to mitigate the issue. Our current investigation indicates the problem is related to backend database latency impacting dependent document-processing jobs. We will share another update as soon as we have more information.
We've made changes on the backend to address the issues with downloads and exports and are monitoring for any further issues.
We have verified and confirmed that the issue has been resolved
Ironclad is currently experiencing Latency in platform. This may cause issues with updating workflows and records with users seeing an error ("Something is not working").
We have resolved all latency issues in Production.