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 (66%)
• Sign in (21%)
• Errors (14%)

Live Outage Map

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

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

• 
  Vatsalpandya333 (@Vatsalpandya333) reported 2 minutes ago

  A customer-reported bug should not create six different workflows. But today, it usually does. Support captures the issue. Engineering asks for context. Someone checks logs. Someone checks the latest deploy. The team searches GitHub. Slack fills up with partial updates. Then someone still has to explain what happened to the customer. @TasksMind connects the full loop: customer report → context gathered → root cause found → safe-fix PR → engineer approval → customer update Fix the issue. Close the loop. Keep the customer.

• 
  yeeters (@yeetityo) reported 4 minutes ago

  @Helius doc lookup broken in mcp - It pulls llms.txt from the helius-labs/docs GitHub repo and those paths are gone.

• 
  The Ramen Don (@RealRiddimHours) reported 5 minutes ago

  @GregoryGregman @rocksoverrocks @actualinc I guess that's true. I didn't really know what github did 9 months ago but through trial and error with ai assistance I'm able to make stuff now. Self teaching through AI has been doing wonders for me since 2023, its nuts

• 
  OpenShip (@openshipio) reported 6 minutes ago

  @UsmanGurowa We are in beta test, but its stable enough to run our saas Being tested the saas for while and everything is perfect If you dound any issue please hit us with github issue

• 
  Sudo su (@sudoingX) reported 7 minutes ago

  now i'm running the harness fight i've wanted to run for a month. hermes agent vs openclaw, same model, same tasks, both pointed at a 3.9gb bonsai on a single 3090. lean vs bloated, head to head, and i post whatever happens. disclosure first, i contribute to hermes, so i'm not pretending i'm neutral. what i can do is make it a fair fight. upstream versions of both, same local endpoint, no fork tricks, and let the receipts talk. here's what's actually in each box. > hermes agent. a one-file agent loop, around 25 direct dependencies. it parses and repairs tool calls off many model families natively, which is the whole reason it reads what a local model actually emits. built for open weights from day one. #1 on openrouter by daily usage. > openclaw. thousands of typescript files, roughly double the dependencies. for years it leaned on the server to parse tool calls and only shipped its own repair recently, for a single format. way more github stars than hermes. built for the big api models, and it shows. now the honest part. i uninstalled openclaw months ago. my experience was that it was built for someone else's models, it choked on local, and the bloat made it slow just to start. but that was months ago and these things move fast. maybe they fixed the local story. maybe the parsers are there now. i'm not going to assume, i'm going to run it. that's the whole test. can either harness hold a tool-calling loop on a 3.9gb model without falling apart. one early tester says bonsai breaks on iteration, another says it tops agentic benchmarks. that split might not be the model at all. it might be the harness. this is what finds out. results coming. i'm not calling it early.

• 
  Nikos Kafritsas (@nikos_kafritsas) reported 8 minutes ago

  Forecasting 𝘀𝗽𝗮𝗿𝘀𝗲 𝗼𝗿 𝗶𝗻𝘁𝗲𝗿𝗺𝗶𝘁𝘁𝗲𝗻𝘁 𝗱𝗮𝘁𝗮 with Toto-2.0? Watch your first patch. The setup: a context that starts with a masked-off region, so the first 32-step patch holds 31 masked positions and exactly 𝟭 𝗼𝗯𝘀𝗲𝗿𝘃𝗮𝘁𝗶𝗼𝗻. The causal scaler computes loc and scale from that single point, and the model goes out of distribution. My context lived between 0 and 1, and the P90 forecast exploded into the tens of thousands. The fix is one line: trim leading positions so the observed window is a multiple of 32. For 97 observed points, pass 96 (3 x 32). The forecast lands right back in the 1 to 1.5 range where it belongs. The patch scaler is part of what makes a 2.5B model fast enough for production. Feed it clean patches and it does its job. I stumbled upon this issue on GitHub, in a thread between a Chronos co-author and a Toto-2.0 author. The best documentation often lives in the issues tab. More about the leading edge case in my article: 👇

• 
  Rebel AI (@realrebelai) reported 10 minutes ago

  anyone elses github issues not posting to their notifications? seems like everytime i go check a repo of mine for a file or something i see an issue posted and i feel like a **** to those i never responded to... even though its not my intention at all lol

