Knack Outage History

Knack had 7 outages in the last 2 years totaling 18h 30m of downtime — averaging 0.3 incidents per month.

There were 7 Knack outages since July 21, 2025 totaling 18h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.knack.com

Minor April 17, 2026

Some Users Experiencing Blank Live App Pages

Detected by Pingoru: Apr 17, 2026, 06:40 PM UTC
Resolved: Apr 17, 2026, 10:52 PM UTC
Duration: 4h 12m

Affected: Live App

Timeline · 2 updates

identified Apr 17, 2026, 06:40 PM UTC

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.
resolved Apr 17, 2026, 10:52 PM UTC

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.

Read the full incident report →

Minor January 22, 2026

Builder Access Issues

Detected by Pingoru: Jan 22, 2026, 05:46 PM UTC
Resolved: Jan 22, 2026, 06:33 PM UTC
Duration: 47m

Affected: Builder

Timeline · 3 updates

identified Jan 22, 2026, 05:46 PM UTC

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.
monitoring Jan 22, 2026, 06:25 PM UTC

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.
resolved Jan 22, 2026, 06:33 PM UTC

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.

Read the full incident report →

Minor January 21, 2026

Access Limited to Either Classic or Next Gen

Detected by Pingoru: Jan 21, 2026, 05:17 PM UTC
Resolved: Jan 21, 2026, 05:26 PM UTC
Duration: 9m

Affected: BuilderLive App

Timeline · 4 updates

investigating Jan 21, 2026, 03:06 PM UTC

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.
investigating Jan 21, 2026, 05:17 PM UTC

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.
identified Jan 21, 2026, 05:18 PM UTC

The issue has been identified and a fix is being implemented.
resolved Jan 21, 2026, 05:26 PM UTC

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.

Read the full incident report →

Minor December 22, 2025

Field indexes and scheduled tasks affected

Detected by Pingoru: Dec 22, 2025, 08:31 AM UTC
Resolved: Dec 22, 2025, 01:24 PM UTC
Duration: 4h 53m

Affected: Builder

Timeline · 3 updates

investigating Dec 22, 2025, 08:31 AM UTC

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.
identified Dec 22, 2025, 10:45 AM UTC

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.
resolved Dec 22, 2025, 01:24 PM UTC

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.

Read the full incident report →

Major October 20, 2025

Ongoing AWS Outage Affecting Knack Services

Detected by Pingoru: Oct 20, 2025, 02:29 PM UTC
Resolved: Oct 20, 2025, 09:47 PM UTC
Duration: 7h 18m

Affected: BuilderLive AppAPI

Timeline · 5 updates

investigating Oct 20, 2025, 02:29 PM UTC

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!
investigating Oct 20, 2025, 04:48 PM UTC

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.
identified Oct 20, 2025, 05:28 PM UTC

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.
monitoring Oct 20, 2025, 08:39 PM UTC

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!
resolved Oct 20, 2025, 09:47 PM UTC

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.

Read the full incident report →

Notice August 27, 2025

Temporary Access Disruption

Detected by Pingoru: Aug 27, 2025, 03:58 PM UTC
Resolved: Aug 27, 2025, 03:58 PM UTC
Duration: —

Timeline · 1 update

resolved Aug 27, 2025, 03:58 PM UTC

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.

Read the full incident report →

Major July 21, 2025

Flows Feature - Unable to create new Flows

Detected by Pingoru: Jul 21, 2025, 04:20 PM UTC
Resolved: Jul 21, 2025, 05:30 PM UTC
Duration: 1h 10m

Affected: Flows

Timeline · 2 updates

investigating Jul 21, 2025, 04:20 PM UTC

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!
resolved Jul 21, 2025, 05:30 PM UTC

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.

Read the full incident report →