17 comments

  • Arubis1 minute ago
    Github Actions are rapidly becoming an argument against dogfooding into your critical path.
  • arandomhuman10 minutes ago
    I love how even self hosted workers don't work during these outages - running jobs on their infrastructure being flakey is marginally acceptable, but the API to simply schedule workflows having this availability is mind boggling. Github just doesn't seem like a serious company anymore.
  • peterldowns26 minutes ago
    Can't wait for the Graphite/Cursor alternative (Origin) to become available. Actions being down for an hour in the middle of the US East workday is crazy. It's super frustrating to be an enterprise customer of Github, seems like we don't get any dedicated resources or additional stability. At this point our only option is self-host github enterprise or move away.
  • Insanity46 minutes ago
    Soon we can start posting "GitHub {x} is up!" instead, that's becoming more news-worthy lol. I know they like to blame AI/scaling, but really they are owned by one of the main hyperscalers, so I find that excuse kind of weak..
    • clickety_clack40 minutes ago
      Maybe they bought an “it has been 1 day since our last incident” board instead of one with numbers you can change, so to save money on buying a new one they just keep having incidents.
  • rvz0 minutes ago
    Do we need to say this again? GitHub appears that they are never going to improve. Just look at how GitHub spark has deprecated, now we have this.<p>After 6 years of this nonsense of &quot;centralizing everything on GitHub&quot;, it is not a good idea at all.<p>You might as well self host. Just self-host.<p>[0] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=22868406">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=22868406</a>
  • KyleTheDev1 hour ago
    Incident number 6 for the month of August, notably on August 6th. This pattern does not bode well.
    • paularmstrong30 minutes ago
      Four of them were regarding AI&#x2F;Copilot. So that&#x27;s really just one long running incident and will probably continue to be 50&#x2F;50 chance of being down.
  • presbyterian48 minutes ago
    The speed at which GitHub is tanking their reputation is fascinating
  • newtonianrules41 minutes ago
    Did Microsoft fire all the people working on the GitHub features people actually use?
    • Topfi37 minutes ago
      I mean, Github doesn&#x27;t have its own CEO anymore, so arguably.
  • denysvitali25 minutes ago
    Was? Still is
  • h2aichat39 minutes ago
    I am having their issues, also... Anyway this guys are great!
  • dboreham11 minutes ago
    Someone needs to work on improving the way Actions deals with resource exhaustion like this. Today it exploded all the CI jobs with &quot;failed&quot; and an inscrutable message about &quot;The job was not acquired by Runner of type hosted even after multiple attempts&quot; then &quot;Internal server error&quot;. It should say &quot;Timed out due to no runner available, our apologies, try again later, or pay $$$ here to get priority for runners&quot;.
    • jubilanti9 minutes ago
      But you can&#x27;t even pay more $$$ to get priority! This isn&#x27;t even a good grift, it&#x27;s just incompetence.
  • dlcarrier1 hour ago
    So, it&#x27;s a normal Thursday?
  • whateveracct20 minutes ago
    any 9s left?
    • theamk12 minutes ago
      there is one 9 of uptime, but the dashboard hasn&#x27;t been updated yet: <a href="https:&#x2F;&#x2F;mrshu.github.io&#x2F;github-statuses&#x2F;" rel="nofollow">https:&#x2F;&#x2F;mrshu.github.io&#x2F;github-statuses&#x2F;</a><p>Once this goes in, I&#x27;d expect to see 89%, which is zero nines. (I&#x27;d like to say, &quot;a new low!&quot;, but sadly we&#x27;ve had this before)
    • ch4s312 minutes ago
      They&#x27;re running 9 8s of uptime.
  • Topfi1 hour ago
    Very frustrating, nothing more I can add at this point.
  • homeonthemtn36 minutes ago
    Ah. So that&#x27;s why.
  • dinny33 minutes ago
    man.. again?
  • andrewmcwatters18 minutes ago
    [dead]