- Detected by Pingoru
- May 12, 2026, 02:53 PM UTC
- Resolved
- May 12, 2026, 03:56 PM UTC
- Duration
- 1h 2m
Affected: FS ID - Login Auth and Admin Panel
Timeline · 3 updates
-
investigating May 12, 2026, 02:53 PM UTC
We are currently investigating an issue where reCAPTCHA verification during login is looping back to the verification step for a limited number of accounts. Our team is actively investigating the root cause.
-
investigating May 12, 2026, 02:56 PM UTC
We are currently investigating an issue where reCAPTCHA verification during login is looping back to the verification step for a limited number of accounts. Our team is actively investigating the root cause.
-
resolved May 12, 2026, 03:56 PM UTC
The issue affecting reCAPTCHA verification during login has now been resolved. Users should be able to log in successfully without being redirected back to the verification step. We appreciate your patience while our team investigated and implemented the fix.
Read the full incident report →
- Detected by Pingoru
- May 11, 2026, 04:21 PM UTC
- Resolved
- May 11, 2026, 07:15 PM UTC
- Duration
- 2h 54m
Affected: API & Document Generation
Timeline · 4 updates
-
investigating May 11, 2026, 04:21 PM UTC
Due to recent Salesforce OAuth/security changes, some customers may experience Salesforce Delivery/authentication failures. Affected users may experience merge or delivery failures accompanied by errors such as: “INVALID_SESSION_ID: Session expired or invalid” “Could not refresh your Salesforce access token” In some cases, re-authenticating the Salesforce connection temporarily restores functionality, though reports indicate the issue may recur.Our Engineering team is actively investigating. We will continue to provide updates as we learn more.
-
identified May 11, 2026, 04:50 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 11, 2026, 05:14 PM UTC
We have implemented a fix and are currently monitoring the results.Some customers may still need to re-authenticate their Salesforce connection before Salesforce Delivery resumes successfully. If you continue to experience merge or delivery failures, please re-authenticate your Salesforce connection and retry the affected delivery. We will continue monitoring the situation and provide additional updates as needed.
-
resolved May 11, 2026, 07:15 PM UTC
This issue has been resolved. Some customers may need to re-authenticate their Salesforce connection before Salesforce Delivery resumes successfully. If you continue to experience merge or delivery failures, please re-authenticate your Salesforce connection and retry the affected delivery. We appreciate your patience while our team investigated this issue.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 06:15 PM UTC
- Resolved
- May 08, 2026, 07:06 PM UTC
- Duration
- 50m
Affected: FormsDocuments
Timeline · 3 updates
-
identified May 08, 2026, 06:15 PM UTC
We have identified an issue in Streamline workflows where workflow sessions may experience unexpected behavior when transitioning from a Forms step to a Document step with field mappings between the steps. Our team is currently working on a fix.
-
monitoring May 08, 2026, 06:41 PM UTC
We have identified an issue in Streamline workflows where workflow sessions may experience unexpected behavior when transitioning from a Forms step to a Document step with field mappings configured between the steps. A fix has been implemented, and we are currently monitoring the results.
-
resolved May 08, 2026, 07:06 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 06:11 PM UTC
- Resolved
- May 08, 2026, 06:38 PM UTC
- Duration
- 27m
Affected: Documents
Timeline · 2 updates
-
investigating May 08, 2026, 06:11 PM UTC
We are investigating reports of customers being intermittently prompted to sign in while signing Formstack Sign documents.
-
resolved May 08, 2026, 06:38 PM UTC
The issue causing some users to be intermittently prompted to sign in while signing Formstack Sign documents has been resolved. If any users continue to experience the issue, retrying the action or reopening the signing link should allow the signing process to complete successfully. We appreciate your patience while our team investigated and resolved the issue.
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 03:05 PM UTC
- Resolved
- Apr 29, 2026, 05:39 PM UTC
- Duration
- 2h 33m
Affected: Documents
Timeline · 4 updates
-
investigating Apr 29, 2026, 03:05 PM UTC
We are currently investigating an issue where the Formstack Sign API may not reflect updated document statuses after the signing process is completed. Signing workflows are completing successfully, but some integrations may not receive the correct status updates. Our team is actively working to identify and resolve the issue.
-
identified Apr 29, 2026, 03:08 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 29, 2026, 03:31 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 29, 2026, 05:39 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 01:25 PM UTC
- Resolved
- Apr 24, 2026, 01:45 PM UTC
- Duration
- 19m
Affected: FormsSessions
Timeline · 4 updates
-
investigating Apr 24, 2026, 01:25 PM UTC
We are currently investigating reports of errors affecting some Streamline projects. Impacted users may see a “Something went wrong” message while progressing through affected workflows. Our engineering teams have identified a likely frontend issue introduced in a recent deployment and are actively working to confirm root cause and prepare remediation. We will provide another update as soon as more information is available.
-
investigating Apr 24, 2026, 01:30 PM UTC
We are continuing to investigate this issue.
-
identified Apr 24, 2026, 01:30 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Apr 24, 2026, 01:45 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 12:58 PM UTC
- Resolved
- Apr 14, 2026, 01:38 PM UTC
- Duration
- 40m
Affected: CollaborationData and Data MappingNotificationsWebhooksFormsDocumentsSignStep LogicDatabase ConnectionSessionsOther
Timeline · 3 updates
-
investigating Apr 14, 2026, 12:58 PM UTC
We are investigating an issue affecting workflow sessions in Streamline (us.streamline.intellistack.app), where users may be unable to run sessions in production. Workaround: As a temporary solution, replace intellistack.app with formstack.app in Session URLs.
-
identified Apr 14, 2026, 01:17 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Apr 14, 2026, 01:38 PM UTC
The issue affecting workflow sessions in Streamline (us.streamline.intellistack.app), where users were unable to run sessions in production, has been resolved. If you continue to experience issues, please clear your browser’s DNS cache: In Chrome: chrome://net-internals/#dns → Clear host cache In other Chromium-based browsers (e.g., Edge): replace chrome:// with the appropriate scheme (e.g., edge://net-internals/#dns)
Read the full incident report →
- Detected by Pingoru
- Apr 10, 2026, 04:06 PM UTC
- Resolved
- Apr 10, 2026, 04:44 PM UTC
- Duration
- 38m
Affected: Main Application
Timeline · 4 updates
-
identified Apr 10, 2026, 04:06 PM UTC
Partial Submissions in Formstack Forms are currently unavailable. The issue has been identified, and the engineering team is actively working on implementing a fix while systems are being closely monitored.
-
monitoring Apr 10, 2026, 04:21 PM UTC
Partial Submissions in Formstack Forms were temporarily unavailable. A fix has been implemented and functionality has been restored. We are now actively monitoring the system.
-
monitoring Apr 10, 2026, 04:24 PM UTC
We are continuing to monitor for any further issues.
-
resolved Apr 10, 2026, 04:44 PM UTC
The incident occurred at 9:02 AM EST. A fix was implemented and released, restoring functionality at to 12:15 PM EST, and the issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 01:41 PM UTC
- Resolved
- Apr 07, 2026, 02:21 PM UTC
- Duration
- 39m
Affected: Main Application
Timeline · 3 updates
-
identified Apr 07, 2026, 01:41 PM UTC
We have identified the cause of an issue where customers experience a blank screen after logging in. Our team is actively working on implementing a fix.
-
monitoring Apr 07, 2026, 02:12 PM UTC
A fix has been released for the issue causing a blank screen after login. You can now be able to successfully log in and access the application.
-
resolved Apr 07, 2026, 02:21 PM UTC
This incident has been resolved. A fix was released and we have confirmed that customers are now able to log in and access the application normally.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 02:17 PM UTC
- Resolved
- Apr 01, 2026, 02:51 PM UTC
- Duration
- 34m
Affected: Other
Timeline · 3 updates
-
identified Apr 01, 2026, 02:17 PM UTC
We are currently experiencing an issue where some workflows may fail to publish. This does not impact live workflows or active sessions; however, publishing a new version may fail for some workflows. Our team has identified the root cause and prepared a fix. We are working to deploy the solution and will provide updates as progress continues.
-
identified Apr 01, 2026, 02:18 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Apr 01, 2026, 02:51 PM UTC
We have deployed a fix for the issue causing some workflow publish failures. The issue is now resolved, and publishing is functioning as expected.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2026, 05:22 PM UTC
- Resolved
- Mar 31, 2026, 07:26 PM UTC
- Duration
- 2h 3m
Affected: Documents
Timeline · 2 updates
-
investigating Mar 31, 2026, 05:22 PM UTC
We are currently investigating an issue affecting Formstack Sign that may cause failures or delays when uploading documents.
-
resolved Mar 31, 2026, 07:26 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 06:35 PM UTC
- Resolved
- Mar 30, 2026, 07:16 PM UTC
- Duration
- 40m
Affected: Workflows
Timeline · 3 updates
-
investigating Mar 30, 2026, 06:35 PM UTC
We are currently investigating an issue where some Workflows Pro customers are unable to access their Workspace. At this time, all other functionality outside of the Workspace remains operational. Our engineering team is actively working to identify the root cause. We will provide updates as more information becomes available.
-
identified Mar 30, 2026, 06:58 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Mar 30, 2026, 07:16 PM UTC
The issue affecting access to Workflows Pro Workspaces has been resolved. If you are still experiencing issues, please log out of Workflows and log back in to refresh your session. We appreciate your patience while we worked to resolve this issue.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 08:02 PM UTC
- Resolved
- Mar 19, 2026, 08:56 PM UTC
- Duration
- 54m
Affected: Documents
Timeline · 3 updates
-
investigating Mar 19, 2026, 08:02 PM UTC
We are currently investigating reports of incorrect document output in Formstack Sign for workflows configured to return documents separately. Affected users may experience documents being combined, incorrectly split, out of order, or missing from the final output. Our engineering team is actively working to identify the root cause and implement a resolution.
-
identified Mar 19, 2026, 08:24 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Mar 19, 2026, 08:56 PM UTC
The issue affecting document output in Formstack Sign workflows configured to return documents separately has been resolved. A fix has been implemented to address cases where documents were combined, incorrectly split, out of order, or missing from the final output. Please note that any documents impacted during the incident will need to be resubmitted to ensure correct processing. If you continue to experience issues, please contact our support team for assistance.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 12:26 AM UTC
- Resolved
- Mar 18, 2026, 01:12 AM UTC
- Duration
- 45m
Affected: Main Application
Timeline · 2 updates
-
investigating Mar 18, 2026, 12:26 AM UTC
We are currently investigating an issue impacting a subset of custom notification and confirmation emails, where field IDs may appear in place of submitted data. We will provide updates as more information becomes available.
-
resolved Mar 18, 2026, 01:12 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 07:05 PM UTC
- Resolved
- Mar 19, 2026, 10:59 AM UTC
- Duration
- 1d 15h
Affected: Notifications
Timeline · 4 updates
-
investigating Mar 17, 2026, 07:05 PM UTC
We are currently investigating an issue impacting email delivery, resulting in some messages not being delivered. Our team is actively working to restore full service and will provide updates as more information becomes available.
-
identified Mar 17, 2026, 07:06 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Mar 17, 2026, 10:28 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 19, 2026, 10:59 AM UTC
The issue impacting email delivery has been resolved. The affected sending domain has been restored, and email functionality is operating normally. All impacted customer emails during the incident window have been successfully re-sent.
Read the full incident report →
- Detected by Pingoru
- Mar 17, 2026, 03:29 PM UTC
- Resolved
- Mar 17, 2026, 05:18 PM UTC
- Duration
- 1h 48m
Affected: Notifications
Timeline · 3 updates
-
investigating Mar 17, 2026, 03:29 PM UTC
We are investigating an issue affecting Streamline Email Notifications where notification steps may not send as expected. Impacted workflows do not fail and may appear to complete successfully, but notification steps can silently fail to deliver notifications. SMS notifications are not impacted and are sending as expected. Our team is actively investigating the root cause. We will share another update as soon as we have more information.
-
monitoring Mar 17, 2026, 03:51 PM UTC
A fix has been implemented for the issue affecting Streamline Notifications where notification steps were not sending as expected. Workflows are now sending notifications correctly. SMS notifications were not impacted during this incident.
-
resolved Mar 17, 2026, 05:18 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 05, 2026, 09:35 PM UTC
- Resolved
- Feb 06, 2026, 07:10 PM UTC
- Duration
- 21h 35m
Affected: Main ApplicationDocuments
Timeline · 4 updates
-
identified Feb 05, 2026, 09:35 PM UTC
Formstack Sign recently implemented a security upgrade. As a result, users on older or unsupported browsers may experience issues loading documents in Sign. To avoid potential degradation, please ensure your operating system and browser are updated to a supported, recent version. Supported browser versions: • Chrome 119 or later • Edge 119 or later • Safari 17.4 or later • Firefox 121 or later This issue does not impact any other Formstack products and is specific to Formstack Sign. We are actively investigating options to mitigate this limitation and will provide updates as they become available. We apologize for any inconvenience this may cause.
-
identified Feb 06, 2026, 03:18 PM UTC
A fix has been identified and is expected to be deployed within the next few hours. In the meantime, updating to a supported, recent browser and operating system remains the recommended workaround to avoid potential issues loading documents in Formstack Sign.
-
monitoring Feb 06, 2026, 04:34 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Feb 06, 2026, 07:10 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 23, 2026, 06:20 PM UTC
- Resolved
- Jan 23, 2026, 09:26 PM UTC
- Duration
- 3h 6m
Affected: API & Document Generation
Timeline · 3 updates
-
investigating Jan 23, 2026, 06:20 PM UTC
We are currently investigating intermittent delays with Formstack Documents, where some jobs are being queued. This may cause slower document processing and creation than usual.
-
identified Jan 23, 2026, 08:25 PM UTC
We’ve identified an issue affecting how some jobs are queued and processed, which can result in intermittent processing delays. We are actively working to improve processing behavior and restore normal performance.
-
resolved Jan 23, 2026, 09:26 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 09:58 PM UTC
- Resolved
- Jan 24, 2026, 01:20 AM UTC
- Duration
- 1d 3h
Affected: Email System (SendGrid)SendGrid API v3SendGrid SMTPEmail System (SendGrid)
Timeline · 5 updates
-
monitoring Jan 22, 2026, 09:58 PM UTC
External email services are reporting issues starting about 2:00pm Eastern with errors peaking about 3:00pm. Intellistack became aware of an ongoing outage affecting some of the third-party email service providers, which may be impacting the delivery of some emails (including notifications, submission received emails, and alerts). Our core platform and customer data remain fully secure and operational. However, during this incident, you may experience delays or failures in receiving certain emails from us. Our engineering teams are actively monitoring the situation and working closely with the email provider to restore full service as quickly as possible. We will continue to share updates as more information becomes available.
-
monitoring Jan 22, 2026, 11:28 PM UTC
We're continuing to track the ongoing service disruption with third-party email providers. We appreciate your patience while we await the provider's resolution of the root cause. We'll post our next update as soon as we have a significant change in status.
-
monitoring Jan 23, 2026, 12:44 AM UTC
We are continuing to monitor the 3rd part email delivery disruption. We will provide updates as they become available.
-
monitoring Jan 23, 2026, 04:32 PM UTC
Intellistack Support and Engineering continue to monitor success metrics for email deliveries across all of our products related to the 3rd party services disruption that occurred yesterday 1/22/26.
-
resolved Jan 24, 2026, 01:20 AM UTC
We are seeing normal email delivery success rates for most customers.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 09:32 PM UTC
- Resolved
- Jan 22, 2026, 10:49 PM UTC
- Duration
- 1h 16m
Affected: Payments Integrations
Timeline · 3 updates
-
identified Jan 22, 2026, 09:32 PM UTC
We are currently experiencing intermittent errors with payment integrations for some users on a subset of forms. The error message may state: "Error rendering field: Invalid value for create(): disabled should be a boolean. You specified: null." We are working on a remediation and will update the status page with more information shortly.
-
monitoring Jan 22, 2026, 09:40 PM UTC
A fix has been released. We are now observing successful payment authorizations through Formstack Forms. We will monitor success rates and provide an update in one hour.
-
resolved Jan 22, 2026, 10:49 PM UTC
All functionality related to payments fields has been restored.
Read the full incident report →
- Detected by Pingoru
- Jan 20, 2026, 05:34 PM UTC
- Resolved
- Jan 20, 2026, 06:57 PM UTC
- Duration
- 1h 22m
Affected: Documents
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Jan 12, 2026, 11:05 PM UTC
- Resolved
- Jan 13, 2026, 12:56 AM UTC
- Duration
- 1h 51m
Affected: API & Document Generation
Timeline · 3 updates
-
identified Jan 12, 2026, 11:05 PM UTC
We have identified an issue where Standard users are unable to access Documents and receive an access error, while Admins are still able to access without issue.
-
monitoring Jan 13, 2026, 12:03 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 13, 2026, 12:56 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 12, 2025, 08:01 PM UTC
- Resolved
- Dec 12, 2025, 08:56 PM UTC
- Duration
- 54m
Affected: Main Application
Timeline · 3 updates
-
investigating Dec 12, 2025, 08:01 PM UTC
We are investigating an issues affecting the Export All functionality for form submissions. Workaround Step 1: From the form's Submission tab, choose how to filter your submissions. Use the search bar to find keywords Use the default filters: Read or Unread to update the view Select Create Filter to make a custom filtered view NOTE: Similar to Conditional Logic, you may choose All or Any criteria options within the filters. Manually check submissions For further information, please see: https://help.formstack.com/hc/en-us/articles/44592427644819-Export-Submission-Data Our team is actively working toward a permanent fix and will provide additional updates as they become available. We appreciate your patience.
-
monitoring Dec 12, 2025, 08:14 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 12, 2025, 08:56 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 09, 2025, 07:44 PM UTC
- Resolved
- Dec 10, 2025, 02:11 AM UTC
- Duration
- 6h 26m
Affected: Documents
Timeline · 3 updates
-
identified Dec 09, 2025, 07:44 PM UTC
The process appears to be hanging and remains on a continuous loading spinner. The issue has been identified, and the estimated time to resolution is around 4:00 PM Eastern.
-
monitoring Dec 09, 2025, 08:31 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Dec 10, 2025, 02:11 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 08, 2025, 04:19 PM UTC
- Resolved
- Dec 08, 2025, 06:21 PM UTC
- Duration
- 2h 1m
Timeline · 2 updates
-
investigating Dec 08, 2025, 04:19 PM UTC
We’re aware that www.formstack.com is currently down and returning a 502 error. Our team is actively investigating the issue.All products, as well as our help sites, remain fully operational and are not impacted by this outage. We’ll provide updates as soon as more information becomes available.
-
resolved Dec 08, 2025, 06:21 PM UTC
The issue causing www.formstack.com to return a 502 error has been resolved. The site is now fully operational.
Read the full incident report →