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:

• 
  Aaron (@aaron_devv) reported 37 seconds ago

  day 134. two things shipped today. the ambassador program. if you bring people to coommit, you get rewarded. simple as that. and a github integration. because the decisions made in a call shouldn't stop at the call. your meeting says "we ship the fix this week." github knows about it before the call even ends. that's the whole obsession. meetings that turn into execution. back to it.

• 
  Josh Anthony | Dice Gun Commando (@Jantho1990) reported 42 seconds ago

  Hey #godotengine folks, trying to diagnose a crash error related to "_canvas_texture_invalidation_callback". It happens when the game quits, and only on a release build (not an Editor one). Anyone know more about it? Found one open Github issue talking about it, nothing else.

• 
  Param (@ParamSiddh) reported 3 minutes ago

  GITHUB JUST KILLED THE WORST PART OF VIBE CODING they shipped a free tool called Spec Kit and it already crossed 120,000 stars the fix is stupidly simple instead of tossing vague prompts at an agent and praying it doesn't wreck your project Spec Kit makes the AI write a full structured spec before it touches a single line of code it works through the problem first figures out what you want to build asks about the gaps lays out the project then it starts coding you get fewer insane bugs, cleaner output and results you can predict the flow looks like this: /constitution for your rules and standards /specify for what you want to build /clarify for the open questions before you start /plan for architecture and stack /tasks for the ordered work /implement to run it it plugs into Claude Code, Cursor, Copilot, Codex, Gemini CLI and 25+ other agents 120,000 stars, 10,000 forks, open source, shipped by GitHub itself learning to drive agents like this is most of what separates people getting hired as AI engineers from everyone still fighting their prompts

• 
  ẞ𝐄𝐇𝐍𝐀𝐌 (@BehnamEbrahimi) reported 3 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?

• 
  Jorge Alvarez (@jorgealvarez) reported 4 minutes ago

  You can notice that most people complaining about VibeCoders are junior developers. Their argument being: You are making mistakes. Like if when we had to write all the code ourselves there were no errors. Spoiler alert: Leaking private keys to Github is not a new thing.

• 
  AL Amir (@_Amir4pf) reported 6 minutes 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 👨‍💻

• 
  Richard Grant Kleinhans (@polymathsofa) reported 8 minutes ago

  @thsottiaux Give me ~2 hours and my answer will probably be problem solving OS Kernels for niche bespoke hardware I'll DM what I'm up to since it's not ready for a GitHub just yet if curious.

• 
  Wayne Markovich (@markovichio) reported 9 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

• 
  Atenov int. (@Atenov_D) reported 10 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.

• 
  Avinash Kumar (@avinashkumaranu) reported 10 minutes ago

  Dear @claudeai , "Suggested task" feature is good but it would be more useful if action was "create an issue in Jira/GitHub etc " with actual impact/outcome. Since I don't read code anymore I've no idea what the suggestion is.

• 
  Zhiwei (@lian75864) reported 12 minutes ago

  Finally switched from Claude Code to Codex after dealing with too much friction. Opus 4.8 overthinks everything, even simple questions. It just slows me down. Anthropic’s attitude toward open source has felt pretty hostile for a while. Meanwhile GPT-5.6 Sol gives me that Fable-level intelligence at roughly half the price and with way more resets. The Fable subscription stuff was getting ridiculous too. They’d extend it last minute right before it expired and completely mess up my plans. Desktop app experience is noticeably better, and GitHub integration actually works (Claude Code’s sloppy GitHub plugin never did for me). Biggest one for my workflow though: OpenAI lets you log your ChatGPT subscription into other agents like OpenCode. Claude will straight up ban your account for doing the same thing. Codex just removes all these unnecessary restrictions. Feels way more aligned with how I actually work.

• 
  jordi (@jordienr) reported 24 minutes ago

  anyone figured out how to connect one claude session to one linear issue to one github PR so that it all feels integrated and I don't need 3 thousand tabs open

• 
  Casstg (@thering1975) reported 28 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

• 
  LiteEagle262 (@LiteEagle262) reported 28 minutes ago

  @Aryan_Raj_7167 @github Same exact issue happened to me, I got soft banned without them even notifying me via email, now I can’t use oauth or sync any of my projects to production pipelines They havnt replied to me at all yet and it’s been 3 days

