Is Knack down?

We are currently investigating reports of login failures and page/table loading failures affecting Knack. Our team is actively working to identify and resolve the root cause. We will provide additional updates as more information becomes available. We appreciate your patience as we work through this issue.

This issue has been resolved. Customers should now be able to access Knack and load pages and tables normally. We are actively monitoring systems to ensure stability has been restored across all customers. If you continue to experience any issues accessing Knack, please contact support. Thank you for your patience while we investigated and resolved this incident.

This incident has been resolved. All systems are operating normally and all customers have regained access to Knack. Thank you for your patience during this time

We are currently investigating an issue affecting some Flows for some applications hosted in our US region. Affected Flows may not be triggering as expected. The issue began at approximately 9:20 AM ET on Tuesday, August 25, 2026. Our engineering team is actively investigating the root cause. We will provide an update as soon as we have more information.

Our engineering team has located the root cause and applied a fix to Flows. Actions not triggered earlier will be processed.

We are currently investigating an issue where equations and formulas are not updating as expected for some customers.

Our Engineering team has identified the issue and a fix is being implemented. We appreciate your patience.

A fix has been implemented and we are monitoring the results.

On August 6th at 6pm ET, we resolved this issue. We sincerely apologize for the disruption this caused to your work and workflows. The root cause was a change deployed on Thursday, July 30th around 10am ET that caused some equation fields, text formula fields, and aggregation fields (such as counts, sums, mins, and maxes) in some apps to not consistently recalculate when their source records and fields were updated. All formula, equation, and aggregation fields will are now properly recalculate when source records and fields are updated. If you believe your app may have stale field values from the affected window, we recommend triggering a bulk update on the relevant source table to prompt recalculation -- our support team can walk you through this if needed. We appreciate your patience throughout this process. For more details or assistance, please contact our Support team.

Some customers were unable to create or edit records on August 1st. Customers saw the following error: 400: 167a79500000000000000002 is invalid for field_XXXX (Updated By) connecting to object_X This issue has been resolved, and users should be able to create records now

We are currently investigating an issue that prevented certain jobs from processing over the weekend, affecting some users. Connections, Text Formulas, Thumbnail generation, and task updates were impacted. Our servers are now catching up on the backlog of pending jobs. During this time, you may experience delays while jobs are being processed. What to expect: We expect all pending jobs to be completed later today. We appreciate your patience as our systems work through the backlog. We will update this page as we have more information.

The issue has been identified and our team is working on a fix

Our Engineering team has identified the root cause of the issue that began on August 1st. While some jobs have already been completed successfully, we are seeing other jobs fail as our servers process the backlog. Our team is actively working on a fix to resolve the remaining failures. We will continue to monitor and provide further updates.

Our engineering team has identified a targeted fix and is finalizing the code now. We expect to deploy it later today.

A fix has been implemented and is now propagating to all affected customers/apps.

The fix for this issue has been deployed to all affected customers/apps. Records will update correctly on incremental changes, formula fields will recalculate as expected on the next update that triggers the formula, and behind-the-scenes jobs will run cleanly moving forward. If there was an automated-process that 1) ran since Saturday, August 1st at 10am ET and 2) is on a Weekly, Monthly, Yearly, or a custom schedule and 3) was not for sending emails (email-sending was unaffected by this issue), we recommend reviewing and re-running that automated-process. We take any customer-impacting issue seriously and apologize for the disruption this may have caused your business. Please continue to reach out to our team if there are outstanding questions by emailing [email protected]