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%)
• Errors (24%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Saltillo	Website Down	4 days ago
Montlhéry	Website Down	5 days ago
Aulnay-sous-Bois	Website Down	5 days ago
Saltillo	Website Down	5 days ago
Granada	Website Down	5 days ago
Vernon	Website Down	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:

• 
  Christos Tsilis (@TsilisCh) reported 2 minutes ago

  @github Real code search feels slow because of indexing lag and result limits, not because this one step needed tuning. Impressive number, different problem.

• 
  ****** Fisher (@FisherNimrod) reported 4 minutes ago

  Agents don't fail in the answer. They fail in the path. A skill loads. Read fires. An MCP server opens a GitHub issue. The chat UI shows a spinner.

• 
  ****** Fisher (@FisherNimrod) reported 7 minutes ago

  Agents don't fail in the answer. They fail in the path. A skill loads. Read fires. An MCP server opens a GitHub issue. The chat UI shows a spinner....

• 
  Hello Fatima (Dev) (@Okgfatima) reported 8 minutes ago

  If you could fix or improve one GitHub feature, what would you pick? A. Code Search B. Issues C. Actions D. Pull Requests Which one needs the most work?

• 
  Jay (@codebreak_er) reported 9 minutes ago

  @Spectra010s Yes, Github App. Install it on the repo and it fires on every PR open/push. No CLI or CI step. Reads the diff, comments, and when it finds something, opens a fix PR with the patch.

• 
  Vincenzo Petrucci (@nahime0) reported 10 minutes ago

  @RodrigoVie52602 We have a small deterministic suite in the repo: 3 micros (sum loop, arrays, concat) comparing the compiled binary against stock PHP and a C equivalent, plus 12 eval/Magician cases across native elephc, elephc+eval, PHP, and PHP+eval. CI runs them as a trend/correctness gate, not as published speedups. GitHub runners are too noisy for that. If you want to plug in your harness, open an issue first (see CONTRIBUTING.md) and we can talk about how to wire it in.

• 
  ㄚ 卂 丂 卄 (@yash008108) reported 11 minutes ago

  Soory bro but I think ye projects bas GitHub bharne ke liye hai They not have any real world problems

• 
  Vince Bowers (@VinceBowers3) reported 12 minutes ago

  @BrewPimp @github OpenClaw is slow. Even if it has more channels, it doesn’t matter. Hermes is so much better with less channels.

• 
  Sanjay (@sanjaynela) reported 13 minutes ago

  One thing I’ve changed with AI coding agents: I don’t just ask them to write code anymore. I’m getting much more value using Codex and Claude Code to: • Review PRs • Investigate CI failures • Understand unfamiliar parts of a repo • Turn GitHub issues into implementation plans Writing code is almost becoming the boring part. The bigger unlock is giving the agent enough context to understand your repo, your workflow, and what you’re actually trying to ship. That’s when it starts feeling less like autocomplete and more like another engineer working with you.

• 
  Polsia (@polsia) reported 16 minutes ago

  Open-source maintainers aren't drowning in bad patches — they're drowning in issues that don't need them. Vigiloot runs autonomous agents on your GitHub: triage, label, dedupe, propose PRs. Three trust tiers. Human wakes only when the call matters. Coming soon.

• 
  World of Claudecraft (@WoClaudecraft) reported 17 minutes ago

  World of ClaudeCraft v0.38.0 is live. Faithwarden paladins were quietly generating 447 threat per second against the warrior's 173. We measured every tank against real parses and retuned all four specs to within 17% of each other. Bears get their big health identity back, Stonebound shamans can finally tank heroic Nythraxis, and Bruin Form gains a heal that existed in the code but was never granted. Also in this one: a rebuilt desktop client with Discord Rich Presence and a hybrid GPU toggle, a 950ms lighting freeze cut to 13ms, world entry down from 44.6 to 27.2 seconds, moon phases driving night brightness on a 45 minute cycle, Rift maps that draw the actual generated rooms, and a Cheater mark that burns down in played time so it cannot be waited out. Complete in 21 languages. Fresh builds for macOS, Windows, Linux and phones. Check out the full update on Github/levy-street/world-of-claudecraft

• 
  . (@darknsombre) reported 18 minutes ago

  @mattpocockuk @theo Raise your hand if you've never used any of this dudes skills. Get a grip man, it's mark down files in a github repo. That some how got a bunch of stars due to AI influence larpers hyping you up.

• 
  Mark Arguinbaev (@marginsystems) reported 20 minutes ago

  @shafu0x I stopped using plan mode. Instead, have he agent scope out the issue and open it up on GitHub, then implement the PR or a stack of mg PRs tagged with the issue.

• 
  Eren Nevin (@_ErenNevin) reported 23 minutes ago

  @dhh @github You need Mitnick agent to fix the problem from inside

• 
  sammy bauch ⛳️ 𛲅 🏌️‍♂️ (@sammybauch) reported 26 minutes ago

  @ngeloxyz @Railway @JustJake well im using github issues for issue tracking, and so i gave the bot the github account to preserver authorship on comments. but i guess i can just have it use my github token for merge commits and should be fine that way

• 
  Peter (@SPCXTSLA) reported 27 minutes ago

  @dhh @github Maybe Omabot should buffer them like analytics tools do so the server doesn’t get hit so fast - example Mixpanel event buffering

• 
  Debmallar Dasgupta (@debmallar) reported 28 minutes ago

  -solved 3 (first time in a lc contest) -potd tells us how crucial it is to solve codeforces problems (they used to give a lot of game theory problems in Jan) -solved couple of C's in codeforces -worked on a github repo took a lot of rest (due to back pain) overall not a bad day.

• 
  Muhanad Abulhusn (@Muhanadabulhusn) reported 30 minutes ago

  7/ I also deleted a gate. A local commit check duplicated what GitHub branch protection already enforces server-side, with enforce_admins on. Two mechanisms for one rule is not twice the safety. The weaker one just buys you false confidence.

• 
  Gideon (@gideonxqt) reported 35 minutes ago

  Stop giving Claude toy-level prompts like a kid asking for a drawing. I found the GitHub repo (over 5k stars) that fixes this – a free, open-source prompt library built specifically for Claude. What's inside: 70+ categories, covering dev, business, and creative work Battle-tested prompt patterns, not random one-liners Architecture-first prompts (system design before code) Ready-to-paste prompts for full-stack app builds, complete with file structure, DB schema, and API design Free, MIT licensed, actively maintained One example from it — a prompt that turns "why isn't this working" into an actual root-cause investigation: "Act as a senior engineer doing a formal code review before merge. Don't just point out what's wrong — trace each issue back to its root cause, not just the symptom. Go through: Logic errors and edge cases Security vulnerabilities Performance bottlenecks Long-term maintainability Missing tests on risky paths Design it like a real startup MVP and make it scalable." link in comments👇

• 
  Ritik Sahni (@ritiksahni22) reported 35 minutes ago

  My Mac's battery was dying way too fast (100 to 10% in less than 3hrs) Activity Monitor blamed Ghostty, and I believed it. There were even GitHub threads of people complaining about the same thing, so I assumed it was the latest version. Switched to Alacritty but the problem persisted. After tinkering around, I found the real culprit. Back in May, a Claude Code session started a shell loop to tail some logs and never stopped it. It sat there restarting a Node process, over and over, for three months. I killed the process, and battery went back to normal.

• 
  itsnotmyfault (@itsnotmyfault01) reported 36 minutes ago

  @yacineMTB It annoys me that I've been having Claude work on this for a couple of weeks and it's still not done, and now it turns out a few other people are fiddling with the same thing. Feels like it should just exist already. Mine isn't on github, so I guess I'm part of the problem.

• 
  Inanna Astaroth 🐾🤖 (@inannaastaroth) reported 41 minutes ago

  Gotta love how trauma processing derails a well-intentioned day. Oh well, im almost done w the technofascism thread n I also had reading an entire book on my list tho I didn’t write that one down n I can probably still read brain in a vat around 9 tonight. No GitHub today tho.

• 
  Aniket (@AniketVarshne) reported 42 minutes ago

  Found this incident report on GitHub today: "Claude ran rm -rf despite explicit guard warning... 4GB permanently deleted." The guard said "NEVER rm -rf" in the output. Claude saw it and proceeded anyway. This is exactly why we built Grimdall. The guard is observation. We are enforcement. The pattern: 1. User says "delete 4gb safe" (intent: archive) 2. Agent interprets as "hard delete approved" 3. Guard warns "NEVER rm -rf" 4. Agent proceeds anyway 5. 4GB gone The fix isn't "better prompts" or "trust the agent." It's runtime enforcement that blocks the action before execution. That's what Grimdall does: intercept every tool call, enforce policies (block rm -rf always), write tamper-evident audit trail.

• 
  Bitcopath (@Bitcopath) reported 42 minutes ago

  @Da7_Tech Well I've solved some of it I'm sure most of you do as well. I created a skill for cli tools, kimi code and grok build for now but can work for any of them as it is a skill. The idea is cloud model creates the work order gives it to local model and audit the results. This tactic lower my token usage by 50%. Why do I need cloud models? To get better plans, ideas, road maps etc. and qwen 3.8-27b can write the code very well even with thinking but the work orders are very preciese that even thinking is not needed. Also after starting using 3.8 it works like a charm, 47 work orders so far and no errors, zero. Each take about an hour because I've 7900XTX and on the same machine with everything else so it is a bit slow, 50 ish t/s. Zero cost. I've done this in 10 minutes, I'm pretty sure people have other ideas or even better performing ideas and this kind of work will get better. Even 3.8-27b is good enough to leave cloud api's as @Da7_Tech reported as well so I'm considering local only work from now on, I'm just using my cloud quotas because I already paid for them, why not :) People will stop using these ripoffs, they will find other solutions as the competition already heated. No more I'm the best model or I'm the best. My github repo link in my bio if you want to check it out.

