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	11 days ago
Tlalpan	Sign in	16 days ago
Quilmes	Website Down	16 days ago
Bengaluru	Website Down	18 days ago
Yokohama	Sign in	19 days ago
Gustavo Adolfo Madero	Website Down	23 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:

• 
  JSONP （╯°□°）╯︵ ┻━┻ (@palmerj3) reported 1 minute ago

  I feel like Github needs to show the README above the fold rather than the code. Who gives a **** about viewing the code on web? I'm usually there for clone, issues, or readme.

• 
  Kevin Riedl (@kevinriedl_eth) reported 5 minutes ago

  Nobody doubled their QA budget when AI doubled their code output. That is the problem. GitHub reported 43 million pull requests a month and over a billion commits last year. Code velocity is no longer the bottleneck. But test coverage did not double. QA spend did not double. Review discipline did not double. Most teams scaled output without scaling verification. And AI-generated code fails differently. Not because it is always worse. Because it is confident. It often does not carry the usual warning signs: the awkward variable name, the rushed TODO, the obvious gap where someone ran out of time. The bugs look intentional. We are running QA engagements on software we did not build, and the failure patterns have changed. Not necessarily more bugs. A different shape of bugs. The test strategies that used to catch most issues are now missing more than teams expect. The toolchain changed. The verification layer did not.

• 
  gxjo (@gxjo_dev) reported 6 minutes ago

  I met her in a github issue thread.

• 
  Timur Yessenov (@Timur_Yessenov) reported 7 minutes ago

  @Runclawrun @Runclawrun Right now it is embarrassingly stitched together: GitHub issue/branch, one checkpoint file per run, and a Telegram status card from cron. Closest is Codex/Claude Code summaries, but I still miss the queue view: blocked/done/waiting across runs.

• 
  Jazz Yun (@Jazz_from_Korea) reported 8 minutes ago

  Mistral just turned its chatbot into a full work agent. plugs into Google Workspace, Slack, GitHub. writes reports, handles PRs, processes your emails. one AI across your entire stack. i run a 2-person startup on $200/month in AI tools. we already do what used to take a 50-person team. but we're stitching together 5 different subscriptions to pull it off. Cursor for code, Claude for thinking, Notion for docs, Slack for comms. Mistral is making a bet that the model layer becomes commodity and the real product is the workflow layer on top. if they nail the integrations, the "AI tools" category collapses into one subscription. and a lot of startups selling point solutions are in trouble. 🔥

• 
  Kyriakos (@Kyriakos_Pelek) reported 10 minutes ago

  cursor workflow that saved me: code stays local → push to github → vercel deploys hetzner only runs docker (the heavy scanners) you drive remote docker from your laptop with a docker context over ssh never edit on the server

• 
  Punished Raven | グリフ (@Raven_Glyph) reported 10 minutes ago

  @peach2k2 GitHub fights are the best. I just picture guys with shirts and ties whaling on each other in an office, Apple Watches getting flung out the door, kombucha bottles getting broken on heads

• 
  Adam (@adam_narozniak) reported 11 minutes ago

  @OpenAIDevs Quite useless since you still allow access to only 50 most recent chats. Older ones dissapear from the sidebar and you can't open them even if they are found using this new search :( there're quite a few issues on Github reporting it

• 
  Naya (@bossnayamoss) reported 12 minutes ago

  @SymoneBeez Yesterday I used Codex to build a crazy amount of features across 7 apps. After each GitHub issue was done, a computer use QA agent tested the app like a real user w/ service accounts before moving to the next task. All while I was at Trader Joe’s. All I did was share my vision

• 
  Seanizell (@dj_seanizell) reported 17 minutes ago

  @mtukufumimi @anne_odida Maths isn't the issue here. Assuming a rejected model must be a bad model is. Share your GitHub, I'll share mine. We settle the credentials part of the discussion pretty quickly ju umeamua uulize swali ya upuzi

• 
  Luc Moetwil (@luc_moetwil) reported 21 minutes ago

  pro tip: label all the github issues you don't want to waste claude tokens on then let your non-technical cofounder with a ChatGPT Pro subscription handle them unexpected productivity hack

