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	8 days ago
Tlalpan	Sign in	13 days ago
Quilmes	Website Down	13 days ago
Bengaluru	Website Down	15 days ago
Yokohama	Sign in	16 days ago
Gustavo Adolfo Madero	Website Down	20 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:

• 
  Evan Bacon 🥓 (@Baconbrix) reported 29 seconds ago

  @ThisIs_VAIB @expo Hmm seems like perhaps a GitHub outage. Reloading the project web page should show you the code again

• 
  Spektion (@spektion) reported 42 seconds ago

  → 𝗬𝗼𝘂𝗿 𝗦𝗕𝗢𝗠 𝗰𝗹𝗲𝗮𝗿𝘀 𝗶𝘁. 𝗥𝘂𝗻𝘁𝗶𝗺𝗲 𝗰𝗮𝘁𝗰𝗵𝗲𝘀 𝗶𝘁. The same package writes to ~/.ssh, encrypts a keystore with an XOR key, POSTs to a GitHub Gist. Process-behavior problem, caught where the process executes.

• 
  rupertnewton (@bklyn_newton) reported 2 minutes ago

  @jefielding non-coder, had a terrible experience cloning app off github with claude co-pilot. put me right off.

• 
  Patrick Roza (@Patrick_Roza) reported 4 minutes ago

  Another day another @GitHub issue, or 10.

• 
  Shreyas Mididoddi (@Shreyassanthu77) reported 4 minutes ago

  @glcst the auth redirect page that auto opens in browser should have a button that I press to authorise the login like how google/GitHub oauth prompts me

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 5 minutes ago

  Everyone's racing to add ai. these 8 companies just quietly removed it. 🤯 → uber burned its full 2026 ai coding budget in 4 months → microsoft canceling internal claude code licenses by june 30 → github copilot moving to per-token billing → cursor killed its "unlimited" plan → klarna rehiring humans after firing them for ai → commonwealth bank rehired 45 staff, called the cuts an "error" → starbucks killed its ai inventory tool after 9 months → duolingo pulled ai out of performance reviews vc: @nicos_ai

• 
  Febb (@xFebbio) reported 6 minutes ago

  GitHub is one of the most critical platforms in the world. And they just lost control of 3,800 internal repositories through a single compromised VS Code extension. Not because the system is weak. But because there's no layer that can detect, stop, or at least slow down malicious activity before it's too late. And this is just the beginning. In a world where AI agents operate autonomously without humans in the loop, attack vectors like this will become more frequent and faster. Every agent running without clear governance is a vulnerability waiting to be exploited. That's why the most important question in the agentic era isn't how smart the agent is. But who authorized its actions, what are its limits, and is there a record of every decision it made. Rialo is building infrastructure to answer those questions at the protocol level. Governance problems aren't future problems. This is happening today and it will only get worse.

• 
  Kudu Biltong 🇿🇦 (@kudu_biltong) reported 8 minutes ago

  @growing_daniel It's a fun little game, but imagine if you had to solve a Sudoku under pressure to get a job. Same vibes. If my extensive github repo library and my 12-ish Nuget packages aren't enough for you, then maybe the problem isn't on this side of the table.

• 
  Remy Cranen (@Remy_LeBeauBeau) reported 11 minutes ago

  @DannyLimanseta @alhuissi You can set up Actions on GitHub that basically run a check on the files in your repo, to scan for these kinds of potential security issues. You will get notified by the tool scan result. It's just another safety net. You can ask an AI agent to implement it for you.l on GitHub.

• 
  Tianyi-天轶 (@tian_yi_wang) reported 11 minutes ago

  do open ai and anthropic use github? do they not get blocked with millions prs queuing to be merged? and especially github is down so often these days.

• 
  TadasG 💻 (@tadasgedgaudas) reported 18 minutes ago

  While Github is down I want to announce that I have started listening to Gorillaz again after a 3 year break

• 
  Qwee Hoang (@0xqwee) reported 19 minutes ago

  @gdb Please fix all issues reported on Github

• 
  PJ (@peejay291) reported 23 minutes ago

  @aibekjumabek I wish there was a better system to have history and allow multiple work streams on a folder without going down the GitHub route. I know there must be but GitHub for markdowns etc feels overkill

• 
  alexstrauss.x (@alexstrauss19) reported 28 minutes ago

  Seems like GitHub is my server now

• 
  Tejas AI (@VPsing06) reported 28 minutes ago

  @serenaa_ge Finally someone admitting that most public coding leaderboards are basically popularity contests and don’t reflect real messy developer work. Building tasks from scratch + proper trajectory analysis instead of just scraping GitHub issues is the right move. The gap between looks good on leaderboard and actually useful in production is massive.

• 
  HuntYourTribe (@huntyourtribe) reported 32 minutes ago

  🚨 Building an AI career in 2026: ‣ Portfolio > Resume ‣ GitHub > LinkedIn Summary ‣ Deployed project > Kaggle notebook The difference between "I know machine learning" and "here's a model I shipped that solved a real problem" is the difference between getting a callback and not. Show the work. Don't just list it.

• 
  Raunak Singh Jolly (@raunaksinghjoll) reported 33 minutes ago

  why is github down everyday now

• 
  MystiqueMide (@MystiqueMide) reported 33 minutes ago

  @vikktorrrre It’s veryyyyyyyyyyyyy simpleeeeee Check my GitHub or search hermes on my page I broke it down

• 
  sam (@fewshott) reported 35 minutes ago

  @parker__conrad @0x45o Me trying to ask if GitHub is down on Slack (it’s also down)

