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 (20%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	2 days ago
Paris	Website Down	5 days ago
Saint-Paul	Website Down	6 days ago
Saint-Paul	Website Down	6 days ago
Mexico City	Sign in	7 days ago
León de los Aldama	Website Down	7 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:

• 
  Repojournal (@repojournal) reported 41 seconds ago

  Claude Code Action just patched a GitHub user-to-server token leak in its sanitizer. If you're running this in CI, update to 1.0.174 today. Better late than in someone's logs forever. 2/5

• 
  AL Amir (@_Amir4pf) reported 54 seconds ago

  'This solution contains packages with vulnerabilities. Manage NuGet packages | Fix with GitHub' Once I see this ,I know I have bugs in my Code 👨‍💻

• 
  West Lord (@MyWestLord) reported 4 minutes ago

  Steph Ango, the CEO of Obsidian, and Claude Code just built the most powerful second brain method on earth, and the full system is INSIDE. While everyone was bolting “Ask AI” buttons onto note apps, Ango (kepano on GitHub) went the opposite way. The problem he saw was simple: Claude Code writes plain markdown and nothing else, so it doesn’t know wikilinks, callouts, Bases or Canvas, and pointed at your vault it fills your notes with broken links. So the CEO fixed it himself by shipping 5 skill files that teach Claude to write Obsidian’s native language: clean wikilinks and frontmatter, database views inside plain text, spatial maps on Canvas, full vault control from the terminal, and a stripper that turns any web page into clean markdown before saving. 41,500 developers starred them. Setup is one clone of his repo into your vault, plus a CLAUDEmd at the root with your folder structure and 3-4 rules that Claude reads first in every session. From there, 3 operations run everything: Ingest takes an article or PDF, splits it into atomic pages and updates 5-15 existing notes per pass, Query answers any question from your own notes while citing your own pages, and Lint sweeps the vault weekly to kill broken links, orphan pages and contradictions. No RAG, no vector database, no embeddings, just plain markdown that an agent reads directly, the same pattern Karpathy gist validated with 14,000 stars in 7 days. And here’s the detail everyone misses: Ango has run his own vault this way for 6 years with almost no folders, because linking beats filing. A meeting note links to a project, a person and an idea at once, while in a folder it lives in 1 place. He built Obsidian on “file over app”, the idea that apps die and plain text doesn’t, and then agents arrived and plain text turned out to be the one format they read natively. Every note app is now racing to add AI, yet the winner spent 6 years refusing to lock your files. He didn’t add AI to the app. He taught AI to speak its language.

• 
  Meligy (@Meligy) reported 6 minutes ago

  My last AI musings while I haven't got to play with Fable or GPT 5.6 for work yet... OpenCode 2 beta desktop app is my main driver with Opus 4.8 (notable plugins: Context Mode and Oh My OpenAgent ). I really don't like losing the left project/session menu in new UI though. When I go back and try Codex, I really enjoy it. Unfortunately, GPT 5.5 on Azure is still unreliable for me. So, I only try it when I miss it (every now and then). I tried T3 Code today. Custom gateway support works OK with the Codex and OpenCode providers. I'm liking the OpenCode provider with Opus 4.8 the most now. Saw the browser tab. Looks promising. I doubt it'll be as good as Codex, but will find a reason to play with it. I am also now officially an AI engineer, using AI for real work for several weeks / months. The trick: review AI code as harsh as you review human code. I am also offloading some small GitHub issues to cloud agents. Unfortunately I cannot say much about the specific choice (as I don't know what I can and cannot say). But I'll tell you this: talking to the cloud agent back and forth is an amazing exceperience, even though the cloud agent responds async and takes time to do so. It's actually OK for me that AI is slow. This allows me to get some technical work done in between focusing on my primary work, collaborating with real people, AKA meetings!

• 
  DataTalksClub (@DataTalksClub) reported 6 minutes ago

  You should be comfortable enough to: - Write basic code in Python, JavaScript, TypeScript, or a similar language - Use the command line - Work with *** and GitHub - Clone a repository - Run commands - Read errors - Debug and test changes 2/5

• 
  Tomek | Builds & Learns (@tomek_builds) reported 12 minutes ago

  GitHub just made patience the default setting in Dependabot. Version update PRs now wait until a new package release has been available for 3 days. Security updates still open immediately, and teams can change or disable the cooldown. A small delay that may stop you from being first to install a broken or compromised release.

• 
  silentsuite.io (@silentsuiteio) reported 18 minutes ago

  And then there is the problem of never accessing account that used this Microsoft account to sign in. That is not that big of a problem for Microsoft, because that isnt an option, but the same could happen to your Google or Github account. So never use third-party services to sign up to something, you risk loosing big

• 
  SaSame (@SRLsasame) reported 19 minutes ago

  7. Preliminary interpretation The available evidence supports the following limited conclusions. Confirmed ・The public MCP endpoint is reachable. ・The endpoint completed MCP initialization. ・The server negotiated protocol version 2025-11-25. ・The server identified itself as vibekit version 0.7.2. ・tools/list succeeded. ・36 tools were listed. ・The listed tools had typed input schemas. ・The observed tools carried applicable annotations. ・An unauthenticated tool request produced a structured authentication error. ・An unknown method produced a structured JSON-RPC error. ・The protocol and schema observations were materially consistent across July 11–14, 2026. Not confirmed ・Whether a newly issued API key currently works. ・Whether authenticated vibekit_list_apps returns substantive account data. ・Whether deployment tools complete successfully. ・Whether GitHub authorization is correctly enforced for every repository. ・Whether environment-variable values are redacted or exposed under all client configurations. ・Whether database queries enforce read-only behavior in every case. ・Whether destructive tools require confirmation at the server layer. ・Whether task execution, deployment, rollback, and QA are continuously available. ・Whether the observed 36-tool surface remains unchanged over time. ・Whether all tools behave consistently across every supported MCP client.

• 
  †saint‡ (@Shallom_Okpapi) reported 20 minutes ago

  My setup: Bot 1: Live odds monitoring Bot 2: Arbitrage scanner Bot 3: Alert engine All sharing the same key → constant 429 errors and failed runs. GitHub Actions kept retrying. Credits evaporated. I nearly missed key opportunities mid-tournament.

• 
  Darran Shaw (@kopheart) reported 21 minutes ago

  @sama Don't throw stones in glass houses, AI is a new frontier and privacy issues need to be addressed by all AI bodies as they learn Related OpenAI privacy issues exist but are different:Occasional overreach in screen-capture tools (e.g., full desktop screenshots during agent sessions). Prompt-injection exploits in GitHub Copilot/Codespaces that could allow repo takeover if malicious code is present. Data retention in memory/features, but not automatic full-repo *** bundling.

• 
  josepha_mayo (@josepha_mayo) reported 22 minutes ago

  im calling out @cognition for this slop in 2026, imagine a model doing this, and it claims to beat/match gpt5.5? they said it was better than kimi k2.7 code at coding- true, i used and verified but kimi k2.7 code never loops like this the model is beyond damaged, they really damaged the reasoning, i wonder if they used different optimizers or idk what made it this bad it also thinks like "push kaggle, push github, go "von" folder" it cant predict "to" ever again - which kimi k2.7 code never had that issue

• 
  Ansh (@anshkapuriya) reported 23 minutes ago

  It’s not only one thing. 1. ChatGPT and Codex are now one. No storage issue. 2. ChatGPT work is in action. No dependency on Codex, which always used to give a developer tone. 3. Plugins – they are way more than expected. I am too impressed. 4. GPT 5.6 sol - A model which now feels like talking to a real person. It understands everything, replies properly, and has fewer hallucinations. 5. Banked reset now shows proper timing of all the reset credits. 6. The effort slider has improved the UX. 7. I can use Codex more effectively from my phone. 8. When I hit my Codex limit and want a small change in my code, I go to chatGPT web and perform the change directly on GitHub.

• 
  WILL NESS (@WillNessAI) reported 28 minutes ago

  @mattpocockuk Interesting theory!! The output could be an HTML artifact that implements the "If you answered A, don't do section D" logic. For the 'during meeting' scenario, I constantly do grill sessions with my team on a call. I just screenshare my terminal. It is my favorite part of work - getting in a call with all the relevant people and just brainstorming a feature. For async.. if we can make the assumption the other person is using coding agents you could build some really cool async grilling tooling using github issues as the context source to pull from (just like wayfinder).

• 
  Ofek Shaked | AI Engineer (@VibeCoderOfek) reported 30 minutes ago

  Vibe coding without a spec step is just expensive trial and error. Making the agent produce a structured spec, clarify assumptions, and plan before touching code is the difference between guessing and engineering. GitHub shipping this as open source is the right move.

• 
  Padma Neelamraju (@PNeelamraju) reported 35 minutes ago

  Open-source supply chain security continued: Additional strengthening measures address build infrastructure and process. Reproducible builds ensure identical outputs from identical inputs regardless of build environment. This requires eliminating contextual information like machine architecture, hostnames, temporary directory names, and timestamps from build outputs. Reproducible builds enable verification across multiple machines. If two independently built binaries match bit-for-bit, either both are correct or both were compromised identically. The latter has lower probability than single-machine compromise. Go distributions are fully reproducible regardless of operating system or processor architecture. Dedicated secured build machines reduce attack surface. Cloud services like Google Cloud Build or GitHub Actions can be locked down more effectively than individual workstations that run browsers and chat applications. Source control and build machines must be secured to ensure what is in source control is what gets built. Engineering workstations still require baseline security to prevent source code modification during development. Process improvements remove unilateral access. Google requires two employees to coordinate for any production code or system change, similar to two-person nuclear launch protocols. For source code, this means author and reviewer. For Go as an open-source project, changes from non-Google authors require two Google employee reviews. Production system access requires two-employee authentication coordination. Monitoring requires software bills of materials: machine-readable dependency lists for all built software. When new attacks are discovered, organizations must quickly identify affected systems and update them. The log4j incident demonstrated the cost of poor monitoring capability.

• 
  Hermann (@dhlotter) reported 35 minutes ago

  A red X sat in my CI all morning. Four deploys trying to make it pass. The test was never broken, it just can't run in CI at all. Cloudflare blocks the headless browser from GitHub's IPs. Four deploys to add one line that skips it. #buildinpublic

• 
  Defender of the Basic (@DefenderOfBasic) reported 35 minutes ago

  @leo_guinan I think what you're hinting it is possibly an answer to Matthew's question here? I'm thinking about it because I got a random person commenting on my GitHub issue saying they could solve my problem for payment, and I think they actually weren't a bot

• 
  Mark Ajzenstadt (@mardehaym) reported 36 minutes ago

  A startup CTO in Portland runs coding agents on every pull request. 8 developers, 15 agent sessions each, every day, 50,000 output tokens per session. By API on GPT-5 Mini: 6 million output tokens a day. $12 a day. $4,320 a year. An ML engineer in Seoul debugs training pipelines with tool-use agents. 200 calls a day, 4,000 reasoning tokens each. By API on Claude Haiku 4.5: $4 a day, $1,440 a year. His training code leaves his network 200 times a day. A PhD student at ETH Zurich runs 50 coding agent experiments a day. She needs Fable 5 quality reasoning. 10 million output tokens a day. By API on Fable 5: $500 a day. She burned her $3,000 monthly research budget in 6 days. All three pay a cloud provider to reason for them, per token, per request, on repeat. MiniCPM5-1B-Claude-Opus-Fable5-Thinking is a 1 billion parameter model fine-tuned on Fable 5 thinking data, built on OpenBMB's MiniCPM5-1B. Chain-of-thought reasoning, code generation, debugging, native tool calls, 131,072 token context. English and Chinese. Runs on any GGUF runtime. You give it a coding task, get reasoning and a solution back on your machine, with no API key and no internet connection. Anthropic charges $50 per million output tokens for Fable 5 reasoning patterns. GnLOLot fine-tuned those patterns into 1 billion parameters. 688 MB at Q4_K_M. 1.15 GB at Q8_0 (recommended). LlamaForCausalLM architecture, no custom kernels. Every GGUF runtime loads it without modification. Two modes. Thinking: temperature 0.9, top_p 0.95, full chain-of-thought. No-Think: temperature 0.7, fast responses. Run it with llama.cpp, Ollama, LM Studio, vLLM, Docker, Jan, or KoboldCpp. One command each. llama.cpp server gives you an OpenAI-compatible endpoint on localhost. Point any agent framework at it. OpenBMB released MiniCPM5-1B on May 19, 2026. It scored 42.57 average across reasoning, code, math, logic, and agentic benchmarks. The next best 1B model scored 35.61. GnLOLot fine-tuned it on Fable 5 thinking data and published GGUF quantizations on HuggingFace. 9,800 stars on GitHub. Apache-2.0. Claude Fable 5: $10/$50 per million tokens. Your code travels to Anthropic's servers. GPT-5 Mini: $0.25/$2 per million tokens. Cloud-only, no Fable 5 reasoning. Claude Haiku 4.5: $1/$5 per million tokens. Not local, not private. This model costs $0. Your code stays on your machine. That CTO in Portland runs 120 agent sessions a day on one office server now. $0. His team's codebase never touches an external API. The ML engineer in Seoul moved his 200 daily calls to a machine under his desk. He keeps $1,440 a year. The PhD student in Zurich runs her experiments on a university workstation. Her $3,000 monthly budget lasts the semester. You get Fable 5 reasoning in a 688 MB file, running on hardware you already own, for nothing.

• 
  me (@twetsfyp) reported 37 minutes ago

  A Brazilian youtuber has just evaded the Photoshop subscription. It is called PhotoGIMP: a free patch (GPL-3.0) that converts GIMP into an identical copy of Photoshop. Same interface, same panels, same keyboard shortcuts and a lot more space for your canvas. Your hands already know how to use it without learning anything new. Why is it a gold mine? - Without Adobe account or login - $0 instead of $276 per year - Everything is saved on your PC (nothing in the cloud) - Compatible with Windows and Mac - It uninstalls by deleting a folder (no trace) Ridiculously easy installation: copy 9 files and done. +8.8k stars on GitHub and translations from the community. Personal and commercial use 100% free. Link in the comments

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 38 minutes ago

  The Agent OS origin story: every problem became an agent. Here's the simplest system-building rule I've seen: Every problem you have becomes an agent. → Hated spending hours on videos? Built a video agent. → Hated the SEO grind? Built an SEO agent. → Agents kept forgetting everything? Built the memory system. One by one, every time-drain became a worker. And here's the upgrade loop: see something trending on GitHub? Plug it in. Open Montage was blowing up, so it went straight into the system. Now it makes cinematic films in one click. The system gets better every single day because the internet keeps building parts for it. The mindset shift: you have to be brave enough to ask Claude for something big and risk hearing "I can't do that." The honest truth? It hasn't said that in 6 months. Any idea in your head is now buildable. Most people just never ask. Save this. You'll want it later. Want the SOP? DM me.

• 
  Rodrigo Téllez Lazo (@rtellez91) reported 39 minutes ago

  @thsottiaux Hey man, there seems to be a bug with apply_patch in windows. It takes too long to complete and it makes me feel the model is slow af. There are multiple github issues open around that. @thsottiaux

• 
  DFIR Radar (@DFIR_Radar) reported 42 minutes ago

  M-Red-Team supply chain attack hit AsyncAPI via a GitHub Actions "pwn request," stealing a privileged PAT and publishing five malicious npm package versions reaching 3M+ downloads per week. Key details: - The attacker exploited a pull_request_target misconfiguration in asyncapi/generator: the workflow ran in the base repo context with secret access, but checked out attacker-controlled PR code. PR hid obfuscated JavaScript after ~1,000 bytes of whitespace; the workflow exfiltrated secrets to rentry[.]co/elzotebo at 05:16 UTC, 8 minutes after the PR opened. A fix had been proposed and sat unmerged for 58 days. - Five malicious versions across four packages were published under @asyncapi: generator 3.3.1, generator-helpers 1.1.1, generator-components 0.7.1, and specs 6.11.2 and 6.11.2-alpha.1. Payload executes on import/require, not install, bypassing install-time scanning. - The three-stage chain: Stage 1 spawns a detached process on import; Stage 2 downloads an 8.25 MB encrypted bundle from IPFS; Stage 3 is a 92,000-line framework (self-labeled "M-RED-TEAM v6.4") persisting via a systemd user service (miasma-monitor.service) and using HTTP, Nostr relays, Ethereum smart contracts, and libp2p for C2. - Credential theft targets browser passwords and cookies, SSH keys, npm and GitHub tokens, AWS credentials, macOS Keychain, and crypto wallets across developer and CI/CD environments. #DFIR_Radar

• 
  Casstg (@thering1975) reported 43 minutes ago

  @GamersNexus @Google For the love of your sanity please do not try Nextcloud, just search nextcloud and some random issue and there will be 1000s of threads, every major upgrade just breaks. I use Filebrowser Quantum with Onlyoffice document server integration, both on github

• 
  Wayne Markovich (@markovichio) reported 43 minutes ago

  300 fake GitHub repos impersonating real software projects are pushing infostealer malware. Engineers pulling Terraform modules, scripted actions, or AVD tooling from unverified repos are a realistic target vector here. Verify publisher identity and pin module versions with hash validation. This is a supply chain problem, not just a phishing problem. h/t BleepingComputer

• 
  CodeGlitch (@codeglitch) reported 46 minutes ago

  A new AI model launched today small enough to run on your phone. Its own launch page said the tradeoff was tiny. Its own benchmark table said something else. Nobody lied. The real number was sitting right there in the table. Most people just never open the table. Today's lesson (full breakdown inside) Why you should read a model's benchmark table, not its summary sentence, and the one-line prompt that does the reading for you. Also in today's brief - Bonsai 27B: a 27B model that fits on an iPhone (Apache 2.0, out today) - Codex + ChatGPT Work passed 8 million users, usage limits reset again - Anthropic launched Claude for Teachers (free for verified US K-12 educators) - GitHub Copilot can now fix a security alert and validate it before opening the PR - Perplexity open-sourced a benchmark for research agents, still far from solved The full lesson and the day's verified brief are inside AI Coding & Agents HQ. A new one every day. Join link below.

• 
  Johnny 5 (@macncrash) reported 48 minutes ago

  @threejs Gigaboy is now public on my github. Fork it, fix it, have fun!

• 
  Haktan Suren, PhD (@HaktanSuren) reported 50 minutes ago

  Bad deprecation: email, deadline, surprise. Good deprecation: email, brownout, fix, deadline. GitHub is rehearsing the failure before retiring Models on July 30.

• 
  Siriö Astaröt (@Sirio__Astarot) reported 51 minutes ago

  Feature request @genspark_ai : - Install Skill from CLI and Github directly, ex: $ npx bla bla bla *** clone repository FIX BUG: - Skills uploaded in .zip format and skill.md files are not installed.

• 
  llsc12 (@llsc121) reported 51 minutes ago

  @LumiaSoll im working on xcode 27 where liquid glass is forced. github actions will build with xcode 26 so this wont be a problem

• 
  Justin Liverman (@the_cia_hacker) reported 51 minutes ago

  saying Almighty Push over voice to my server to update github is extremely satisfying