GitHub down? Current status and problems

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.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (50%)
• Errors (39%)
• Sign in (11%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Nové Strašecí	Website Down	2 days ago
Perpignan	Website Down	7 days ago
Piura	Website Down	7 days ago
Tokyo	Website Down	8 days ago
New Delhi	Sign in	15 days ago
Kannur	Website Down	18 days ago

Full Outage Map

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:

• 
  simeonGriggs (@simeonGriggs) reported 45 seconds ago

  Just spent an hour debugging something until I came across the answer. The answer I wrote a month ago on a GitHub Issue describing a fix to that problem.

• 
  Edgar Rodríguez (@codingedgar) reported 7 minutes ago

  I need to stop posting github issues at 2am, all my copy&paste are fd up. Is my clipboard drunk at 2 am consistently? …or am I

• 
  Jeff Hodges (@jmhodges) reported 9 minutes ago

  @ljharb @github They should have fixed the complaints instead of making it opt-out. I could imagine they didn't think they had the resources and community support at the time. All the problems discussed in there are solvable

• 
  Ryan Kennedy (@rckenned) reported 9 minutes ago

  @jmhodges @github right, but the transitive dependency thing means it only takes one broken link in the chain to create issues

• 
  Clare Griffiths - out of office until 27 December (@statsgeekclare) reported 13 minutes ago

  @Letxuga007 @Pouriaaa @ChrisBeeley I closed an issue in GitHub.

• 
  Retired Kevin w/ Da Pack (@The_Mystery_One) reported 14 minutes ago

  I can’t work on anything from github and its slowing everything down

• 
  Son Luong (@sluongng) reported 16 minutes ago

  @paulienuh My suggestion is try to funnel all support requests/engagements through 1 portal: Github issues / discussion or Discourse. There you can measure traffics as a signal.

• 
  ThreatMonIT (@ThreatMonIT) reported 22 minutes ago

  Given how ubiquitous this library is, the impact of the exploit (full server control), and how easy it is to exploit, the impact of this vulnerability is quite severe. We're calling it "Log4Shell" for short. POC posted on GitHub. This has been published as CVE-2021-44228 .

• 
  Michael Irwin (@mikesir87) reported 25 minutes ago

  @github Gah! Was too slow this time. Will have to watch for them to come back!

• 
  Jeff Hodges (@jmhodges) reported 29 minutes ago

  @rckenned @github (Er, to join some dots, those libraries would hopefully be doing releases on security problems like this. But if we don't trust that, dependabot and equiv should step in, I mean)

• 
  Jennifer Shehane (@jennifershehane) reported 37 minutes ago from Cuauhtémoc, Mexico City

  Why don’t @github ‘issues/123’ links reroute to ‘pull/123’ links anymore? Is this intended? Because it’s broken a lot of links where we were assuming this rerouting.

• 
  RayOfLight (@kironroydev) reported 39 minutes ago

  @palashv2 Note: GitHub disabled ‘back to top’ (in-page navigation). I am working on problem.

• 
  borud (@borud) reported 39 minutes ago

  Now that people have calmed down and gotten over their disappointment with Github Copilot, could we perhaps put down the crackpipe for a minute and put more smarts into language servers? For really useful things like better error messages and suggested mitigations on code errors?

• 
  Tauqueer Khan | tauq.sol (@_tkoriginal) reported 40 minutes ago

  @TomGeshury @therealchaseeb @armaniferrante Do you mean locally? By going through Solana github issues I found that when running the validator locally, BPF-JIT doesn't support ARM. So running solana-test-validator --no-bpf-jit lets you deploy locally

• 
  Dean Herbert (@ppy) reported 40 minutes ago

  @Spaceman_Atlas it's unfortunate github don't give the tools we need to fix this. if we switched back to issues 100%, we could use the new templates they offer to force users to include certain details.. but they can still bypass it intentionally via url or accidtanlly via not-logged-in bug

• 
  David (@Dave_Canada) reported 41 minutes ago

  @githubstatus Hey, is there a potential issue with GitHub actions and self hosted nodes? We're seeing failures across multiple projects: "The self-hosted runner: xxx lost communication with the server. Verify the machine is running and has a healthy network connection."

• 
  Matt Welke (@MattWelke3) reported 42 minutes ago

  @shipilev @yazicivo Would a private fork help with this? I remember the GitHub researchers mentioning this. They said that one way to fix it would be to fork the repo, collaborate on the fix in the fork, then do a PR from the fork to upstream when it's done.

• 
  Phil Archer (@philarcher1) reported 42 minutes ago

  A quick public apology to @valexiev1 for not yet responding to all the GitHub issues that have tagged me. I know, I know, sorry...

• 
  Jeff Hodges (@jmhodges) reported 43 minutes ago

  @ljharb @github Yeah, thats the kind of stuff that folks making opt-in systems end up with, and working to make them opt-out is great pressure to fix it

• 
  Yılmaz Yağız Dokumacı (@Yagizdoo) reported 44 minutes ago

  Day[3] I looked at Shared Preferences today. I made 2 samples. I couldn't move on to another topic because I was dealing with a lot of mistakes. If I can fix the error in the 2nd example I made, I will post it on github. I'll share it here. #100DaysOfCode

• 
  nawaz khan (@thenawazkhan) reported 45 minutes ago

  Can we make human rights open-source on Github and bug fix all the open issues? Let’s keep updating the versions, folks! #OpenSource #HumanRights #HumanRightsDay2021

• 
  Dallin Warne (@forewarnedyou) reported 49 minutes ago

  I don't have a pcap of exploit attempts, so please test and open an issue in Github

• 
  Dom Barnes (@domster) reported 50 minutes ago

  @xjki @agiletortoise @RebeccaSlatkin Can you even find stackoverflow through all the search results of sites that just scraped every page? See also GitHub issues.

• 
  z80.eth 🦇🔊 | z80.sol (@z80dev) reported 53 minutes ago

  what's the best place to publish a technical tutorial? don't want to go through the trouble of setting up my own domain rn github?

• 
  Matt Welke (@MattWelke3) reported 54 minutes ago

  @shipilev @yazicivo I've been trying to understand why this is so different than other CVEs I've seen. I worked on a CVE where GitHub's researchers were in contact with me privately as they let me choose a schedule to fix a vulnerability they detected in an open source library I maintained.

• 
  Alex Ellis (@alexellisuk) reported 54 minutes ago

  @PierreDeWulf Yes but on GitHub sponsors instead. Try not to let it get you down.

• 
  Jeff Miller (@jmeowmeow) reported 55 minutes ago

  @ln1draw I dropped journaling when I noticed I was circling around the same issues. I've been coming back in little ways "reflect on the day" (GitHub's Good Day) and "anticipate the day" (Lysa Tula Penrose's card draw prompts).

• 
  Louis Nyffenegger (@snyff) reported 56 minutes ago

  @jasonbcox0 The exploit was available 6 hours before this lab. The course actually provides less details that there are publicly available on GitHub. It provides a test environment for people to understand the issue and setup everything to be able to then make sure they properly patched.

• 
  sentient 6 (@sentientsixp) reported 56 minutes ago

  @scottlinux @kawikacheco I thought the GitHub only tracked Nt Mini issues?

• 
  Joe (@Joe_Stead) reported 59 minutes ago

  @TomasJansson @github Yeah, that's an option, but when I've got a broken environment (which I did manually like an idiot) and want to rereun an automatic deploy to fix it, it's really annoying to go through the full workflow just this once.