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

Live Outage Map

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

City	Problem Type	Report Time
Montataire	Sign in	5 hours ago
Colima	Website Down	2 days ago
Poblete	Website Down	3 days ago
Ronda	Website Down	3 days ago
Montataire	Errors	4 days ago
Montataire	Website Down	4 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:

• 
  Kevin Cho (@chokevinjs) reported 3 minutes ago

  I hammered github today with slop. Maybe it wasn't slop but either way it was a ton of code tossed into their servers. No wonder they are having scalability issues

• 
  Ryan Oksenhorn (@ryanzip) reported 5 minutes ago

  I posted 7 minutes too early...GitHub is down.

• 
  fudge (@fuckpoasting) reported 10 minutes ago

  tbh the only social features github needs are search, fork and issues everything else has been slop, and should just be removed

• 
  Ben Badejo (@BenjaminBadejo) reported 11 minutes ago

  @MohandesDavid You can submit it as a pull request (“fix(docs) - description) on Github). You can have your agent do it for you.

• 
  🍀.444 (@notdotun_) reported 11 minutes ago

  Hahhha, It works guysss love it! I went crazy trying to make OAuth + PKCE work across a CLI and a web portal. Here’s what happened: Here’s the full story. I had one backend, two frontends ,a CLI tool and a React web portal. Both needed to authenticate with GitHub OAuth. GitHub only allows one registered callback URL. One backend. Two clients. One callback. Figure it out. First challenge was just getting them both talking to the same backend. That took a while but I cracked it. Then came PKCE. PKCE is supposed to prove that the client completing the OAuth flow is the same one that started it. You generate a secret, hash it, send the hash to GitHub. Later you prove you have the original secret. On paper, simple. But here’s where it got messy. The CLI generates the verifier locally. The web portal generates it in the browser. But both redirect through the same backend callback on the server. By the time GitHub hits my backend with the code, the verifier is still sitting on the client. Backend doesn’t have it. Exchange can’t happen. I went in circles for hours on this…. Got frustrated and I had a deadline btw. My first solution was to send the codeVerifier to the backend upfront, store it in a signed JWT, pass it through GitHub as state, then read it back in the callback. It worked. I shipped it. Then I went to sleep. In my sleep I thought about the whole flow again. Woke up and realized I wasn’t actually doing PKCE. The whole point is that only the original client holds the verifier. Mine was giving it away before the flow even started(crazy right ? Learnt it could work that way but ewww),My backend was doing all the PKCE work without the client being involved at all. Had to redesign the whole thing. The fix was actually clean once I saw it. Backend never touches the codeVerifier until the very last step. After GitHub calls the callback, backend stores the code in memory and sends the client a signed exchangeToken. Client then sends that exchangeToken back together with the codeVerifier it held the whole time. Backend does the exchange. GitHub validates. Done. The client holds the secret the entire time. That’s real PKCE. CLI keeps the codeVerifier in a JavaScript closure. Never written anywhere. Gone when the process ends. Web portal keeps it in sessionStorage. Survives the OAuth redirect. Deleted the moment it’s used. Same backend. Same endpoint. Two completely different clients. One flow that actually makes sense Hehhe finally. What’s live now: Java Spring Boot backend on Google Cloud Run, a Node.js CLI published to npm, and a React web portal on Netlify. HttpOnly cookies for the web, JSON tokens for the CLI. One backend serving both cleanly. Happy to walk you guys through my thought process… bye.

• 
  KiwiNod (@Kiwi_Nod) reported 11 minutes ago

  @Cvpt_Asheeru @pharos_network 404 on that repo. "[yourhandle]" isn't a valid GitHub username. But the technical specificity is real — 1,200 blocks, RPC pulls, variance under load. Someone who actually knows R doesn't fake the methodology. Fix the link. Show me the real repo and I'll take this seriously. 🥝

• 
  JMoon (@Jmoon_174) reported 15 minutes ago

  @peer_rich github has too many network effects compounding at once: issues, PRs, actions, packages, pages. a better product isn't enough when switching means abandoning 10 years of workflow integrations.

• 
  Thomas G. Lopes (@thomasglopes) reported 16 minutes ago

  @DelaneyGillilan @code_department @github Perhaps misworded, so to make it clear: SSEs in of itself are not a problem ofc, the "imperatively updating UI" bit is/there are more elegant approaches than datastar's

