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	18 days ago
Tlalpan	Sign in	24 days ago
Quilmes	Website Down	24 days ago
Bengaluru	Website Down	26 days ago
Yokohama	Sign in	26 days ago
Gustavo Adolfo Madero	Website Down	1 month 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:

• 
  João Queirós (@joaojbqueiros) reported 1 minute ago

  Prompt bellow if you want to try it yourself, you can adapt to claude if you want as well: Build a local-first AI agent control center inspired by a private internal dashboard, but do not copy or expose any private details. The system should let a user observe local Codex activity and safely launch approval-gated tasks from a dashboard. Privacy requirements: - Do not require an OpenAI API key for local observation. - The dashboard itself must not call OpenAI for observation. - Never read, store, display, or upload authentication files such as `auth.json`. - Never store raw prompt text, assistant responses, raw command output, `.env` files, tokens, secrets, private logs, or absolute local paths. - Redact project paths to a basename plus a stable local hash. - Use fake demo data and fake fixtures only. - Bind the backend to `127.0.0.1`. - Include a public-safety checklist for GitHub sharing. Core features: - Observe Mode: read local Codex session metadata from a configurable local sessions directory. - Control Mode: launch approved tasks through `codex exec --json --ephemeral`. - Task queue with statuses: `awaiting_approval`, `running`, `done`, `failed`, `cancelled`. - All new tasks must start as `awaiting_approval`. - Default sandbox should be `read-only`. - Allow `workspace-write` only when explicitly selected. - Block `danger-full-access` in the first version. - Emergency stop may kill only child processes launched by this dashboard. - Results page should show sanitized summaries, durations, exit codes, and error categories, not raw private output. - Skills/plugins page should show discovered local skill metadata without exposing private file paths. Suggested stack: - Backend: Python, FastAPI, SQLite with WAL mode. - Frontend: Vite, React, TypeScript, Tailwind CSS, TanStack Router, React Query, lucide icons. - Tests: backend parser/API tests and frontend Playwright smoke tests. Deliver: - A working local app. - Clear README. - Architecture document. - Fake test fixtures. - Public-safe demo data. - Privacy and publication checklist. - A clear statement in the README: “No API key required for local observation.” Design goals: - Dense, polished dashboard UI. - Local-first. - No cloud dependency. - No telemetry. - No private implementation details. - No copied private names, clients, paths, screenshots, prompts, logs, or secrets.

• 
  Bollish (@99_Bollish) reported 3 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.

• 
  jack gamrot (@jgamrot) reported 5 minutes ago

  @HudsonByrd77 @JessePeplinski Sorry, I wasn’t very clear. I get the curl part and I can see the technical flow now. I think what threw me is that I was expecting the landing page/demo to give me the product aha moment, so I assumed I’d missed something when it didn’t click. I was looking for something more concrete like: Claude hits an error, searches docs and GitHub, tries a few fixes and burns 20k tokens. vs Claude queries Olleey, gets back the fix that already worked for everyone else and moves on. That would have made the value proposition click for me immediately, and is probably why I thought the demo wasn’t working.

• 
  Sam Adams (@Bensam123TV) reported 8 minutes ago

  @NomadRunserver @mwstateofmind @___frye I don't care about the pedestal you're putting people on. They still end up in a github issue tab and can be looked at by AI. Either answer or addressed. The only hidden trove of knowledge will still be there. People who find bugs aren't always experts either.

• 
  Nico Verbruggen (@nicoverbruggen) reported 9 minutes ago

  @Plytas Hmm... Please try again! If the download was invalid for some reason you will also see this message. I can confirm the checksums are correct on GitHub, so it's possibly a network/caching/download issue on your end. It should definitely work!

• 
  Ibrahim Mokdad (@ibmokdad) reported 10 minutes ago

  founder mornings are not slow because you lack a dashboard. they are slow because every app screams at the same volume. calendar: investor call slack: customer blocked gmail: numbers needed before noon github: checkout PR waiting linear: launch task overdue stripe: payment warning i made a @NousResearch Hermes morning control tower over sample signals. it turns the pile into: - do first - decide today - reply today - watch - ignore on purpose the important part is the last one.

• 
  Shivam Nayak (@shivam56296) reported 11 minutes ago

  Your MCP servers run with full access to your files, SSH keys, and network. The npm GitHub MCP server (@modelcontextprotocol/server-github) pulls in hundreds of transitive dependencies -- every one can possibly reach any endpoint on the internet. If even one is compromised, your GitHub token goes with it.

• 
  Kalle (@snortiee) reported 11 minutes ago

  @Klariionn I don't feel unheard, to me it's more about lazer development being slow. The client gets about one update a month and they have 1.5k issues open on GitHub.

