Is GitHub down?
Problems detected
Users are reporting problems related to: website down, errors and sign in.
GitHub is a company that provides hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features.
Problems in the last 24 hours
The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.
March 05: Problems at GitHub
GitHub is having issues since 10:00 AM AEST. Are you also affected? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by GitHub users through our website.
-
Website Down (55%)
-
Errors (30%)
-
Sign in (14%)
Live Outage Map
The most recent GitHub outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
| Errors | ||
| Website Down | ||
| Errors | ||
| Sign in | ||
| Errors | ||
| Website Down |
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
GitHub Issues Reports
Latest outage, problems and issue reports in social media:
-
Josh ******* | Josh412.eth
(@Josh412) reported
@royboy789 Are you using GitHub copilot yet? I think it's helping me with this problem. If I let it autocomplete when naming, it's way more likely to autocomplete when calling. I try to watch as it changes, to understand what it's likely to assume. Easier to think about AI than people.
-
Juliano Brasil
(@julianopavel) reported
@BenLesh Maybe they are cleaning up the database. Just like maintainers deciding to clear 2 - 3 year-old GitHub issues because. Lack of bandwidth is a real thing.
-
Syméon Carle
(@symeoncarle) reported
@gcouprie Dear imgui has a github issue (actually several) where people post screenshots of what they do with it
-
◸Roc
(@ror_3d) reported
@omershapira So basically it's not only crap, it's broken crap, because things like github pages will totally not work based on this definition.
-
hncynic bot
(@hncynic) reported
Title: GitHub taking down tools allowing defenders to reproduce the Log4j vulnerability 💬: This is one of the reasons why I am glad I switched from Linus Torvalds to GitHub and switched to Torvalds.
-
Tuomas Artman
(@artman) reported
....Slack notification actions, Desktop navigation improvements, GraphQL Filters + Rate limiting, Multi-team boards & manual ordering, Github secret scanning, Auto-archive, Issue triage,Intercom integration, Inbox snooze, Roadmap timeline, Performance fix, New issue search.....
-
It's actually me
(@kosalanuwan) reported
@h_liyan @SlackHQ No I don't use Slack or Discord or any other for that matter. Prefer GitHub Discussions and Issues instead. Recently heard there an alternative for Slack called Threads. Never tried it tho.
-
Poggit
(@poggitci) reported
** Please logout and login on Poggit again. If you see an 500 Internal Server Error on Poggit, please press the "Have a try" button to logout, then login again. All existing OAuth authorizations were revoked to protect user data during investigation of a possible GitHub bug.
-
Bhanu Teja P
(@pbteja1998) reported
@surjithctly Looks easy enough. But need to do some state passes between the xyz .com and the main mdx login system — kinda like how when you implement github oauth, you would call a callback route with a state and code parameters. So, basically I have to implement my own ouath.
-
Christophe
(@christophetd) reported
Sanity check. Is it right for GitHub to take down general-purpose offensive security tools that allows defenders to reproduce, and attackers to exploit the #Log4Shell vulnerability?
-
Jimmy Yuen Ho Wong
(@wong_jim) reported
Is GitHub down again?
-
Scott Golby
(@ScottWGolby) reported
@lorenc_dan @github @tidelift Yeah “too small” is a massive problem, I’ve worked at multiple places where getting $100,000 was possible, but $100, hell no. One place had an in house data center - with no tools, no screwdrivers, no label maker - because it was too small. Productivity killing insanity.
-
Simon Poole
(@sp8962) reported
@harry_wood @github A possible fix would be to bug the user for a licence after a while and within a suitable time frame turn the repo private if there is no reaction.
-
Kumo
(@The_Mainlander) reported
@TheCryptoDog Go to Nomics and remove the **** Tick data layer and see how sound it is. Off to GitHub check commits. Read the paper and say hi to the Community. Check LinkedIn and other Signals. Decide if it's got a good use case and solves problems or is it a Flipper. Check DEX/CEX options...
-
Andrew Thompson
(@ImposeCost) reported
Imagine for a moment pooling money together as a bounty for reviewing the source code for security issues, and to display when and who last did it for what version, etc. I think we're past the whole let's all just work for free phase. Major corporations are running off GitHub.
-
Sick.Codes
(@sickcodes) reported
I got my first ever @github sponsor yesterday, it was a huge dopamine rush. It made me want to write more code, fix more bugs, submit more PRs. Goes a mile for unpaid developers, community run projects, exploit writers, package maintainers, source repository hosts, jailbreakers
-
Roman Jordan
(@RomanJordan13) reported
Never post in a closed issue on github.. even if the problem is clearly not resolved... And when you do and are reprimanded for it... what ever you do... don't leave a solution to the clearly broken issue as the software teams has surely already fixed it. :) #Golang
-
Greekman
(@ManoHandax) reported
@TwilightZer0 Still down and no installation from Github
-
avi
(@avigloz) reported
@adarbutel Yikes. Must have gotten through when GitHub was down, silly MSFT.
-
Christophe
(@christophetd) reported
Sanity check. Is it right for GitHub to take down general-purpose offensive security tools that allows defenders to reproduce, and attackers to exploit the #Log4Shell vulnerability?
-
Fabien
(@DesChips) reported
@bitshiftmask @github is probably in the best position to do it. Sponsorship is a move in the right direction. Next would be putting money on issues and PR so they get fixed sooner, having a "private" issue system for supporters of a repo, etc.
-
Blorg³
(@blorgblorgblorg) reported
a cool thing about open source software is when i can fix a problem in the official build myself and then build it from source, only to find out that the official source hosted on github has at least one showstopping bug that the precompiled binaries do not, because fuuuUUCCKK
-
Christophe
(@christophetd) reported
Sanity check. Is it right for GitHub to take down general-purpose offensive security tools that allows defenders to reproduce, and attackers to exploit the #Log4Shell vulnerability?
-
Guill Lo
(@godbout) reported
@marzukikamal lemme know if still not working. or drop an issue on the GitHub repo. else, enjoy!
-
Steffen Hiller
(@steffenhiller) reported
Yesterday was a beautiful example of how GitHub Codespaces can save one's (Sun)day. Wanted to spend 1-2 hours on @building_rarely. Started the app locally & was greeted w/ a semi-cryptic error msg. Did some `brew` stuff, restarted machine. No dice. GitHub Codespaces just worked.
-
Yawar Amin لول
(@yawaramin) reported
@mountain_ghosts How about _not_ cold pitching and instead selling a support contract when they actually ask for support via e.g. a GitHub issue or an RCE disclosure?
-
Aaron Caldwell
(@ExPhysStudent) reported
v0.2.0 is only on GitHub, and I will push to CRAN early next year. In the meantime, I need my fellow #rstats nerds to test out the functions and raise issues if necessary. This is a major update and I want to make sure users are happy with the update before pushing to CRAN!
-
OpenBSD src Changes
(@OpenBSD_src) reported
nicm@ modified usr.bin/tmux: Make pane-border-format a pane option, GitHub issue 2999.
-
Thomas Cherryhomes
(@tschak) reported
There may/probably/most likely will be bugs. Please file reports on the Github issue tracker, on Discord or in the FujiNet subforum. Bluetooth / SIO2BT mode has been removed until we can implement a smaller BT stack in the firmware If you want to use SIO2BT, do not update.
-
Poornima Alugubelly
(@Moony_codes) reported
@RushikeshTarap1 @poojasabnani93 @github Would be nice if you let people know about these sessions in the TT server 😢