Sliplane had 16 outages in the last 2 years — averaging 0.7 incidents per month.
There were 16 Sliplane outages since September 1, 2024. Each is summarised below — incident details, duration, and resolution information.
Type: Maintenance Duration: 50 minutes Affected Components: Dashboard, Public API May 12, 08:15:00 GMT+0 - Identified - We are currently working on scaling our systems. May 12, 09:04:40 GMT+0 - Completed - Maintenance has completed successfully.
Type: Incident Duration: 5 minutes Affected Components: Dashboard, Public API Apr 23, 07:42:00 GMT+0 - Investigating - We are currently investigating this incident. Apr 23, 07:47:00 GMT+0 - Resolved - This incident has been resolved.
Type: Maintenance Duration: 8 minutes Affected Components: Server, Public API Apr 11, 22:00:00 GMT+0 - Identified - We're migrating the DNS nameservers for [sliplane.app](http://sliplane.app) to new infrastructure. Existing services are not affected. Services created during the migration window (approx. 5 minutes) may experience a brief delay in DNS resolution. Apr 11, 22:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 11, 22:08:00 GMT+0 - Completed - Maintenance has completed successfully.
Type: Incident Duration: 19 minutes Affected Components: Dashboard, Public API Feb 4, 11:08:39 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 4, 11:27:57 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 42 minutes Affected Components: Dashboard, Public API Jan 2, 12:30:24 GMT+0 - Investigating - We are currently investigating this incident. Jan 2, 14:12:28 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jan 2, 14:12:42 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 25 minutes Affected Components: Dashboard, Public API Nov 12, 16:38:14 GMT+0 - Identified - We are continuing to work on a fix for this incident. Nov 12, 16:47:28 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Nov 12, 17:03:04 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 43 minutes Affected Components: Server Oct 20, 09:02:29 GMT+0 - Identified - Due to DockerHub having a widespread outage (), deploying from DockerHub on Sliplane is currently not possible. Oct 20, 09:45:36 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 32 minutes Affected Components: Dashboard Sep 22, 12:27:19 GMT+0 - Investigating - We are currently investigating this incident. Sep 22, 13:59:19 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 6 hours and 11 minutes Affected Components: Dashboard Sep 9, 16:24:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 9, 14:45:00 GMT+0 - Investigating - We are currently investigating this incident. Sep 9, 20:55:43 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 9 minutes Affected Components: Dashboard, Public API Jun 17, 20:10:00 GMT+0 - Resolved - This incident has been resolved. Jun 17, 20:00:56 GMT+0 - Identified - The Github API is completely down. Deploys from Github are currently not possible. Existing services and deploys from DockerHub are not affected.
Type: Incident Duration: 2 hours Affected Components: Dashboard, Public API Jun 3, 12:00:00 GMT+0 - Identified - Due to a fault in our upstream infrastructure provider creating new servers is currently not possible. Existing servers and services are not affected. We are continuing to work on a fix for this incident. Jun 3, 14:00:22 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 day, 19 hours and 7 minutes Affected Components: Dashboard May 1, 08:11:00 GMT+0 - Resolved - This incident has been resolved. May 1, 07:57:52 GMT+0 - Investigating - We are currently investigating this incident. May 1, 08:10:24 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Type: Incident Duration: 2 hours and 20 minutes Affected Components: Remote Build Server Jan 31, 11:30:00 GMT+0 - Resolved - This incident has been resolved. Jan 31, 08:40:00 GMT+0 - Investigating - After a successful build, pushing the image to our registry failed and the deploy did not go through. Garbage collection of the registry was not working, which caused the disk to fill up quickly until the registry was not able to process any more uploads.
Type: Incident Duration: 1 hour Affected Components: Dashboard Dec 18, 06:45:00 GMT+0 - Resolved - This incident has been resolved. Dec 18, 05:45:00 GMT+0 - Identified - Hardware failure at our upstream provider.
Type: Incident Duration: 8 minutes Affected Components: Dashboard Dec 15, 16:36:00 GMT+0 - Investigating - We are currently investigating this incident. Dec 15, 16:44:12 GMT+0 - Resolved - This incident has been resolved. No customer servers where affected.
Type: Incident Duration: 26 minutes Affected Components: Remote Build Server Dec 13, 10:15:00 GMT+0 - Resolved - This incident has been resolved. Dec 13, 09:49:00 GMT+0 - Identified - Deploys from Github are failing after a successful build during the registry push. Our Falkenstein Docker Registry had capacity issues and did not scale up fast enough.