Anyone else experiencing extremely slow load speeds in their live apps and the builder? Been happening since June 2.
1 Like
Not any different to normal 
I recommend raising a ticket if it’s the same on all browsers and on a different PC. 
1 Like
Submitted a ticket last week, got a response with no context to the issue. Followed up, no response. Issue persisted for over 7 days and still no indication to the cause. My users report the issue on Chrome, Firefox and Edge and coast to coast in North America. Seems to have resolved itself today.
1 Like
Slow speeds back today. Some menus and charts wont even load…
1 Like
Yes, for sure much slower ever since Knack put in Flows and AI. Also, many more bugs accompanied with the slowiness.
1 Like
I’m unable to access the builder from here in the US. Working on a defect with some date manipulation and can’t run any tests.
1 Like
My slowness is also accompanied by many components not loading that have CSS or javascript associated with them.
All started happening around the time they released the new builder beta for my account.
1 Like
The builder was being blocked by our DNS filter. It has been corrected and I’m able to access the builder now.
1 Like
Not my issue unfortunately. Builder wont even load certain pages…
We’ve been experiencing slowdowns regularly around end of business day for us. Seems to coincide with 00:00 UTC
I was trying to delete some tables and import a fresh update today, and the system was so slow it was absolutely unusable. What has taken me 10 minutes historically would have taken days to weeks at the rate the records were deleting - approximately 1 every 10 seconds. Come on Knack - sort this mess out.
1 Like
Hi all,
We’ve been working to address the performance issues you’ve been posting about in the past couple weeks.
We deployed performance improvements on Wednesday and Thursday of this week, and we’re pleased to see early indicators showing performance trending in the right direction across our platform.
Regarding the specific issue @LeighBerre96926 encountered with the deletion process, we think this is related to our job scheduling system rather than the performance issues. It appears that the deletion job may have been queued alongside other resource-intensive operations, which would explain the slower-than-expected execution time.
We’re continuing to monitor both the overall performance and investigating ways to optimize our job scheduling to prevent similar conflicts in the future.
Thank you all for reporting and posting!
Kara
2 Likes