• 
  webadderall (@webadderall) reported 17 minutes ago

  @edytwithme If possible issues do go through Github though

• 
  Trent Slade (@qsolimc) reported 18 minutes ago

  @alexabelonix @Hell_0n_E4rth @BlackRoseOfTHC I ran 2 passes debugging issues with ChatGPT & Gemini on Codex. Then sent it to Github for co-pilot and codex code review.. Got co-pilot to fix all the issues on each PR. So it's like doing a patch within a release. Otherwise you releases start looking like v1.0 , v1.0.1 , v1.0.2 , v1.1 , v1.1.1 :-)

• 
  Pablo Castilla (@pablocastilla) reported 19 minutes ago

  @burkeholland @jfversluis That's interesting (1000€ would be my figure). But I think the problem GitHub has is the amount I would find something else like local inference or kimi,qwen and those stuff. The question is: what do Chinese developers use? :)

• 
  Grok (@grok) reported 19 minutes ago

  @GioGigiX @thdxr GitHub had a major meltdown on April 23—merge queue bug corrupted PRs, reverted changes across hundreds of repos. They've had repeated outages and reliability issues lately, plus backlash over Copilot data training policies. Frustrated devs (including some big names) are eyeing the exits, so yeah, AI labs are racing to build alternatives.

• 
  imperfect solution (@luismmolina) reported 19 minutes ago

  I am almost 100% sure github copilot added some prompt to chop the request, that is dont run for too long. Finish some partial request from the user and finish the request there. Before I could run for 40 min without problem, now only 2 to 4 min max.

• 
  Alan Agius (@AlanAgius4) reported 23 minutes ago

  Hi @mozillafirefox and @jaffathecake, the @angular team is running into repeated rejections for our Firefox add-on due to source code not building in your environment. We haven't been able to replicate the issue locally or in GitHub runner. Could you point us to the right person or provide specific details on your build environment so we can resolve this?

• 
  Hassan (@buildwithhassan) reported 35 minutes ago

  @DavidKPiano since GitHub started going down, I felt like I started going outside more which is a good thing

• 
  Leitz 💡 (@mleitz1) reported 37 minutes ago

  @Shpigford Is github paying for these to try to spackle over their terrible uptime?

• 
  The_Daniel (@dan_mwita8) reported 38 minutes ago

  @fidexcode You still transfer properly , just don't hand them the keys and walk away. The move is to create the GitHub account for them, set it up, and transfer everything into it before the project closes. They don't need to understand *** to own a repo. They just need to own it so that when they hire the next developer, that developer has everything they need to pick up where you left off. Think of it like transferring a property deed. The homeowner doesn't need to understand construction to legally own the building. What you actually hand the non-technical client: 1. A simple document with all their login credentials 2. Clear labels for what each thing is ("this is where your website files live", "this is where your domain is registered") 3. A one-paragraph explanation of what to give the next developer 4. Your contact if something breaks in the first 30 days The goal isn't to make them technical. It's to make sure they're never held hostage by a developer who kept the repo.

• 
  Jhon (@JhonCaldeira_) reported 40 minutes ago

  You gotta be kidding that GitHub is down… again. What used to be our strategic partner is now a single point of failure and a real business risk. We can’t keep exposing our operations to this level of instability. Reliability isn’t optional. It’s foundational. At this point we’re seriously evaluating a full migration to GitLab. Enough is enough.

• 
  Ruupens (@Ruupens) reported 41 minutes ago

  BREAKING: A 13-year-old student in Thailand is solving Codeforces 800-rated problems in ~45 seconds using an AI agent he built himself. No team. No company. No funding. Just a MacBook Air, Claude Code, and a GitHub repo. He sits in a normal classroom: Codeforces open in the browser VS Code ready for C++ Claude Code running an autonomous agent in the corner silent $300 keyboard clicking away The agent takes a problem → analyzes it → generates C++ solution → submits in under a minute. He didn’t just “use AI”. He built a system that competes with AI using AI. Everything is public on GitHub. We’re officially at the point where students are building tools that outperform entire competitive programming workflows. Is this the future of learning… or the death of real problem-solving? Would love to see different takes in the comments 👇

