Top
Best
New

Posted by Footkerchief 22 hours ago

GitHub Actions and Pages are experiencing degraded availability(www.githubstatus.com)
https://www.githubstatus.com/uptime/br0l2tvcx85d
426 points | 351 commentspage 9
whateveracct 21 hours ago|
any 9s left?
theamk 20 hours ago||
there is one 9 of uptime, but the dashboard hasn't been updated yet: https://mrshu.github.io/github-statuses/

Once this goes in, I'd expect to see 89%, which is zero nines. (I'd like to say, "a new low!", but sadly we've had this before)

ch4s3 20 hours ago|||
They're running 9 8s of uptime.
pbkompasz 20 hours ago|||
nein nein nein
canadiantim 19 hours ago||
Ah that checks out, was wondering why my PR's were piling up.
timetraveller26 19 hours ago||
If anybody is looking for alternatives, self host Woodpecker is really easy and it's a very capable CI/CD https://woodpecker-ci.org/docs/intro
homeonthemtn 19 hours ago||
Still twiddling thumbs over here
dboreham 20 hours ago||
Someone needs to work on improving the way Actions deals with resource exhaustion like this. Today it exploded all the CI jobs with "failed" and an inscrutable message about "The job was not acquired by Runner of type hosted even after multiple attempts" then "Internal server error". It should say "Timed out due to no runner available, our apologies, try again later, or pay $$$ here to get priority for runners".
throw03172019 12 hours ago||
Degraded is an understatement. It’s been totally down all day. Crazy.
homeonthemtn 21 hours ago||
Ah. So that's why.
gajus 18 hours ago||
so... what happened?
jmaw 18 hours ago|
Sorry folks, guess my GHCP query was too large...
swyx 17 hours ago||
i guess this is a good time to mention that smol forge is open for the first 100 alpha users!

point clanker to forge.smol. ai/llms.txt

for now its just a fast agent native git remote and u can check docs for the extras.

richwater 15 hours ago|
Gotta wonder what they're up to over there.

Is the AI slop that bad? Culture change?

Wafje 15 hours ago||
Unprecedented load.

From the GitHub COO on April 3rd:

    Platform activity is surging. There were 1 billion commits in 2025.
    Now, it's 275 million per week, on pace for 14 billion this year if
    growth remains linear (spoiler: it won't.)

    GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week
    in 2025, and now 2.1B minutes so far this week.

    So we're pushing incredibly hard on more CPUs, scaling services, and
    strengthening GitHub’s core features.
mgh95 15 hours ago|||
I find this hard to believe in this context. They should be utilizing load shedding or admission control and killing/rejecting jobs rather than hard failures if it is a scaling issue. It's much more likely an actual software defect than just more load. If this was the case (which they would likely prefer) free/public tiers would be removed first to preserve paying customers services.
woodruffw 15 hours ago||
Why not both? Higher base load combined with insufficient internal controls for ratelimiting/load-shedding (as in, they don’t know who to shed) would be explanatory.
mgh95 15 hours ago||
If they can't implement something as simple as "decode upstream headers and determine if 429/503" I don't know what to say. Since this has knocked out all customers it indicates they likely don't have anything of this form implemented.
woodruffw 15 hours ago||
I meant shedding of legitimate base load, not retries. I think we can safely assume they do the latter.
mgh95 14 hours ago||
[dead]
maccard 15 hours ago||||
They’ve said that, but it doesn’t add up. The outages started shortly after the migration to Azure became the top priority, and before the load massively increased form agentic coding (by their own dates).
marricks 15 hours ago|||
I guess the AI Slop is that bad in terms of increasing commits/actions/etc
More comments...