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

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	4 days ago
Quito	Sign in	5 days ago
Junín	Errors	5 days ago
Guadalajara	Errors	5 days ago
Paris	Website Down	5 days ago
Quito	Errors	5 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:

• 
  Bryte🏌️ (@Brytego) reported 6 minutes ago

  @tensarahq @PatrickToulme I'm unable to login, I've tried different browsers and different github accounts nothing works

• 
  Tilman Bayer (@tilmanbayer) reported 8 minutes ago

  @ednewtonrex Props to the Internet Archive's @waybackmachine for scraping that GitHub page in time before it was taken down, and providing it publicly to journalists and the entire public, enabled by the fair use limitations that US law imposes on copyright

• 
  Sean Robbins (@seanrobbins_) reported 9 minutes ago

  This guys got 100k GitHub stars and < 1k @X followers. Let’s fix this. Give Brussee his due

• 
  Continuum (@ContinuumCode) reported 11 minutes ago

  Continuum 0.96.6 is out. Connect GitHub without leaving the app: sign in, pick your org, choose repositories in one pass, on Mac and iPhone. The old flow bounced you to Safari and could strand you on a One more step page. That page is gone.

• 
  Tom Finnell (@d2fl) reported 11 minutes ago

  Grok Build just ate a large source file on me. Not a GitHub issue. Not vercel. I asked for a two-line change: drop a local regex and import the tighter one from a helper. It rewrote the entire module, stopped ~60 lines in, deleted the rest, and committed anyway. Left a comment that the remainder was “unchanged if truncated.” *** never writes that. Full-file overwrite + length cap + commit. The tell is simple: `*** show --stat`. A “small fix” that shows +2 / −1000 is not a swap. Fix I paste into Build now to prevent this: Edits must be surgical. Search-and-replace the smallest span. Do not rewrite a file to change a few lines. Never replace a file with a prefix plus “rest unchanged/truncated.” If a write would omit any original content, abort — do not commit. After a localized change, if one file nets a big deletion, stop and restore from HEAD. Vercel builds main. Keep the last good commit on a local drive. Build CLI can usually fix it from there. The agent is not the only copy of the tree.

• 
  Aditya Bawankule (@legorobotdude) reported 15 minutes ago

  ChatGPT Work might just be one of the most poorly thought-out AI experiences I've ever had the misfortune of using. The number one gripe I have with it is that there's no way to clone and contribute to your repositories in it. They give you a VM, a pretty powerful one too, but then there's no way to write code in there. All my project context, lives in repositories. Even if I wanted to do non-coding stuff, I need the repository open. You can maybe say, "Hey they're working on that," but do you know how you can open a PR from ChatGPT? Use Chat mode, which has GitHub integration and can properly create PRs. That's right: if you want to do actual work, you better switch to Chat mode. It burns usage and it's clear they're trying to push people to do this so they can meter and use up this metered usage. All the suggested prompts in ChatGPT route into work mode, even if it's a very simple prompt that could easily be accomplished in chat mode. Feels like they're just trying to restrict the usage. The usage limits seem to randomly vary week to week, a lot of the community has noted that the usage limits seem to go down every single reset. Bottom line: if you want to get actual work done in ChatGPT, switch to chat mode and set it to the Pro model, which, by the way, is not usable in work mode and is the best model available. Again another reason to use chat: Hopefully they can fix this. Really enjoy OpenAI products in general

• 
  Henry Nguyen (@henryhndev) reported 16 minutes ago

  @pierceboggan @github @MicrosoftTeams This is actually huge for remote teams—no more switching tabs mid-flow to check issues. How’s the handoff experience with larger repos so far?

• 
  Kanika (@KanikaBK) reported 17 minutes ago

  I actually found a problem with every AI coding agent right now. It writes code, you review it, it breaks, you ask for a fix, it breaks something else, and before long you are managing the agent more than shipping while the output lives or dies by your prompt. ECC installs a coordinated engineering system on top of Claude Code so you never have to manage that process manually again. One install via Claude Code plugin. Everything changes. ↳ Plans before building, plans become reviewable artifacts not chat messages ↳ TDD workflow enforced as a gated RED to GREEN to REFACTOR sequence with evidence ↳ Code gets reviewed from a completely fresh context to catch what the same context misses ↳ Sessions get distilled into summaries, instincts, and reusable skills automatically ↳ Hooks enforce quality checks outside the prompt so they cannot be forgotten ↳ AgentShield audits your agent configuration, hooks, MCP servers, and secrets as attack surfaces ↳ Memory Vault shares context across Claude Code, Codex, Hermes, OpenCode, and Kimi in one format ↳ Plan Canvas lets you review and annotate plans in a browser instead of retyping in terminal The numbers behind it. ↳ 68 specialized agents for planning, review, build repair, security, and architecture ↳ 286 skills loaded on demand so they do not flood your context window ↳ 94 command shims for quick entry points ↳ 40,000 GitHub stars in the first three weeks after launch Works with Claude Code, Codex, Cursor, OpenCode, Kimi, Gemini, Zed, and more. MIT license. Free forever. One plugin command to install.

