starslingdev Status - Incident history https://status.starsling.dev starslingdev Tue, 19 May 2026 16:27:38 +0000 Delayed job pickups for high volume customers Type: Incident Duration: 2 hours and 44 minutes Affected Components: GitHub Runners May 19, 16:27:38 GMT+0 - Investigating - We are currently investigating this incident. May 19, 17:42:20 GMT+0 - Identified - We are continuing to work on a fix for this incident. Infrastructure and job execution outcomes are nominal. The source of degraded performance is Github API rate limiting. May 19, 19:11:43 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 44 minutes

Affected Components:

<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>16:27:38</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>17:42:20</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. Infrastructure and job execution outcomes are nominal. The source of degraded performance is Github API rate limiting. .</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>19:11:43</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 19 May 2026 16:27:38 +0000 https://status.starsling.dev/incident/cmpcujgqd019lp73deahjqzfh https://status.starsling.dev/incident/cmpcujgqd019lp73deahjqzfh Delayed job pickups Type: Incident Duration: 1 hour and 18 minutes Apr 30, 23:54:37 GMT+0 - Investigating - We are currently investigating this incident. May 1, 00:17:40 GMT+0 - Identified - Impact is focused on a single customer with high concurrency. We are continuing to work on a fix for this incident. May 1, 01:12:34 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 18 minutes

<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>23:54:37</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 1</var>, <var data-var='time'>00:17:40</var> GMT+0</small><br><strong>Identified</strong> - Impact is focused on a single customer with high concurrency. We are continuing to work on a fix for this incident. .</p> <p><small>May <var data-var='date'> 1</var>, <var data-var='time'>01:12:34</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 30 Apr 2026 23:54:37 +0000 https://status.starsling.dev/incident/cmom553cx00tkmbn8je2k94d4 https://status.starsling.dev/incident/cmom553cx00tkmbn8je2k94d4 Delayed job starts on larger runners Type: Incident Duration: 1 hour and 33 minutes Apr 23, 17:07:55 GMT+0 - Investigating - We are investigating reports of degraded availability for 8 and 64 core runners Apr 23, 17:11:57 GMT+0 - Identified - We identified limited availability on one of the public cloud providers that we use for the 8 and 64 vCPU runners. 4 vCPU runners are not effected. Apr 23, 18:40:35 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 33 minutes

<p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>17:07:55</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating reports of degraded availability for 8 and 64 core runners.</p> <p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>17:11:57</var> GMT+0</small><br><strong>Identified</strong> - We identified limited availability on one of the public cloud providers that we use for the 8 and 64 vCPU runners. 4 vCPU runners are not effected..</p> <p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>18:40:35</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 23 Apr 2026 17:07:55 +0000 https://status.starsling.dev/incident/cmobqj3rw000qrbh3blxuwmif https://status.starsling.dev/incident/cmobqj3rw000qrbh3blxuwmif