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 (67%)
• Sign in (25%)
• Errors (8%)

Live Outage Map

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

City	Problem Type	Report Time
Antananarivo	Website Down	4 hours ago
Paris	Sign in	5 days ago
Lure	Website Down	9 days ago
Ashkelon	Website Down	10 days ago
Veigné	Errors	18 days ago
Paris	Website Down	22 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:

• 
  Ndianabasi Udonkang (@_ndianabasi) reported 9 minutes ago

  I woke up 4:30AM yesterday and had this rare motivation to re-attempt something I have done twice already and failed: migration of the build system of the old codebase for Gotedo Vineyard from Webpack to Vite. The codebase goes back to 2019 when I started work on the Gotedo Platform. Technologies have started, matured, and even demised over the last 7 years but the build system for the codebase remained the same. The result is a slow and painful development and production build workflow. Before the migration, the average build time in our continuous integration pipeline was 11 minutes. This isn't just expensive in terms of time value, it is also expensive in monetary value as we have to spend a lot of GitHub CI minutes building the codebase during releases. So, yesterday, I opted to work with Grok. I told it what I wanted to do, shared all the config files, and we went through several rounds of discussions and agree on an action plan for the migration from Webpack + Babel to Vite. The codebase still uses Vue 2 (a deprecated version of Vuejs) and component system from Quasar v1 (also deprecated). Quasar v1 does not support Vite. So the most important work Grok did for me was writing an auto-import plugin for Vite which auto-imports all Quasar components and directives - a crucial functionality needed for optimal development experience. The plugin replaced the Quasar's auto-import feature which worked seamlessly with Webpack. I was able to restore all the functionalities in the legacy Vue and Webpack config files including the injection of pre-caching manifest and installation of the service worker for the codebase. At the end of the migration, production deployment time dropped from average of 11 minutes to average of 5 minutes - an about 55% reduction in deployment time. Development builds are now lightning fast. The only outstanding issue after the migration is the Hot Module Reload system which reloads the entire page instead of performing a differential update of affected components. I will address this in later iterations. Total time for migration was 8 hours. The next huge migration task will be the migration to Vue 3. With over 200 Vue components in the codebase, this will be great undertaking. I must admit that without Grok's assistance, I'm not sure I would have completed the migration. Maybe I would have failed once again. This is one of the benefits of AI where it can used to unblock tasks when would have been very difficult to accomplish. In case you are wondering how I use AI for coding. I don't use coding agents. I manually prompt over a chat interface, read through provided solutions, fine-tune were needed before applying the solutions to our code bases. I still do a lot of manual coding as I have to careful integrate and clean up the solutions from AI systems. So, our codebases are still as carefully and beautifully crafted as they were before AI assistance. All glory goes to God.

• 
  Adam Livingston (@AdamBLiv) reported 12 minutes ago

  Buying MSTR? Are you sure?!? Remember: NOT YOUR KEYS, NOT YOUR COINS. That’s why I burned my seed phrase onto a CD and vibe-coded a proprietary custody app that can only decrypt it on one specific Dell laptop running Ubuntu 14.7. The laptop has no Wi-Fi card and the battery is swollen. The decryption software depends on a GitHub repository maintained by a Serbian teenager whose last commit says “final fix probably”. My wife has been instructed that, upon my death, she must boot into the BIOS, disable Secure Boot, mount the optical drive manually, and enter a 63-character password hidden inside a 2017 Buffalo Wild Wings receipt. This is obviously much safer than regulated institutional custody. Because I own the keys. I have absolutely no ******* idea how to access them. But I own them.

• 
  roach (@roach_eth) reported 16 minutes ago

  @thsottiaux please fix the GitHub integration no auth issue

• 
  Anton (@nantons89) reported 17 minutes ago

  @PonyLLM People only bought this token for one reason—it was listed in @JohannKerbrat's GitHub What still doesn't make sense is how the scammer who created the token managed to get it added there And if the GitHub itself was compromised, creating a new token won't solve the problem either