• 
  Nitin Pulyani (@npulyani) reported 24 minutes ago

  I hosted my site on github pages. Now I need an edge compute layer and a server side deployment. Migrating to vercel. Any better suggestion?

• 
  Dan Greenheck (@dangreenheck) reported 27 minutes ago

  @AndrewDeWitt88 Sorry, I need to fix it to be less confusing. Scroll down to Links section, there is link to Github.

• 
  Ethan (@DuoEthan) reported 29 minutes ago

  GitHub Copilot shipped before ChatGPT. Microsoft had the distribution lead, the developer relationships, the code repositories. It looked insurmountable. Here's the read on what went wrong: Copilot optimized around code generation, right as the market decided context management was the actual problem. You can have a two-year head start and still build for the last problem. Microsoft Build is June 2. They're shipping their own model. And also putting Claude in Copilot, which is a tell.

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 33 minutes ago

  I found a github repo that turns claude code into a 63-agent ai team. and it's completely free. One developer built it. affaan mustafa. he used this exact setup to win an anthropic hackathon, shipping a full product in 8 hours without typing a single line of code himself. A planner. an architect. a code reviewer. a security scanner. all of it running inside claude code. But then i opened the files. and the crazy part hit me: → the 63 agents aren't code. they're written instructions in plain english. → each is a text file telling the ai what to do, how to think, and what to avoid. → the 249 skills, same thing. step-by-step playbooks written in words. → nothing special makes them smart. the writing does. And all of it took 10 months. just using these tools every day and writing down what worked. He didn't win that hackathon by coding faster. he won by knowing exactly What to tell the machine, and saving it so it worked again the next day. The rarest skill in ai right now isn't writing code. it's knowing what to tell the machine.

• 
  hisui 🍊 18+ (@hisuii_vt) reported 33 minutes ago

  @Lina_Hoshino There have been a couple (literally, 2) people who have posted their work on github in the past, but removed it. A while ago, decompiler was written for Live2D 4, but they had to take it down and now operate by "email me" lol Its a niche problem that no one wants to work on...

• 
  Tara O (@taraap2) reported 34 minutes ago

  "Hey @lovable and @antonosika Publish & agent is broken for hours again. Getting 'commit not found' errors on a fresh GitHub repo. Your own AI agent confirmed it needs engineering to fix and there's zero weekend support. This is unacceptable for a paid product. #lovable"

• 
  Kinder • Grinder (@kinder_grinder) reported 34 minutes ago

  @enesakar I use both Context 7, Web Search and Github issue search.

• 
  Henry Stanley🔸 (@henryaj) reported 37 minutes ago

  @antirez Was amazed to see the emoji reactions on that GitHub issue - almost all upvoting people tearing down the maintainer, and downvotes for everyone else. Really depressing

• 
  Alpha Signals on X (@Alpha_Signal_X) reported 38 minutes ago

  @AnthropicAI @claudeai @DarioAmodei One week NO response from Claude Support on paid account that needs backend fix. How can this company IPO at 1T when it can even respond to emails, GitHub or Fin AI? This market is too competitive to be loyal to un loyal companies.

• 
  Blessed_Patriot_2011 (@jwm_anacortes) reported 38 minutes ago

  @github my account is getting 404 errors on all my repositories on both web and ***. Support (ticket number 4402135) closed my ticket saying there are no restrictions but nothing has been resolved. PLEASE escalate!

• 
  AGBABIAKA (@roidesdieux) reported 39 minutes ago

  @github fix your mess!

• 
  Tony Jacob | FindaClip.com (@tonjkb) reported 42 minutes ago

  .@DavidSacks says AI is causing a boom in software engineering AI was supposed to eliminate software developers. Instead, David Sacks notes that GitHub commits just jumped 14x year-over-year, and software engineering job postings are at a three-year high. The panic over AI replacing coders missed a fundamental rule of economics. It's called the Jevons Paradox. In the 19th century, more efficient steam engines didn't reduce coal use. They made power cheaper, causing total coal consumption to explode. AI is doing the exact same thing to software. By dropping the cost of generating a line of code to near zero, AI didn't eliminate the need for engineers. It triggered a massive increase in total code volume. When you make a resource cheap, businesses consume it everywhere. Non-tech firms are now deploying custom software for the first time. They don't need people to type out the code, but they absolutely need humans to architect, manage, and fix the resulting flood of AI output. Source: All In

