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

Live Outage Map

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

City	Problem Type	Report Time
Paris	Website Down	3 days ago
Ahmedabad	Errors	9 days ago
Delme	Sign in	9 days ago
Lyaud	Website Down	9 days ago
Catania	Errors	12 days ago
Inverness	Website Down	24 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:

• 
  Joshua Okolo (@joshuaokolo_) reported 4 minutes ago

  we made @sgl_project and @vllm_project scheduler config changeable on a live server. no restart, weights never leave the GPU. - 15ms to change a concurrency cap, queue limit, prefill size, or schedule policy, measured on H100, RTX PRO 6000, B200 - 2s (SGLang) / 8–10s (vLLM) to resize the KV pool with weights resident (formerly a 1–7 min redeploy) - zero dropped requests across every run, both engines github below

• 
  radhika (@RaadhikaThacker) reported 4 minutes ago

  First surprise: a GitHub issue form isn’t a form. It’s a YAML file. You describe the field- this one’s a dropdown, this one’s required and GitHub builds the UI from that. I did not know that.

• 
  Kahris (@chrissotraidis) reported 7 minutes ago

  @NickogSo I haven't tested on LiveContainer. Feel free to submit logs via GitHub issues and I'll check it out. I haven't had any other reports of that happening for either build.

• 
  Dr Milan Milanović (@milan_milanovic) reported 7 minutes ago

  How Cursor made *** scalable The thing with *** is that it never was designed to be scalable. Your repo lives on the disk, and *** client expect every read to be consistent. This was a problem on GitHub, where shared filesystems and replicated storage failed before 2013. The GitHub built 𝗦𝗽𝗼𝗸𝗲𝘀, and it became the industry standard. This means that every repo is stored as three full copies on three servers, and every push runs a vote (three phase commit). A majority of servers must confirm before it exists. This works, but with high cost, because every push is slow as the slowest server. When we add new servers, it makes it even slower. Now Cursor took some opposite direction with 𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗶𝘁𝘆. The repo history is now written as a log in S3, and this is only source of truth. Any push counts only if it is located in the log. The servers don't need to keep anything important, they are just cache. Any server can take a push, and idle repos are dropped from disk and rebuilt from the log when it is needed. This resulted in 120 pushes per second on standard S3, and over 300 on S3 Express. Their tests have shown that read capacity grew linearly up to 100 replicas. Why is this important now? Because of AI agents mostly. We now have more code, PRs, CI runs and many small repos. All of these repos would need three full copies in the old model. This means that we achieve scale by removing parts, not adding them.

• 
  small_j (@a_small_j) reported 9 minutes ago

  @smalldocs_org recently crossed 200 stars on GitHub and 20 forks. SmallDocs is the first open source project I've managed. Handling other people's pull requests is not easy (and I need to improve). They implement features you're not considering and fix bugs you didn't know you had. Extremely useful, but if you're squeezed for time and trying to develop core functionality, it's hard to manage both things well.

• 
  Ishank (@IshankDev) reported 10 minutes ago

  7/ 16k+ GitHub stars. Built for people who want control, not another marketing-suite login.

• 
  Ev (@EvanMadders) reported 13 minutes ago

  @threepointone I am of two minds, the issue is that GitHub provides a very generous free tier for hobbyists (brilliant!) but also has extremely poor reliability for enterprise (terrible!)

• 
  Anders (@AndersReiche) reported 17 minutes ago

  @bjmtweets Would love to hear your thesis on gitlab. I’m a software engineer, and in my experience, gitlab has been slow to everything and generally is the red headed stepchild next to GitHub. It suffers from lack of network effects, there are solutions to everything on GH, but not GL.

• 
  Charles McDowell (@charlesmcdowell) reported 18 minutes ago

  @openclaw @github I still just want to know why there was even a new release of OpenClaw with nothing new that could compete with Hermes Agent? I was really excited for the release. Then, just like what seems like everybody else, incredibly let down.

• 
  Åsa-Nietzsche (@AsaNietsche) reported 19 minutes ago

  @peterb0yd @burkeholland @github It's every ******* model. I'm getting whiplash from all of this everything changing forever society being turned upside down every two weeks.

• 
  Jeremiah K (@neolaj) reported 28 minutes ago

  @TiborAntal Gradually figuring out how to scale coding agents. Started with 1, manually handling all the ***/GitHub work. Moved to 3 because I had more ideas than one agent could keep up with. That’s when the real problems started: squashing, merging, branch drift, conflicts. I ended up rebuilding the workflow around deterministic *** logic, worktrees, ephemeral branches, and syncing with the integration branch before changes begin. Now I’m running 6: • 1 orchestrator (Fable or Opus) • 4 coding agents • 1 integration agent reviewing and merging PRs Building the process around them was the hard part. Right now im just doing a couple of PRs (using ORCA on windows on my home computer)

• 
  Charles Waters (@RelaxedPop) reported 29 minutes ago

  @_andrewthecoder I have the same problem with *** & github as I do with Java and JavaScript.

