Knak Assets not loading
Timeline · 2 updates
- monitoring May 08, 2026, 01:26 PM UTC
A fix has been implemented and we are monitoring
- resolved May 08, 2026, 03:37 PM UTC
This incident has been resolved
Knak had 10 outages in the last 2 years totaling 68h 13m of downtime — averaging 0.4 incidents per month.
There were 10 Knak outages since June 12, 2025 totaling 68h 13m of downtime. Each is summarised below — incident details, duration, and resolution information.
A fix has been implemented and we are monitoring
This incident has been resolved
We are currently investigating the issue
The issue has been identified
The issue has been identified and a fix has been deployed and we are currently monitoring
This incident has been resolved.
We are currently investigating.
The issue has been identified and we are implementing the fix.
A fix has been implemented and we are now monitoring
We are continuing to monitor for any further issues.
This incident has now been resolved. Assets synced between 9:00 AM and 10:04 AM EST will have to be resynced.
We are currently investigating an issue with global UTM input field not visible
The issue has been identified and we are working to release a fix
A fix has been implemented and we are monitoring the release of the fix
This incident has been resolved.
We are currently investigating the issue.
A fix has been applied and we are monitoring
We are currently investigating an issue of PDFs not being able to download
This incident is resolved PDFs can be downloaded again
We are currently investigating this issue.
We have been experiencing a temporary outage due to the ongoing AWS outage https://health.aws.amazon.com/health/status. We are currently stable but are closely monitoring the situation.
This incident has been resolved.
The issue is believed to be caused by a potential sub-processor outage.
The issue has been resolved and is being monitored.
This incident has been resolved.
On June 12, 2025 \(EDT\), our AI-powered features experienced a temporary service disruption. Our team immediately identified the cause as an outage with one of our sub-processors and monitored the situation until service was restored by the external provider. **Root Cause:** The issue was caused by a temporary service outage on the Google Cloud Vertex AI platform, an external service that our AI features depend on to function.