Knack had 28 outages in the last 2 years totaling 87h 10m of downtime — averaging 1.2 incidents per month.
There were 28 Knack outages since August 28, 2024 totaling 87h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.
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]
We are aware that some customers are experiencing a blank page when accessing their Live Apps. This issue has been identified as a localized DNS/ISP problem affecting several providers in Texas, USA and is not related to our platform. At this time, resolution will depend on the impacted ISPs. As a workaround, users may be able to access their app successfully by switching to a different network or ISP. We will continue to monitor the situation and share updates when available. Thank you for your understanding.
We have received reports that the issue causing some users to see a blank page when accessing their Live Apps has been resolved. We are no longer seeing widespread impact, and this incident is now considered resolved. If you continue to experience issues, we recommend trying an alternate network or contacting your ISP for further assistance. Thank you for your patience while this was ongoing.
Some customers may be unable to access the Builder. The issue has been identified and is related to a problem with one of our service providers. We’re actively working with them to resolve this as quickly as possible and will provide updates as they become available.
A fix has been implemented for the issue affecting access to the Builder. We’re currently monitoring the results to ensure everything is functioning normally and will provide further updates if needed.
The issue affecting access to the Builder has been fully resolved. All systems are operating normally. Thanks for your patience while we worked to address this.
We’re investigating an issue where some accounts have access to only Classic or Next Gen, instead of both. All affected customers should still be able to access their apps, though access may be limited to one version of the platform. Our Engineering team is actively working to identify the cause and restore full access. Updates will be shared here.
We’ve identified the cause of the issue limiting some accounts to either Classic or Next Gen access. This is related to an issue with one of our third-party providers. All affected customers should still be able to access their apps, though access may be limited to one version of the platform. Our Engineering team is working with the provider to resolve the issue and restore full access. Further updates will be shared here.
The issue has been identified and a fix is being implemented.
This issue has been resolved. Access to both Classic and Next Gen has been fully restored for all affected accounts. The issue was caused by a problem with one of our third-party providers and has since been addressed. How We're Preventing This Moving Forward: The logic that determines "Classic" vs. "Next Gen" access will be completely removed from being owned by a third-party vendor, and will be owned by Knack's internal team. This eliminates all exposure our customers have from this third-party vendor publishing a bug/problem that caused this issue. Thank you for your patience while we worked to resolve this.
We have noticed an increased number of errors on our servers related to the processing of automated tasks - we are talking about the scheduled tasks and field indexes (those that need to run at midnight). This does not affect all of the events, but it seems that it might be affecting all regions. Our team of engineers is currently investigating the incident on our side and we are working to get this resolved. We will keep you up to date with our findings.
We have identified a possible cause and are working on a fix. There are still possible minor issues, but the service should mostly be back to normal. We will let you know as soon as this is marked as resolved from our end.
Our engineering team has fixed the issue and services are back to normal. If you notice any more issues after this point please reach out to our support team through the available channels.
Some of our customers in the US region might be experiencing slowdown or partial service disruption. We have identified an upstream provider as the source and we are working with them to get this resolved. We will keep you updated!
We’ve identified that the slowdown and partial service disruption initially reported in the US region is now affecting multiple regions. The root cause remains an issue with one of our upstream providers. We’ll continue to share updates here as we make progress. Thank you for your patience and understanding.
We’re currently experiencing service disruptions due to a broader issue impacting Amazon Web Services (AWS), one of our key infrastructure providers. AWS engineers are actively working to resolve the incident, and we’re closely monitoring their progress. Our team will continue to provide updates here as more information becomes available. Thank you for your patience while we work through this.
We’re starting to see apps and services come back online as AWS systems recover from the earlier outage. You may still experience some slowness or intermittent issues as traffic ramps back up and everyone reconnects. Our team is continuing to monitor performance closely to ensure stability across all systems. We’ll share another update once everything is fully operational. Thank you for your patience and understanding!
Our Engineering team has been actively monitoring and testing all Knack services, and we’re happy to report that functionality has returned to normal. The underlying AWS incident remains open as their teams continue to run additional tests and validations, but Knack appears to be fully recovered from the impact. Thank you for your patience while this was resolved.
Today, from 11:08am ET to 11:26am ET, a misconfiguration in our feature-flagging tool caused all customer apps to default to the Next-Gen experience only. During this time, attempts to access Classic URLs resulted in errors. At 11:27am ET, the issue was fully resolved, and all access has returned to normal: - Customers with Classic-only access now have Classic-only access restored. - Customers with Next-Gen-only access now have Next-Gen-only access restored. - Customers with both Next-Gen and Classic access now have both restored. We apologize for the disruption and appreciate your patience.
We're currently experiencing an issue with our Flows feature. New flows cannot be created at this time, and users may see a 502 Bad Gateway error. Our engineering team is actively investigating and working to resolve the issue as quickly as possible. We’ll provide updates here as we learn more. Thank you for your patience!
The issue affecting the Flows feature has been resolved, and new flows can now be created successfully. If you're still experiencing any problems, please try clearing your browser’s cache and cookies, then reload the page. Thank you for your patience while we worked to restore functionality.
Some customers are seeing "Uh oh! This page does not exist" when loading pages in the Builder and Live App. Our team is investigating and working to restore service. Thanks for your patience while we resolve this issue.
The issue has been identified and a fix is being implemented.
Our team identified the root cause of the problem affecting page loading in the Builder and Live App. The issue has been resolved, and functionality should be back to normal now. If you continue to experience any problems, please refresh your browser or contact support. Thanks for your patience while we worked to fix this!
We are aware that some customers are currently experiencing issues affecting app styles, including custom menus, fonts, and other visual elements. Our team has identified the cause of the problem and is actively working on a fix. We understand how important consistent branding and styling are to your business, and we sincerely apologize for the disruption.
A fix has been implemented to address the styling issues impacting custom menus, fonts, and other app visuals. Our team is now closely monitoring the results to ensure that everything is functioning as expected. If you continue to experience any problems, please reach out to our support team so we can assist you further. We appreciate your patience and understanding while we resolved this issue.
We have confirmed that the styling issues affecting custom menus, fonts, and other visual elements have been fully resolved. All systems are now operating normally. Thank you for your patience and understanding while we worked to address this issue. If you notice any lingering problems, please don’t hesitate to contact our support team.
We're currently investigating an issue where changes made to custom JavaScript and CSS are not being saved as expected. Our Engineering team has identified the root cause and is actively working on a fix. We’ll continue to provide updates as we make progress. Thank you for your patience.
Our Engineering team has deployed a fix for the issue preventing custom JavaScript and CSS changes from being saved. This functionality is now working as expected. Thank you for your patience while we resolved this.
We're currently investigating an issue where images are not loading for some customers. Our engineering team is actively working to identify the root cause and resolve it as quickly as possible. We appreciate your patience and will share more updates here as soon as we have them.
The issue has been identified and a fix is being implemented.
A fix has been deployed, and the issue causing images not to load for some users has been resolved. Everything should be working as expected now. If you're still experiencing any issues, please reach out to our support team. Thank you for your patience!
We have discovered that the Builder and Live app services are not loading at the moment. Our engineering team is already aware of the situation and the investigation is ongoing. Once we have more details we will be posting an update.
The issue is resolved on our end and the services are back online at the moment. We appreciate everyone's patience while we worked on finding a solution. If you have any more issues with the services, please reach out to [email protected].
During routine system maintenance, we performed an infrastructure update intended to improve performance. While no downtime was expected, an issue arose when certain instances were temporarily assigned new IP addresses. This led to a brief disruption in inter-service communication. The issue was quickly identified and resolved by updating the necessary DNS records and restarting supporting components. We’ve also identified preventative measures to ensure this does not recur in future maintenance windows.
We're currently investigating reports of some Live apps not loading and menus failing to load within certain apps. Our Engineering team is actively working to identify the cause and resolve the issue as quickly as possible. We’ll share updates here as we learn more. Thanks for your patience!
Update: We've identified the root cause of the issue affecting app and menu loading. A fix is currently being deployed, and we expect services to begin recovering shortly. We'll continue to monitor the situation and share another update once the deployment is complete. Thanks again for your patience!
Update: A fix has been implemented, and we're currently monitoring to ensure everything is fully back to normal. Initial signs look good, but if you're still experiencing issues, please try clearing your browser cache and cookies, as that may help resolve any lingering problems. We'll share a final update once we've confirmed full recovery. Thanks for sticking with us!
Resolved: The issue affecting app and menu loading has been fully resolved. All services are now operating normally. If you continue to experience any issues, please try clearing your browser cache and cookies, or reach out to our Support team for help. Thanks again for your patience while we worked through this!
Some customers have seen degraded performance in the EU region today. The incident was resolved in about 1 hour by our engineering team. This was caused by an infrastructure issue which was preventing the servers from working at optimal capacity.
We’re currently experiencing an issue with our Maps feature. When searching for an address, the address details are displayed correctly, but the map itself appears blank. Our team is actively investigating this and working on a fix. We appreciate your patience and will provide updates as soon as we have more information. Thank you for your understanding.
The issue has been identified and a fix is being implemented.
This incident has been resolved
We are currently investigating an issue where API keys appear to have been reset or changed unexpectedly. Our engineering team is actively working to identify the cause and resolve the problem as quickly as possible. We’ll provide updates here as we learn more. Thank you for your patience!
The issue has been identified, and we are actively working to implement the best solution.
The issue has been resolved and the affected apps can now use the previous API key. We have also taken the necessary measures to prevent this from happening again in the future.
We have received some complaints about degraded performance in the EU region. These vary from slow loading of the page to intermittently being able to access the apps. Our team is looking into the issue and we will come back with an update as soon as we have more details.
14:00 CET. It looks like performance is starting to get back to normal values. We will continue to monitor the servers to be sure that the trend remains the same.
15:30 CET. It seems that the services are all back to normal and are stable. We will be closing this issue. If you are still experiencing issues with degraded performance please reach out to our support team.
Update: 8:00 AM EST. Things are looking stable at this point so we will be closing out the alert. If you have any other issues with the service please reach out to the Support team through the regular communication channels. Update: 6:30 AM EST. It seems that the services are back to normal at this time. We will continue to monitor on our end for a few more hours. At this time we will decrease the severity of the issue. Update: 6:00 AM EST. We have found the cause and are working on a permanent fix on all the regions. We still need to run some tests on our end to ensure compatibility. Once we have the fix deployed we will add another update. At around 2:30 AM EST we have discovered an API service interruption across all platforms. If you got a 500 error for any API calls, it is related to this incident. Our engineering team has been working since then on identifying the cause and implementing a solution. We will come back with a reply soon.
This incident has been resolved.
We are currently experiencing an issue where some scheduled tasks have stopped running, impacting a small subset of customers. Our Engineering team is actively investigating the root cause and working to restore full functionality as soon as possible. Affected customers may try updating the "Next Run Date" in the task settings, which may help trigger the tasks to resume.
We have identified the issue affecting scheduled tasks and have pushed a fix. To ensure your scheduled tasks resume as expected, please update the "Next Run Date" in the task settings. This will help verify that tasks are triggered correctly moving forward. Thank you for your patience as we worked to resolve this issue.
This incident has been resolved.
Update: We have identified the cause as an upstream provider and the issue has been resolved. The website is accessible again. We have discovered that the knack.com website is not accessible at the moment, throwing a 404 error. Our engineers are already investigating this on our end. Only the website is affected and the knack builder and live app are still accessible at the moment.
This incident has been resolved.
We are currently experiencing an issue with our Payments/E-Commerce feature in the Live App, and it is temporarily unavailable. Our team is actively working to resolve the problem as quickly as possible. We will provide updates as soon as we have more information. Thank you for your patience and understanding.
The issue has been identified and a fix is being implemented
A fix has been implemented and we are monitoring the results
This incident has been resolved.
This morning, some customers encountered issues with CSS and JavaScript loading between 11:00 AM and 1:30 PM UTC. Our team has addressed the problem, and it should now be resolved. If you continue to experience any issues, please don't hesitate to reach out