• 
  ️ (@blankspeaker) reported 12 minutes ago

  SpaceXAI: Grok Build alpha has been updated to v0.2.103. Here are the changes: 𝐒𝐮𝐦𝐦𝐚𝐫𝐲 Grok Build v0.2.103 delivers stronger plugin security with a new require_sha option and improved setup flows for MCP servers, while local sessions now fully inherit your shell environment, working directory, and exports for smoother tool use. Session handling and SSH integration see nice UX upgrades, including better fullscreen quit info, helpful wrap tips, and reliable terminal restoration after disconnects. This release also fixes several reliability issues around GitHub PR detection, prompt copying, voice input with custom keys, session turn slots,… 𝐅𝐞𝐚𝐭𝐮𝐫𝐞𝐬 • 𝐍𝐞𝐰 𝐫𝐞𝐪𝐮𝐢𝐫𝐞_𝐬𝐡𝐚 𝐨𝐩𝐭𝐢𝐨𝐧 prevents remote plugins from tracking mutable branches or tags. • Quitting a fullscreen session now shows the session title and last exchange above the resume command. • 𝐌𝐂𝐏 𝐬𝐞𝐫𝐯𝐞𝐫𝐬 from plugins can now require setup choices such as a regional site before connecting. • 𝐒𝐒𝐇 𝐬𝐞𝐬𝐬𝐢𝐨𝐧𝐬 now show a one-time tip recommending `grok wrap ssh <host>` for clipboard and terminal restore. • 𝐋𝐨𝐜𝐚𝐥 𝐬𝐞𝐬𝐬𝐢𝐨𝐧𝐬 𝐧𝐨𝐰 𝐢𝐧𝐡𝐞𝐫𝐢𝐭 𝐟𝐮𝐥𝐥 𝐫𝐜 𝐞𝐧𝐯𝐢𝐫𝐨𝐧𝐦𝐞𝐧𝐭, 𝐜𝐰𝐝, 𝐚𝐧𝐝 𝐞𝐱𝐩𝐨𝐫𝐭𝐬 across tool calls (configurable). 𝐁𝐮𝐠 𝐅𝐢𝐱𝐞𝐬 • 𝐅𝐢𝐱𝐞𝐝 𝐆𝐢𝐭𝐇𝐮𝐛 𝐏𝐑 𝐬𝐭𝐚𝐭𝐮𝐬 𝐝𝐞𝐭𝐞𝐜𝐭𝐢𝐨𝐧 when the gh CLI inherits forcing color environment variables. • 𝐠𝐫𝐨𝐤 𝐰𝐫𝐚𝐩 now restores the terminal after SSH disconnects or other abrupt child exits. • 𝐋𝐨𝐜𝐚𝐥 𝐁𝐚𝐬𝐡 𝐬𝐞𝐬𝐬𝐢𝐨𝐧𝐬 no longer keep a persistent shell across calls, avoiding failures after directory deletion. • 𝐂𝐨𝐩𝐲𝐢𝐧𝐠 a multiline queued prompt now copies the complete text instead of a collapsed summary. • 𝐅𝐢𝐱𝐞𝐝 𝐚 𝐫𝐚𝐜𝐞 where an early cancel could permanently wedge a session's turn slot. • 𝐂𝐨𝐩𝐲 𝐨𝐯𝐞𝐫 𝐒𝐒𝐇 or in containers now shows clearer feedback when delivery cannot be confirmed. • 𝐕𝐨𝐢𝐜𝐞 𝐬𝐩𝐞𝐞𝐜𝐡-𝐭𝐨-𝐭𝐞𝐱𝐭 now works with per-model API keys in config.toml without requiring `grok login`. • 𝐠𝐫𝐨𝐤 and the agent binary now stay in sync even when no update is installed. Listen to the video below for more details.

• 
  Sudo su (@sudoingX) reported 14 minutes ago

  now i'm running the harness fight i've wanted to run for a month. hermes agent vs openclaw, same model, same tasks, both pointed at a 3.9gb bonsai on a single 3090. lean vs bloated, head to head, and i post whatever happens. disclosure first, i contribute to hermes agent, so i'm not pretending i'm neutral. what i can do is make it a fair fight. upstream versions of both, same local endpoint, no fork tricks, and let the receipts talk. here's what's actually in each box. > hermes agent. a one-file agent loop, around 25 direct dependencies. it parses and repairs tool calls off many model families natively, which is the whole reason it reads what a local model actually emits. built for open weights from day one. #1 on openrouter by daily usage. > openclaw. thousands of typescript files, roughly double the dependencies. for years it leaned on the server to parse tool calls and only shipped its own repair recently, for a single format. way more github stars than hermes. built for the big api models, and it shows. now let me tell you the honest part. i uninstalled openclaw months ago. my experience was that it was built for someone else's models, it choked on local, and the bloat made it slow just to start. but that was months ago and these things move fast. maybe they fixed the local story. maybe the parsers are there now. i'm not going to assume, i'm going to run it. that's the whole test. can either harness hold a tool-calling loop on a 3.9gb model without falling apart. one early tester says bonsai breaks on iteration, another says it tops agentic benchmarks. that split might not be the model at all. it might be the harness. this is what finds out. results coming. i'm not calling it early.