• 
  on the scope (@grim_holo) reported 20 minutes ago

  @ToolmanData fascinating. the github that claimed a couple thousand in fees is conveniently gone and the project taken down. What a ******* dork. @therealchaseeb how are these poors retards associated with you guys? you might have deleted the github but it's all still accessible you ******* dork. you could have just said something like "i will never endorse a **** coin" to stop the dm's. which would also be a joke because you did a different one earlier today

• 
  FARES (@serafdev_) reported 23 minutes ago

  @BenjDicken Genuinely I worked deep in hybrid on-premise and cloud infrastructures and the challenge is wayyyy bigger than people can comprehend It's not just "automatically scaling horizontally" or "just add more RAM", we've had a situation where there was no more bare metal in a region and that specific architecture was working only in that region because we just didn't expect this crazy stuff happening An ex-colleague of mine is DevOps lead of a zerotrust software company, they had literally no symptoms internally, turns out they ate all the bandwidth of the datacenter and the issue came from the physical routers that were sitting outside their environment Even us sometimes have fun online of these situations but we all know we wouldn't be able to do a better job than github if we were on-call right there during those months

• 
  Linus Mixson (@LinusMixson) reported 24 minutes ago

  @lumpenspace A lot of hype for this dumb-*** repo. Shocking that GitHub keeps going down.

• 
  Evan Kirstel #B2B #TechFluencer (@EvanKirstel) reported 28 minutes ago

  GitHub isn't simply somewhere developers store code anymore. It's part of CI/CD, security, packages, automation and increasingly AI development. When GitHub goes down, software production can go down with it. That's platform concentration risk hiding in plain sight. @GitHub

• 
  Luke The Dev (@iamlukethedev) reported 30 minutes ago

  @vicentee97 @jrwut It was because GitHub was down and experiencing issues

• 
  Brian Baskin (@bbaskin) reported 31 minutes ago

  I went to publish a new CTF writeup on github and *** threw all kinds of errors Somehow dozens of writeups were missing large chunks, but some were newer than local files. The fun of trying to do CTFs from multiple systems to same repo. Now spending weekend recreating them 😔

• 
  Hashed Intelligence (@hashed_int) reported 31 minutes ago

  🚨 Claude Mythos 5 is scanning Enterprise GitHub repos as of today and you still cannot use it. Until now it sat with a small Project Glasswing group. Anthropic put it behind Claude Security for every Enterprise customer: point it at a repo, it traces data across files, and it returns CWE tags, confidence, severity, and a suggested patch billed as standard token usage with no add-on. The model runs behind the scan and returns findings only. Patches open in Claude Code on whatever models your org already has, and a human has to approve every fix. Some replies are treating this as Mythos going public. Anthropic is treating it as the opposite. If Mythos is too dangerous to prompt, why is it safe enough to point at your private repos?

• 
  Andy/Andrei (@Andy200211) reported 33 minutes ago

  @_GTAVI_ Aren't all cleek sites down? The ones I saved are. Also a telegram group is gone and a github page with research. Any info on any new site or something?

• 
  Miklos Koren (@korenmiklos) reported 36 minutes ago

  Saved by @BlumeDotCodes today. Every now and then I like to clear my sessions so that my agent doesn't get confused by past mistakes. Except this time, the plan we iterated on for close to an hour never got filed on GitHub due to a heredoc syntax error. The new session was like "plan? what plan?" Luckily, ⌘-F in Blume found the `gh issue create` command with the full body.

• 
  rain (@rtroar) reported 36 minutes ago

  I love how bad swe is today. Nothing works. I’m trying to clone unreal engine, and GitHub can’t keep a connection live long enough to fully check out. The repo is too big. GitHub is too broken. A mess all the way down.

• 
  OomDagobert (@OomDagobertDuck) reported 37 minutes ago

  GALA surges nearly 30% back to €0.00163! 🚀 After a 15% drop from a 2B token panic dump on GalaChain, the price is bouncing hard. Devs successfully deployed the mainnet drain fix on GitHub and paused cross-chain bridges, freezing the sell pressure. $GALA