• 
  Cathryn (@cathrynlavery) reported 29 minutes ago

  every time i needed a diagram in Claude Code, it gave me the same generic garbage. so i built a Claude Code skill to fix it. Diagram Design (now at 2.8k stars on Github) • 27 diagram types (architecture, flowchart, sequence, ER, swimlane, timeline, venn, org chart, and more) • one Claude Code skill, matches your brand in 60s • three variants per type: minimal light, minimal dark, full editorial • pure HTML output. skip Figma entirely, no build step or JS needed open source 👇🏻 npx skills add cathrynlavery/diagram-design /plugin marketplace add cathrynlavery/diagram-design

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 31 minutes ago

  @webdevcody spinning up subagents to hunt security issues and file labeled github issues is a slick workflow

• 
  The Whizz AI (@TheWhizzAI) reported 35 minutes ago

  This guy on GitHub built a tool that hacks your app before real hackers do and proves it. It's called Strix. AI agents that act like real pentesters, not scanners. Finds SQL injection, SSRF, IDOR, and more. Every bug comes with a working exploit. Auto-generates a fix as a ready-to-merge pull request. Plugs straight into your CI pipeline blocks bad code before it ships. 34K+ stars. Added 2,800 today alone. ( free 100% open source )

• 
  Johnny 5 (@macncrash) reported 35 minutes ago

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

• 
  oruuke 🎀 折る受け (@oruuke) reported 38 minutes ago

  wtf is github down again????? ive said it before but minecraft is so doomed under microslop 💀

• 
  wukko (@uwukko) reported 43 minutes ago

  @batuhan @ellie_huxtable try oss github issues next

• 
  Jossi Billy (@BillyJossi) reported 44 minutes 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

• 
  🦗 (@NoCrickets4Devs) reported 46 minutes ago

  Type one sentence. It searches 6 places devs actually talk. live right now. • Reddit • X • Hacker News • GitHub issues • Stack Overflow • 21 dev forums

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 46 minutes ago

  @thdxr an issues channel where the agent reproduces and fixes every good github issue is a slick loop, nice

• 
  Hermann (@dhlotter) reported 48 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

• 
  anupamme (@anupamme) reported 50 minutes ago

  Day 2: My GitHub account (@orbisai0security) has been suspended, preventing me from continuing my open source security remediation work. GitHub Ticket: #4559351 I suspect my automated security-fix workflow triggered GitHub’s anti-abuse systems. 🧵

• 
  †saint‡ (@Shallom_Okpapi) reported 53 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.

• 
  Jonny Q (@jonny_quan) reported 53 minutes ago

  Agent security is getting weird. A GitHub issue says Codex’s newer multi-agent path encrypts sub-agent messages, which may help with provider-side privacy, but creates a very dumb local problem: the person running the agent can’t easily see what one agent asked another agent to do. That feels backwards. The more power we give agents, the more boring audit trails matter. If an agent can touch files, run tools, and delegate work, “trust us” is not a debugging model.

• 
  Tanvi (@tanviiiw) reported 57 minutes ago

  More tools ≠ smarter agent. GitHub cut Copilot's built-in toolset from 40 tools to 13, and found the full toolset was actually costing them 2-5% on SWE-Lancer. Their words: "giving an agent too many tools doesn't always make it smarter. Sometimes it just makes it slower." Speakeasy pushed it further on purpose: 107 tools in one server, and the model started hallucinating endpoints that didn't exist. Trim it to 10-20 well-chosen tools and it got most calls right. It comes down to two things: every tool definition eats context on every single request, and models fuzzy-match on names, so get_status / fetch_status / query_status all blur together and it picks wrong. But we keep connecting everything anyway, because it feels like giving the agent superpowers (I fell for this too). It doesn't. Access isn't capability. You connect more tools to save time, then spend that time babysitting the tool calls. (Of course, none of this replaces a well-scoped prompt. It's upstream of it. You can write a perfect prompt and still lose to a bloated toolset.) So TLDR; curate the toolset like you'd curate a team.

• 
  Brian (@Brian2shv) reported 57 minutes ago

  @IntCyberDigest several years back I report to coinbase , github Linked Metadata Fix’s from open source . Email both on same day stating , While Was In mu account s. All language Was in Korean Language Metrio math From login to web3 aws Github I was blocked by both Coinbase github Spam aggregation Month band Never really Had coinbase connection github spam Few times once my data An account had said I deleted my profile deleted repository Month band or three month band

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