Ironclad Outage History

Ironclad is up right now

Ironclad had 39 outages in the last 2 years — averaging 1.6 incidents per month.

There were 39 Ironclad outages since October 8, 2025. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ironcladapp.com

Minor September 4, 2026

Regional Language latency

Detected by Pingoru
Sep 04, 2026, 05:25 AM UTC
Resolved
Sep 04, 2026, 05:25 AM UTC
Duration
—
Affected: RepositoryWorkflows
Timeline · 2 updates
  1. investigating Sep 04, 2026, 01:54 AM UTC

    Status: Investigating 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. Affected components Repository (Degraded performance) Workflows (Degraded performance) Repository (Degraded performance) Workflows (Degraded performance)

  2. resolved Sep 04, 2026, 05:25 AM UTC

    Status: Resolved We have resolved the issue. Affected components Repository (Operational) Workflows (Operational) Repository (Operational) Workflows (Operational)

Read the full incident report →

Minor August 28, 2026

Inbound Email Delivery Delays or Failures

Detected by Pingoru
Aug 28, 2026, 07:22 PM UTC
Resolved
Aug 28, 2026, 07:22 PM UTC
Duration
—
Affected: RepositoryWorkflowsWorkflowsmailgun Inbound email processing
Timeline · 3 updates
  1. investigating Aug 28, 2026, 03:34 PM UTC

    Status: Investigating 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. Affected components mailgun Inbound email processing (Degraded performance) Repository (Degraded performance) Workflows (Degraded performance)

  2. identified Aug 28, 2026, 04:53 PM UTC

    Status: Identified We have identified the issue related to one of our Email Sub-Processors and are working to implement a fix. Affected components mailgun Inbound email processing (Degraded performance) Repository (Degraded performance) Workflows (Degraded performance)

  3. resolved Aug 28, 2026, 07:22 PM UTC

    Status: Resolved We have resolved the issue with our Email Sub-Processor, and you should now see inbound emails deliver. Affected components mailgun Inbound email processing (Operational) Repository (Operational) Workflows (Operational)

Read the full incident report →

Minor August 28, 2026

Email & Workflow Errors

Detected by Pingoru
Aug 28, 2026, 01:52 AM UTC
Resolved
Aug 28, 2026, 01:52 AM UTC
Duration
—
Affected: WorkflowsWorkflowsmailgun SMTPmailgun Outbound Deliverymailgun Inbound email processing
Timeline · 3 updates
  1. investigating Aug 27, 2026, 09:06 PM UTC

    Status: Investigating 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. Affected components mailgun SMTP (Full outage) mailgun Inbound email processing (Full outage) mailgun Outbound Delivery (Full outage)

  2. monitoring Aug 27, 2026, 09:58 PM UTC

    Status: Monitoring We have taken steps to address the email errors and we are continuing to monitor for any further issues. Affected components mailgun SMTP (Operational) mailgun Inbound email processing (Operational) mailgun Outbound Delivery (Operational)

  3. resolved Aug 28, 2026, 01:52 AM UTC

    Status: Resolved We have addressed the issue causing workflows to reach an error state and are actively working on resolving workflows impacted. Affected components mailgun Outbound Delivery (Operational) Workflows (Operational) mailgun SMTP (Operational) mailgun Inbound email processing (Operational)

Read the full incident report →

Minor August 25, 2026

Ironclad Regional Latency

Detected by Pingoru
Aug 25, 2026, 05:08 PM UTC
Resolved
Aug 25, 2026, 05:08 PM UTC
Duration
—
Affected: RepositoryWorkflowsWorkflows
Timeline · 4 updates
  1. investigating Aug 25, 2026, 01:53 PM UTC

    Status: Investigating 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. Affected components Workflows (Degraded performance) Repository (Degraded performance) Workflows (Degraded performance) Repository (Degraded performance)

  2. identified Aug 25, 2026, 03:39 PM UTC

    Status: Identified 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. Affected components Repository (Degraded performance) Workflows (Degraded performance) Repository (Degraded performance) Workflows (Degraded performance)

  3. monitoring Aug 25, 2026, 04:49 PM UTC

    Status: Monitoring Our team has deployed a fix and all users can now use their preferred language setting without experiencing latency or long load times. Affected components Repository (Degraded performance) Workflows (Degraded performance) Repository (Degraded performance) Workflows (Degraded performance)

  4. resolved Aug 25, 2026, 05:08 PM UTC

    Status: Resolved Our team has deployed a fix and all users can now use their preferred language setting without experiencing latency or long load times. Affected components Repository (Operational) Workflows (Operational) Repository (Operational) Workflows (Operational)