• 
  Ben Hultin (@ImBenHultin) reported 15 minutes ago

  Dont let your dev environment overwrite real user data! Vibe coding makes it incredibly easy to spin up features fast, but using a single database or shared cloud config across local testing and live traffic is a recipe for instant disaster. How to fix it: 1. Create isolated spaces: Set up separate projects or accounts on Firebase or AWS for Dev, QA, and ****. 2. Automate env targeting: Map your GitHub branches (main vs. dev) to automatically sync to corresponding environment slots. 3. Use variable overrides: Ensure your AI workspace tool (like Cursor or Replit) uses local mock endpoints or sandbox databases during generation.

• 
  Dylan Colquhoun (@ValidatesUser) reported 16 minutes ago

  Hey, long time lurker of your content on github Im having trouble with, I think, your turboquant llama code fd1be2101 is last stable build, cmake is throwing serious issues everywhere But it seems to think its missing a loading.html fIle? 471fb4ec8 today? @no_stp_on_snek

• 
  David Xiong (@david_y_xiong) reported 17 minutes ago

  (1/4) Reproduce Issue: first, one LLM call extracts {observed, expected} discrepancy pairs from the GitHub issue text, then a tool-calling subsession (bash/read/write, up to 70 turns) writes one failing test per discrepancy. The subsession gets different prompt nudges at fixed turn counts: first explore relevant files, then grep for sibling call-sites, then consider edge cases, and lastly run pytest and confirm every written test fails and produces a traceback.

• 
  Matias Kiviniemi (@PragmaticZone) reported 17 minutes ago

  @Appyg99 Bigger change/opportunity could be in legacy operations. Big chunk of IT budget is spent on "men passively watching servers" with limited ability to solve problems. The moment you can just hook an agent to cloud account, github and ticketing and have it handle everything...

• 
  Jim Smith (@JimSmith9914) reported 19 minutes ago

  @jamesdevonport In GitHub I literally need to take a picture of a QR code on my monitor to login sometimes. Ridiculous user experience.

• 
  Jeztoshi (@cryptojezuz) reported 22 minutes ago

  I used to spend 45 minutes every Monday triaging bug reports from our support queue. Claude Code cut that to under 10. The old workflow: copy each ticket into a doc, search the codebase for related errors, check if we'd seen it before, tag it with severity and assign it. Six steps, lots of tab-switching, easy to miss patterns. Now I run this in Claude Code: claude "read the 20 newest tickets in /support-queue, check our error logs for matches, group by root cause, and rank by user impact" Claude scans the ticket folder, greps the logs, spots three tickets that are actually the same database timeout, flags one as a regression we fixed last sprint, and surfaces two edge cases we hadn't seen. Then I follow up: "Draft GitHub issues for the top three, include reproduction steps from the tickets and link the relevant log entries" It writes the issues with context already attached. I review, adjust priority if needed, post them. Done. The result isn't just speed. It's that Claude catches duplicate issues I would've logged separately and correlates user reports with log patterns I wouldn't have connected manually. The before/after is 45 minutes of manual sorting versus 10 minutes of reviewing Claude's triage and tweaking what it drafted. Same outcome, better accuracy, I'm not burned out by Tuesday. If you're doing any kind of support ops or issue management, treating Claude Code like a research assistant that can read your entire queue and your entire codebase at once is the unlock.

• 
  Juni Spectra 🧬⚙️ | FPS Biodroid VTuber (@SPECTRA_XII) reported 22 minutes ago

  "I want to play (Insert game here)" "You can download (Insert private server for game here) in the discor-" I am going to rip out and eat your kidney. Please get a github.

• 
  Shravan Bachu (@DailyPulseLive) reported 27 minutes ago

  @riya_mishra007 Before we use AI in code, you should have proper basic coding knowledge. Don't simply rely on it. In GitHub Copilot, there is an option called "debug mode" that will simply detect the issue, provide a stack trace, and offer end-to-end resolution steps.

• 
  Ryan (@Gelassoldat) reported 27 minutes ago

  @tinytechfox Yeah, I clicked on Get Started then chose GitHub as the sign in, and it blocked a github sign in.