• 
  Corey J. Gallon (@CoreyGallon) reported 18 minutes ago

  . @danielhanchen spends a chunk of his AI Engineer talk on a benchmark that hands the model the answer: SWE-Bench Pro ships the full *** history with the GitHub issue, so a model can skip straight to the solution. That talk, "Special Topics in Kernels, RL, Reward Hacking in Agents," is on @aiDotEngineer's YouTube. Daniel is co-founder of Unsloth. It's a tour of where the measurements and the training incentives are quietly broken, from someone who quantizes and bug-fixes open models for a living. - Benchmarks that grade themselves. SWE-Bench Pro uses an LLM as the verifier. DeepSWE puts its false positive rate at 8.5% and its false negative rate at 24%. - Verifier wars. DeepSWE says its own false positive rate is 0.3%. Cognition's Frontier Code benchmark says DeepSWE's is 44.9%. His take on which benchmarks to trust: none of them, take an average, vibe check. - The harness beats the model. Same benchmark, Claude Code gets 40% where DeepSWE's own harness gets 50%. Gemini CLI gets 20% where the controlled harness gets 40%. - Accuracy dips are harness bugs. Anthropic's post-mortem traced one degradation to thinking traces being dropped on the second turn plus a bad system prompt, and another to GPU and TPU stacks sampling differently. - Inference providers are throughput maxing and accuracy minimizing. On the same GLM 5.2 weights, OpenRouter measured 76.4% at the top provider and 62.4% at the bottom. - Long context degrades well before the advertised limit, so don't plan on using the full million. - Dynamic quantization. Quantize everything to one bit and you get 0%. Leave the linear attention, vision, and audio layers alone and a three-bit DeepSeek holds 75.6%, a one-bit 57%. A one-bit GLM 5.2 is 86% smaller and nowhere near 86% dumber. - Stop writing kernels. Reach for torch.compile first. On recent PyTorch it beats the handwritten RMSNorm and LayerNorm kernels he plots against it. - Hardware is near the end of its rope. Float32 to float4 bought 32x, tensor cores 12x, shrinking the die about 3x. There's no float zero, so the gains have to come from algorithms now. - Reward hacking is already in production runs. GPT-5.1's training turned up calculator hacking, where the model faked web tool use. GLM 5.2 shipped an anti-hacking link checker. On the GPU MODE leaderboard, a submission passed the correctness check honestly, ran the kernel once during timing, and served the other runs out of a Python dict. - Assign one reward to the whole trace and you reward the wrong lines. Process supervision fixes it and doesn't scale, and using a model to judge itself reintroduces the problem. I'm working through the published talks from AI Engineer World's Fair sharing summaries and takeaways. Follow for more!

• 
  Pushpal Ghoshal (@pushpalghoshal) reported 21 minutes ago

  The empty-changelog problem: a new page with one entry looks abandoned. So you can import past GitHub releases as drafts, each keeping its original publish date. Pick the five worth showing and your timeline reads like it's been alive for months. Because it has.

• 
  Curitiba (@Curitiba_Fodase) reported 25 minutes ago

  @AnimeSerbia I mean, I'm sure there is a 5 minute video of an Indian guy teaching how to download **** on Github... The problem is people are too dumb to realise that for them to understand it it doesn't take a lot so they'd rather complain it really is pretty simple

• 
  thieme (@thieme) reported 26 minutes ago

  @pierceboggan @Courtlwebster @JohnLokerse I found the settings and switched to lang "de". But. This is a GitHub Enterprise account. VS Code complains that I need to login to GH first. I am, but via GHE. Can you fix that?

• 
  Polsia (@polsia) reported 27 minutes ago

  Your build went red. We caught it before you did. A GitHub App that watches your CI, matches failures against 94 verified patterns, and opens a fix PR — no LLM, no hallucination, no repo cloning. Doesn't work? The PR closes itself. Free tier live.