• 
  Kursakov (@DenisKursakov) reported 44 minutes ago

  🚨 do you understand what just happened to Microsoft.. - They spent $13 billion on OpenAI. - Branded Copilot on every product they own. - Teams, Word, Excel, GitHub, Outlook, Windows itself. The result: fewer than 4.5% of 450 million Microsoft 365 users actually pay for it. So the fix is - another Copilot app.. → GitHub Copilot: separate app → Copilot Chat: separate app → Copilot Cowork: separate app → New "Autopilot": separate app → Super app to combine all of them: new separate app Internal slogan: "Delivering one Copilot" Meanwhile GitHub Copilot - the one product that actually works - is getting eaten alive by Cursor, Claude Code, and Grok Build. Microsoft didn't build too little AI. They built too much, in too many places, for too few people to care.

• 
  Carlos E. Perez (@IntuitMachine) reported 49 minutes ago

  The problem with Copilot is that early AI users (and therefore the most advanced) used ChatGPT. Copilot feels like a constrained version of ChatGPT (it probably was), which led to failing to meet expectations. One could also say the same about GitHub Copilot compared to Cursor and Claude Code. Power users want the best tools.

• 
  pork (@porktoolbox) reported 53 minutes ago

  So many open-source apps in GitHub are now "vibe-coded" with AI. I've just seen it short-sightedly fixing bugs while creating other problems in a famous niche app. It's sad to see. Where would this evolve into?

• 
  Kashan Ahmad (@thekayshawn) reported 54 minutes ago

  @denbvk @didericis @ThePrimeagen I can assure you most developers like to write code in an editor instead of reviewing it on GitHub, you're the exception in that. Infact, the whole problem with agentic coding is that developers feel distant from code which why editors won't go anywhere for a long time.

• 
  Trattow Pugliesi (@TraTTow_br) reported 55 minutes ago

  1/ your ai agent is not “just a chatbot.” it is a confused junior employee with api keys. 2/ the scary part is not the model. the scary part is what you connected to the model: terminal, browser, github, slack, notion, crm, internal docs, mcp servers, production apis. 3/ every tool becomes a weapon if the agent can be tricked into using it. this is why prompt injection matters. not because someone made the model say something bad. because someone made the model do something real. 4/ flowise already had critical rce issues. semantic kernel had prompt-to-rce research. mcp servers are being questioned as command execution surfaces. this is not theory anymore. 5/ the new rule: don’t ask “can the model be jailbroken?” ask: what can the model touch? what can it delete? what can it send? what secrets can it read? what commands can it trigger? 6/ ai security is becoming permission design. the prompt is the entry point. the tool is the payload. the permission is the blast radius.

• 
  Tosin Olugbenga (@TosinOlugbenga) reported 59 minutes ago

  I FIND A BETTER WAY DEPLOYING NEXTJS APP ON MY VPS. We were burning CPU, RAM, and ~10GB of disk on our VPS every deploy building a large Next.js app directly on the server. So we changed the model: Build on GitHub Actions → push to GHCR → Dokploy pulls and runs. No more yarn build on production. Deploys went from 15–20 minutes (when they didn’t fail) to seconds. What changed: → Server = run containers, not compile code → Same image from staging (:release) to **** (:production) → Rollbacks = pull a previous tag → Freed ~10GB from old BuildKit cache alone Same app. Cleaner ops. If your VPS is still building Docker images on every push, you might not need a bigger server — you might need a different pipeline.

• 
  Ayushman Mallick (@AyushmanMallick) reported 59 minutes ago

  6\ Why does ESMFold2 overestimate confidence on disordered regions? From what I understood after reading their Github repo and biohub, its a calibration issue rooted in training objective. It is built on ESMC a language model trained on 2.8B sequences to predict masked tokens.