KnowledgeOwl Status

Postmortem: Thank you for your patience through yesterday’s incident. We know performance impacts to our app and your live knowledge bases are never pleasant, and we appreciate your patience and grace while we worked through things.

Here’s a brief postmortem of what happened and our steps to remediate:

An unexpected spike in traffic led to intermittent 504 errors.

To maintain core system availability, we temporarily restricted computationally heavy operations while scaling our infrastructure.

Once that was complete, we returned back to normal operations. We’ve noticed no significant spikes or errors since then.

Resolved: Our fix seems to be working and we haven't seen any further issues. We'll share a post-mortem tomorrow. Thank you for your patience today!

Monitoring: We've rolled out a fix for the issue and we're monitoring performance.

Identified: We've identified the issue and are working to implement a fix.

Investigating: We're investigating reports of 504 gateway timeouts and other slowness accessing knowledge bases and the KnowledgeOwl application.

Resolved: The fix is holding and this incident is now resolved. We'll share a post-mortem later this week. Thanks for your patience today.

Monitoring: A fix has been implemented and we are monitoring the results. All systems should be back online. We will continue to monitor over the next hour before marking this as resolved, and we will share a postmortem once our review is complete.

Identified: Our team is actively investigating and has attempted several mitigations, none of which have resolved the issue. We'll continue posting hourly updates, or sooner if the situation changes.

Identified: We are still in emergency maintenance mode as we sort out the underlying issues that were causing the 504 errors. We are so sorry and are trying to get you all back online as quickly as possible. As one of our customers said, it is the Mondayest Monday.

Identified: All services are currently in maintenance mode. This includes knowledge bases, the application, files, and the API.

Identified: We are temporarily putting KnowledgeOwl into maintenance mode in order to let the system recover. We will be bringing everything back on line as quickly as possible.

Investigating: We are currently investigating reports of 504 errors and slow load times.

Postmortem: Thank you for your patience through yesterday’s incident. We know performance impacts to our app and your live knowledge bases are never pleasant, and we appreciate your patience and grace while we worked through things.

Here’s a brief postmortem of what happened and our steps to remediate:

An unexpected spike in traffic led to intermittent 504 errors.

To maintain core system availability, we temporarily restricted computationally heavy operations while scaling our infrastructure.

Once that was complete, we returned back to normal operations. We’ve noticed no significant spikes or errors since then.

Resolved: Our fix seems to be working and we haven't seen any further issues. We'll share a post-mortem tomorrow. Thank you for your patience today!

Monitoring: We've rolled out a fix for the issue and we're monitoring performance.

Identified: We've identified the issue and are working to implement a fix.

Investigating: We're investigating reports of 504 gateway timeouts and other slowness accessing knowledge bases and the KnowledgeOwl application.

Resolved: The fix is holding and this incident is now resolved. We'll share a post-mortem later this week. Thanks for your patience today.

Monitoring: A fix has been implemented and we are monitoring the results. All systems should be back online. We will continue to monitor over the next hour before marking this as resolved, and we will share a postmortem once our review is complete.

Identified: Our team is actively investigating and has attempted several mitigations, none of which have resolved the issue. We'll continue posting hourly updates, or sooner if the situation changes.

Identified: We are still in emergency maintenance mode as we sort out the underlying issues that were causing the 504 errors. We are so sorry and are trying to get you all back online as quickly as possible. As one of our customers said, it is the Mondayest Monday.

Identified: All services are currently in maintenance mode. This includes knowledge bases, the application, files, and the API.

Identified: We are temporarily putting KnowledgeOwl into maintenance mode in order to let the system recover. We will be bringing everything back on line as quickly as possible.

Investigating: We are currently investigating reports of 504 errors and slow load times.

Postmortem: Thank you for your patience through yesterday’s incident. We know performance impacts to our app and your live knowledge bases are never pleasant, and we appreciate your patience and grace while we worked through things.

Here’s a brief postmortem of what happened and our steps to remediate:

An unexpected spike in traffic led to intermittent 504 errors.

To maintain core system availability, we temporarily restricted computationally heavy operations while scaling our infrastructure.

Once that was complete, we returned back to normal operations. We’ve noticed no significant spikes or errors since then.

Resolved: Our fix seems to be working and we haven't seen any further issues. We'll share a post-mortem tomorrow. Thank you for your patience today!

Monitoring: We've rolled out a fix for the issue and we're monitoring performance.

Identified: We've identified the issue and are working to implement a fix.

Investigating: We're investigating reports of 504 gateway timeouts and other slowness accessing knowledge bases and the KnowledgeOwl application.

Resolved: The fix is holding and this incident is now resolved. We'll share a post-mortem later this week. Thanks for your patience today.

Monitoring: A fix has been implemented and we are monitoring the results. All systems should be back online. We will continue to monitor over the next hour before marking this as resolved, and we will share a postmortem once our review is complete.

Identified: Our team is actively investigating and has attempted several mitigations, none of which have resolved the issue. We'll continue posting hourly updates, or sooner if the situation changes.

Identified: We are still in emergency maintenance mode as we sort out the underlying issues that were causing the 504 errors. We are so sorry and are trying to get you all back online as quickly as possible. As one of our customers said, it is the Mondayest Monday.

Identified: All services are currently in maintenance mode. This includes knowledge bases, the application, files, and the API.

Identified: We are temporarily putting KnowledgeOwl into maintenance mode in order to let the system recover. We will be bringing everything back on line as quickly as possible.

Investigating: We are currently investigating reports of 504 errors and slow load times.

Resolved: The fix is holding and this incident is now resolved. We'll share a post-mortem later this week. Thanks for your patience today.

Monitoring: A fix has been implemented and we are monitoring the results. All systems should be back online. We will continue to monitor over the next hour before marking this as resolved, and we will share a postmortem once our review is complete.

Identified: Our team is actively investigating and has attempted several mitigations, none of which have resolved the issue. We'll continue posting hourly updates, or sooner if the situation changes.

Identified: We are still in emergency maintenance mode as we sort out the underlying issues that were causing the 504 errors. We are so sorry and are trying to get you all back online as quickly as possible. As one of our customers said, it is the Mondayest Monday.

Identified: All services are currently in maintenance mode. This includes knowledge bases, the application, files, and the API.

Identified: We are temporarily putting KnowledgeOwl into maintenance mode in order to let the system recover. We will be bringing everything back on line as quickly as possible.

Investigating: We are currently investigating reports of 504 errors and slow load times.