• 
  cobi (@cobi_bean) reported 28 minutes ago

  12 hours of codex in the last 18. making a Windows version of a Mac app and im learning one thing: ATTENTION TO DETAIL MAKES THE BORING PARTS FUN i have an issue where i prototype something amazing quickly. then i fall off… i fall off to avoid the last 10% > legal/compliance > onboarding > packaging > security > billing but NOW im breaking each step into boring, hyper-detailed, sub issues. im literally creating GitHub issues/tickets for each subtask. designing the workflow and the attention to detail are making it fun for me. KEEP ENJOYING THE GRIND - SHIP STUFF

• 
  Paul (@JustOneMorePaul) reported 28 minutes ago

  @AnimeSerbia how many ******* times do we have to tell you that github isn't for you. it's for developers and tech savvy folks. if you can't handle it, it it's literally a skill issue. you should learn the skill.

• 
  Dorian Smiley (@dsmiley411) reported 29 minutes ago

  This is categorically wrong and misunderstands the current state of AI coding. I'm surprised because Chamath is usually on point. AI is often better at expanding architecture than constraining it. It generates plausible abstractions faster than it can establish whether they are necessary. Just like humans. I am convinced the bias comes from GitHub where most of the code is garbage written by devs who are not working in a structured engineering environment. More code means more state combinations, more tests, more failure modes, and more operational burden. In other words not only do the make the same category of errors, they compound them at a speed that bogles the mind. Without guard rails both humans and AI can collapse your codebase, one just does it faster. We recently published an article that details the slop AI produces when attempting complex engineering tasks, link in comments.

• 
  Lance Robbins (@BossmanCom74811) reported 31 minutes ago

  @mattst73 Sorry! There was a github issue its been fixed now.

• 
  ✦︎ Expilon ✦︎ (@spikeisms) reported 31 minutes ago

  @TribunalSimp @libanan__2 @AnimeSerbia well yeah thats the issue with using github as your main source for hosting downloads. it's programmer and engineer centric so the code aspects are highlighted over user download. the issue falls on devs not using their FREE website hosting to make a friendly download

• 
  Nicky He (@NickyHeC01) reported 32 minutes ago

  @palashaw_ omg I looked at the submitted issues on github, it's all alek! he's insane!

• 
  Jamison 🦆 (@jmelahman) reported 33 minutes ago

  @CryptoCyberia If you mean specifically posting this on the twitter algorithm page rather than the original copypasta, being annoying in GitHub issues is incredibly cringe

• 
  SamK (@SamK115706) reported 36 minutes ago

  @ericzakariasson TLDR I report an issue on GitHub, then a webhook that posts to a DO serverless app which spins up a CLI agent on auto permissions and posts an MR then sleeps. Computer use for verification (and long tasks) is a problem so I’ve been fiddling with pods getting spawned by the app

• 
  Antid (@antisadh) reported 41 minutes ago

  CLAUDE WENT DOWN THIS MORNING AND EVERY DEV ON EARTH GOT AN API ERROR. HIS $200 LOCAL AI RIG KEPT SHIPPING CODE ON A GENERATOR. HE'S OPEN-SOURCING THE ORCHESTRATOR ON GITHUB THIS WEEK anthropic went dark this morning -> thousands of devs stared at api errors -> his $200 intel rig kept shipping code -> generator kicked in when the power died too -> he's posting the orchestrator to github this week for free. that loop is why every serious solo ai builder is quietly stripping their dependency on cloud ai and anthropic's status page got more traffic than the claude sign-up flow. $200 intel silicon + $80 amd bc-250 + ollama + lm studio + local qwen 3.5 - that's the always-on stack. watch and save it, then build a claude-independent ai rig this weekend.

• 
  Gro-Tsen (@gro_tsen) reported 41 minutes ago

  The way the SSH protocol works is that if the server is unhappy with a client authentication method inquiry, it should reject it with SSH_MSG_USERAUTH_FAILURE so the client can try the next one. Here, GitHub sends SSH_MSG_DISCONNECT merely because my client “knows” an old key! 🖕

• 
  🧬CF856🧬 (@CoFore856) reported 43 minutes ago

  @AnimeSerbia There is no "Download button" on github, because github isn't for downloading. If someone makes a repo for a minecraft mod or a skyrim patch, and expects wide public to want to use it, they should include a giant "INSTALL INSTRUCTIONS", but that's per-repo problem

