- Detected by Pingoru
- May 20, 2026, 03:41 PM UTC
- Resolved
- May 20, 2026, 07:30 PM UTC
- Duration
- 3h 48m
Affected: FormAssembly EssentialsFormAssembly TeamFormAssembly EnterpriseFormAssembly Government
Timeline · 4 updates
-
investigating May 20, 2026, 03:41 PM UTC
Our team is currently investigating reports of loss of access to a small subset of Team and Enterprise accounts. We will update here with more information shortly.
-
investigating May 20, 2026, 03:43 PM UTC
We are continuing to investigate this issue.
-
resolved May 20, 2026, 04:36 PM UTC
This incident has been resolved. Please note that responses received during the downtime may need to be reprocessed for the connector run to complete. Please check your response log to confirm.
-
postmortem May 20, 2026, 06:29 PM UTC
**Update:** We previously marked this incident as resolved, but we have since identified additional accounts that may be affected. Our team is actively investigating and working to restore access. We apologize for the confusion and will continue to provide updates here as we learn more. As a reminder, responses received during the downtime may need to be reprocessed for the connector run to complete. Please check your response log to confirm.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 04:30 AM UTC
- Resolved
- Apr 17, 2026, 04:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 17, 2026, 02:09 PM UTC
Earlier this morning, some accounts hosted on our Sydney servers experienced errors when loading forms, including “There was a problem on our end trying to load forms” and “An unknown error occurred.” The issue has been resolved, and services have returned to normal. We will continue to monitor.
Read the full incident report →
- Detected by Pingoru
- Apr 07, 2026, 07:35 PM UTC
- Resolved
- Apr 08, 2026, 02:49 PM UTC
- Duration
- 19h 14m
Affected: FormAssembly Professional/PremierFormAssembly Basic
Timeline · 3 updates
-
investigating Apr 07, 2026, 07:35 PM UTC
Some customers are reporting that email notifications aren't being sent as expected upon form completion, and our team is investigating now. We will post more information as it becomes available.
-
monitoring Apr 07, 2026, 11:56 PM UTC
We have identified the cause of the email notification delivery issue as a temporary listing of one of our sending IPs on a third-party blocklist, which resulted in email rejections for some customers. The listing has since been removed, and we have not observed any new rejection logs since 2:21 PM ET. Email notifications should now be functioning normally. We are continuing to monitor the situation to ensure stability. We will provide another update once we confirm the issue is fully resolved.
-
resolved Apr 08, 2026, 02:49 PM UTC
The issue affecting email notification delivery has been resolved. A temporary third-party blocklist listing was identified and removed. Email notifications are now functioning normally. If you continue to experience issues, please contact support.
Read the full incident report →
- Detected by Pingoru
- Mar 26, 2026, 02:50 PM UTC
- Resolved
- Mar 26, 2026, 03:57 PM UTC
- Duration
- 1h 7m
Affected: FormAssembly EssentialsFormAssembly TeamFormAssembly EnterpriseFormAssembly Compliance
Timeline · 3 updates
-
investigating Mar 26, 2026, 02:50 PM UTC
We are investigating reports of inaccessible form lists affecting accounts in the Frankfurt region. We understand the disruption this may cause and are actively working to resolve it as quickly as possible. We will provide updates as more information becomes available.
-
monitoring Mar 26, 2026, 03:18 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 26, 2026, 03:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 12, 2026, 07:10 PM UTC
- Resolved
- Feb 12, 2026, 08:22 PM UTC
- Duration
- 1h 11m
Timeline · 3 updates
-
investigating Feb 12, 2026, 07:10 PM UTC
We are currently investigating an issue impacting Microsoft Excel and Sharepoint connectors on the platform. At this time, customers who encounter connector errors are unable to successfully reconnect to Microsoft. Once the error appears, reconnection attempts are failing, and affected connectors remain blocked. Our team is actively working to identify the root cause and restore reconnection functionality as quickly as possible. We will provide updates here as soon as more information becomes available.
-
monitoring Feb 12, 2026, 07:55 PM UTC
A fix has been implemented. Existing authorizations should now function as expected. If you’re still seeing an error, please re-authenticate the connector.
-
resolved Feb 12, 2026, 08:22 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 08:27 PM UTC
- Resolved
- Feb 04, 2026, 08:27 PM UTC
- Duration
- 2d
Timeline · 3 updates
-
investigating Feb 02, 2026, 08:27 PM UTC
We are currently investigating an issue where some form submissions are not redirecting respondents as expected after submission. Under normal circumstances, respondents are redirected back to the form if there is a validation or connector error, allowing them to correct their information and resubmit. If no errors occur, respondents are redirected to the configured thank-you page or redirect URL. Some submissions may remain on the response processing page and display a default confirmation message instead of submissions displaying potential errors. Our team is actively investigating the root cause of this issue. We will continue to post updates here as more information becomes available.
-
identified Feb 02, 2026, 08:58 PM UTC
We have identified the cause of the issue impacting form submission redirects. Our engineering team is actively working on a fix, which will be implemented as soon as possible. We will continue to provide updates here as progress is made.
-
resolved Feb 04, 2026, 08:27 PM UTC
The fix for this issue has been deployed. We are currently monitoring to ensure normal behavior has been fully restored.
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2026, 02:51 PM UTC
- Resolved
- Jan 29, 2026, 02:51 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 29, 2026, 02:51 PM UTC
We experienced processing delays with Salesforce connectors in the London region due to increased system load. Our team has upgraded system capacity and the issue is now resolved. All connectors are operating normally.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 03:00 PM UTC
- Resolved
- Jan 23, 2026, 07:11 PM UTC
- Duration
- 1d 4h
Timeline · 2 updates
-
identified Jan 22, 2026, 11:57 PM UTC
We confirmed a secondary issue related to yeseterday's SAML concern where SAML authenticated forms are not preserving URL query parameters after authentication. The team has identified the root cause and is working to resolve the issue. Additional details will be provided here as they become available.
-
resolved Jan 23, 2026, 07:11 PM UTC
This incident has been resolved. Please reach out to [email protected] if you run into any further issues.
Read the full incident report →
- Detected by Pingoru
- Jan 21, 2026, 08:40 PM UTC
- Resolved
- Jan 21, 2026, 11:02 PM UTC
- Duration
- 2h 22m
Timeline · 3 updates
-
investigating Jan 21, 2026, 08:40 PM UTC
We are currently investigating an issue that is impacting SAML authentication. At this time, some respondents are unable to access SAML-authenticated forms. This issue may also affect SAML-based login. Our engineering team is actively working to identify the root cause and implement a fix. We will provide updates as more information becomes available.
-
identified Jan 21, 2026, 09:52 PM UTC
The issue impacting SAML authentication has been identified, and a fix is currently being implemented. Some respondents may still be unable to access SAML-authenticated forms, and SAML-based login may continue to be affected during this time. Our engineering team is actively deploying the fix and monitoring the situation closely. We will provide another update once the fix has been fully applied and we’ve confirmed service restoration.
-
resolved Jan 21, 2026, 11:02 PM UTC
The issue impacting SAML authentication has been fully resolved. Respondents can now access SAML-authenticated forms as expected, and SAML-based login is functioning normally. Our team has confirmed service restoration and is continuing to monitor the system to ensure stability. Thank you for your patience while we worked to resolve this issue.
Read the full incident report →
- Detected by Pingoru
- Jan 21, 2026, 06:42 PM UTC
- Resolved
- Jan 21, 2026, 06:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 21, 2026, 06:42 PM UTC
What's Happening: We've deployed an update to improve Fai, our AI agent. During this enhancement, some users may experience a brief disconnect message. Quick Reconnection Steps: To reconnect to Fai, please try one of the following: - Refresh your browser page - Clear your browser cookies - Log out and log back in Still Having Trouble? If you continue to experience issues after trying these steps, please contact our support team and let us know which troubleshooting options you've already attempted so we can help you get back up and running.
Read the full incident report →
- Detected by Pingoru
- Jan 07, 2026, 09:24 PM UTC
- Resolved
- Jan 07, 2026, 11:16 PM UTC
- Duration
- 1h 52m
Affected: FormAssembly EssentialsFormAssembly Team
Timeline · 2 updates
-
investigating Jan 07, 2026, 09:24 PM UTC
We are aware of an issue impacting some customers where changes made to forms are not saving as expected. In some cases, customers may see a 400 Bad Request error when attempting to save form updates. Additionally, attempts to apply changes on the Processing page of a form may redirect customers to a “Something Went Wrong” error page. Other unstated issues may also surface, related to this issue. Our engineering team is actively investigating the cause of these issues and working toward a resolution. We will provide updates as more information becomes available.
-
resolved Jan 07, 2026, 11:16 PM UTC
This incident has been resolved. Customers who were previously unable to save form changes or update settings on the Processing page should now be able to do so without issue. The underlying cause was identified and corrected, and the system is operating normally. We apologize for any inconvenience caused and appreciate your patience.
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 06:31 PM UTC
- Resolved
- Dec 03, 2025, 07:40 PM UTC
- Duration
- 1h 9m
Affected: FormAssembly Professional/PremierFormAssembly Basic
Timeline · 3 updates
-
investigating Dec 03, 2025, 06:31 PM UTC
We’re currently investigating reports of the Forms List not loading. Our apologies for the inconvenience. Our team is working to resolve this as quickly as possible. We’ll continue to share updates here as soon as more information becomes available.
-
monitoring Dec 03, 2025, 07:24 PM UTC
A fix has been implemented, and we are monitoring the results.
-
resolved Dec 03, 2025, 07:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 17, 2025, 04:08 PM UTC
- Resolved
- Nov 17, 2025, 04:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Nov 17, 2025, 04:08 PM UTC
Details: Planned system maintenance for critical infrastructure updates will occur on Sunday, November 16th, starting at 10:00 PM ET, lasting up to 7 hours. The application & all forms will be completely inaccessible during this time. This proactive measure is essential for platform security and reliability.
Read the full incident report →
- Detected by Pingoru
- Oct 21, 2025, 08:48 PM UTC
- Resolved
- Oct 21, 2025, 09:29 PM UTC
- Duration
- 40m
Affected: FormAssembly EssentialsFormAssembly EnterpriseFormAssembly ComplianceFormAssembly Government
Timeline · 3 updates
-
investigating Oct 21, 2025, 08:48 PM UTC
We are investigating reports of 404 (Page Not Found) error, which is preventing some users from logging in. Our team is working to identify the cause and will update this page as soon as we have more information.
-
monitoring Oct 21, 2025, 09:01 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 21, 2025, 09:29 PM UTC
This incident has been resolved. Users should now be able to access their accounts successfully.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 02:16 PM UTC
- Resolved
- Oct 20, 2025, 05:00 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2025, 12:56 PM UTC
- Resolved
- Oct 06, 2025, 04:19 PM UTC
- Duration
- 3h 23m
Affected: FormAssembly EssentialsFormAssembly TeamFormAssembly BasicFormAssembly EnterpriseFormAssembly ComplianceFormAssembly Government
Timeline · 3 updates
-
investigating Oct 06, 2025, 12:56 PM UTC
We are currently investigating reports that are impacting FormAssembly, such as access to the Admin Dashboard and Form Builder for account admins. Our engineering team is actively investigating and working to resolve this as quickly as possible. We will continue to post here as more information is available.
-
identified Oct 06, 2025, 02:30 PM UTC
Our team has identified the issue affecting the Admin dashboard, Builder and Locked connectors. They are currently working on a fix for the issue. We will continue to update here as more information becomes available and a fix is issued.
-
resolved Oct 06, 2025, 04:19 PM UTC
A fix has been implemented. The Admin Dashboard, Builder, and connectors are now accessible. The incident has been resolved.
Read the full incident report →
Notice September 17, 2025 - Detected by Pingoru
- Sep 17, 2025, 06:09 PM UTC
- Resolved
- Sep 18, 2025, 05:06 PM UTC
- Duration
- 22h 57m
Affected: FormAssembly Professional/PremierFormAssembly EssentialsFormAssembly TeamFormAssembly BasicFormAssembly EnterpriseFormAssembly ComplianceFormAssembly Government
Timeline · 3 updates
-
investigating Sep 17, 2025, 06:09 PM UTC
We are currently investigating an issue where users are unable to drag and drop fields within the form builder. Our team is actively working to identify the root cause and implement a solution. In the meantime, you can use the form outline as a workaround to reorder your form fields. https://help.formassembly.com/help/introducing-the-form-builder#form-outline We will post an update on this page as soon as more information is available.
-
identified Sep 17, 2025, 09:13 PM UTC
We are continuing to work toward a fix for this issue. We will continue to share updates here as more details become available.
-
resolved Sep 18, 2025, 05:06 PM UTC
As of 12:51 PM ET, a fix has been implemented for the issue affecting the ability to move fields within the form builder. Thank you for your patience while we worked to resolve the issue.
Read the full incident report →
Notice September 16, 2025 - Detected by Pingoru
- Sep 16, 2025, 08:56 PM UTC
- Resolved
- Sep 17, 2025, 09:02 PM UTC
- Duration
- 1d
Affected: FormAssembly EssentialsFormAssembly TeamFormAssembly EnterpriseFormAssembly ComplianceFormAssembly Government
Timeline · 4 updates
-
identified Sep 16, 2025, 08:56 PM UTC
We are investigating an issue affecting a subset of accounts where forms using SAML authentication fail to load. Respondents may encounter an infinite loading screen when attempting to access these forms. Our team is actively working to identify the root cause and resolve the issue. We apologize for the disruption this has caused. We will provide updates here as more information becomes available.
-
identified Sep 17, 2025, 03:53 PM UTC
We are continuing to work toward a fix for this issue. We'll continue to update here as we have more details.
-
monitoring Sep 17, 2025, 07:46 PM UTC
A fix has been implemented, and we are monitoring the results.
-
resolved Sep 17, 2025, 09:02 PM UTC
This incident was resolved at 3:35 PM ET. Thank you for your patience while we worked on a fix.
Read the full incident report →
- Detected by Pingoru
- Aug 29, 2025, 04:30 PM UTC
- Resolved
- Sep 04, 2025, 09:15 PM UTC
- Duration
- 6d 4h
Affected: FormAssembly EssentialsFormAssembly TeamFormAssembly BasicFormAssembly EnterpriseFormAssembly ComplianceFormAssembly Government
Timeline · 3 updates
-
identified Aug 29, 2025, 04:30 PM UTC
We’re aware of an issue affecting forms with Stripe connectors and Save and Resume enabled that may result in failed payments. Upon form submission, respondents may see the error: “An error occurred while processing your payment. Please try again later.” Stripe Connector logs show: “The Stripe connector failed for an unknown reason. Please contact support.” The issue occurs when a response is saved, resumed, and then submitted. Temporary Workaround: To prevent this error for new respondents, we recommend disabling the Save and Resume feature on affected forms. Our team is actively working on a fix and will provide updates here as soon as the issue is resolved.
-
identified Sep 01, 2025, 09:43 PM UTC
We are continuing to monitor this incident and will update once we have further information.
-
resolved Sep 04, 2025, 09:15 PM UTC
A fix has been implemented. This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 01, 2025, 03:22 PM UTC
- Resolved
- Aug 06, 2025, 05:54 PM UTC
- Duration
- 5d 2h
Affected: FormAssembly EssentialsFormAssembly TeamFormAssembly BasicFormAssembly EnterpriseFormAssembly Government
Timeline · 3 updates
-
identified Aug 01, 2025, 03:22 PM UTC
We’re currently aware of an issue where some users who have forms with reCAPTCHA enabled are seeing the CAPTCHA appear multiple times when published using server-side script (REST API) or our WordPress plugin. Our team is actively working on a fix. As a temporary workaround, you can publish your form using an iFrame. Please refer to the following guides for more information: https://help.formassembly.com/help/340359-publish-with-an-iframe https://help.formassembly.com/help/wordpress#publish-with-an-iframe-inline-frame- We apologize for the inconvenience and will share another update as soon as we have more information.
-
identified Aug 04, 2025, 12:32 PM UTC
We are continuing to work on a fix for this issue. Thanks for your patience.
-
resolved Aug 06, 2025, 05:54 PM UTC
The issue causing multiple reCAPTCHA checkboxes to appear on some forms has been resolved. Affected forms are now functioning as expected. We appreciate your patience while our team worked to implement the fix.
Read the full incident report →
- Detected by Pingoru
- Jul 25, 2025, 03:20 PM UTC
- Resolved
- Jul 23, 2025, 06:23 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 25, 2025, 03:20 PM UTC
From July 23 at 2:23 PM to July 24 at 2:07 PM EST, forms published via Quick Publish displayed incorrect text when special characters were used. This issue has been resolved by rolling back a recent update. We are actively working on a permanent fix to prevent this from recurring.
Read the full incident report →
- Detected by Pingoru
- Jul 17, 2025, 10:30 PM UTC
- Resolved
- Jul 15, 2025, 01:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 17, 2025, 10:30 PM UTC
As of July 15, we identified an issue affecting a small number of forms with special characters on select Gov Cloud instances, where some form content appeared with garbled characters. While this was partially resolved on July 16, affected forms or connectors that were modified during this time may have become inaccessible or may experience errors. Customers can restore their forms to a revision prior to July 16 to resolve the issue.
Read the full incident report →
- Detected by Pingoru
- May 29, 2025, 09:13 PM UTC
- Resolved
- May 29, 2025, 04:50 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 29, 2025, 09:13 PM UTC
Between 12:50 PM and 2:30 PM ET, some respondents may have encountered validation errors or issues when attempting to submit forms. The issue was related to a recent update, which has since been rolled back. We are actively investigating a permanent fix to prevent this from recurring.
Read the full incident report →