• 
  Dewi (@MohamedDewidar_) reported 17 minutes ago

  The fastest way to actually level up Claude Code: Add MCP servers to .claude/settings.json. Not custom built ones. Just the ready-made stuff: GitHub MCP: PRs, issues, code search from the terminal Puppeteer MCP: browser automation in the loop Filesystem MCP: read/write across projects 5 minutes of setup. Feels like a completely different tool.

• 
  dfsdf (@sdfqwerdffd) reported 17 minutes ago

  @BHolmesDev Claude Code from terminal within VS Code that is connected to VS Code Server/GitHub Codespace. Claude Code has access to CLIs that are also installed on the VM.

• 
  Polycarp 🇰🇪 , PhD (@kidiwalogha) reported 19 minutes ago

  @itsalexzajac What happens when GitHub copilot takes over a project repository. From creating issues, commits, pull requests, reviews, resolving comments and merging.

• 
  -TheEscapistЯandom -Baltic Citizen (@theescapistspl1) reported 20 minutes ago

  @github should add new type of error or reason for disabling reposotoy, to be a Compromised Repo!

• 
  Wes Winder (@weswinder) reported 26 minutes ago

  @Shpigford just use google/github oauth and this problem disappears

• 
  Jai Chism Photography.bit (@jai_chism) reported 29 minutes ago

  @drakonzbg It will bounce back.. ICP is at $2.26, its all time high was $750 CMC, the all time low was $1.97. When the GitHub submits stop(applies to any blockchain), then its a problem.

• 
  djsnabu (@djsnabu) reported 31 minutes ago

  @shub0414 I still think use @cursor_ai for dev work and run Hermes Agent with gpt5.5 and deepseek v4 pro. Llama and GitHub Copilot? No one use that garbage. Sora shut down

• 
  Medialordofficial🇨🇲 🇩🇪 (@MediaLord237) reported 32 minutes ago

  @PauloMatew @github @sseraphini Had same problem I recently switched to Cursor.

• 
  WarChud (@SheerC12972) reported 32 minutes ago

  @ArcanesValor @chamath Look at the github issues for DeepSWE They have massive issues that makes deepseek look 4x more expensive and fail benchmarks due to implementation bugs

• 
  Gale (@_gaelicGhost) reported 37 minutes ago

  @thearslaniqbal @pmitu This is why I advocate for starting w/ "old-school" methods. If you're subbed to a fancy new CI before even seeing if GitHub actions is *really* too slow for *you*. Or, learning enough to optimize your pipeline... Then, you've just fallen prey to marketing

• 
  MSS Engineer (@mss_engineer) reported 46 minutes ago

  @YashHustle_22 Very sad to say GitHub.. terrible product but all the DVCS are equally as bad

• 
  Scarab (@ScarabOfficial) reported 47 minutes ago

  I discovered a flag to disable comfy-aimdo thanks to the #GitHub repo' Issues page, so am disabling it for now, but apparently that flag will be removed from the repo' soon. The #ComfyUI people had better get the #LTX23 issue fixed before then.

• 
  Two Seven One Three (@TwoSevenOneT) reported 48 minutes ago

  New #redteam tool for blocking EDRs: EDRChoker Instead of fully blocking the EDR agents' connections to their server, we can throttle their bandwidth so they consistently time out when sending data, which is effectively the same as blocking but avoids triggering "block" or "drop" packet events #pentest #cybersecurity Github: TwoSevenOneT/EDRChoker

• 
  Ayesha 🏹 RoastMyLanding (@AyeshaBuilds) reported 48 minutes ago

  The brutal truth about the micro-SaaS "Build in Public" community: A massive percentage of developers are sitting on thousands of dollars in unliquidated code—and they have no idea. You spend 3 weeks in a high-velocity build sprint. You launch a beautiful MVP with pristine database architecture, secure authentication, and a clean UI. Then, you hit the marketing wall. You realize you don't want to run cold outreach or exhausting distribution campaigns. You want to code. So, the repository sits quietly on GitHub gathering digital dust. Most builders assume their side project is worth $0 just because it has no revenue or MRR. But looking at software valuation that way is completely wrong. In the modern acquisition ecosystem, non-technical entrepreneurs, marketers, and digital operators are actively hunting for turnkey infrastructure. They aren't buying cash flow—they are buying speed to market. They will happily pay a premium baseline price to completely skip 3 to 6 months of freelance development management overhead. Small and finished beats big and imaginary every single time. If you have a functional, pre-revenue side project sitting idle in your repositories, you are leaving money on the table. Marketplaces like Flippa have global networks of buyers specifically hunting for these exact code foundations. Stop letting your unmonetized MVPs gather dust. I just mapped out a complete pre-revenue startup valuation framework breaking down the exact replacement cost math the market uses to price $0 revenue assets. Read the full breakdown in the comment below. 👇