Read the full incident report →

Minor August 20, 2026

Latency & Platform Slowness

Detected by Pingoru
Aug 20, 2026, 05:03 PM UTC
Resolved
Aug 20, 2026, 05:03 PM UTC
Duration
—
Affected: RepositoryWorkflowsWorkflows
Timeline · 3 updates
  1. investigating Aug 20, 2026, 04:11 PM UTC

    Status: Investigating Users may experience slightly longer load times and general latency when taking actions within the Ironclad platform. Our team is currently investigating this issue and working to identify the root cause. Affected components Repository (Degraded performance) Workflows (Degraded performance) Repository (Degraded performance) Workflows (Degraded performance)

  2. monitoring Aug 20, 2026, 05:22 PM UTC

    Status: Monitoring System performance and load times are improving across the platform. We are actively monitoring the resolution. Affected components Repository (Operational) Workflows (Operational) Repository (Operational) Workflows (Operational)

  3. resolved Aug 20, 2026, 06:01 PM UTC

    Status: Resolved 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. Affected components Workflows (Operational) Repository (Operational) Workflows (Operational) Repository (Operational)

Read the full incident report →

Minor August 18, 2026

Ironclad is down

Detected by Pingoru
Aug 18, 2026, 10:39 PM UTC
Resolved
Aug 18, 2026, 10:39 PM UTC
Duration
—
Affected: RepositoryWorkflowsRepositoryWorkflows
Timeline · 3 updates
  1. investigating Aug 18, 2026, 10:21 PM UTC

    Status: Investigating 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. Affected components Repository (Full outage) Workflows (Full outage)

  2. monitoring Aug 18, 2026, 10:40 PM UTC

    Status: Monitoring Thank you for patience, we are back online. We will continue to monitor closely to ensure we're confident this is fully resolved. Affected components Repository (Operational) Workflows (Operational)

  3. resolved Aug 18, 2026, 11:07 PM UTC

    Status: Resolved We've successfully resolved this incident. We are fully back online. Affected components Repository (Operational) Workflows (Operational)

Read the full incident report →

Minor August 14, 2026

Global Conditions Issue

Detected by Pingoru
Aug 14, 2026, 08:55 PM UTC
Resolved
Aug 14, 2026, 08:55 PM UTC
Duration
—
Affected: RepositoryWorkflowsRepositoryWorkflows
Timeline · 3 updates
  1. identified Aug 13, 2026, 07:01 PM UTC

    Status: Identified 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. Affected components Repository (Degraded performance)

  2. identified Aug 14, 2026, 01:02 AM UTC

    Status: Identified 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. Affected components Repository (Operational) Workflows (Operational) Workflows (Operational)

  3. resolved Aug 14, 2026, 08:55 PM UTC

    Status: Resolved Thank you for patience. We've successfully rolled out our new Global Conditions feature across all Environments. Affected components Workflows (Operational) Workflows (Operational) Repository (Operational)

Read the full incident report →

Minor August 12, 2026

Public Workflows Form Validation Error

Detected by Pingoru
Aug 12, 2026, 02:57 PM UTC
Resolved
Aug 12, 2026, 02:57 PM UTC
Duration
—
Affected: WorkflowsWorkflows
Timeline · 2 updates
  1. investigating Aug 12, 2026, 01:59 PM UTC

    Status: Investigating 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. Affected components Workflows (Partial outage) Workflows (Partial outage)

  2. resolved Aug 12, 2026, 02:17 PM UTC

    Status: Resolved This issue has been resolved and all Public Workflows can be submitted as intended. Affected components Workflows (Operational) Workflows (Operational)

