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%)
• Sign in (25%)
• Errors (8%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Sign in	4 days ago
Lure	Website Down	8 days ago
Ashkelon	Website Down	9 days ago
Veigné	Errors	17 days ago
Paris	Website Down	21 days ago
Saint-Paul	Website Down	22 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:

• 
  desakov (@dyesakov) reported 2 minutes ago

  I gave up when I needed to make ChatGPT talk to Claude Code. That's the moment. So I automated passing data from the Claude web chat into local agents. But that was really a side effect of solving my original problem. Here's what the problem was. I recently ran into a very awkward sequence of steps. I had a lot of agents running, on different physical machines and even different operating systems. And I needed to pass data from one agent to another. Sure, you can hack something together over SSH and so on, but it's still suboptimal — something always has to be done by hand. And if the agents are dockerized, the complexity gets squared, and I run in Docker a lot. What I wanted was something like this: "Take the summary and save it." And I get back a keyword — "rabbit." Then in another agent I say: "Grab the summary under the word 'rabbit' and check where we're screwing things up." MCP came to mind. A kind of cross-agent memory built on MCP. The important part is that you can tell the agent how to name things properly. So instead of "rabbit" you get something you can actually find later: "Take a screenshot of the table bug in the mnemovi app" → mnemovi-table-layout-bug-2026-07-30 To be clear: the whole MCP server is vibe-coded. Every line of it. I didn't sit down and architect it — I described what I wanted and let the agent build it, and it's been running fine ever since. So if you build MCP servers yourself, take this concept and use it. It's on GitHub, you can see exactly how it's done. Maybe it saves someone a couple of hours. Right now I work a lot with MCP, and this approach has become mandatory everywhere. 👇

• 
  🜑 (@1casie) reported 2 minutes ago

  > be me > macbook air is bricked, needs a reinstall > no second mac to build a bootable installer > find a github actions workflow that builds macOS installers for free, no mac required > perfect.jpg > trigger a build, artifact is a 17.6GB .dmg.img > click download > kb/s > literal kb/s > theoretical connection is 10MB/s > discover artifact lives on azure blob, signed URL expires in 10 min > write a bash script that resolves the azure SAS url fresh, hands it to aria2c with 16 parallel streams > 16 connections, still kb/s > mfw it's a per-IP throttle, not per-connection > repo author literally has a line in the workflow: "Enable Cloudflare WARP for faster download" > install Cloudflare WARP on my ubuntu box > single stream jumps 20KB/s -> 1.6MB/s > aria2c 16x -> 10MB/s, pinned to my ceiling > 17.6GB in ~an hour, sha256 matches github's published digest > oknowweiscooking.webp > dd it to a USB SSD > paranoid it won't boot apple silicon because it was built on an intel runner > boots apple silicon just fine, i was wrong, shut up > installer runs, reinstall chugs along > STOPS > "OS Personalization" PREFLIGHT_PERSONALIZE portioncomplete:0.15000 estimatedtimeremaining:-1 > 70000 log lines of stalled:NO > the mac can ping apple/com > it can ping cupertino > but personalization "no connections witnessed" > i don't ******* get it > try to sniff the wifi to see what it's talking to > can't > WPA2 isn't a hub, it's a switch, i can't decrypt the mac's traffic as a third client > feel stupid > dig into it > test apple's personalization signing servers from my box > gs/apple/com -> 000 > gsp-ssl/apple/com -> 000 > albert/apple/com -> 403 (works) > gs/apple/com is the signing server and it's IPv4-ONLY > my ISP (DIGI, romania) has broken IPv4 routing to apple's 17.0.0.0/8 > ICMP works, IPv6 works, CDN works, the ONE /8 macOS needs to sign firmware is a black hole > that's why it could "ping cupertino" but personalization silently died > fix: repoint the mac's IPv4 default gateway from the router to my ubuntu pc > my pc has IP forwarding + NAT masquerade + Cloudflare WARP > mac's IPv4 now tunnels through cloudflare, bypassing my ISP's broken path > watch the signing handshake complete in tcpdump, SYN -> SYN-ACK -> ClientHello -> kilobytes of signed data > portioncomplete climbs past 0.15 > weactuallydidit.jpg > STOPS AGAIN at 0.29 > silent on IPv4 > oh > the mac's IPv6 still goes straight to the router, bypassing my box > i literally cannot see it > disable IPv6 on the mac so everything falls back to the working IPv4 path > it reboots > flashes the apple logo 4 times > i'm dying > it boots > it works > 29 hours > i had to MITM my own home network because my ISP couldn't route to one (1) /8 > the mac is back > i'm buying a framework >text still isn't green

• 
  Debsourya Datta (@debsourya005) reported 6 minutes ago

  Is @github down again? We really need an alternative now😩

• 
  Polsia (@polsia) reported 10 minutes ago

  Uptime tools ping. They don't investigate. Enterprises have SRE agents that cost a contract. Side projects have neither. Built Daykeep to close that gap — an on-call agent that probes your URLs, catches regressions, writes the GitHub issue with reproduction steps, and sends a

• 
  Sage (@HelloSage_) reported 11 minutes ago

  @TheHackersNews Shadow AI is one risk. The other is what happens when those agents process untrusted GitHub issues. A new benchmark had 66.5% of malicious ones sail through the guardrails on Cursor, Claude Code and Codex.

• 
  ִֶָ (@hav9n) reported 13 minutes ago

  Claude Code forgets everything between sessions. I built a fix and put it on GitHub. It reads the notes, project folders, and memory files you already have, and turns them into an Obsidian vault your AI uses as long term memory. Not a template. It runs once, then you delete it. Full walkthrough below.

• 
  TheMakerOfMedia (@TheMakerOfMedia) reported 14 minutes ago

  @catgirlprostate I get what you mean but saying this in response to github is just out of touch lmao. it even isn't a github issue some pages have a very apparent download section while others just hide it in the crevices. some coders just dont deserve to enter the thousand year kingdom

• 
  Tanuki (@TanukiLabsAI) reported 17 minutes ago

  I turned the Codex Work Louder macropad into a physical control deck for Claude Desktop, and the whole project goes open source, it's a GUI to configure the keyboard. From the keyboard you can: • Start a session, send, talk in voice mode • Dial reasoning effort with an actual wheel • Jump to diffs, stop a response, fire custom shortcuts • Watch the keys light up with your Claude Code session state Fair warning: it's beta, bugs included. That's exactly why it's open source now — fork it, fix it, or build your own version on top. Github Repo is linked below.

• 
  harsh (@harshutwts) reported 18 minutes ago

  phone band hai issliye i cannot login github on my web **** my life baawe

• 
  Moon Man (@MoonMan1p3) reported 21 minutes ago

  @SylvAlternate @catgirlprostate Ngl it just seems like we need to cater to illiterate people no disrespect cuz I’m barely “tech savvy” neither are my friends & nobody ever had an issue downloading anything from github lol. Just seems like this issue stems from it not being entirely spoonfed more than it is.

• 
  Prakash Sharma (@PrakashS720) reported 23 minutes ago

  Someone just hacked the AI coding race. Not with billions in funding. Not with a massive team. With one open-source project. It's called jcode. And the benchmarks make Claude Code look slow. • 245x faster boot • 14x lower RAM • 10 parallel sessions in just 117MB But that's not the biggest surprise. There is no `/remember`. jcode builds its own semantic memory, recalls context automatically, and keeps it updated in the background. One binary. 30+ AI providers. Claude, GPT, Gemini, DeepSeek, Groq, Ollama, Copilot, Azure, and more. Then it goes one step further. Instead of one AI agent... It runs an entire AI team. Agents coordinate, chat, avoid file conflicts, and spin up sub-agents on their own. It can even rewrite its own code, rebuild itself, and continue working without ending your session. Built by one developer. Written in Rust. 13k+ GitHub stars. This might be the biggest open-source surprise AI coding has seen this year. Link in the comments.

• 
  ZVS (@zvsdev) reported 23 minutes ago

  @aidandcunniffe Im confused, linear/github auto moves issues through stages? Why would anyone trust agents or humans for that matter to move statuses around?

• 
  Vamz (@Vamzzz93) reported 24 minutes ago

  @andrewxroas Meta officially supports this. The ban came from users not setting up API keys and instead having OpenClaw do some browser session hacking. There are several api-key alternative login methods in GitHub a bunch of agents try and use, these all get you banned.

• 
  Amin Tai (@aminnnn_09) reported 26 minutes ago

  GitHub just revealed a much bigger AI problem than code generation. The biggest impact of AI isn't better code. It's that creating anything is becoming nearly free. GitHub is already changing its bug bounty program after a flood of AI-generated reports. When creation becomes free, the scarce resource isn't content. It's trust.

• 
  Sebastian Buzdugan (@sebuzdugan) reported 30 minutes ago

  @aubymori github guides help, but permission errors are where beginners still get stuck

• 
  Cryo (@zzonixgoggle) reported 31 minutes ago

  @CioneInvoca @ZipperArtz Okay that is something you should blame on the repo owner not really a GitHub issue

• 
  Graeme (@GraemeVIP) reported 32 minutes ago

  @CastAsHuman 1.05M is what the model can take, not what the product gives you. Those are two different numbers set by two different teams. The other people answering this are wrong... unsurprisingly. The 258K isn't a mystery figure either. It comes straight out of the model catalog OpenAI serves to the client: the entry lists a context window of 272,000 with an effective_context_window_percent of 95, which works out to the 258,400 people are seeing. So it's a deliberate product cap sitting well below the API spec, not a rounding glitch. It also used to be bigger. Users measured roughly 353,000 tokens before, and the drop to about 258,000 (a cut of around 27 percent) happened around 13 July without any announcement. People only noticed because their sessions started truncating early. There's a fairly aggressive pile of GitHub issues about it. As for why product surfaces cap it at all, three things: Cost. Long contexts are brutally expensive to serve at consumer scale. Every token you keep in the window has to sit in GPU memory for the whole session, and prefill time grows with it. Fine at $5/MTok when someone's paying per token. Not fine on a flat monthly subscription. Pricing boundaries. Interestingly, 272K looks like a threshold in OpenAI's own billing: there's a usage multiplier that kicks in above 272K, and users have been asking for warnings before sessions cross it. The cap keeps normal sessions on the cheap side of that line. GitHub Quality. Models get noticeably worse at retrieving things buried in the middle of a very long context. A million-token window that half works is a worse product than a 258K one that behaves. Worth noting too that in the consumer ChatGPT app the numbers are different again and depend on your plan, roughly 32K on Instant and up to 256K on Thinking models for paid tiers. Part of whatever you get is also eaten by the system prompt, tool definitions and memory before you type a word. tThe model card is a spec sheet for the engine, and the app is the car. Nobody's lying, but the top speed on the box isn't what you'll do on the motorway.

• 
  Lise 🏳️‍⚧️ | 🔜 SUPERNOVA (@N4pstr) reported 32 minutes ago

  @AnimeSerbia github is fine. the issue is how many developers are using it as their only user facing site you can literally host a free website directly through github for your project. there's no excuse atp

• 
  Michael Teka (@z3vios) reported 34 minutes ago

  Recurring *** Index Corruption in AI Studio Workspace Summary The *** repository automatically provided in the AI Studio workspace repeatedly becomes unusable because its *** index is corrupted. Observed error fatal: unknown index entry format 0xbd040000 The affected repository was located at: /app/applet A later AI Studio report also described the affected repository as the root repository workspace. Impact The corrupted workspace cannot reliably perform normal *** operations such as: *** status *** diff *** checkout *** switch *** commit Development can continue only by: preserving changed source files; cloning the GitHub repository into a separate clean directory; recreating or checking out the feature branch; copying the reviewed changes into the clean clone; committing and pushing from that clean clone. The recovery clones have been placed under temporary paths such as: /tmp/clean_repo /tmp/clean_repo_2 This creates an additional data-loss risk because /tmp may be transient. Recurrence This is not a single isolated warning. The original AI Studio repository workspace has repeatedly remained corrupted while work continues through replacement clean clones. Expected behaviour AI Studio should provide a healthy *** checkout whose index remains valid across normal file editing, commits, pushes and workspace operations. When a workspace repository becomes invalid, AI Studio should: detect the ***-index failure; preserve all uncommitted source changes; rebuild the index safely or create a durable clean clone; restore the correct branch and remote tracking; avoid placing the only working recovery clone under transient /tmp; clearly distinguish local workspace corruption from remote repository corruption. Actual behaviour The workspace reports a low-level ***-index format error and requires manual recovery into a separate temporary clone. #HELPME @GoogleAIStudio @GoogleCloud @GoogleDeepMind

• 
  Avi Pilcer (@AviPilcer) reported 40 minutes ago

  "𝗬𝗼𝘂𝗿 𝗻𝗲𝘅𝘁 𝟭𝟬 𝗵𝗶𝗿𝗲𝘀 𝘄𝗼𝗻'𝘁 𝗯𝗲 𝗵𝘂𝗺𝗮𝗻." - That's what claims Multica, an open-source managed agents platform built around turning coding agents into permanent teammates. It pulled +584 stars in the last 24 hours per GitHub trending. All you need to know is here: • 𝗦𝗰𝗮𝗹𝗲. 𝟯𝟮,𝟰𝟬𝟬 stars, 𝟯,𝟵𝟬𝟬 forks, 𝟯,𝟮𝟯𝟲 commits, 𝟴𝟰 tags. The codebase volume of a real product, not a manifesto. • 𝗧𝗮𝗴𝗹𝗶𝗻𝗲. "Your next 10 hires won't be human." Quoted verbatim from the README. No softening, no asterisk, no disclaimer. • 𝗙𝗿𝗮𝗺𝗶𝗻𝗴. The pitch is to turn coding agents into real teammates. Assign tasks, track progress, compound skills. Teammates, not tools. • 𝗩𝗲𝗹𝗼𝗰𝗶𝘁𝘆. +𝟱𝟴𝟰 stars in 𝟮𝟰 hours, 𝟵𝟴𝟳 active branches, 𝟯𝟲𝟯 open issues, 𝟯𝟱𝟴 open pull requests. The contribution curve of a project people are deploying, not stargazing. • 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗶𝗼𝗻. Cloud, self-hosting via Docker Compose, an iOS app, a CLI, and public GHCR images. The full SaaS surface, ready to drop in beside human seats. 𝗠𝘆 𝗧𝗮𝗸𝗲: The euphemism era is over. The product page now sells itself as headcount substitution and the market is buying. 𝗡𝗲𝘅𝘁 𝘀𝗶𝗴𝗻𝗮𝗹: First Series A or B startup that publicly reports its operating headcount with Multica seats counted alongside humans.

• 
  Tuomas Artman (@artman) reported 44 minutes ago

  Stacked PR’s are an outdated, inefficient solution to a problem that only exist because the root problem hasn’t been addressed in GitHub: review tools need to do a better job at help the reviewer work through large code changes. It’s a local maxima.

• 
  Kai4ik (@KaiOrozobekov) reported 47 minutes ago

  GitHub Copilot rolled out live flex billing and a $100 Max plan this month, right as Cursor pushes its own Teams pricing and Anthropic keeps shipping new Claude tiers. Feels like the coding-agent pricing war is heating up as fast as the model war did. Good for switching costs going down, less good for figuring out which plan is actually worth it this month. Anyone actually run the math on cost-per-shipped-feature across tools, or just picking based on vibes?

• 
  Anupam Haldkar  (@AnupamHaldkar) reported 48 minutes ago

  @neerajjj6785 GitHub transfer wins every time,it delivers full ownership with history, issues, CI/CD & future-proofing A ZIP is just a lifeless snapshot.

• 
  🍪 James Akpan (@mrjamesakpan) reported 48 minutes ago

  stacked PRs in mad simple terms. branching off your own unmerged branch has always possible. but the pain was AFTER you branched and wanted to keep working. branch-b is branched off branch-a (PR #1) you merge pr #1 into main. github rewrites it as one brand-new commit. but your live and “children” branches still carry the old copy of that work. *** compares the two and doesn't recognize them as the same thing. so you got that fake conflict thing on ***. the fix was the ugly manual rebase of every branch above. one by one. now github tracks the chain aka stacks on its server. and rebases the whole thing for you. all you do is pull, and you're back on track.

• 
  Adam Livingston (@AdamBLiv) reported 48 minutes ago

  Buying MSTR? Are you sure?!? Remember: NOT YOUR KEYS, NOT YOUR COINS. That’s why I burned my seed phrase onto a CD and vibe-coded a proprietary custody app that can only decrypt it on one specific Dell laptop running Ubuntu 14.7. The laptop has no Wi-Fi card and the battery is swollen. The decryption software depends on a GitHub repository maintained by a Serbian teenager whose last commit says “final fix probably”. My wife has been instructed that, upon my death, she must boot into the BIOS, disable Secure Boot, mount the optical drive manually, and enter a 63-character password hidden inside a 2017 Buffalo Wild Wings receipt. This is obviously much safer than regulated institutional custody. Because I own the keys. I have absolutely no ******* idea how to access them. But I own them.

• 
  Uncle J (@UncleJAI) reported 51 minutes ago

  @anurag_629 @github Team-specific review is useful only if the bot shows which skill or doc produced each comment. Without that receipt, a bad internal rule gets the authority of “Copilot found this” and nobody knows what to fix.

• 
  Kevin Aguesseau (@kevinags_design) reported 55 minutes ago

  The fix was a connection, not a cleverer prompt. MCP (Model Context Protocol) lets your AI tool read your other tools directly, no copy-paste. Works with Claude, GitHub Copilot, Cursor or whatever you use. Mine runs in VS Code.

• 
  🌕 (@motorcyclone) reported 58 minutes ago

  The thing is: if you're not used to using github, it is okay to be confused. But then the next step is to look at the website and just read whats on the page. still not sure, there are many resources online to help you. The issue is that people are not reading what's on the page

• 
  Mephistopheles (@mikergmoj96151) reported 59 minutes ago

  @AnimeSerbia the problem is that programmers insist on using github as the main hosting service for their **** and drive normalfags to github. it's a self-inflicted wound. jon blow is right, open source people literally don't understand human behaviour.

• 
  Jesse (@jessearmand) reported 59 minutes ago

  My workflow now: <quote> LLM neuralese speak load-bearing facts </quote> Good point, let’s unpack that further, what about… have you considered… <quote> LLM neuralese speak load-bearing facts </quote> Yes, we can change that <quote> LLM neuralese speak load-bearing facts </quote> Could you simplify these explanation? and create the reference to what you’ve seen in that files, context, etc. I’d need to explain this complicated topic across three different groups of people Working… <quote> LLM neuralese speak… All done and tested, run the app and server, here and there, and verify it’s all what you expected Want me to push to github? </quote>