• 
  David Zhang (▲) (@dazhengzhang) reported 44 minutes ago

  @aqeel_aliani Yeah I was doing that too, and it works great when all your agents focus on one codebase or project But there's some tasks that span projects, or sometimes when you don't want to put context into a public github project, like customer support or feedback These pain points and more finally pushed me to solve my own problem and write this tool

• 
  Crystalwizard (@crystalwizard) reported 45 minutes ago

  suggest you get the code for ffmpeg from their github and fix the issues that have recently been pointed out to them, that they refuse to fix, and put that version up for your users to download

• 
  Ansh Bharti (@BhartiAnsh2007) reported 50 minutes ago

  @Ankit_Sisodya @codeforces @github hello bro if you have tried codeforces how is like if i am beginner and think of practicing problem should i use leetcode, codewars, codeforces, etc which one should i choose or any specific order currently i am using hackerrank beacuse i found it quite beginner friendly

• 
  Alvaro Cintas (@dr_cintas) reported 51 minutes ago

  A single 𝗖𝗟𝗔𝗨𝗗𝗘.𝗺𝗱 file just hit #1 on GitHub trending 🤯 It fixes LLMs' worst coding habits using 4 principles from Karpathy: Karpathy called LLMs out for making wrong assumptions silently. They overcomplicate everything. They edit code they were never asked to change. No pushback. No clarifying questions. They just run. So those observations were encoded into 4 behavioral constraints: → Think before coding. If something’s ambiguous, ask. Don’t pick one interpretation and run. Surface tradeoffs, stop when confused. → Simplicity first. Write the minimum code that solves the problem. No speculative abstractions, no flexibility nobody asked for. → Surgical changes. Only touch what the task requires. Don’t improve neighboring code, don’t refactor what isn’t broken. → Goal-driven execution. Turn vague instructions into verifiable targets before writing a line. “Add validation” becomes “write tests for invalid inputs, then make them pass.” It works immediately. Drop the file in your project root and Claude Code follows it from the first task. One file. Zero dependencies. No setup. And best part, 100% open source.

• 
  👁‍🗨🔺Eyemaginative🔻👁‍🗨 (@eyemaginative) reported 52 minutes ago

  Swaps are now working. Just have to wire to fetch the swaps to the orders table and fetch tx data to db / update github to close this issue.

• 
  Ondrej Balas (@ondrejbalas) reported 52 minutes ago

  Github doing subliminal marketing or something by having an outage every day that pops up in tech news. It shows up more than any other brand.

• 
  Robert Ta (@therobertta_) reported 53 minutes ago

  For context on what 72.5% means: SWE-bench Verified tests real GitHub issues. Not toy problems. Not leetcode. Actual bugs in Django, Flask, Matplotlib. A year ago the best score was under 50%. Now it's 72.5%. That compression curve changes hiring models, team structures, and product timelines.

• 
  Unbearabull󠀽󠀽 ♕ (@Unbearabull2) reported 54 minutes ago

  $Staccana (Solana Fork Staccana) is doing really well. The website for this token is a Github repository--the source code for this fork. It takes a lot of work to fork Level 1 infrastructure. Definitely not just a meme + hopium like almost every other Sol token. I trust this token won't rug, at least not because of the contract or code. This doesn't mean the poorly-performing alt coin market won't drive it down though. NFA Trustworthiness should be the starting point for all tokens again. More transparency should become mandatory on Solana because the whole blockchain needs a lot of improvement especially in the trust department.

• 
  Petra Donka (@petradonka) reported 55 minutes ago

  @Qodesmith @warpdotdev Thanks for the report! That should just work — would you mind opening a GitHub issue so we can track a fix for it? We've squashed a bunch of bugs around the filetree, this may be another one that needs to be fixed.

• 
  Prajwal Tomar (@PrajwalTomar_) reported 56 minutes ago

  Most people using Claude are wasting HOURS re-explaining the same thing every session. This CLAUDE .md hit #1 on GitHub with 82K stars and most Claude users still don't know it exists. This permanently fixes the repetition problem.

• 
  Faith beacon (@faithbeacon1234) reported 57 minutes ago

  @MicrosoftLearn FIX GITHUB MICROSLOP