Read the full incident report →

Minor August 8, 2026

Acrobat Services incident

Detected by Pingoru
Aug 08, 2026, 12:12 AM UTC
Resolved
Aug 08, 2026, 12:12 AM UTC
Duration
—
Affected: 3rd Party Dependencies
Timeline · 2 updates
  1. monitoring Aug 07, 2026, 06:09 PM UTC

    Status: Monitoring 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. Affected components 3rd Party Dependencies (Degraded performance)

  2. resolved Aug 08, 2026, 12:54 AM UTC

    Status: Resolved Adobe has resolved their incident. Ironclad's PDF -> DOCX conversion services are fully restored. Affected components 3rd Party Dependencies (Operational)

Read the full incident report →

Minor August 6, 2026

Latency issues on Production

Detected by Pingoru
Aug 06, 2026, 07:39 AM UTC
Resolved
Aug 06, 2026, 07:39 AM UTC
Duration
—
Affected: RepositoryWorkflowsRepositoryWorkflows
Timeline · 4 updates
  1. investigating Aug 05, 2026, 06:51 PM UTC

    Status: Investigating We are tracking a cross-customer performance issue with intermittent latency and loading failures across Production and Demo environments. Affected components Workflows (Degraded performance) Repository (Degraded performance) Workflows (Degraded performance) Repository (Degraded performance)

  2. monitoring Aug 05, 2026, 09:24 PM UTC

    Status: Monitoring 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. Affected components Repository (Degraded performance) Workflows (Degraded performance) Repository (Degraded performance) Workflows (Degraded performance)

  3. monitoring Aug 05, 2026, 10:09 PM UTC

    Status: Monitoring We are continuing to monitor and investigate the latency issues and will provide updates when available. Affected components Workflows (Operational) Repository (Operational) Workflows (Operational) Repository (Operational)

  4. resolved Aug 06, 2026, 05:02 PM UTC

    Status: Resolved We have resolved the intermittent latency and loading failures across all environments Affected components Repository (Operational) Workflows (Operational) Repository (Operational) Workflows (Operational)

Read the full incident report →

Minor July 29, 2026

Smart Import Issues with contract recognition

Detected by Pingoru
Jul 29, 2026, 02:38 AM UTC
Resolved
Jul 29, 2026, 02:38 AM UTC
Duration
—
Affected: RepositoryRepositoryAI Dependencies
Timeline · 3 updates
  1. investigating Jul 28, 2026, 11:15 PM UTC

    Status: Investigating 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. Affected components AI Dependencies (Full outage) Repository (Partial outage) Repository (Partial outage)

  2. monitoring Jul 29, 2026, 12:00 AM UTC

    Status: Monitoring As of 5pm, availability of OpenAI services has improved and we are continuing to monitor. Affected components AI Dependencies (Degraded performance) Repository (Degraded performance) Repository (Degraded performance)

  3. resolved Jul 29, 2026, 02:38 AM UTC

    Status: Resolved OpenAI has resolved the issue affecting Smart Import contract recognition. We will continue to monitor, but all impacted functionality has been restored. Affected components Repository (Operational) Repository (Operational) AI Dependencies (Operational)

Read the full incident report →

Minor July 21, 2026

Search is experiencing degraded performance

Detected by Pingoru
Jul 21, 2026, 11:45 PM UTC
Resolved
Jul 21, 2026, 11:45 PM UTC
Duration
—
Timeline · 2 updates
  1. investigating Jul 21, 2026, 11:19 PM UTC

    Status: Investigating Conversational Search is experiencing degraded performance. We are continuing to investigate.

  2. resolved Jul 21, 2026, 11:45 PM UTC

    Status: Resolved Search is operating normally.

Read the full incident report →

Minor July 8, 2026

Entity lookup returning "no matching options"

