Stonly had 33 outages in the last 2 years totaling 112h 19m of downtime — averaging 1.4 incidents per month.
There were 33 Stonly outages since August 6, 2024 totaling 112h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
We're investigating infrastructure issues that result in intermittent failures when loading Stonly guide content
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
We've fine tuned our scaling policies and see the systems stabilizing. Guides are loading, but it can be a bit slower than usual. We expect everything to get back to normal in 3-5 minutes given the traffic we're seeing.
The issue is fully resolved now.
We are experiencing a delay in email delivery due to an outage with our third-party email provider. The provider is aware of the situation and is actively working on a resolution. We will update our status page once the issue is confirmed to be resolved.
Our email provider informed us that the issue should be resolved. We will now enter the monitoring phase and will update once we have confirmation that it's completely resolved.
Our email provider informed us that the issue should be fully resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
Our individual fix improved situation, but we've just pushed another change that should further improve stability and response times.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
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.
We are continuing to investigate this issue.
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.
We're seeing an issue with our Javascript resources failing to load, making guides and KBs unavailable
We've rolled back the changes, things seem to be stable now, but we keep monitoring. If your guide or KB is failing to load, please refresh the page.
We've rolled back the changes, things seem to be stable now, but we keep monitoring. If your guide or KB is failing to load, please refresh the page.
This incident has been resolved.
We're seeing bigger than usual load on our servers that is causing slow responses and occasional failures when loading stonly KB and guides
Things have stabilized. We keep monitoring our platform.
This incident has been resolved.
We're seeing delay in consuming new targeting events. Our team is investigating the issue.
We've identified the issue and fixed it. Our queue is slowly decreasing, and we keep monitoring the situation.
The issue is now resolved, the queue is fully processed and all targeting events and properties should be captured close to real-time now.
Stonly guides are not loading
We've identified the underlying issue, fixed the problem and monitor the systems.
This incident has been resolved.
We're noticing slower than usual response times from our API, which affects loading times for widgets, knowledgebases and guide saving in the editor.
We are continuing to investigate this issue.
We've identified the issue and scaled up our systems to match the increased traffic demand. Things are looking stable and we're monitoring the situation.
We are continuing to monitor for any further issues.
Our response times are back to normal levels. We're marking this incident as resolved.