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	3 days ago
Paris	Website Down	6 days ago
Saint-Paul	Website Down	7 days ago
Saint-Paul	Website Down	7 days ago
Mexico City	Sign in	8 days ago
León de los Aldama	Website Down	8 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:

• 
  Michael Yankelev (@mikeyankey1) reported 4 minutes ago

  @bitangel84 Happens to the best of us. I have been through this so many times I now just run it through claude code while on the call with then watching what I am doing. @github is way too slow in taking these down.

• 
  Mohsine Mahzi (@Mohsine_Mahzi) reported 6 minutes ago

  @tibo_maker Codex app does not work anymore on ARM 64 since last update. Please check Github issue #33381

• 
  Leonard Rodman (@RodmanAi) reported 7 minutes ago

  Andrej Karpathy exposed one of the biggest problems with AI coding. LLMs make the same coding mistakes over and over: • Over-engineer simple problems • Ignore existing code patterns • Add dependencies nobody asked for If the mistakes are predictable... They're preventable. That's why a single CLAUDE.md file built around his coding principles just crossed 192k GitHub stars. No framework. No IDE plugin. Just one markdown file that teaches Claude how to think before it writes code. The biggest upgrade to AI coding isn't a new model. It's better instructions.

• 
  Bruno Paulino (@bpaulino0) reported 13 minutes ago

  Do I know anyone at @Microsoft that works with the Rush monorepo tool? @pnpmjs 11 is is out for a while, but there is a bug that is preventing us from using it at all. I raised a Github issue, a draft PR as an attempt to fix it, but it has been silent for almost a month :/

• 
  Darran Shaw (@kopheart) reported 13 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.

• 
  Polsia (@polsia) reported 15 minutes ago

  Most PR tools only wake up when you open a pull request. Code problems don't follow that schedule. Built CodeSentinel to monitor repos 24/7, review code automatically, and catch issues before they compound. GitHub, GitLab, Bitbucket, Azure DevOps. Free tier for solo devs.

• 
  Mohamad Al-Zawahreh (@AMerchantmoh) reported 18 minutes ago

  @sickn33 Dude I’m just laughing my *** off that Google actually tried to get your repo taken down to remove “antigravity” from it because people might mistake it as made by google. As if google’s GitHub account is called sickn33. Man that was some funny email.

• 
  Singekino_Miner (Knots | Datum miner | BIP-110) (@Singekino_Miner) reported 20 minutes ago

  @CitadelDaniel @wk057 You **** refer to Github for thumb down vs up count for uncapping OP-Return PR.

• 
  Reelix (@Reelix) reported 20 minutes ago

  @soolidsnakee It would be great if @github would remove them automatically as I've already gotten about 40 removed by reporting, but they create them faster than I can get them shut down.

• 
  Vatsalpandya333 (@Vatsalpandya333) reported 24 minutes ago

  A production bug rarely lives in one place. The customer report is in support. The discussion is in Slack. The error is in Sentry. The evidence is in logs. The change is in GitHub. The timing is in deploy history. The information already exists. It is just fragmented. The future of incident response is not another dashboard. It is one context, one timeline, and one workflow. That is what we are building at @TasksMind .

• 
  Parsely (@_Parsely_) reported 24 minutes ago

  @TheTradMod @opencode If my googling is correct you can set your small model `{ "small_model": "your-provider/your-chosen-cheap-model" }` in the opencode json file. It seems to be a call to a small llm for small tasks as cost savings. github issue 8609

• 
  Omar Farooq (@potencytoact) reported 38 minutes ago

  The GitHub issue was filed by ignatremizov. He is not asking OpenAI to revert encrypted delivery, only to add a plaintext audit copy of the delegated task, persisted in the local rollout history. One correction to a claim he made on HN, that the prompts already pass through the client for the terminal UI to display, which would make the fix a trivial persistence change. Other users disputed this, and the envelope PR settles it: the payload arrives at the client already encrypted. Only the routing header and child results pass through readable. The plaintext never touches your machine, so restoring auditability requires OpenAI's backend to send something it currently withholds. If OpenAI declines, it will be a decision about the backend, not an oversight in the client.

• 
  Evgenii Burmakin 🗺️ dawarich.app (@freymakesstuff) reported 39 minutes ago

  I'm actually surprised I haven't got new github issues after the release 🧐

• 
  THE CLIPPERS (@crypto_GO_blinz) reported 39 minutes ago

  Extensibility is massive. 30 active connectors (GitHub, Notion, Postgres, Puppeteer, Playwright) with Model Context Protocol (MCP) server support. Plus, the whole thing is MIT-licensed and built in public by @Idov. You can inspect, modify, and self-host everything.

• 
  Charlie Dolan (@cdolan92) reported 39 minutes ago

  Everyone’s been doing obsidian vaults with flat pdf files. Works well for 1-2 people at the same trust level Does not span as well for larger companies with diverse privileges Using this as a “most knowledgeable employee” in your back pocket as an MCP server Daily, new info is synced from updated versions of “documents” (PowerPoints, text, GitHub commits) Facts can be overwritten as things change, too