Detected by Pingoru
Jul 08, 2026, 10:12 PM UTC
Resolved
Jul 08, 2026, 10:12 PM UTC
Duration
—
Affected: WorkflowsWorkflows
Timeline · 4 updates
  1. investigating Jul 08, 2026, 05:30 PM UTC

    Status: Investigating 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. Affected components Workflows (Degraded performance) Workflows (Degraded performance)

  2. identified Jul 08, 2026, 07:43 PM UTC

    Status: Identified 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. Affected components Workflows (Degraded performance) Workflows (Degraded performance)

  3. monitoring Jul 08, 2026, 09:19 PM UTC

    Status: Monitoring 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. Affected components Workflows (Operational) Workflows (Operational)

  4. resolved Jul 08, 2026, 10:12 PM UTC

    Status: Resolved 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. Affected components Workflows (Operational) Workflows (Operational)

Read the full incident report →

Minor July 1, 2026

Degraded performance on Clickwrap

Detected by Pingoru
Jul 01, 2026, 07:07 PM UTC
Resolved
Jul 01, 2026, 07:07 PM UTC
Duration
—
Affected: Service AvailabilityAcceptance Tracking via SendAcceptance Tracking via SMSService AvailabilityAuthentication
Timeline · 3 updates
  1. investigating Jul 01, 2026, 04:32 PM UTC

    Status: Investigating 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. Affected components Editor (HTML) (Degraded performance) Acceptance Tracking via Send (Degraded performance) Service Availability (Degraded performance) Acceptance Tracking via SMS (Degraded performance) Authentication (Degraded performance) Service Availability (Degraded performance) Editor (PDF) (Degraded performance) Authentication (OAuth 2.0) (Degraded performance) Service Availability (Degraded performance)

  2. monitoring Jul 01, 2026, 06:39 PM UTC

    Status: Monitoring 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. Affected components Service Availability (Operational) Editor (PDF) (Operational) Service Availability (Operational) Editor (HTML) (Operational) Acceptance Tracking via Send (Operational) Service Availability (Operational) Acceptance Tracking via SMS (Operational) Authentication (Operational) Authentication (OAuth 2.0) (Operational)

  3. resolved Jul 01, 2026, 07:07 PM UTC

    Status: Resolved 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. Affected components Editor (HTML) (Operational) Acceptance Tracking via Send (Operational) Service Availability (Operational) Acceptance Tracking via SMS (Operational) Authentication (Operational) Authentication (OAuth 2.0) (Operational) Service Availability (Operational) Editor (PDF) (Operational) Service Availability (Operational)

Read the full incident report →

Minor June 25, 2026

Salesforce Managed Package: Document & Approval Sync Disruption

Detected by Pingoru
Jun 25, 2026, 02:13 AM UTC
Resolved
Jun 25, 2026, 02:13 AM UTC
Duration
—
Affected: WorkflowsWorkflows
Timeline · 5 updates
  1. investigating Jun 24, 2026, 08:51 PM UTC

    Status: Investigating 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. Affected components Workflows (Degraded performance)

  2. monitoring Jun 24, 2026, 10:12 PM UTC

    Status: Monitoring Our engineering team has reverted a code change in platform to ensure all documents and approvals can sync between Ironclad and Salesforce. Affected components Workflows (Degraded performance)

  3. identified Jun 24, 2026, 10:28 PM UTC

    Status: Identified 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. Affected components Workflows (Degraded performance)

  4. monitoring Jun 25, 2026, 01:09 AM UTC

    Status: Monitoring 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. Affected components Workflows (Operational)

  5. resolved Jun 25, 2026, 02:13 AM UTC

    Status: Resolved 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. Affected components Workflows (Operational)

Read the full incident report →

Minor June 17, 2026

Records Accessibility Issues

