FormAssembly logo

Is FormAssembly Down?

SaaSLive status, outages, and incident history

No. FormAssembly is up right now.

Every monitored FormAssembly system is operational as of October 7, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment FormAssembly breaks

FormAssembly is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official FormAssembly status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

FormAssembly Component Status

The main FormAssembly systems on this page. All 16 are operational right now.

1maintenance15operational
Support Live Chat
Maintenance
API
Operational
Autosuggest service
Operational

13 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Background services, Emails, FormAssembly Basic, FormAssembly Compliance, FormAssembly Enterprise, FormAssembly Essentials, FormAssembly Government, FormAssembly Professional/Premier, FormAssembly Team, FormAssembly.com, Salesforce » Salesforce Connector, Salesforce » Salesforce Marketing Cloud Connector, and 1 more.

See all of them free

Component statuses may change independently during partial outages.

Recent FormAssembly Outages & Incidents

Incident history from the official FormAssembly status page, including resolution updates.

Salesforce connector authorizations invalidated on October 3 - small subset of account across the platformResolved Oct 6, 2026 · 2h 58mResolved

We have reauthorized the Salesforce connections that were disconnected between 00:31 and 05:25 UTC on October 3 (8:31 PM to 1:25 AM ET). The exception is connections that customers had already reconnected themselves. What this means for you: - No action is needed to restore your Salesforce authorization. Connectors and dynamic picklists that depend on it should be working again. - Form responses submitted while your connector was failing were saved in FormAssembly and were not lost. If you haven't already, reprocess them from the connector log. - If you reauthorized on your own after October 3 and your connectors are working, no further action is needed. Current status - We are monitoring all affected accounts to confirm the reauthorizations worked. If we detect an authorization that is still failing, we will contact you directly. - We are still establishing the root cause. We will share more once our analysis is complete. If you still see "Error connecting to Salesforce" or "Authorization is no longer valid," please contact FormAssembly Support. If you reauthorize manually, do it once per Salesforce user from Preferences > External Authorizations, not form by form. Salesforce allows five active authorizations per user per app, and reconnecting form by form can exhaust that limit. --- [2026-10-06T10:27:36.715-04:00] (identified) Between 00:31 and 05:25 UTC on October 3 (8:31 PM to 1:25 AM ET), Salesforce rejected a set of token refresh requests from FormAssembly. As a result, Salesforce authorizations for a subset of customers across all regions were marked invalid in FormAssembly. Connectors and dynamic picklists that depend on those authorizations have been failing since then with "Error connecting to Salesforce" or "Authorization is no longer valid." Scope is currently being evaluated. Each identified account will be proactively identified. This affected a very small subset of accounts across the platform. If your Salesforce connectors are failing and you need them working now: Go to Preferences, then External Authorizations, and select Reauthorize on the affected Salesforce authorization. Reauthorize once per Salesforce user, from this page, rather than from each individual connector. Salesforce allows five active authorizations per user per app, and reconnecting form by form can exhaust that limit and break working connections. Form responses submitted while the connector was failing were saved in FormAssembly and were not lost. Once the authorization is restored, reprocess them from the connector log. If you have reauthorized since October 3 and your connectors are working, no further action is needed.

Submission and Connector Errors for a Subset of AccountsResolved Sep 30, 2026 · 29 minResolved

This incident has been resolved. --- [2026-09-30T13:49:23.248-04:00] (monitoring) Between approximately 10:30 AM and 12:40 PM ET, a small number of customers experienced errors during our scheduled release. Affected actions included submitting a form, editing or finalizing a response, resending a response, and running workflow connectors and form-level connectors. The issue was resolved once the release was fully deployed, and we have confirmed that no new errors have occurred. If a workflow connector step failed during this window, you can replay the step from the workflow response. https://help.formassembly.com/help/replay#replaying-a-connector-step If a form-level connector failed, you can reprocess the response to send it through your connectors again. https://help.formassembly.com/help/responses#reprocess-a-response If a payment connector failed, please reopen the response so the respondent can re-enter their payment information. and submit the form again. https://help.formassembly.com/help/responses#reopen-response We apologize for the disruption this caused.

Salesforce Connector Authorization Issues Following Recent Salesforce OutageResolved Sep 16, 2026 · 15h 46mResolved

This incident has been resolved. --- [2026-09-16T20:57:23.524-04:00] (monitoring) Our team has restored a number of Salesforce authorizations affected by the recent Salesforce service disruption. If your Salesforce Connector, Prefill Connector, or dynamic picklists are now working normally, no further action is needed. Some authorizations may still require manual reauthorization. If you're continuing to experience issues, please follow the troubleshooting steps in our previous update before reauthorizing your connection. --- [2026-09-16T18:43:32.352-04:00] (identified) Following the recent Salesforce service disruption (see our previous resolved incident: https://status.formassembly.com/incidents/0ksdl7t3kjvv), we’re seeing reports that one or more FormAssembly Salesforce authorizations may have been invalidated during the outage. If your Salesforce Connector, Prefill Connector, or dynamic picklists are still failing, please first check your FormAssembly External Authorizations page: 1. In FormAssembly, hover over your username in the upper-right corner and select External Authorizations. Check whether the Salesforce authorization used by the affected connector is marked as invalid. 2. If the authorization is invalid, do not reauthorize it yet. First, check how many active FormAssembly connections you currently have in Salesforce. Click your profile icon in the upper-right corner of Salesforce, then go to Settings > Manage Connections. 3. In the OAuth Apps table, check how many times FormAssembly Connector appears. 4. If you have fewer than five FormAssembly Connector connections, return to FormAssembly and reauthorize the invalid authorization. 5. If you already have five FormAssembly Connector connections, revoke a connection with the lowest use count first. This will free up an OAuth token and help prevent Salesforce from revoking another connection that may still be actively used. Then, return to FormAssembly and reauthorize the invalid authorization. We’ll continue to monitor the issue and post additional updates here as needed.

FormAssembly Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a FormAssembly incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history61 days observed
Aug 8100.00% average · 8 days with incidentsOct 7

Live FormAssembly Outage Reports

Problems reported by engineers using FormAssembly. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No FormAssembly problems reported yet.

Something wrong with FormAssembly on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About FormAssembly

Is FormAssembly down? FormAssembly reports live availability for 17 components at status.formassembly.com, among them FormAssembly.com, Salesforce Connector and API. Track FormAssembly outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured FormAssembly uptime at 99.93%. Response times, incident history, and SLA tracking for FormAssembly are available on the PulsAPI dashboard.

FormAssembly Status FAQ

Is FormAssembly down right now?

The verdict at the top of this page comes from the latest poll of the official FormAssembly status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if FormAssembly is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until FormAssembly recovers.

How do I check FormAssembly uptime history?

PulsAPI tracks FormAssembly uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.93%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever FormAssembly changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect FormAssembly outages?

PulsAPI reads the official FormAssembly status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual FormAssembly components?

Yes. PulsAPI monitors 16 individual FormAssembly components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when FormAssembly goes down?

Yes. Create a free account and subscribe to FormAssembly: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with FormAssembly to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot FormAssembly problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor FormAssembly?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so FormAssembly plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track FormAssembly with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services