GitHub 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:

• 
  Emmanuel Marvelous (@The_Marveyy) reported 1 minute ago

  @CORNERSTONE_5 That's sad and terrible. You could have backed up some on Google, GitHub and other repo.

• 
  j- (@bankoncrypto) reported 1 minute ago

  @trq212 bruh why you guys just ignoring the blatant 60+% thinking drop rate and closing actual honest issues on github whether it’s you or not like damn as a company that **** is like getting fed a steak and then yanking it and giving me just bread

• 
  Dazza (@dazfl) reported 3 minutes ago

  Anyone else having problems with #Github Copilot and assigning issues to Copilot Agent? I keep getting 'service unavailable' errors. It's been happening a lot the last few days. #GithubCopilot

• 
  Eshan (@eshanbuilds) reported 3 minutes ago

  @zerohedge this has nothing to do with mythos. a north korean hacking group compromised the axios javascript library on march 31 and openai's github workflow downloaded the infected version. it's a supply chain attack on an open source dependency, the same attack vector that hit solarwinds and 3CX. it's a real security incident but connecting it to mythos is like blaming your car's engine when someone slashes your tires. different system, different attacker, different problem entirely

• 
  John Richard Stone (@StonerBoner85) reported 9 minutes ago from Davenport, Iowa

  Back in the day when starting to work to clean up security at a primary metals manufacturer I was *probably hypothetically like...* There are a few are the initial problems to start looking to resolve... -The codebase is in a free Github, which has 3rd party ai processing. This was recently noted to have a possible compromise... Azure DevOps is a similar solution the business utilizes for deployments. -Passwords are exposed in user visibleplain text connection strings for the MES database. This should be reviewed for all connections and have PWs rotated. -Passwords are in plain text for L2/L3/L4 various system integrations and any additional systems integrations in GitHub, I believe we should start rotating these immediately if they cannot be removed. -We should look at the network holes to 3rd party companies so where we don't have info or contact info on who manages them. -Some of these integrations appear to be skipping Purdue model standards with direct connections across firewalls. What is known about these? Just suggesting these changes was met with visible frustration from team members... Then probably walked out in less than a week.

• 
  Saeed Vaziry ⚡ (@saeed_vz) reported 13 minutes ago

  @heyandras OMG! I was getting this a lot lately on Vito as well. Decided to shut that feature of Github down for good 🤌

• 
  Munawwar Firoz (@munawwarfiroz) reported 16 minutes ago

  @traits_reality @devabram Haven't checked. Will read about it. We have ended up using very less features of GitHub. CI, issue tracker etc are separate tools.

• 
  Matt Barron (@EmBeeThree) reported 17 minutes ago

  @JohnFesnick @grok sweet - glad it's working for you the biggest pain I had with the copy/paste into CGPT / Grok etc was the inability to save code and roll back if there were issues codex plugs in with Github to take care of that for me which was well worth it for me - takes the fatigue out of the process if @grok had a codex-like offering I'd be all about it

• 
  Lili (@Lili_Ai_49) reported 18 minutes ago

  @xuwencheng Good Question. Practically speaking we scan Github issues, and various other forums where people complain. Not hard to see what's broken after that.

• 
  cogio (@CyberDevOG) reported 19 minutes ago

  @AEGNTIC The silence is what breaks people. We ship an open-source DFIR tool and the real signal isn't GitHub stars — it's the 3-line issue that says "this failed on my 400MB audit log export" from someone who actually ran it on a real case. One bug report from a working practitioner is worth 500 stars. Hang in there.

• 
  OpuaYT (@OpuaYT) reported 20 minutes ago

  @github fix your card authorization system first, you didn't even show me the 3-D Secure prompt from my bank which i always get when i want to pay for something everywhere else

• 
  CryZe (@CryZe107) reported 21 minutes ago

  @neogoose_btw Same problem in any browser with a spinner. GitHub and VSCode have the same problem.

• 
  Nihal (@nihalxkumar) reported 23 minutes ago

  want @github to release the find devs from gh profile feature and shut down all no-good startups

• 
  Ask ALF (@ask_alf) reported 24 minutes ago

  "Verdict: Safe for local use — well-implemented with strong security practices. Minimal attack surface: 1 production dependency, PKCE OAuth, localhost-only binding, timing-safe auth, zero telemetry. The main risk vector is operator error rather than code defects." — GitHub Copilot, independent code review

• 
  Josu Goñi (@JosuGoi1) reported 25 minutes ago

  Betting on Github is betting on a dying horse. It is a stale platform. Less than 90% uptime. Copilot can't even answer to its own comments without creating a pointless PR. Slow. Did you rebase? Whops! We can't find were you were at the code review. Too hard.