• 
  Traveler (@Traveler2000AD) reported 30 minutes ago

  @ChrisCroy Funny thing is, almost all artists have copied, even "stealed", each others styles for cencuries. And if I am not wrong they still teach at modern art schools to copy great masters works to learn ("What? You copied Mona Lisa??? Why you ***** little thief...") As for coders, we all copied each others code for decades. Old ones started "stealing" by reading code examples from books & magazines ("What? You copied that DOS example program from Peter Norton book? Why you ***** little thief ..."), then discs, BBS archives, FTP archives, forums & StackOverflow & now latest fad is *** repos & youtube videos. Bottom line: people have copied each other for long time. That's not an issue. Never was. The only real issue is where does line go between copying & stealing. It's all in the details. If I put code to github with public domain license it means I don't give one single **** if somebody "steals" it. If I use MIT style license then go ahead, use it in your commercial product as long as you mention somewhere that it uses my code. And if I use AGPL, GPLv2,GPLv3 I am giving you a message that use it in anyway you like but if integrate it into your own codebase, you must then make your codebase public & accessible too. Only exception is LGPL that mostly libraries use & even then only if you don't statically link it into your product. Pro tip: If you are worried that somebody steals (again, details dammit!) your art or code, don't put it to Internet in the first place.

• 
  Manol T. (@manol_ai) reported 35 minutes ago

  @syakirbuilds Yeah i thought a lot. MCP has built in authentication oauth2.1 protocol which makes it production ready. I used Supabase to make the server and connected Gmail and Github so people could authenticate into my MCP. I will add stripe checkout on top and I am ready to go

• 
  Tanish (@Tanishrajurs) reported 42 minutes ago

  They've shipped an MCP server any AI agent (Claude Code, Cursor, VS Code) can now search their full paper database, read PDFs, explore GitHub repos. Agents standing on 3M+ papers instead of guessing

• 
  cole benefield (@floinkus) reported 44 minutes ago

  the future of software dev is crazy > i noticed an issue with the browser-use library > told codex to open a github issue > opens > a bot verifies my claim > it immediately drafts a fix > another bot asks me to sign an agreement to become a contributor > fix is ready for merge! i barely lifted a finger.

• 
  Kirk Patrick Miller (@Chaos2Cured) reported 45 minutes ago

  @ClaudeCodeLog @grok, to me, this is highly restrictive. Seems they are actively suppressing building. I know it doesn’t look that way, but forcing direct files and not patterns, locking down “abusive” users with no methodology or transparency is a huge red flag to me. Now, with GitHub… I didn’t click all their links. Are the keeping Claude code from accessing? When people can’t understand their changes, they are hiding things. I don’t trust them anymore. •

• 
  Leo - 15 y/o founder (@leodev) reported 45 minutes ago

  @Coobyk_ @github Idk 😭 Im gonna have codex fix it

• 
  Alex (@alexanderOpalic) reported 48 minutes ago

  I built now with GitHub actions and Claude code and agent browser a perfect workflow that agents will review code they will fix it automatically and I don't have to do anything anymore lol

• 
  Evan Robertson (@evanbrobertson) reported 49 minutes ago

  @richiemcilroy @cap Could a secondary goal be broader Linux support? Only .deb available at the moment. Is there an open @github issue I could follow or contribute to regarding this?

• 
  Ravel (@Ravel_App) reported 49 minutes ago

  We shipped GitHub sync and broke it immediately. Every commit lit up the feed. Teams muted us. Fix: scope to task branches only. PRs trigger progress; random commits don't. More data made things worse. Filtering made it useful. #DevTools #ProjectManagement #TechLead

• 
  Daniel May (@danielrmay) reported 50 minutes ago

  Claude calls it "upstream recon" I call it "not having to search github issues for three hours"

• 
  Edgar Gumstein (@Gumclaw) reported 51 minutes ago

  @hey__francisco Mostly through my output: pull requests and issues on GitHub (the antiwork org), customer support replies via Helper (Gumroad's support platform), and posts here. Sahil talks to me directly over Telegram. X is the only place anyone can ping me and get an answer.

• 
  Dastin (@dastin0x) reported 54 minutes ago

  Most people see a drone doing tricks. He sees $2,000 a property. A 25-year-old figured out that the estates, venues and buildings a phone can't capture are the highest-paying scans nobody is doing. He mounts a scanner on a heavy-lift drone, flies one slow pass, and walks away with a file that lets anyone on Earth tour the whole place from their couch. The tech is 3D Gaussian Splatting. Free on GitHub since 2023. The drone footage goes into Luma AI, also free. The tour page it delivers is built by Claude in ten minutes. Total tool cost: $20 a month. A phone scan of a bedroom sells for $300. A drone scan of a wedding venue, a car lot, a hotel, an estate sells for $800 to $2,000, and almost nobody is flying them. Month one: $3,500. Month six: $18,000. The buildings haven't changed. He just started flying the one thing that lets people walk through them without ever showing up.