Resolved after 3 hours 3 minutes, on February 21, 2025.
This incident has been resolved. We have finished our investigation into this issue. The root cause was a recent change we made which inadvertently caused some draft posts to return an error when loaded. This error resulted in increased memory usage, degrading performance and preventing some posts from loading or saving in a timely manner. In the process of resolving the first issue, we encountered a separate, unrelated caching problem which required additional time to resolve. Both issues were ultimately resolved by restoring a previous version of the application. We have been monitoring our error rates and memory usage, and they have remained stable since the incident's resolution..
Update timeline
- investigating Feb 21, 2025, 12:14 PM UTC
We are currently investigating this incident..
- resolved Feb 21, 2025, 03:17 PM UTC
This incident has been resolved. We have finished our investigation into this issue. The root cause was a recent change we made which inadvertently caused some draft posts to return an error when loaded. This error resulted in increased memory usage, degrading performance and preventing some posts from loading or saving in a timely manner. In the process of resolving the first issue, we encountered a separate, unrelated caching problem which required additional time to resolve. Both issues were ultimately resolved by restoring a previous version of the application. We have been monitoring our error rates and memory usage, and they have remained stable since the incident's resolution..
Your product runs on more than Slab
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services