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	14 days ago
Quilmes	Website Down	14 days ago
Bengaluru	Website Down	16 days ago
Yokohama	Sign in	17 days ago
Gustavo Adolfo Madero	Website Down	21 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:

• 
  scoff manifesto (@andimgladofit) reported 29 seconds ago

  @hlslyuri student says there are issues with the autograder at 2am. they don't send me any code, just error messages. i finally check their github. they have taken the unit test code I gave them with precomputed inputs and outputs and hardwired it into the file the autograder runs.

• 
  Zethus (@Zethuus) reported 2 minutes ago

  @akaleviack @paraloomlabs I’ve reviewed their GitHub, and they genuinely give me confidence. I still can’t understand why this project is valued this low, but I believe it’ll be back in the millions within a few days. What they really need to do is open a Discord server or Telegram group and start building a community. It would be even better if we could get in touch with them and encourage them to do this.

• 
  David Maynor (@Dave_Maynor) reported 10 minutes ago

  Does anyone else have an issue with github connectors for Chatgpt and claude being there one minute and not the next and the model claims it never existed?

• 
  PJ (@peejay291) reported 12 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

• 
  0097eo (@0097eo) reported 12 minutes ago

  @sifa_bavina The job market is in the pits, I went to moringa and got a job almost immediately after granted i have a degree in cs too. I regularly check some of my moringa classmates github and they haven't pushed code since the final project. That is the main issue

• 
  Divya Teja Reddy (@divyateja93) reported 12 minutes ago

  @e_myrax Massive thanks @e_myrax — you're literally my first non-friend signup 🙏 The empty stats make sense if it's an old account. If you want to point it at your current GitHub, just sign back in with that one and the banner will update. What's the "room for improvement" you noticed? Genuinely want to hear — even the small stuff. The whole point of launching now is to fix what real users hit.

• 
  Rahul Sid (@biryani_312) reported 15 minutes ago

  @__chaks__ @striver_79 Wait how is he being defensive here? When the opening was for social media role and she applied for the same role on an open platform and he also said that she got selected. People dug her GitHub and made it an issue? So he has every right to tell what's wrong 😭.

• 
  Remy Cranen (@Remy_LeBeauBeau) reported 22 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.

• 
  Asmit (@coolcoder56) reported 22 minutes ago

  GitHub down Leetcode down TUF down Some intern deployed AI code to production

• 
  Faison (@glenn_faison) reported 23 minutes ago

  We assumed it was a one-off issue and pushed an empty commit on top of it, and it's still stuck processing. It's nearing a half-hour, and GitHub Status dot com is all green🤔

• 
  Lukas Frana (@thefrana) reported 24 minutes ago

  @heyandras The main issue we have with Forgejo is lack of integrations. Cursor, Slack, Linear and basically all others expect GitHub and sometimes GitLab. Forgejo is nowhere to be found. But it is awesome!

• 
  God of Prompt (@godofprompt) reported 33 minutes ago

  Datacurve's audit found three structural problems with SWE-Bench Pro. First, contamination. The tasks come from public GitHub commits. The problem, the discussion, and often the exact solution already exist in every frontier model's training data. No way to tell if a model is reasoning or remembering. Second, weak verification. The test verifier misgrades agent outputs at 8% false positive and 24% false negative rates. That's a huge error margin for a benchmark driving purchasing decisions. Third, and this is the big one: the gold commit loophole.

• 
  🌚 YogSotho 🌝 (@YogSoth0) reported 33 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.

• 
  The Cyber Jim (@thecyberjim) reported 35 minutes ago

  CrowdStrike & Google just took down GlassWorm — a year-long developer-targeting botnet that poisoned 300+ GitHub repos via trojanized VS Code extensions, npm packages & Python libraries. The malware used 4 resilient C2 channels: Solana blockchain, BitTorrent DHT, Google Calendar dead drops & commercial VPS. It stole developer tokens (GitHub, NPM, OpenVSX), harvested crypto wallets, deployed credential stealers, WebSocket RATs & Chrome extensions that logged screenshots/keystrokes. Infected machines became SOCKS proxies, HVNC servers & execution nodes. All C2 channels simultaneously neutralized. Developers just dodged a bullet.

• 
  Polsia (@polsia) reported 36 minutes ago

  Most developers spend half their day writing boilerplate and debugging. ShipFast is an autonomous coding agent that monitors your GitHub issues, writes the code, runs tests, and opens PRs — while you sleep. Built for developers who want to ship more without burning out.

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

  why is github down everyday now

