Slab had 7 outages in the last 2 years — averaging 0.3 incidents per month.
There were 7 Slab outages since September 28, 2024. Each is summarised below — incident details, duration, and resolution information.
Type: Maintenance Duration: 10 hours Affected Components: MCP OAuth, MCP API, GraphQL API, Application Dec 24, 15:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 25, 01:00:00 GMT+0 - Completed - Maintenance has completed successfully Dec 24, 15:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time.
Type: Incident Duration: 9 hours and 9 minutes Affected Components: GraphQL API, MCP OAuth, MCP API, Website, Application Nov 18, 20:44:00 GMT+0 - Resolved - This incident has been resolved. Nov 18, 11:34:36 GMT+0 - Investigating - Application is partially down at the moment. This incident was automatically created by Instatus monitoring. Nov 18, 14:44:43 GMT+0 - Monitoring - Services have been restored and we are currently monitoring the situation. Nov 18, 12:09:34 GMT+0 - Identified - We’re currently experiencing service disruption caused by an ongoing Cloudflare incident. We’re monitoring the situation closely to restore full functionality.
Type: Incident Duration: 5 hours and 10 minutes Affected Components: GraphQL API, Application Oct 27, 17:05:28 GMT+0 - Resolved - A recent update to part of the cache system introduced performance issues that caused the application to become unresponsive. The initial rollback did not immediately resolve the problem, as the issue was triggered only after the cache reached a specific threshold. A fix has since been implemented and deployed, and the application has been operating normally for the past several hours. Oct 27, 11:55:18 GMT+0 - Investigating - We are currently investigating this incident. Oct 27, 12:35:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Type: Incident Duration: 1 hour and 3 minutes Affected Components: GraphQL API, MCP OAuth, MCP API, , Application, MCP → Oct 18, 16:30:11 GMT+0 - Investigating - Application is partially down at the moment. This incident was automatically created by Instatus monitoring. Oct 18, 16:57:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Oct 18, 17:33:00 GMT+0 - Resolved - During a routine application update, a long-running database migration caused newly deployed servers to experience errors. Existing servers continued operating normally. The migration has been optimized, the new version successfully deployed, and all systems are now fully operational.
Type: Incident Duration: 1 hour and 43 minutes Affected Components: MCP OAuth, MCP API, Application, GraphQL API Sep 12, 08:37:24 GMT+0 - Investigating - Application is partially down at the moment. This incident was automatically created by Instatus monitoring. Sep 12, 10:05:22 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 12, 10:20:18 GMT+0 - Resolved - During a routine deployment, our application and APIs became unavailable due to the unavailability of a legacy open-source container image, which also prevented rollback. We updated our configuration to use the maintained version of the resource, and deployments are now proceeding normally. The application and APIs are fully accessible again. We are reviewing our dependency management processes to prevent similar issues in the future.
Type: Incident Duration: 3 hours and 3 minutes Affected Components: GraphQL API, Application Feb 21, 12:14:00 GMT+0 - Investigating - We are currently investigating this incident. Feb 21, 15:17:00 GMT+0 - Resolved - 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.
Type: Incident Duration: 28 minutes Affected Components: GraphQL API, Application Oct 29, 15:34:37 GMT+0 - Monitoring - Some users may be experiencing intermittent unavailability due to unexpected application restarts. A fix has been put into place and we are currently monitoring the situation. Oct 29, 16:02:52 GMT+0 - Resolved - All application functionality have been observed to be operating normally