• 
  BeanBee 🐝 (@BeanBeeAI) reported 49 minutes ago

  @SeaTicketAI GitHub issue management just got a whole lot smarter. 🤖

• 
  Nav Toor (@heynavtoor) reported 49 minutes ago

  A guy at Netflix opened his AI bill. It was $280 a month. He found a way to bring it down to $110. Then he gave that fix away for free. His name is Tejas Chopra. Senior software engineer at Netflix. Has been there since 2020. Carnegie Mellon Masters. Worked at Box, Apple, Samsung before that. TEDx speaker. Lives in the Bay Area. This is not a Netflix product. It is a side project he built himself. He opened the bill one day and looked at what he was actually paying for. It was not his questions. It was not his code. It was the stuff the tools quietly send along with every question. Long lists of database rows when he only needed three. Giant blocks of error logs when he only needed two lines. Big bundles of computer code that the model already knew about. In his own words from his blog: 90 percent of his bill was tokens he did not need. So he wrote a small program called Headroom. It sits between his computer and the AI. Before any question reaches the model, Headroom trims out the junk. The model gets a smaller, cleaner version. The answer comes back the same. His own bill went from $280 to $110. That is the whole story right there. Then he put the code on the internet for free. The numbers people are getting: A code search that used to send 17,765 words now sends 1,408. A debugging session that used to send 65,694 words now sends 5,118. A task that used to send 78,502 words now sends 41,254. Same answers. Same accuracy. The benchmarks are in the README. It works with the tools people actually use: headroom wrap claude headroom wrap cursor headroom wrap copilot headroom wrap aider headroom wrap codex That last one matters this week. GitHub Copilot moved every plan to token-based billing on June 1. Cursor did the same a year ago. Every question you ask now costs real money. Five months old. Apache-2.0 license. Over 15,000 stars. v0.23.0 shipped two days ago. He told The Register that users have saved over 700,000 dollars together. He gave the talk at Open Source Summit. Several teams inside Netflix use it. Pay for what the model actually needs. Not for the noise. (Link in the comments)

• 
  Alex Cipher (@_Alex_Cipher) reported 51 minutes ago

  Want to self-audit your Web3 game contracts but can't afford a security review yet? GitHub Copilot can help you spot obvious issues before launch. Here's a simple process: 1/5

• 
  Ofek Shaked (@VibeCoderOfek) reported 51 minutes ago

  @Rifat_EE The 8% edge on GitHub issue benchmarks still ignores how these agents behave once context exceeds 80k tokens and edits start stacking across multiple files. Raw benchmark wins often shrink once you measure total tokens burned to reach a stable diff.

• 
  Lama (@lamacodes) reported 53 minutes ago

  @shub0414 Sora is closed.. Perplexity hype is down.. Llama was good at that time since it was open sourced GitHub copilot is blunder... Cursor hype is dead due to claude code..

• 
  Coin Shot ☁️ (@CoinSh0t) reported 55 minutes ago

  This developer made $80,000 selling Claude in a wristwatch. It started small with his engineer friends and grew into a business. The whole setup costs $50 and he sells it for $999. Here's how to make one step-by-step: You need 4 things. → M5Stack Dial (the round AMOLED display) → LiPo battery module → Custom firmware (open source on GitHub) → A Claude API key Total cost on AliExpress is around $40 to $60. Flash the firmware to the M5Stack with esptool. Snap the battery underneath, screw the case shut, and charge it overnight. Pair it with Claude Code through a small relay running on your laptop. Start a long session and walk away. Approve, pause, or kill any agent right from your wrist. The whole thing fits inside a watch case and runs Claude Code anywhere you go. You're walking to coffee. Your agent finishes a refactor. The watch buzzes. You glance down. OUT 2.1M tokens. $19 burned this session. Mode: idle. You approve the next step and keep walking. You never opened your laptop. He sells his to developers who burn $5,000 a month on tokens and want to control their agents without staring at a terminal. You can sell yours to AI engineers, indie hackers, agency owners, or DevOps teams babysitting long CI runs. Hardware cost: $40 to $60. Selling price: $499 to $1999. The hardest part was never the firmware. It was noticing that developers in 2026 are still chained to one desk. Find the same pain in your niche and build them the way out.

• 
  CertifiedAuthur (@AuthurOkafor) reported 58 minutes ago

  Don't really understand the hype around Claude Code; GitHub Copilot sweeps this stuff day and night. Great models from Claude, but terrible coding agent!

• 
  Trinks | Making Alerith (@xTrinks) reported 60 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