Stonly had 17 outages in the last 2 years totaling 84h 50m of downtime — averaging 0.7 incidents per month.
There were 17 Stonly outages since August 8, 2025 totaling 84h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.
Any modifications to the triggers, including enablement, disablement, and updates, are applied with a delay. This is due to widget servers losing an established connection to the main server and the self-healing process being defective.
We're currently investing an issue with Stonly not loading and returning 504 Gateway Timeout error.
The issue seems to be our cloud provider network problem. We've escalated the issue to their support and are trying to build a temporary workaround to restore services in parallel.
While we're working on resolving the underlying issue, we're actively working on implementing a workaround that should bring us back in the next 20 minutes
We're rolling back the workaround, restoring our services one after another
We were able to restore access to content hosted via stonly.com and it's subdomains. We're still evaluating how to restore access to knowledge bases hosted under custom domains.
We've implemented a workaround. Things are working as expected and we continue to monitor the situation.
This incident has been resolved.
We're investigating an elevated number of AI Answers errors
We've identified the source of errors to be related to ongoing scan on our infrastructure. We've blocked the offending traffic and our error rates are back to normal. We continue monitoring the case.
This incident has been resolved.
We are investigating an issue with guide summaries not being generated and AI Agent assist returning errors.
We've identified and issue and put some mitigations in place. AI AGent assist is now fully functional. We're working on resolving the guide summary issue and process the backlog of jobs to process.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between 12:29 and 13:27 we've seen increased amount of errors when loading guides.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
The issue is caused by Azure OpenAI issues. More details can be found on Azure status page. We're currently monitoring the status of Azure incident and looking into remediation options.
We've rerouted traffic to endpoints that are not affected. All functionality should now be restored. We continue monitoring the situation.
This incident has been resolved.
After deplying new version of the application, we are observing some instability for some customers.
We are rolling back to the previous version.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're investigating an issue where data used by our AI Bot is not updated after a guide is modified. That may lead to AI bot answering based on outdated guide content. All guide modifications will be automatically processed without additional actions after we restore the functionality.
We've found an issue and we're preparing a fix, that should go out in the next 15 minutes.
A fix was deployed and we're seeing embeddings being properly processed now. All data returned by AI bot should be up to date now.
This incident has been resolved.
We are experiencing an increased rate of errors connected to the loading on embedded guides. We are actively investigating the situation.
We know what the issue is, we are implementing a temporary fix, ETA around 10 minutes
Once the fix was effectively deployed, we observed a decrease in the error rate. This issue is now moved to the monitoring state.
This incident has been fully resolved.
We are under a huge load, and some of our databases have degraded performance. We are applying modifications to the database systems. We will be back with further information in 15 minutes.
We are observing recovery symptoms, and will keep updating in the next 15 minutes
A fix has been implemented and we are monitoring the results.
The incident was fully resolved.
We've identified an issue affecting ability to display stonly guide and knowledgebases and we're working on a fix, which should be deployed in the next 15 minutes.
A fix was implemented and things should be back to normal.
Our metrics are back to normal and monitoring confirms that the issue is fully resolved now.
Dear Customer, We are currently investigating an issue impacting: Stonly Website.Our technical team is working to identify the cause and restore service as quickly as possible. We apologize for this disruption and appreciate your patience.As soon as we have more information, we will post updates on our status page. Sincerely, The Stonly Team
Dear Customer, In response to the issue with, we have taken corrective actions. The system is currently under monitoring to ensure its stability.We appreciate your patience and understanding. Sincerely, The Stonly Team
This incident has been resolved.
We are currently experiencing image service provider issues. The fixes are underway.
While we continue to resolve the underlying issue with our Image service provider, we've implemented a workaround that allows displaying original images in the Stonly guides. Since original images are not being resized, it may result in content looking different and images taking longer time to load.
We are continuing to work on a fix for this issue and restoring full functionality.
The issue is now fully resolved - uploading and viewing images should work as expected.