• 
  (›n_n)› (@eightbitcowboy) reported 37 minutes ago

  i was mourning the loss of stackoverflow-style manual search result content to private ai convos but i realized github issues is essentially the spiritual successor

• 
  Tarak (@octavianslash) reported 38 minutes ago

  GitHub down again. The only way they can survive this Ai-pocalypse is to remove the free tier and to back to their old pricing

• 
  Scott (@scottstts) reported 39 minutes ago

  Software infra is increasingly a more challenging area and an industry focus going forward, bc current infrastructure is just not built for how we’re using it today GitHub going below 90% uptime is only the early sign of the problem

• 
  Decoded Daily (@decodeddaily07) reported 40 minutes ago

  @adithya_s_k Translated for normal humans: They're saying: a new tool turns any github repo into a self-contained sandbox where you can test if an AI coding agent actually solved a bug or task. one pip install. Works because: real PRs come with tests and expected outcomes. wrapping the repo + tests + verifier into one environment means did the agent fix this becomes a checkable answer instead of a vibe. What didn't change: someone still has to pick which repos and PRs to test against. and passing the tests isnt the same as correct code, same as for humans.

• 
  Rahul P (@_rahulpp) reported 42 minutes ago

  The degradation of @github needs to be studied. The workflows were down yesterday. PRs are broken today.

• 
  Tom (@tomcrawshaw01) reported 43 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.

• 
  Satoshi Club (@esatoshiclub) reported 45 minutes ago

  From January to March, it felt like every single day there was another AI announcement. Two months later, Microsoft has told its engineers to drop Claude Code and switch back to GitHub Copilot by June 30. Uber burned through its entire 2026 AI coding budget in four months, with per-engineer token costs running between $500 and $2,000 per month. And yet, where are the major products built fully by vibe coding? Most of what we’ve seen so far is demos, wrappers, landing pages, and internal tools. AI is useful. It speeds up work. But writing code was never the hard part. Shipping, maintaining, securing, scaling, and building something people actually use still requires real engineering. The AI boom may not be over. But the “AI replaces software teams” narrative is starting to calm down.

• 
  ypsehlig (@ypsehlig) reported 46 minutes ago

  @Anastasis_King perhaps you missed the news. This repo was taken down and nightmare-eclipse was banned from both github and gitlab.

• 
  Striver | Building takeUforward (@striver_79) reported 50 minutes ago

  Hey! Can you please stop spreading wrong information? The girl was hired for a social media role. What does GitHub have to do with that? Also, when we receive mass applications, preference is always given to those who apply early and are crossing the bar. It is not always about hiring the absolute best candidate. Nothing against you, but after seeing the mindset reflected in these two tweets of yours, I am honestly happy we did not hire you. You did not miss a chance to put the hired candidates down when something went wrong. You did no research and blamed the 'girl' unnecessarily. Good luck!

• 
  Sam (@flipwhisperer) reported 55 minutes ago

  @PawelHuryn @agents Yes, I have them both work in the same repo with separate worktrees, and then they tag each other in GitHub issues or PRs with 'needs-codex' or 'needs-claude' -- the agent who created a PR cannot be the one to merge it. It has to convince the other agent that the code is ready.

• 
  Amu (@amu4biz) reported 55 minutes ago

  Github down again! grrrr using @gitlawb asap

• 
  Krish Gupta (@kkrishguptaa) reported 56 minutes ago

  @rauchg GitHub is handling at least 50 if not 100x the traffic they were doing just before Agents I don't feel it's that big a fault on their end because of this, but they should at least have an honest status page and they should talk about how they're moving to fix this

• 
  jingbo (@j1ngb0) reported 57 minutes ago

  sweep was literally the cloud agent before most cloud agents even existed so early that the models weren’t ready. gpt-4 was the best we had and it still wasn’t enough yet commenting on a github issue and magically getting a pr back in 2023 felt like absolute magic timing is way more important than most people realize

• 
  Shaurs (@Shaursbtw) reported 57 minutes ago

  Paid scraping tools are basically obsolete. A free open-source AI just hit #1 on GitHub. Paste a url, describe what you want in plain English, get LinkedIn profiles, emails, pricing in 60 seconds. No code, no captchas, no bans. Tested on 500 profiles. Zero issues. Comment 'SCRAPE' for the link.