Untitled topic
1–8 of 8 posts
No post body was provided.
Re: undefined
#2[deleted]
Re: undefined
#3[deleted]
Re: undefined
#4https://www.githubstatus.com/incidents/j2fdyn2v9df9
"We are currently investigating this issue." at Aug 11, 2025 - 18:51 UTC
Re: undefined
#5Yes, seeing periodic 5xx errors (though eventually succeeds).
Interestingly `bun upgrade` catches "GitHubIsDown" as a specific case:
$ bun upgrade
Bun v1.2.20 is out! You're on v1.2.18
Downloading [38003/21788202] Bun upgrade failed with error: GitHubIsDown
Please upgrade manually:
curl -fsSL https://bun.sh/install | bash
(Appears to have been triggered by a 503 for https://github.com/oven-sh/bun/releases/download/bun-v1.2.20...)Re: undefined
#6Yes, seeing periodic 5xx errors (though eventually succeeds). Interestingly `bun upgrade` catches "GitHubIsDown" as a specific case: $ bun upgrade Bun v1.2.20 is out! You're on v1.2.18 Downloading [38003/21788202] Bun upgrade failed with error: GitHubIsDown Please upgrade manually: curl -fsSL https://bun.sh/install | bash (Appears to have been triggered by a 503 for https://github.com/oven-sh/bun/releases/download/bu…
That's hilarious. GitHub going doing is definitely a common enough case to flag. It's been better the last six months or so, but still pretty bad. Half the incidents aren't flagged either.
Re: undefined
#7Such situations happen from time to time... Unfortunately, outages and downtime are what we need to learn to put up with
Re: undefined
#8GitHub outages should be taken seriously - they can really leave u with no access to data, damaged reputation and a complete stop of business operations. I found this report which u may find useful.
https://gitprotect.io/blog/cisco-guide-to-devops-threats-pip...