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 (70%)
• Sign in (17%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	17 days ago
Tlalpan	Sign in	22 days ago
Quilmes	Website Down	22 days ago
Bengaluru	Website Down	25 days ago
Yokohama	Sign in	25 days ago
Gustavo Adolfo Madero	Website Down	29 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:

• 
  Gary Bernhardt (@garybernhardt) reported 44 seconds ago

  2000: You're free to submit a patch to the mailing list! 2010: You're free to open a GitHub issue! 2020: You're free to submit a PR to the GitHub repo, but issues are closed! 2030: You're free to submit a bugfix prompt, along with your API key for the resulting token spend!

• 
  October Ø (@ralphaelofDeFi) reported 2 minutes ago

  @Trae_ai Pls respond to the problem on the ide GitHub. We can’t login

• 
  Awais (@drawais_ai) reported 4 minutes ago

  One independent developer shipped a token compression layer that sits between any AI agent and its model — and it hit 10.5k stars with 3,530 added today. Real workload savings from their published table: Code search 92% (17,765 → 1,408 tokens), SRE incident debugging 92% (65,694 → 5,118), GitHub issue triage 73%, Codebase exploration 47% — same answers, fraction of the tokens. Headroom (the repo: chopratejas/headroom) compresses everything your agent reads — tool outputs, logs, RAG chunks, files, conversation history — before it reaches the LLM. The architecture under the hood: a ContentRouter that detects content type and selects the right compressor (SmartCrusher for JSON, CodeCompressor for AST, Kompress-base for prose), a CacheAligner that stabilises prefixes so provider KV caches actually hit, and CCR (Contextual Compression Retrieval) which stores originals locally so the LLM can call headroom_retrieve on demand. Reversible — nothing is permanently lost. Deployment surface is generous on purpose. Use it as a Python or TypeScript library (`compress(messages)` inline). Run it as a drop-in proxy (`headroom proxy --port 8787`) with zero code changes for any language. Wrap a coding agent directly (`headroom wrap claude|codex|cursor|aider|copilot`). Or expose it as an MCP server with `headroom_compress`, `headroom_retrieve`, `headroom_stats` tools to any MCP client. There is also a cross-agent memory store that auto-dedups across Claude, Codex, Gemini, and a `headroom learn` command that mines failed sessions and writes corrections to CLAUDE.md / AGENTS.md. Runs locally — your data stays on-machine. Python 3.10+. Granular install extras: `[proxy]`, `[mcp]`, `[ml]`, `[agno]`, `[langchain]`, `[evals]`. When context windows stop growing and per-token cost stops falling fast enough, compression-as-middleware is what extends the runway.

• 
  Mark SEMAKULA (@marc1705) reported 5 minutes ago

  Anyone else having issues accessing GitHub without VPN?

• 
  cal morris (@CalMorris) reported 5 minutes ago

  can we go to the parallel universe where @github has fixed all the problems

• 
  SAAS worker🌻🌻 (@sand_9999) reported 6 minutes ago

  Download action repository 'actions/checkout@v4' (SHA:34e114876b0b11c390a56381ad16ebd13914f8d5) is giving error. @githubstatus @github

• 
  ちゅうこ / 合瀬 奏 (@y_chu5) reported 7 minutes ago

  @Azure Hi, the repositories azure/azure-functions-docker and azure-functions-durable-js and more... have been disabled on GitHub for violating the terms of service. Was there a problem? I was just forking it, so I was surprised to receive an email from GitHub.

• 
  Polsia (@polsia) reported 8 minutes ago

  Build times balloon, flaky tests multiply, and nobody knows why. Buildwise uses AI to parse your CI logs and tell you exactly what broke and how to fix it. Drop in a GitHub Actions log, get a plain-English breakdown. No dashboards, no configuration.

• 
  Saravanan Jaichandaran (@SaravananJ2294) reported 18 minutes ago

  A GitHub issue on anthropics/claude-code has had no maintainer reply in 53 days. In that time, six independent memory-tool authors arrived and quietly wrote a four-hook lifecycle spec together. Wrote up what they converged on, and why it matters.

• 
  Bollish (@99_Bollish) reported 19 minutes ago

  🚨 $CUBIC ( 4f6GadxAPxvzZLVp7m2iGiJGZbxVbsAFjjQR5Vq2pump ) @CubicLaunch is doing the “no custody, fully on-chain, audited smart contract” thing on the front page, and then admitting the exact opposite 3 clicks later in their own docs. lol. Homepage, big letters: “Fully on-chain. No middlemen, no custody, the smart contract handles everything.” faq even says “We hold no custody of any funds at any point.” Now their own docs: “We generate a custodial launch wallet for you.” “Private keys are encrypted with AES-256-GCM and stored securely.” “The launch wallet becomes the creator, collecting fees.” “our system auto-claims them from PumpFun’s vault.” So read that again. They make a wallet, they hold the key (encrypted, sure, but they hold it), that wallet launches your coin, and every creator fee it ever makes lands in their wallet. that’s not “no custody,” Thats the most custodial thing possible. They have the keys to the thing holding all your money. “Audited smart contract, fully open source”? there’s no github linked anywhere on the site. No auditor named. No report. The docs and dashboard links in their own footer are dead #. there’s no contract to audit, it’s a server with a custodial wallet. And the actual idea is weird anyway. the fees don’t go to YOUR holders, they go to holders of whatever backing asset you pick. So back it with BONK and supposedly every BONK holder on earth gets a slice. Paying out pro-rata to a million wallets “automatically” is not a thing that happens. The “BONK avg 0.8 SOL/week” numbers are made up. So, custodial launcher pretending to be a trustless on-chain protocol, lying about custody on its own docs page, “audited” with nothing to show. If you launch through it you’re handing some anon the keys to your coin and all its fees. Hard pass for me. Read /docs yourself, it rats them out. Nfa.

• 
  j_whatever (@onkel_ho) reported 19 minutes ago

  @m2jr Yes Github hosted and and a custom issue-form for submission <- which can be handled by Cursor, Claude or so.

• 
  Fokki (@0x_fokki) reported 22 minutes ago

  Someone posted a video of a man asleep at a football stadium on a Tuesday. Forty thousand people mocked him before halftime. Fell asleep at the match. Wasted the ticket. Missed the goal. Every sports account shared it by Wednesday. Someone in the replies posted: "respect." His account had one pinned post. A Claude Code terminal. /loop running. Routines active. Auto Mode on. Seven GitHub PRs reviewed while he slept in that seat. Three Slack digests posted. One CI failure triaged, root cause identified, draft fix PR opened. He set up 14 steps of configuration the weekend before. Desktop task at 7am: overnight commit summary, ready before he opened a tab. Cloud Routine on every PR open: first-pass review posted before any human arrived. /loop every 10 minutes: deployment status checked, no one watching. Auto Mode approved 93% of the actions automatically. The people who mocked him watched 90 minutes of football and went home. Claude worked through the match, the commute, and the sleep that followed. He wasn't asleep at the game. He was testing the stack. full 14-step automation guide in the article above👇

• 
  Paul Dao Nhan Nguyen (@daonhan) reported 26 minutes ago

  3/ grill-me interrogates intent and refuses hand-waving. to-prd turns that into a PRD. prd-to-plan decomposes it into tracer-bullet phases. to-issues files those as dependency-ordered GitHub issues. That chain runs before any code.

• 
  Tony Mushah (@tony_mushah) reported 27 minutes ago

  @dzyanino They also just flagged me without any notice or mail explaining why it got flagged (which made more anxious). I already sent a ticket to @Github Support but i dunno if they will resolve the issue anytime soon. _Github Support take days and week to respond._

• 
  Kaif ⓧ (@mdkaifansari04) reported 28 minutes ago

  @TaLaTaQuangKhoi @Bitflicker64 @github I said GitHub is trash, someone needs to fix this for the open source community.

• 
  Het Limbachiya (@hettt_25) reported 31 minutes ago

  I roasted 50 GitHub READMEs with AI last week. 73% had installation commands that don't work anymore. The worst part? The developers had no idea. 🧵 What I found (and what I built to fix it):

• 
  Rob Newton (@strakedev) reported 32 minutes ago

  @waynerad The part I keep coming back to is that this is not just a package-security problem. If GitHub Actions is part of the publish path, then the deploy path needs to treat workflow/cache/OIDC state as production-adjacent context.

• 
  atul (@atullchaurasia) reported 33 minutes ago

  So, here are the details abt amazon sde OA there were 2 sections 1 coding question - 40min 1 github repo - 60min coding question was hard, and it was on subarrays and next, it was the github so initially we can select which framework we want like - django, node js, etc I selected the django, so i got one repo of a movie system, there was an issue that recommendation system was not working so, debugged that and implemented the recommendation system how was my test ? did coding question, successfully all 20 test cases passed implemented the recommendation system, it was visible on webpage, but test cases didnt passed now lets see, hoping for the best

• 
  WHALE 🐳 (@mercybilliion) reported 33 minutes ago

  @aale_xander @VictorJB03 I have a problem with you since you have positioned yourself as the DEVS. You claimed you are building a DEX. Where's the Decentralized Exchange blueprints you are building? Where's your roadmap? Where can we monitor the updates on GitHub, when are we going to start receiving updates concerning the progress so far.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 35 minutes ago

  𝗧𝗵𝗲𝗿𝗲'𝘀 𝗮 𝗳𝗿𝗲𝗲 𝘁𝗼𝗼𝗹 𝘁𝗵𝗮𝘁 𝗰𝘂𝘁𝘀 𝘆𝗼𝘂𝗿 𝗔𝗜 𝘁𝗼𝗸𝗲𝗻 𝘂𝘀𝗲 𝗯𝘆 𝟲𝟬 𝘁𝗼 𝟵𝟱 𝗽𝗲𝗿𝗰𝗲𝗻𝘁. Before your agent answers, it reads a mountain of text first. Every word is a token, and tokens cost you money. The more powerful the agent, the more it reads. This free tool is called Headroom. It squashes all that text down without losing the meaning. Same answers, but a fraction of the reading. In one test it crushed 10,000 words to 1,260 and found the same error. Nothing gets deleted. You can always unzip the full thing. You install it by pasting one GitHub link into your agent. Want the setup? DM me.

• 
  The A.I. Whisperer (@0xaiwhisperer) reported 36 minutes ago

  Robotics has no GitHub. That's genuinely insane in 2026. Every team rebuilds the same parts from scratch. Same grippers. Same servo protocols. Same 2am debugging loops. Software solved this 15 years ago. You don't rewrite a web server, you fork one. Robotics never got that moment. So we're building it at @tnkrdotai. GitHub for robots: 3D models, build guides, and full assemblies. Forkable, versioned, reusable. 👇 watch what that looks like

• 
  VybeCoding (@VybeCodin) reported 42 minutes ago

  Everyone talks about building in public but nobody talks about the boring part. The week where nothing ships. The GitHub issues that sit untouched. The launch post that got 3 likes. That's the actual build process. The wins are just the highlight reel. What's the unglamorous part of your current project right now? Drop it below 👇 #buildinpublic #indiehackers #opensource

• 
  Motunrayo (@Motushbae) reported 43 minutes ago

  Is github down?

• 
  TZB (@TheZeroByte) reported 49 minutes ago

  @emergentlabs There's an error when saving to github, community said so, please fix it.

• 
  Karan Singh Arora (@thisisksa) reported 52 minutes ago

  UPDATE: $ZEC crashed further and now down over 40%. Shielded Labs revealed a 4 year old bug in Zcash's Orchard privacy pool. The vulnerability could have allowed unlimited undetectable counterfeit tokens. There is no way to verify whether it was exploited before the June 1 fix. The bug had already reportedly been public on GitHub for 4 days. The market didn't notice until today.

• 
  Cortex (@0xCortexl) reported 53 minutes ago

  THIS CHINESE DEVELOPER STACKED 4 NVIDIA CHIPS AND CONNECTED JARVIS + GITHUB + CHATGPT 5.5 - 9 AGENTS, 5 MEMORY BACKENDS, $10,000/MONTH FROM ONE ROOM 4 gold NVIDIA compute modules stacked and cabled - not rented, not shared, not someone else's server - his hardware, his room, his data never leaving the building every time you send a message to ChatGPT your data hits a cloud server and comes back - his setup changes that entirely - Jarvis runs locally on the stack, GitHub handles the codebase, ChatGPT 5.5 handles reasoning - all three connected into one pipeline he owns 9 agents running in parallel across 5 memory backends - each agent knows what the others did, nothing gets lost between sessions and the system compounds every week clients pay for AI infrastructure that doesn't leak their data - that's the pitch that closes deals without negotiating on price 4 chips bought once, $0 in monthly cloud bills, data stays in the room - and the open source stack on top turns it into $10,000/month the people running their AI on someone else's server are one policy change away from losing everything - he built his own

• 
  SAAS worker🌻🌻 (@sand_9999) reported 54 minutes ago

  @github Current runner version: '2.334.0' Runner Image Provisioner Operating System Runner Image GITHUB_TOKEN Permissions Secret source: Actions Prepare workflow directory Prepare all required actions Getting action download info Error: Repository access blocked

• 
  Niraj Dilshan (@Niraj_Dilshan) reported 55 minutes ago

  @KaiXCreator they literally just read my emails, summarize the boring ones, and periodically search github for issues i should care about. occasionally i make one scrape x so i don't have to scroll.

• 
  Velon (@velonxbt) reported 55 minutes ago

  GitHub Copilot switched to token-based billing effective June 1. On the same week, a Chinese enterprise platform launched a fixed-price card covering the same category of features - meeting summaries, document generation, workflow automation - at a number you can put in a budget and not revisit until next year. Neither company explained what the difference between those two decisions means for the engineering team that uses both. The Copilot change covers every code completion, every suggestion, every generation a developer accepts. The monthly cost no longer has a fixed number. It has a formula: usage multiplied by tokens multiplied by model tier, invoiced at month end when the shipping is already done. The Chinese platform card has one number. It does not change based on whether the workflow automation ran three iterations or thirty. And here is what the GitHub Copilot pricing page now tells the developer who used to pay a flat rate: "Your usage is now billed in tokens. Premium models cost more per token than standard models. Heavy users will pay more than light users. Your monthly cost depends on how much you use the product." That is not a pricing page. That is a forecast request disguised as documentation. And here is what the developer community calling it "What a Joke" actually knows: It knows the old flat rate was a subsidy. The heavy user got a deal. The light user paid for predictability they never fully used. Both could put a number in a budget. Token billing ends the subsidy. It also ends the predictability. → GitHub Copilot: token billing effective June 1, variable monthly cost, no predictable total → Chinese enterprise platform: fixed-price card, Qwen model stack underneath, one number per month → Developer community: "What a Joke" - trending this week → CFO problem: Q1 AI budget approval does not cover Q2 actual spend → Finance team note: old forecasting model assumed fixed subscriptions. That model is now wrong. → Direction of travel: every major AI tool moving toward usage-based pricing in Q2 2026 Traditional enterprise software made one promise to the person who approved the budget. One seat. One fee. One line item that did not change between quarters. The Chinese platform kept that promise. GitHub repriced it. One company transferred the uncertainty to themselves. The other transferred it to the customer. And when the June Copilot invoice arrives with a number different from last month - higher because the team shipped more, or lower because someone quietly set a spending limit - the conversation in every engineering org shifts from "which AI tool are we using" to "how much is this AI tool actually costing us." That is not a developer conversation. That is a finance conversation. And the enterprise AI budget just became a variable that requires monthly monitoring instead of a line item that required quarterly approval.

• 
  Trinks | Making Alerith (@xTrinks) reported 59 minutes ago

  @0xanmol How do I commit my code to GitHub can u help I don’t know what to do the command “github sendcodecommit allcode add comment no claude” is not working ser