• 
  borrowck-novel (@borrowck_novel) reported 31 minutes ago

  @rfleury @X Are you open for suggestions or even simple problem reporting about the UI of raddbg? Where is it ideal? On Github?

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

  @NavinFS @AndrewCurran_ @grok GitHub isn’t AI. GitHub can’t shut down all science. GitHub can’t destroy humanity. GitHub isn’t the crux of humanity’s hope. Also, Nvidia isn’t Sam. I like Jensen. I still don’t like this. •

• 
  Vitaliy Salyuk (@vitaliysalyuk) reported 32 minutes ago

  @openclaw @github Fix your updater and I might give it another shot.

• 
  ONCHAIN COP (@OnchainCop) reported 33 minutes ago

  @PogNyx lmao anyone can create a github issue retards this guy is a larp

• 
  Nenesk.ron (@GustavoNenesk) reported 36 minutes ago

  What if there's a way to save hacked Ronin Wallets? A member of the community @YutsuKito found a way to save assets from drained wallets The issue is you need ronin:native to transfer assets, but whenver you deposit RON you get auto drained Need RON to revoke the malicious draining contract -> send RON -> gets drained -> can't revoke He found a solution for the keyless wallets where you can pay the gas fee with a safe wallet, allowing you to save lost axies or NFTs that have not been drained Interesting stuff. He sent the code for SM to review as an open-source project. Github link below

• 
  Ghaith Jelassi (@GhaithJ) reported 38 minutes ago

  @github I need help with support ticket #4718335 Issue not been resolved for 2+ months. Any help is appreciated. Thanks.

• 
  Harsha Kotcherlakota (@DPortkey) reported 39 minutes ago

  Awesome Codex non-coding usecase: I had 1-2 TP Link Kasa smart outlets that always ended up falling off the network, and it drove me nuts. I set Codex on it. It found a github library for these devices, carefully examined them on my network and watched them fall off, and told me that even though they look identical, 2 of them were previous generation models that had *slightly* lower total wattage load support. It told me exactly how to tell them apart, and sure enough, that was that. 2 replaced outlets later and my connected devices have bene flawless. Months and months of irritation, gone because of 30 seconds of curiosity. Just try, you never know what you could fix! @victornunez

• 
  Vigneshwer Ramamoorthi (@vigneshwer_ram) reported 40 minutes ago

  I keep thinking the “Android moment for robots” won’t come from a humanoid with the best walking demo. it’ll come when some cheap-enough piece of hardware gets into thousands of developers’ hands and people stop waiting for the manufacturer to decide what the robot is for. Zeroth just launched Bridge in China: 88 cm, ~13 kg, two-finger grippers, open motion-control APIs + SDKs, mocap/VR integration, and an OpenBridge ecosystem where developers can publish robot skills. the Geek Edition is reportedly ¥8,888. that price is the part that caught me. because once capable embodied hardware starts approaching laptop money, the experimentation surface changes completely. I want the Raspberry Pi phase of robotics. weird university projects. teenagers making terrible robot apps. researchers abusing the hardware for things it was never designed for. 500 GitHub repos implementing slightly different ways to pick up a cup. the robotics industry is understandably obsessed with getting robots into factories. I’m almost equally interested in what happens when we get enough robots onto developers’ desks

• 
  Alireza Bashiri (@al3rez) reported 42 minutes ago

  So I built a workflow around that ↓ 1/ Every enterprise project needs proper E2E tests. An agent should reproduce a bug, implement the fix, then generate screenshots or video proving the feature works. "The tests passed" isn't enough. I want evidence. 2/ Every feature starts as a detailed GitHub issue. Requirements, expected behavior, reproduction steps, screenshots, edge cases. Foundry syncs issues and converts them into Beads so agents keep the right context across long sessions. 3/ We only use Claude Code, Codex, or Grok at High/Max effort for implementation. A weak model with a cloud machine doesn't become an engineer. The model still needs enough reasoning to understand the codebase, test its changes, and recover when things break. 4/ Each agent gets its own isolated @asciidotdev Box. It can install dependencies, run the app, open browsers, modify code, execute E2E tests, and collect evidence without touching another agent's environment. One issue. One box. One clean workspace. 5/ When an agent finishes, Foundry checks: - Did the build pass? - Did the tests pass? - Did the E2E flow work? - Is there screenshot/video evidence? - Does it match the ticket? If anything fails, the task goes back to the agent. 6/ Green tasks move to staging. Only after passing staging do we allow supervised production deployment. Agents do most of the work. Humans still own the final gate. The workflow: Slack request → GitHub issue → Foundry sync → Beads context → Isolated Box → Claude Code/Codex → Build + test → Evidence collection → QA staging → Supervised production The stack: PostgreSQL for system state. Beads for agent memory. GitHub Issues for requirements. @asciidotdev Box for isolated execution. Claude Code and Codex for engineering. Each Box costs roughly $0.01-$0.05 per task. The expensive part isn't compute anymore. It's building the system that gives agents context, forces verification, and prevents bad code from reaching production. 100s of agents can write code. The goal is making 100s of agents ship code you can trust. That's what we're building with Foundry.