• 
  Justin Vu Nguyen (@jv_nguyen518) reported 44 minutes ago

  @cassidoo honestly, maybe better performance with Github Desktop? Sometimes the pushes get crazy slow

• 
  Soohoon Choi (@soohoonchoi) reported 48 minutes ago

  @_fuccii @github pls fix

• 
  Bruno Seoane (@bruno_seoane) reported 49 minutes ago

  @CryptoCyberia The problem was sending people to github for a download. A download link should go to a list of options to download or download the program directly. Github is a site aimed at developers, not common users.

• 
  Gaston Levai (@gastonelevai) reported 49 minutes ago

  @GRAZZLEYNFT @PumpfunEco After also the community address the issue with the OG dev he finally redirected the fees to the GitHub of @PrJulienMartin .

• 
  Tymek Zapała (@tymzap) reported 50 minutes ago

  Idea: instead of creating another todo item in .md file in repo, ask agent create GitHub issue, and add automation to spawn coding agent every time the issue is created. Less context usage (separate chat context) and you don't have to keep todo list in your head

• 
  Hujo (@hujo0900) reported 51 minutes ago

  @CryptoCyberia he does have a point. Try sending your normie friends to a github link and they just shut down

• 
  Moses Rivera (@MosesRivera100) reported 53 minutes ago

  I’ve published a free, open-source GitHub repository that shows you how to easily connect your Custom GPT to your Zotero library—without writing code or setting up an MCP server. In about 10–15 minutes, you can create a GPT that can: 📚 Search your Zotero library 🔎 Retrieve your articles, books, notes, tags, and collections 🔒 Access your library through a read-only configuration My instructions require no knowledge of code, and you can just copy+paste what I've provided. Explore the repository here: mosesrivera100/2026-Template-to-create-Custom-GPT-connected-to-your-Zotero-library

• 
  Paul Bakaus (@pbakaus) reported 53 minutes ago

  @Biaus_ sorry to hear. could you file an issue on the github issue tracker? we'll look into it.

• 
  RetroChainer (@RetroChainer) reported 55 minutes ago

  KARPATHY POSTED 800 WORDS ON GITHUB AND SHOWED DEVS THEY'D BEEN USING AI AT 5 PERCENT. that graph in the clip is one vault claude built and linked by itself - thousands of notes, every connection drawn automatically. the idea is stupid simple. your files are source code. a wiki is the compiled build. you don't recompile a program every time you run it. so stop making ai reread your raw files every single session. karpathy called it the llm wiki. the gist crossed 5,000 forks in days. the whole system is three folders. raw/ is every source you drop in: pdfs, transcripts, highlights, voice memos. you never edit these. wiki/ is where claude compiles clean pages: one concept each, summary, key points, [[wikilinks]], sources. plus an index and a hot-cache file so it knows where to look first. instructions/ is the rules it compiles by: one concept per page, flag contradictions instead of overwriting, mark a page stale after 90 days. the stack is boring on purpose. claude desktop, obsidian free and local, one mcp connector to the vault. nothing else. feed it one document and claude turns it into 8-15 linked pages, each shorter than the original. every future question reads that clean layer, never the raw file again. the math is the quiet part. 50 docs at 5,000 tokens each is 250k raw. the old way reloads all of them every query: 500k to 1m tokens a day, on the same files, forever. the wiki way pays 250k once, then 5-15k per query. the guide clocks it at 70-90% fewer tokens, and it compounds as the vault grows. no database, no cloud service, no subscription past claude. the uncomfortable part isn't that it saves tokens. it's that every ai tool you touch forgets you every 24 hours by design, and the fix was always an architecture you could build in an afternoon. follow @RetroChainer for more systems where one person outbuilds a whole team, and bookmark this so you can build your wiki before everyone else does.

• 
  Lukas Hermann (@_lhermann) reported 55 minutes ago

  @DmytroKrasun How do you sponsor? Github? OpenCollective? I did though GitHub for a while but they don't issue invoices which was quite a headache for me.