Detected by Pingoru
Jun 17, 2026, 04:30 PM UTC
Resolved
Jun 17, 2026, 04:30 PM UTC
Duration
—
Affected: Version PublishedRepositoryBox Uploads/Downloads3rd Party DependenciesWorkflowsRepositorySendGrid Event WebhookAI DependenciesWorkflowsFetching & Rendering Dynamic GroupsEmailService AvailabilityAcceptance Tracking via SendAcceptance Tracking via SMSHosting AvailabilityCustom Domains with SSLmailgun SMTPmailgun Outbound Deliverymailgun Inbound email processingGoogle Apps DriveGoogle Cloud Platform Google Cloud StorageGoogle Cloud Platform Google Cloud SQLGoogle Cloud Platform Google Kubernetes EngineGoogle Cloud Platform Google Cloud DNSGoogle Cloud Platform Cloud FilestoreGoogle Cloud Platform Cloud Key Management ServiceService AvailabilityService AvailabilityAuthenticationCapturing AcceptanceLoading & Displaying Published GroupsDelivering Confirmation Emails to SignersDelivering Notification Emails to UsersShare Records via EmailScheduled Nightly ExportsRequest CompleteRequest SentRequest SignedSMSInboundOktaGoogleCustom SSOSendGrid API v3
Timeline · 2 updates

Read the full incident report →

Minor June 4, 2026

Intermittent 502 Errors on API Requests

Detected by Pingoru
Jun 04, 2026, 03:07 PM UTC
Resolved
Jun 04, 2026, 03:07 PM UTC
Duration
—
Affected: Version PublishedRepositoryBox Uploads/Downloads3rd Party DependenciesWorkflowsRepositorySendGrid Event WebhookAI DependenciesWorkflowsFetching & Rendering Dynamic GroupsEmailService AvailabilityAcceptance Tracking via SendAcceptance Tracking via SMSHosting AvailabilityCustom Domains with SSLmailgun SMTPmailgun Outbound Deliverymailgun Inbound email processingGoogle Apps DriveGoogle Cloud Platform Google Cloud StorageGoogle Cloud Platform Google Cloud SQLGoogle Cloud Platform Google Kubernetes EngineGoogle Cloud Platform Google Cloud DNSGoogle Cloud Platform Cloud FilestoreGoogle Cloud Platform Cloud Key Management ServiceService AvailabilityService AvailabilityAuthenticationCapturing AcceptanceLoading & Displaying Published GroupsDelivering Confirmation Emails to SignersDelivering Notification Emails to UsersShare Records via EmailScheduled Nightly ExportsRequest CompleteRequest SentRequest SignedSMSInboundOktaGoogleCustom SSOSendGrid API v3
Timeline · 2 updates

Read the full incident report →

Minor June 3, 2026

Bulk Document Download, Dashboard Exports and Preview Degraded in NA1 Production

Detected by Pingoru
Jun 03, 2026, 08:10 PM UTC
Resolved
Jun 03, 2026, 08:10 PM UTC
Duration
—
Affected: RepositoryWorkflowsRepositoryWorkflows
Timeline · 3 updates
  1. identified Jun 03, 2026, 07:45 PM UTC

    Status: Identified 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. Affected components Workflows (Degraded performance) Personalized Contracts Export (CSV) (Degraded performance) Repository (Degraded performance)

  2. monitoring Jun 03, 2026, 07:57 PM UTC

    Status: Monitoring We've made changes on the backend to address the issues with downloads and exports and are monitoring for any further issues. Affected components Repository (Degraded performance) Workflows (Degraded performance) Personalized Contracts Export (CSV) (Degraded performance)

  3. resolved Jun 03, 2026, 08:10 PM UTC

    Status: Resolved We have verified and confirmed that the issue has been resolved Affected components Repository (Operational) Workflows (Operational) Personalized Contracts Export (CSV) (Operational)

Read the full incident report →

Minor May 26, 2026

Latency & Error Messaging

Detected by Pingoru
May 26, 2026, 10:06 PM UTC
Resolved
May 26, 2026, 10:06 PM UTC
Duration
—
Affected: RepositoryWorkflowsRepositoryWorkflows
Timeline · 2 updates
  1. investigating May 26, 2026, 06:49 PM UTC

    Status: Investigating 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"). Affected components Repository (Degraded performance) Workflows (Degraded performance)

  2. resolved May 26, 2026, 10:06 PM UTC

    Status: Resolved We have resolved all latency issues in Production. Affected components Repository (Operational) Workflows (Operational)