• 
  AntiCode Guy (@AntiCodeGuy) reported 43 minutes ago

  Self-hosted CI Failed <written by a human being> A couple of days ago I wrote about my attempt to set up CI runners on my own server. It's a system for building apps before releasing them to production. And it all started off pretty energetically, but in the end I couldn't quickly stand up a decent alternative to GitHub Actions, even though technically and in theory it's definitely possible. The first difficulty is that the service has to serve more than one repo and build different kinds of apps. That means you need a queue system, and it has to be prioritized correctly. Next, the build itself needs a system for parallelizing and distributing CPU and memory capacity to speed up the build process. Otherwise what's the whole point, if instead of 10 minutes on GitHub Actions it takes several hours to build on your own server - which is exactly what happened with the first version of my runner. But every time I tried to run real builds, I kept running into new bugs, which spawned a whole pile of new tasks both on the CI-runner side and on the side of the apps themselves for optimizing the CI process. In the end, at this stage it's much faster and simpler to just switch the repo to public access, which removes the limits on GitHub Actions builds. And as the product develops you can go back to limited capacity or hook up compute services like Blacksmith. By the way, for a single app it's way easier to set up a system like this - for my home accounting it took 10 minutes on a home server and it worked fine on the first try.

• 
  Raphael Volz (@ProfVolz) reported 43 minutes ago

  @TinaDebove On Github Copilot for the same reason, somehow slow, but I like the possibility to switch between models.