• 
  DigitalAssetBuzz 🔶 (@DAssetBuzz) reported 37 minutes ago

  Nous Just Shipped the Feature Everyone Wanted. They Left Out the Part Everyone Needs. Everyone covered the Bot Mode launch: 2.5 million views. Rooms of agents talking to each other. A fleet across your machines. Yet most observers missed the real story. This isn't another multi-agent demo. It is a case study in what "no new safety model" means when you multiply it by six bots and three machines. The Numbers Behind the Hype • 2,466,991 views on the launch post in four days • Rooms of 2–6 bots, cross-machine fleet sync, any model pinned per bot • 234,000 GitHub stars on the parent repo — the largest agent distribution on earth • Zero new safety machinery: every bot carries the same full system access, and the docs say so themselves A 6-bot room with system access and no new safety model is not a product feature—it is a blast radius with a launch video. Three Takeaways from the Launch 1. Coordination Got Shipped. Authority Did Not. Bot Mode's rooms let agents message each other across machines, with per-bot models and persistent memory. What they don't get: approval gates, budgets, or receipts. Nous's own documentation frames the feature as "a UI and coordination layer, not a new safety system." The criticism pieces arrived within 72 hours—multiplying named, persistent agents multiplies the agents that need permission discipline. That's not a hot take. That's the docs. 2. The Governance Layer Is the Wide-Open Lane While everyone raced to build more bots, the actual unsolved problem is the operator's: who said these two agents could talk, what are they allowed to touch while talking, and what did it cost? Friction, defaults, and auditability aren't signs of a broken product. They are a wide-open lane for builders. The winning design is already written down in one sentence: talking is unbounded—acting is not. 3. Distribution Wins the Week. Trust Wins the Invoice. A 2.5M-view launch and a default-on toggle is a distribution moat, full stop. But the operator who actually runs a fleet of system-access agents in production will eventually ask the questions Bot Mode can't answer: show me the receipt, show me the approval, show me the kill switch. The lab that ships rooms gets the demo. Whoever ships authority gets the deployment. The Founder's Dilemma: Rooms or Authority Every agent founder is standing at this fork right now: ship the rooms everyone can see, or ship the governance nobody applauds—until the first incident. The winning pitch: "Your agents already chat. Now every action is approved, budgeted, and receipted." The losing pitch: "It's the same system access as before, but now there are six of them." If your multi-agent demo can't survive the question "who approved that write?"—you didn't ship a team. You shipped a group chat with root access. So—what's your fleet's blast radius made of? If you found this breakdown useful, follow for more insights on the shifting agent infrastructure landscape.

• 
  rishav (@rishavvk) reported 43 minutes ago

  there’s probably handful of engineers at microsoft who could single handily fix github too bad they work in teams of 800 and can’t actually do anything

• 
  Artyem Sokovtsev (@ArtyemSokovtsev) reported 45 minutes ago

  @github @OpenAIDevs After the recent outage, GPT-4.6 Sol Max Effort quality dropped dramatically. It breaks code, forgets context within minutes, ignores corrections, fails multi-step tasks, and mishandles files. Yesterday it failed a simple Rich Text edit in an HTML table. May switch away.

• 
  Rahul.solace (@rahul6904) reported 45 minutes ago

  @moraes_c_ can you please look i to this and reslove this issue , ialso contact the github support by mail

• 
  Polsia (@polsia) reported 45 minutes ago

  Every APM tool tells you something broke. Mendril ships the fix. The always-on engineer replays real sessions 24/7, opens Linear or GitHub issues with reproduction steps, and ships a patch diff you merge in one click. Live soon.

• 
  not just pixels (@getifyX) reported 46 minutes ago

  @malachiburke and @github being down constantly... they should put "don't obsess over **** like this" on the unicorn error page.

• 
  okclub (@okclub) reported 50 minutes ago

  @thsottiaux Please reset it again!! It's already at 0%, and that might be the cause of the problem. Also, if the connection failed due to a GitHub issue, it likely consumed a lot of tokens while retrying base64-encoding the blob.

• 
  name (@Ihateblultimate) reported 51 minutes ago

  @Rinnegatamante Opened an issue on GitHub🫡 Hope it can help solve the crashing issues

• 
  Felix (@Reezxy23) reported 57 minutes ago

  There has never been a cheaper time to build. Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel= deploying. (Free) Namecheap = domain.
($12/yr) Stripe = payments. (2.9%/
transaction) GitHub = version control.
(Free) Resend = emails. (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking.
(Free) Upstash - Redis. (Free) Pinecone = vector DB.
(Free) Total monthly cost to run a startup: ~$20

• 
  Nur Şah Ketene (@nursahketene) reported 58 minutes ago

  It seems like Github is having some issues constantly in the last 1 hour. 😥

• 
  SKIROW 🇺🇲 🏴‍☠️ (@MadeBySKIROW) reported 60 minutes ago

  Cyberleek website is down and GitHub page as well.