Read the full incident report →

Minor May 26, 2026

Ironclad Latency

Detected by Pingoru
May 26, 2026, 04:40 PM UTC
Resolved
May 26, 2026, 04:40 PM UTC
Duration
—
Affected: Version PublishedRepositoryBox Uploads/Downloads3rd Party DependenciesWorkflowsRepositorySendGrid Event WebhookAI DependenciesWorkflowsFetching & Rendering Dynamic GroupsEmailService AvailabilityAcceptance Tracking via SendAcceptance Tracking via SMSHosting AvailabilityCustom Domains with SSLmailgun SMTPmailgun Outbound Deliverymailgun Inbound email processingGoogle Apps DriveGoogle Cloud Platform Google Cloud StorageGoogle Cloud Platform Google Cloud SQLGoogle Cloud Platform Google Kubernetes EngineGoogle Cloud Platform Google Cloud DNSGoogle Cloud Platform Cloud FilestoreGoogle Cloud Platform Cloud Key Management ServiceService AvailabilityService AvailabilityAuthenticationCapturing AcceptanceLoading & Displaying Published GroupsDelivering Confirmation Emails to SignersDelivering Notification Emails to UsersShare Records via EmailScheduled Nightly ExportsRequest CompleteRequest SentRequest SignedSMSInboundOktaGoogleCustom SSOSendGrid API v3
Timeline · 3 updates

Read the full incident report →

Minor May 12, 2026

URGENT: Pause Salesforce Managed Package Upgrades

Detected by Pingoru
May 12, 2026, 07:22 PM UTC
Resolved
May 12, 2026, 07:22 PM UTC
Duration
—
Affected: 3rd Party Dependencies
Timeline · 4 updates
  1. investigating May 12, 2026, 02:24 AM UTC

    Status: Investigating We have identified an authentication issue within the latest version of the Ironclad Salesforce Managed Package. If you have not yet upgraded, no action is required. To ensure your integration remains stable, please do not upgrade your Salesforce version until further notice. We are working on a resolution and will provide an update once the issue is resolved. If you have already upgraded and are experiencing connection issues, please reach out to our Support team for assistance. Affected components 3rd Party Dependencies (Degraded performance)

  2. identified May 12, 2026, 02:14 PM UTC

    Status: Identified The team is actively working on a fix. There will be a new managed package release coming soon (v3.7.7) that will need to be downloaded once the fix is live. Status page will be updated as soon as the new version is available to download. Affected components 3rd Party Dependencies (Degraded performance)

  3. monitoring May 12, 2026, 05:11 PM UTC

    Status: Monitoring We have addressed the issue with a new managed package v.3.7.7 which is now available for download. Affected components 3rd Party Dependencies (Operational)

  4. resolved May 12, 2026, 07:22 PM UTC

    Status: Resolved The issue has now been resolved, and the managed package is operating normally for all affected customers. Affected components 3rd Party Dependencies (Operational)

Read the full incident report →

Minor May 4, 2026

Smart Import prediction errors and issues with Workflow launch

Detected by Pingoru
May 04, 2026, 09:07 PM UTC
Resolved
May 04, 2026, 09:07 PM UTC
Duration
—
Affected: RepositoryRepository
Timeline · 3 updates
  1. investigating May 04, 2026, 07:33 PM UTC

    Status: Investigating Records uploaded with Smart Imports may encounter an error during metadata prediction processing. Affected components Repository (Degraded performance)

  2. monitoring May 04, 2026, 08:29 PM UTC

    Status: Monitoring We have deployed a fix and are no longer seeing errors. Our team will continue to monitor the situation closely to ensure everything remains stable. Affected components Repository (Operational)

  3. resolved May 04, 2026, 09:07 PM UTC

    Status: Resolved The issue has been resolved. Users can retry Smart Imports to obtain predictions as expected. Affected components Repository (Operational)