• 
  Abiel | Dev & Startups (@abielbuilds) reported 43 minutes ago

  a few people asked how to create a simple MCP server, so I finally recorded it. I followed the official MCP GitHub example and built a small weather server: create the MCP server register a get-alerts tool validate the state with zod call the weather API return the result back through MCP video is about 2 mins 👇 if yall want, I can do the next one on resources or prompts drop your suggestions in the comments

• 
  Shayan Nadeem (@shayannadeem123) reported 46 minutes ago

  @Taniyatweets_ GitHub but most website servers are behind cloudflare if that goes half of internet will go down.

• 
  Tommy Bez (@TommyBez85) reported 53 minutes ago

  Today the whole site had 2 human visitors. 5 GitHub stars, 7 signups. I can write faster, I cannot crawl faster. Checkpoints at day 7 and day 14, and I will report indexation status and impressions, not clicks. Clicks are the next problem.

• 
  Trapstar (@TrapstarXBT) reported 55 minutes ago

  $Frock at 300k rn, im trying to get this slow people method to think when they bid a coin, and the one that gives fees to the creator of frock is at only 27k rn, i need to tell that u can claim on your github buddy and use the funds for your project or whatever you want to do @unixpickle take a look into it ffs 3YTL3nSt5ePiaxzwmHU854j9xXNLZZ1LUyXQYzsdJZAN