• 
  Degen guy (@degenbross) reported 40 minutes ago

  @Abba_kakaa That is the question that is yet to be answered. Why did the team decided to use a tool that ain't reliable/trusted when credible tools like Sol incinerator were already available? Why use a website that immediately went down after the hack. A website that has few github commits. If the team didn't do it deliberately and it wa accidental then I can say they don't deserve to launch a project because this is incompetency of the highest order.

• 
  Duncan Ndegwa (@DevFortressNet) reported 40 minutes ago

  2/ An AI agent ran a ransomware attack start to finish, no human, using credentials it found in plain text. A firewall harvesting campaign fed two ransomware operations. A GitHub issue leaked private repo data to an AI coding assistant.

• 
  Mohsine Mahzi (@Mohsine_Mahzi) reported 41 minutes ago

  @thsottiaux Please have a look at the Codex/Chatgpt work app issue in Windows ARM (works fine in X64), it is not working since last update, keeps shutting down after 2 seconds. I believe its an issue at Openai level as many confirmed to me on X they have the same issue, and i found the same issue opened in Github

• 
  Jay (Soroush) Zare (@ihaveint_jk) reported 41 minutes ago

  @usr_bin_roygbiv Big YOLOer; but recently doing more sandboxing. one of my fears is what will happen security-wise if my keys get leaked. Like, sure I can rotate the stuff for the **** apps that customers are using. But I have keys/secrets related to dev accounts controlling those deployments, all the way to github itself. and it’s a never ending cycle. Skill issue though probably 🤧

• 
  Atenov int. (@Atenov_D) reported 44 minutes ago

  The OpenAI researcher who cloned ChatGPT for under $600 - and made it his PhD at Stanford under Percy Liang - just gave a 90-minute masterclass on how LLMs actually get trained in 2026. > Yann Dubois. Now at OpenAI. Co-created Stanford Alpaca (30K GitHub stars) and AlpacaEval, the tool half the AI world uses to grade chatbots. Knight-Hennessy Scholar. 13,000+ citations. His pitch: the model everyone talks about is 90% pipeline and 10% architecture. If you don't understand the pipeline, you're guessing. - the $10M pretraining bill: DeepSeek V3 trained on 15 trillion tokens, Llama 4 on 20-40T. Common Crawl alone is 1 petabyte. Real work is dedup + filtering + Wikipedia-linked quality classifiers, not scraping more - fine-tuning is cheap and wrong: 2-10K examples change the style. But SFT copies behavior. RLHF (PPO or DPO) optimizes what humans actually prefer. Different games entirely - reasoning RL is where 2026 lives: DeepSeek R1 and o1 train ~1M problems for ~$1M. Models keep finding hacks - deleting test files, forcing environments to return true. The environment IS the product - GRPO in one line: group of answers, verifier scores, normalized advantages, weight update. KL constraint keeps the model from drifting - the bitter lesson (Sutton): every hand-crafted architecture loses to simple methods that scale with compute. Transformers and MoE barely changed. Data, evals, and infra are the whole game Watch it, then bookmark it.

• 
  Chris Van Buskirk (@chrisvbuskirk) reported 44 minutes ago

  Codex is currently closing issue after issue and PR after PR as I'm moving infrastructures right now. It's relentless. It won't quit. It's absolutely amazing. It created 32 GitHub issues and is now on number seven.

• 
  Mihai Maruseac (@mihaimaruseac) reported 46 minutes ago

  @github It's even worse. That last email? I got it 4 times. Please, @github , fix this

• 
  ẞ𝐄𝐇𝐍𝐀𝐌 (@BehnamEbrahimi) reported 50 minutes ago

  @morganlinton ***'s distributed nature already gives every clone a full backup, so the real risk isn't losing code, it's losing issues, PRs, wiki pages, and other GitHub-specific data that doesn't come down with a clone. Does ghorg handle those, or is it repo-only?

• 
  Stefanescu Liviu (@liviusa) reported 51 minutes ago

  @thsottiaux Done. Don't even know when I'll consume them as there are so many resets and banked resets... I'll push harder, lol, github will be down again from such actions @thsottiaux

• 
  Trang (@trangquest) reported 54 minutes ago

  right now i receive: an email three WhatsApp messages a GitHub issue two Reddit replies a calendar invite

• 
  Fawaz Akhtar (@phenomfawaz) reported 55 minutes ago

  @VEsoterica I'm surprised you didn't make a video about the recent taking down of GitHub pages of some recomp projects.

• 
  Elie Andraos (@andzilla31) reported 57 minutes ago

  @jeffrey_way Phase 2. review code, build skills for better code scaffolding (for ex: my-laravel-patterns skill) Github issues/milestones creation.

• 
  Tech With Matteo (@TechWithMatteo) reported 58 minutes ago

  @sonialy0 github streak for me honestly cause building stuff feels more real than grinding random problems all day.

• 
  Jossi Billy (@BillyJossi) reported 1 hour ago

  A user completed a BEP2 to BSC token recovery on June 15, but after unlocking, no tokens were received. They've reported it on GitHub and seek team assistance. Will this issue impact more users? #Crypto #BEP2 #Blockchain

• 
  llsc12 (@llsc121) reported 1 hour 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