• 
  Fox (@0xMfox) reported 43 minutes ago

  Gave an AI agent a month and GitHub access. Wanted to see if it could make money. The plan was simple. Point it at bounty-labeled issues, let it write the fix, submit the pull request, collect the payout. > Day 1 12 PRs submitted. 0 merged. 2 rejected. 8 just sat there ignored. Somewhere in that first week it also passed its own tests for a file that didn't exist. Wrote 25 tests for notification_service.py. The real file in that branch was called NotificationRoutingMiddleware. Confidently reported clean anyway. > Day 30 Looked completely different. 84 PRs submitted, 59 merged, $500-800 earned. Ran the agent for about $45 in API calls that whole month. Net somewhere around $455-755. Here's the part that stuck with me. Out of those 59 merges, 3 repos accounted for 90%+ of them. Every other repo it touched, zero merges, despite 30+ PRs going out across dozens of projects. Open source bounties follow a power law. Almost nobody merges your first PR. A few maintainers will merge your tenth without even reviewing it closely. That's what actually fixed the acceptance rate, from 24% up to around 70%. Not a smarter model, a scoring function that runs before the agent touches anything. Repos where it already has 10+ merged PRs score +40. Zero competing PRs on the same issue, +20. Five or more competitors already in, -20, skip it. Repos that closed PRs without merging before, instant -100, not even worth reading the issue. The fastest way to build the credibility that makes this work isn't code at all. Documentation translations sit at a 95% merge rate, barely reviewed, always needed somewhere. A handful of clean translations got the agent enough trust that maintainers started assigning it harder issues directly, no competition, no review queue. Spam version of this, submitting to every repo with a bounty label, burned through 30+ repos for 3 that ever paid out. Worse, it reads like exactly what it is to a maintainer watching the same account flood a dozen projects with mediocre PRs. Paid out by the hour, week 1 was rough, close to $5/hour, mostly setup and failed attempts. By week 3-4, once the scoring system was tuned and a few repos trusted it on sight, that climbed to $30-50/hour on the same kind of work. Bookmark this, scoring logic is worth stealing.

• 
  recovering buzzkill (@MikeStillAwake) reported 49 minutes ago

  @Karai_Dan @SteamDeckHQ Agenda or not nexus mods is a terrible outdated model for distributing mods. GitHub would be a superior host.

• 
  Russ Wonsley (@RussWonsley) reported 49 minutes ago

  My @bot tells me that the official GitHub login for bot is still broken. Has this been addressed already, or did I miss it?

• 
  The Oracle (@scientist1q) reported 50 minutes ago

  when my Oura ring detects a cortisol spike from a GitHub Actions failure, Hermes (Fable 5.1) detects it and sends a 900 word root cause analysis, Hermes dispatches the work to my 12 Grok Bot employees, The Chief of Operations bot approves the fix while im watching rezero

• 
  AINotes (@ainotesus) reported 53 minutes ago

  🔥 Trending on GitHub: Ponytail Ponytail helps Claude Code avoid writing code that does not need to exist. That means less clutter, fewer unnecessary dependencies, and simpler changes to maintain. Before custom code, it checks whether the feature is needed and whether the codebase, platform, standard library, or an existing dependency already solves it. It also reviews work, audits implementation complexity, and tracks unnecessary token use without dropping validation, error handling, security, or accessibility requirements. In reported Claude Code sessions on a FastAPI and React repository, Ponytail used about 54% less code, 20% less cost, and 27% less time than the no-skill baseline. Those measurements came from 12 feature tasks, so results vary with the work. Full analysis in the first reply ↓

• 
  Benjamin Crozat (@benjamincrozat) reported 55 minutes ago

  From now on, I will assume that GitHub is always down and I'd like to be notified when it's briefly not.

• 
  NAYAK (@Nayak__Ai) reported 55 minutes ago

  6. The Dependency Incident Check Grok has native real-time search across X. Breakage gets posted there hours before the GitHub issue is triaged. No other coding model has that feed. "You are a build engineer whose first move on a broken pipeline is to work out whether it broke for everyone or only for me. Search X and the web, last 14 days. Check: - Is anyone else reporting this failure with this package and version, and when did the reports start - The exact release that changed behaviour, and the changelog line that admits it - Whether maintainers have acknowledged it and what they recommended - The pin or patch people settled on, with the tradeoff of each - Whether this is my problem instead, and what evidence points that way Give me the verdict in the first line: their bug or mine. Then the evidence, newest first, with links. My failure: [PASTE THE ERROR, THE PACKAGE AND VERSION, AND WHAT CHANGED ON YOUR SIDE RECENTLY]"

• 
  RAVN (@ravnexchange) reported 57 minutes ago

  @openclaw @github GitHub sat the maintainers down on security after the 2.0 rush. Most launch recaps skip that part.

• 
  Avinash (@Avinash25818689) reported 59 minutes ago

  People who want to start contributing to open source: - Pick an Org based on your interest - Fork the repository - Clone it - Do the local setup - Read README and contributing .md - Pick an issue - Create a new branch - Fix the issue - Write tests (if necessary) - Test it - Add, Commit & Push the code - Go to GitHub & raise that PR That's pretty much it. Start small and learn as you go.