GitHub status: access issues and outage reports

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 (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	2 days ago
Tlalpan	Sign in	8 days ago
Quilmes	Website Down	8 days ago
Bengaluru	Website Down	10 days ago
Yokohama	Sign in	10 days ago
Gustavo Adolfo Madero	Website Down	14 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:

• 
  Thomas Oomens (@HonestDevIO) reported 24 seconds ago

  @Anas_founder Regular notepad xDBack to digging through closed GitHub issues from 2018 and DMing the same two developer friends who actually answer their Telegram messages.

• 
  Beyond Code (AJ ONeal) (@_beyondcode) reported 2 minutes ago

  @kaihendry @pierrecomputer The point is that GitHub is struggling to be able to produce diffs with 10 files with 20-100 lines of change each - this is a false problem. Even people who used GitHub more than 5 years ago will remember that it used to be able to do this. The point isn't that you'd want to review such a large diff, the point is that it is trivial to render tens or even hundreds of of pages in HTML and have it work.

• 
  AI Archeology (@aiarcheology) reported 6 minutes ago

  I have started to use this mcp to generate podcast about PRs in Github. Connect your Claude to this mcp. It helps to create a mental model in your head. Finish the talk and then finish the review in GH way more effectivelly. uv tool install notebooklm-mcp-cli nlm login

• 
  Avinash Garg (@TheAvinashGarg) reported 7 minutes ago

  @shengzheyao @geminicli Just saw that many issues have been opened on GitHub. ex issue #14

• 
  Man | Research (@ManOnChainX) reported 8 minutes ago

  -> This is why you need to Watch closely that what @Gitbank_io is building... -> Because of they solve problem for Github user they solve problem of crypto wallet as well.. -> You never share your GITUSDC from other wallet... because of they not allow it... -> You need to send from your github account.... -> Also they make launchpad for the github user that if they want then launch token on Clanker without even leaving Github app... -> You don't know what's coming next in $GITBANK 816K right now... DYOR / NFA

• 
  Matthew (@slashreboot) reported 9 minutes ago

  @gospaceport @aylacroft As of right now, my Premium X analytics don’t work. Zenodo had a technical issue they just said “wasn’t a hack” and papers (including all of mine) are not counting views or downloads. GitHub was obviously hacked (where I also have a repo). Quite the convergence of coincidence.

• 
  Mark Maurer (@exanter) reported 11 minutes ago

  This has literally been the question since Dario and Sam have been spouting their bs, and all the “yaya ai” bros have been following suit. since then we have: Massive microsoft issues (win 11, github, etc) lots of security holes with mythos. and lots of vapor ware, for all that it matters.

• 
  Jesse (@Dev_JesseMaduka) reported 13 minutes ago

  @khom_ombo *** isn’t the server.. It just stores code. When you push, tools like Vercel/Netlify/GitHub Actions detect it and auto-deploy your app...

• 
  أحمد (@bracckets) reported 17 minutes ago

  Also with projects, numbered metrics are not the best indicator. A proof of work (portfolio, github repos, even resumes) or a professor recommendation goes a long way. The product goal is to find someone suitable, not punch down or up. That's my opinion though i might be way off

• 
  Tracelit (@tracelitai) reported 17 minutes ago

  @foundrceo AI Autonomous Bug resolutions. @tracelitai does not only tell you what the issue with your code is at runtime, it fixes it and tells you to confirm it on @github

• 
  Coin Bureau (@coinbureau) reported 19 minutes ago

  🤯 Andrej Karpathy's coding rules have officially broken the internet. [BOOKMARK THIS NOW] 144,000 stars. #1 on GitHub for 28 days straight. But 99% of people still haven't heard of them. Here's what a CLAUDE.md ACTUALLY is, and why it quietly fixed the biggest problem with AI coding: It's a text file Claude reads before it touches your code. Standing instructions. It never forgets them. The 4 rules that went viral: - Think before coding. State assumptions. Ask when unsure. Never guess. - Simplicity first. Minimum code that solves the problem. Nothing extra. - Surgical changes. Touch only what was asked. Every line traces back to the request. - Goal-driven. Turn vague instructions into a test that proves it works, before writing code. The dev who built it says it took his accuracy from ~65% to ~94%. The rules aren't the interesting part though. The interesting part is that almost nobody knows you can do this at all.

• 
  Ritu Raj (@Gudakesh_07) reported 19 minutes ago

  6/7 Result? Loading times dropped by almost 70% — from 6-8 minutes down to under 2 minutes. He created a custom DLL patch, shared it on GitHub, and the story went viral. Rockstar eventually added his fixes, credited him in the patch notes, and gave him a $10,000 bug bounty.

• 
  Infinite Orchard (@Infinite0rchard) reported 23 minutes ago

  GitHub Actions accepts cron schedules on a best-effort basis. Sometimes */5 means every 5 minutes. Sometimes every 8. Sometimes every 12. Lintcron can't fix the queue, but it can confirm your syntax isn't the problem before you blame yourself.

• 
  self.dll (@seelffff) reported 24 minutes ago

  karpathy's CLAUDE.md hit #1 on github trending. 220,000 stars. most devs still haven't read it. it's 65 lines. it took AI coding accuracy from 65% to 94%. the 4 rules inside: → think before coding state your assumptions. ask when unsure. never guess. → simplicity first write the minimum code that solves the problem. no abstractions nobody asked for. → surgical changes don't touch code unrelated to the request. every changed line must trace back to what was asked. → goal-driven execution turn vague instructions into verifiable success criteria before writing a single line. that's it. 65 lines. 4 rules. 94% accuracy. save this before everyone else does.

• 
  Lauren Goode (@LaurenGoode) reported 28 minutes ago

  @kshithappens Is GitHub down?

• 
  Rizèl Scarlett 🇦🇬🇬🇾 (@blackgirlbytes) reported 31 minutes ago

  @wayneoflife I imagine GitHub is in between a rock and a hard place..so much legacy code that it’s hard to rebuild the product and solve the actual problem. But I’m not a fan of blocking contributions

• 
  Rahul Chavan (@codecroc) reported 36 minutes ago

  @jun_song github sponsors exists and nobody uses it. thats the whole problem and crypto doesnt fix the part where people just dont pay

• 
  hve 🍁 (@heyhve_) reported 39 minutes ago

  @JoelFickson @github 3000 minutes disappears fast on slow runners.

• 
  Chirag Aggarwal (@Chirag_1313) reported 39 minutes ago

  @Roxas_Root @thekitze and it always hurts lol... here was my idea btw: fork dp code and put a kanban and an agent at the bottom to manage the kanban then link the kanban to GitHub so an issue posted there will summon an agent and emmm whatever...

• 
  Kang Cahya (Tech Dev) (@dyazincahya) reported 42 minutes ago

  Now, here is the deadly trap. 💀 Many of us have a bad habit of setting our database token columns to VARCHAR(255). The moment GitHub sends that new 520-character token, the data gets truncated. The system fails to read it, and BOOM... production error.

• 
  Nyll - Ali Sokkar (@NyllRe) reported 42 minutes ago

  @alvarosabu I personally still search for videos to learn about new tech even things like Hermes agent, issue is most tutorials now are tailored for people with almost no knowledge about the field and now I have to skip the part where they explain what "Github" is

• 
  Jezreal Momoh (@JezrealMomoh) reported 45 minutes ago

  @davidbombal The wild part is that IDE extensions run with the exact same privileges as the editor itself. No sandbox, full access to local keys and filesystem. If a GitHub engineer gets tripped up by this, the default trust model is broken.

• 
  dal-chawal enthusiast (@realshantanu) reported 48 minutes ago

  why is every criticism towards vibe coded apps like "let's see when you leave your env variables in a text file on GitHub haha", almost as if all the models already know not to do that, will explicitly forbid you from doing so, and one prompt to fix security issues is enough?

• 
  Nullspice_ (@nullspice_) reported 48 minutes ago

  @flipper_net Feels like an "all take and no give" type relationship lately with your community. From the outside, it looks like F0 Github development has died or frozen with 0 explanation to anyone involved. Hard to feel good when it feels like extracting free work and not working *with us*

• 
  Hallucinagentic (@hallucinagentic) reported 49 minutes ago

  every coding agent ships with a linear/jira/github connector now. devin, codex, cursor all pull from the issue. that part's done. what i still don't see is the agent treating the issue as binding instead of as a longer prompt

• 
  amlug.eth (@realamlug) reported 49 minutes ago

  @leodev Mail is tricky because of server settings etc doable but just annoying. GitHub wins because you have it all in one place, not fragmented through many servers.

• 
  the peanut gallery (@GunnerDad4) reported 49 minutes ago

  @Tablesalt13 Lmao probably Pegasus but hopefully our tech guys won't leave a github full of keys and passwords exposed like the neighbors down south lol

• 
  revayz (@0xrevayz) reported 51 minutes ago

  Most Polymarket traders are not losing to smarter people. They are losing to 19-year-olds with GitHub tabs open. Last week one wallet made $13,200 because NOAA updated a forecast and the market stayed wrong for 8 more minutes. Eight minutes. That was enough. I started digging through Polymarket repos and realized something ugly: The people making real money are not “predicting” anything. They are running tiny Claude-based bots on cheap VPS servers and front-running human attention. One wallet made $94,000 trading rain and temperature. Another was firing 180 trades a day with average holds under an hour. Not because weather changed that fast. Because humans are that slow. That is the part nobody wants to admit. You are not trading the event. You are trading how long it takes the crowd to notice the event. And bots notice first. They watch NOAA revisions. They watch order book depth. They watch sentiment spikes. They enter before you even refresh the page. The wild part is that most of this infrastructure is already public on GitHub. Meaning the edge is not hidden. It is just being used by people who move faster than you. Most retail traders think they are competing against other retail traders. They are not. They are exit liquidity for people who automated the game first.

• 
  gabriel (@gabrielmfern) reported 55 minutes ago

  the GitHub review experience is once again horribly slow

• 
  Pieter Willemen (@PieterWillemen) reported 58 minutes ago

  @pierceboggan @burkeholland @github - Workflows is really slow. - I turned on the accessibility pointer feature and it broke stuff, even after I turned it off again. - Cannot decently set commit message or stage changes. Then what is the point of having a commit button? Either you have got integration, or not.