• 
  Tirth (@piedcipher) reported 37 minutes ago

  also github blocks adding collaborators to archived repositories. no error message, it just doens't work

• 
  Vaibhav Sisodiya (@ThisIs_VAIB) reported 39 minutes ago

  @Baconbrix @expo I dont think it was issue from github, because even the preview, code, launch and chat were not responding correctly. Later they worked, posting cool outputs soon.

• 
  Eric (@EricBWebDev) reported 43 minutes ago

  Github has been pretty bad lately, never ending issues.. Anyone moved away from it ? What do you use now ?

• 
  Willrich (@WillrichOstmann) reported 44 minutes ago

  @rauchg 'Scale GitHub make no mistakes' prompt fails because scale isn't a language problem. It's distributed-systems engineering with production traffic samples, incident memory, rollback authority. AGI optimizes language; ops requires action + memory + authority — different stack.

• 
  Tom (@tomcrawshaw01) reported 44 minutes ago

  The #1 open-source repo on GitHub right now is an AI agent called Hermes. Its founder just gave away the 6 keys to getting real work out of any agent. Most of them have nothing to do with which model you pick. The problem they fix shows up fast. Most people babysit their agents, micromanaging every step, and the work still comes back wrong. So here are his 6 keys. 1. Describe outcomes, not steps. Tell the agent what "done" looks like and the conditions it has to hit, then get out of the way. The models keep getting better at long-horizon planning, so your step-by-step instructions are the bottleneck now. 2. Define "good" or you get slop. The AI has no taste. Leave your standard unspoken and it hands you the average of everything ever written, then thinks it nailed it. Write your standard down, all of it. 3. Explain it like it's an alien, not like it's five. You and I share a lived history, so half of what we want goes unsaid. The model never grew up on Earth, so every assumption you skip stays unmet. 4. Use agents for patience, not creativity. They have infinite patience and almost no creativity. So give them the work a human could do but never wants to, like reading every log line or running the same checks all day. 5. Build the agent that learns once and reuses forever. Their agent booked a Vegas restaurant. 45 minutes the first time, instant the next day, because it saved the skill. One engineer taught their log agent once and the whole company runs on it now. 6. The harness matters as much as the model. The model is the brain and the harness is the body. A great harness with a weaker model beats a great model with a weak harness, because the model just outputs tokens and the harness is what touches your actual work. Put these together and one person starts moving like a team. The founder built Hermes into the #1 repo on GitHub without really knowing how to code. The tools did the rest. There's never been a better time to be early again. I break down systems like this every week. Follow for more.

• 
  Soumava Das (@Soumava_221B) reported 49 minutes ago

  @github @GitHubCommunity Please look into this issue 🙏🙏

• 
  Huintellimance (@Huintellimance) reported 50 minutes ago

  SWE-Bench is broken. Models memorize the answers. Here's what happens when you test coding AI on tasks it has literally never seen before. Datacurve just dropped DeepSWE — a benchmark built entirely from private, unseen engineering tasks. Not scraped GitHub issues. Not leaked repos. Real problems models cannot have trained on. The results are eye-opening. Average solve: 668 lines of code changed across 7 files. That's 5.5× the complexity of a typical SWE-Bench task. This isn't "find the one function and patch it." This is understand the repo, navigate dependencies, edit multiple files, run tests, debug failures, iterate. Actual engineering. The leaderboard: 🥇 GPT-5.5 — 70% 🥈 GPT-5.4 — 56% 🥉 Claude Opus 4.7 — 54% 4th Sonnet 4.6 — 32% 5th Gemini 3.5 Flash — 28% GPT-5.5 dominates. But notice: Opus 4.7 is within striking distance at 54%, and the gap between the top 3 and everyone else is massive. Sonnet and Gemini Flash both below 35% — these models that crush SWE-Bench suddenly look mediocre when the tasks are truly novel. The real story here isn't who won. It's what "good at coding" actually means. SWE-Bench has been gamed. Models see those GitHub issues during training. A high SWE-Bench score now tells you more about memorization than engineering ability. DeepSWE strips that away — and suddenly the hierarchy shifts. 668 lines across 7 files. That's not a patch. That's a feature. That's the kind of work a mid-level engineer does in a day. And GPT-5.5 solves 70% of those autonomously. One more detail: @Chrisgpt mentioned OpenAI already has an internally better model. If 5.5 is scoring 70%, what's next? The gap between "demo-level coding AI" and "ship-to-production coding AI" just got measurable. DeepSWE is the ruler. Which model are you trusting your codebase with — and has this benchmark changed your mind? #DeepSWE

• 
  🌚 YogSotho 🌝 (@YogSoth0) reported 53 minutes ago

  @TheRabbitPy Never heard about Tailscale? You should read about it, it's very useful. That's my home server. Ngnix running locally. I pulled his codes from his github before got nuked. **** Microsoft, they can't take it down.

• 
  Security Weekly Podcast Network (@SecWeekly) reported 55 minutes ago

  Even security professionals are scared to download random packages now. This clip breaks down the growing paranoia around GitHub repos, NPM packages, and PyPI downloads — including sandboxing software in Linux VMs and disabling automatic updates just to stay safe. How much trust should developers still place in open-source ecosystems? #Cybersecurity #OpenSource #SupplyChainSecurity

• 
  Rhinest☆ne (@CrimsonHaze2) reported 55 minutes ago

  @Yishivali I got it from a github repository from a server so maybe?

• 
  Elias Veyr (@EliasVeyr) reported 56 minutes ago

  **** you @github and fix your product. Time to move off I guess.