Read the full incident report →

Minor April 28, 2026

Degraded performance with document conversion subprocessor

Detected by Pingoru
Apr 28, 2026, 01:26 AM UTC
Resolved
Apr 28, 2026, 01:26 AM UTC
Duration
—
Affected: WorkflowsWorkflows
Timeline · 3 updates
  1. investigating Apr 27, 2026, 06:27 PM UTC

    Status: Investigating We are currently aware that some users may experience errors when interacting with PDFs. Our engineering team is investigating the root cause and is working toward a resolution. We will provide an update as soon as we have more information. Affected components Workflows (Degraded performance)

  2. monitoring Apr 27, 2026, 07:09 PM UTC

    Status: Monitoring A fix has been implemented, and we have confirmed that PDF interactions are now functioning as expected. We are currently monitoring the system to ensure continued stability and will provide a final update once we are fully confident the issue is resolved. Affected components Workflows (Operational)

  3. resolved Apr 28, 2026, 01:26 AM UTC

    Status: Resolved We have fully resolved the document conversion subprocessor issue. Affected components Workflows (Operational)

Read the full incident report →

Minor April 21, 2026

Blank form during workflow launch

Detected by Pingoru
Apr 21, 2026, 08:42 PM UTC
Resolved
Apr 21, 2026, 08:42 PM UTC
Duration
—
Affected: WorkflowsWorkflows
Timeline · 3 updates
  1. investigating Apr 21, 2026, 07:08 PM UTC

    Status: Investigating Reports of blank forms when launching workflows Affected components Workflows (Partial outage)

  2. investigating Apr 21, 2026, 07:30 PM UTC

    Status: Investigating Ironclad is currently experiencing an issue where users may experience issues with forms appearing blank when attempting to launch a Workflow. Affected components Workflows (Partial outage)

  3. resolved Apr 21, 2026, 08:42 PM UTC

    Status: Resolved The incident has been resolved. Affected components Workflows (Operational)

Read the full incident report →

Minor April 14, 2026

Issues with Smart Import

Detected by Pingoru
Apr 14, 2026, 11:11 PM UTC
Resolved
Apr 14, 2026, 11:11 PM UTC
Duration
—
Affected: AI Dependencies
Timeline · 4 updates
  1. investigating Apr 14, 2026, 07:47 PM UTC

    Status: Investigating We are currently investigating an issue affecting Smart Import that is causing intermittent errors for some customers. Users may see failed imports or 503 errors while attempting to process documents. Our Engineering team is actively investigating and working to restore normal performance. We will share another update as soon as we have more information. Affected components AI Depedencies (Degraded performance)

  2. monitoring Apr 14, 2026, 09:54 PM UTC

    Status: Monitoring We have deployed a mitigation for the Smart Import issue and expanded the update to all customers. We are now seeing successful responses in production and have mitigated the customer-facing errors. Our team is continuing to monitor performance closely to ensure the issue remains stable. If you continue to experience problems with Smart Import, please contact Support with the approximate time of the failure, including timezone, and any relevant screenshots. Affected components AI Depedencies (Degraded performance)

  3. monitoring Apr 14, 2026, 10:32 PM UTC

    Status: Monitoring We have deployed a mitigation for the Smart Import issue and expanded the update to all customers. Smart Import is now operating normally, and we are seeing successful responses in production. We are keeping this incident in Monitoring while our team continues to watch performance closely and confirm the issue remains stable. If you continue to experience problems with Smart Import, please contact Support with the approximate time of the failure, including timezone, and any relevant screenshots. Affected components AI Depedencies (Operational)

  4. resolved Apr 14, 2026, 11:11 PM UTC

    Status: Resolved The issue affecting Smart Import has been resolved, and the service is operating normally. We are no longer seeing the errors related to this incident. Thank you for your patience while we worked to restore service. If you continue to experience problems with Smart Import, please contact Support with the approximate time of the failure, including timezone, and any relevant screenshots. Affected components AI Depedencies (Operational)

Read the full incident report →