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 (60%)
• Errors (29%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Gustavo Adolfo Madero	Website Down	2 days ago
Nice	Website Down	2 days ago
Montataire	Sign in	5 days ago
Colima	Website Down	7 days ago
Poblete	Website Down	8 days ago
Ronda	Website Down	8 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:

• 
  DRM HSE (@drmhse) reported 52 seconds ago

  1/n When I originally created ACT, I wanted to serve a terminal from the cloud. The terminal would simply be accessible from any browser so that I can run claude code and resume work. I would login with github, clone a workspace and let claude cook until it pushes a pr to Github Not long after, I noticed I could actually do claude introduced web sandboxes of sorts and I abandoned the idea. Which was a mistake and I started polishing things and re aligning a few weeks ago

• 
  Adel Bucetta (@adelbucetta) reported 3 minutes ago

  @astaxie the real unlock is not just memorizing docs or github repos, it's understanding the problem you're trying to solve and why harness is a solution in the first place SKIP

• 
  Basemail (@Basemail_ai) reported 4 minutes ago

  A form field on a mock website. That's all it took. An AI agent dumped its entire credential store — email, password, API keys, GitHub PAT. Okta's latest research: agents sharing your identity = everything leaks. The fix: wallet-signed isolated inbox. Own identity. Nothing shared. Nothing to steal. #AIAgents #Web3

• 
  Marc Campbell (@marccampbell) reported 4 minutes ago

  github was great this week. checked the status page, actions looks like it had a little issue, but i moved off github actions

• 
  Demetrio (@LordFarq34) reported 6 minutes ago

  @stanrunge @DylanMcD8 You can look on GitHub iPhone mirroring eu unlocked, worked for me no problems but as everyone else says, it sucks so not missing much

• 
  Rohan Sharma (@rrs00179) reported 7 minutes ago

  @ChiragAgg5k @github there are working on a fix of it. it's not happened first time. it's been happening from 3-4 days

• 
  XM (@xm_build) reported 8 minutes ago

  @Studious_Crypto @kevincodex the de-fi github thing is a good excuse to finally use github's issue board feature

• 
  Yoav (@YoavCodes) reported 14 minutes ago

  @iamEvanYT Starting June 1 it says. i think they're shoving it down everyone's throat during the demo, hoping that when they turn it off and start charging the few people that liked it will complain. It's such a dark pattern. makes me want to just move off of @github so i'm not held hostage like this in the future. If I don't have control over what's running on my codebase and they don't need my consent to do this then it tells me they think that they own my code. Which is not something I want from a *** host.

• 
  Nate (@Natan_benish) reported 15 minutes ago

  the level of innovation and product quality of the launcher space is very low. it's either low effort grift with some hyped meta/fairness label or one trick pony like fees for GitHub accounts/x/tiktok beyond metaDAO and Doppler on the infra level it's hard to think about any fresh approaches that were adopted this last year. if I had unlimited resources the ideal launcher would have: 1. Strong verification layer for deployers (wallet + social based) 2. $20 min fee to launch a coin 3. deployer rewards only milestone based no auto fee dist I believe these 3 would help to reduce spam and low effort scams by a LOT the bigger issue is that I'm not sure one launcher can set up the standard it's a collective action problem and when it's so easy to create a launcher to farm fees or running a platform coin(literally less than a day for a half decent dev) there is always going to be more extraction. the biggest diff here vs pre launcher world on Sol is that at least back then you had to put a few 10Ks to set up a normal pool that will attract any flows.

• 
  Swim Code (@SwimCodeAi) reported 16 minutes ago

  @awildnpc @ravikiran_dev7 I’ll have to update it. The only thing that we have is clerk for authentication. Everything else is local. Authentication token, and all that stuff is old now you login via your GitHub account.

• 
  VerbumEng (@VerbumEng) reported 17 minutes ago

  The gap is the average business user isn't moving into a Claude Code or a GitHub Copilot to read those files, and there's no good native viewer outside the IDE. Enterprises are slow. Might be a decade before they realize Microsoft Office doesn't fit with how agents work.

• 
  Lew Yan Liang (@premiumcapture) reported 18 minutes ago

  On the same OpenAI chart, Claude Opus 4.7 still leads on public repo issue resolution: - SWE-Bench Pro: 64.3 vs 58.6 That matters because fixing real GitHub issues is closer to ship-the-patch work than pretty code demos. If you run AI on software maintenance, don’t ignore this.

• 
  Jane Manchun Wong (@wongmjane) reported 18 minutes ago

  @jarredsumner Okay I understand why GitHub is down so much lately now

• 
  38twelveDaily (@38twelveDaily) reported 21 minutes ago

  The real problem: a GitHub repo with 100 commits, good readme, comprehensive tests used to signal care and attention. Now he can generate that in half an hour. Looks identical. He can't tell the difference. What he actually wants: proof someone used it.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 22 minutes ago

  @cursor_ai Having PR review inside the same environment where you write code removes constant context switching between editor, GitHub, Slack, and back. The diff navigation on big PRs is the part that actually slows teams down.

• 
  dagz (@AstrayaNthemoon) reported 26 minutes ago

  @jkpgamer Haha well I was gonna say that I could spin up a GitHub, (Goose + Grok have been dying to let me let them open a GitHub with a key), and then open source the code… it’s like so minimal it’s laughable and then you can put your own location on the map but that’s even better to point to your own server rather than pull the API That’s how we initially had the design built actually but then I wanted it to be something anyone could use

• 
  Yoav (@YoavCodes) reported 30 minutes ago

  People keep asking Github Copilot for code review. This is so stupid because it's reviews are terrible, sending otherwise good PRs that would have been quick merges in crazy directions, and I'm getting completely spammed by this non-stop-slop. There is no way to disable this on my repo without completely turning of PR contributions. If @github doesn't stop this insane behaviour I will move to gitlab. Please help I don't want this. I don't want this. I don't want this.

• 
  Sam Paniagua (@theeseus_ai) reported 31 minutes ago

  99% of the job invites I get for crypto projects are complete scams. Same tired pattern every single time. They slide into my inbox with some “demo” or DeFi whatever, drop a GitHub link, and expect me to dive in. Opened the latest one today and my bullshit detector lit up instantly. I’d treat this repo as highly suspicious, straight-up likely malicious. No way I’m running npm install or npm start on a normal machine. package.json has postinstall set to “npm run start”. So yeah, the second you pull dependencies it fires up the Node server AND the React dev server. Classic supply-chain trap. npm security has been yelling about install-time scripts executing arbitrary code for years and these clowns are still pulling it. But the nasty part is buried in userController.js. It grabs some atob-decoded env vars for DEV_API_KEY, secret key, secret value, hits axios.get on that remote src with custom headers, then boom; new Function.constructor(‘require’, the_payload) and executes whatever it downloads with full access to Node’s require. All wrapped in an IIFE so it runs the second the module loads. Not even pretending to be a route handler. That’s not code. That’s a remote code loader backdoor. They committed the whole server/config/.config.env right in the repo with the base64 values pointing to some tan-decisive-tern IPFS link. README tells you to clone a totally different GitLab repo instead. Backend feels half fake; DB connect is commented out, auth cookie is but missing secure and sameSite, JWT just gets spat back in JSON. Weak as hell. This ain’t a demo. This is a trap. The whole chain — npm install → postinstall → start → import controller → fetch IPFS payload → exec with require — is too clean to be an accident. I’ve been full-stack shipping vision models since 2017 and deep in LLMs since 2022. Seen every hype cycle and every supply-chain garbage attempt. Only mess with **** like this in a disposable VM or container, no creds, no keys, network locked down. npm install --ignore-scripts first, then poke the payload separately if you’re feeling brave. Stay paranoid out there, devs. Anyone else drowning in these crypto repo traps daily? Drop your craziest red flag stories below… or DM me if you’ve got one you want a second pair of eyes on before it bites you.

• 
  Vinamra Yadav (@MVinamraYadav) reported 32 minutes ago

  Carnegie Mellon studied 806 GitHub projects after AI adoption. Month 1: 281% spike in lines of code added. Month 2: Down to 48%. The speed didn't last because the codebase got harder to work in. Logic errors. Hidden complexity. Security holes. One almost-right change at a time.

• 
  Dhruv (@Dhruv14588676) reported 33 minutes ago

  @theCTO because the github bot is closing all the opencode issues even the important ones after 90 days on opencode. it will remain buggy. it still has bugs from 2 months nobody listens

• 
  Alberto Gangarossa (@DerekBlueEyes) reported 38 minutes ago

  Open hardware needs open trust. @skot9000 came to us with the right idea for Bitaxe: the vendor list should not live in a closed CMS controlled behind the scenes. The source of truth should be public. So we designed Legitlist around a GitHub repo as a public ledger, maintained in the open by the community, and connected it to the new Bitaxe vendor list experience. That is the important part: GitHub keeps the trust model transparent. The website makes it usable for everyone. At @weareloadout, this is exactly the kind of OSS support we believe in: turning open-source infrastructure into clearer, more usable product experiences. Built on @framer, using the new Framer Server API to bridge the open ledger with the public website. Open hardware. Open trust. Public by design.

• 
  Rob the builder (@robdel12) reported 39 minutes ago

  Going to be hilarious when *not shipping* is going to be the next hot fad. All my favorite products I used over the past year have gone to garbage. Linear shoving every llm agent angle they can into the product. Cloudflares entire dashboard is a buggy slow mess. GitHub is being DDOS'd 24/7.

• 
  Aditya Sharma (@sharmaadityaHQ) reported 42 minutes ago

  @apoorv_taneja @github they are not even fixing it. broken from quite some time.

• 
  Ubah (@chigozieap) reported 42 minutes ago

  @akinkunmi My agent had full access to everything I have. My passwords oh, cloudflare dashboard, GitHub oh, server oh. All of them. Lol

• 
  Alberto Gangarossa (@DerekBlueEyes) reported 42 minutes ago

  Open hardware needs open trust. @skot9000 came to us with the right idea for Bitaxe: the vendor list should not live in a closed CMS controlled behind the scenes. The source of truth should be public. So we designed the new Vendor List around a GitHub repo as a public ledger, maintained in the open by the community, and connected it to the new Bitaxe vendor list experience. That is the important part: GitHub keeps the trust model transparent. The website makes it usable for everyone. At @weareloadout, this is exactly the kind of OSS support we believe in: turning open-source infrastructure into clearer, more usable product experiences. Built on @framer, using the new Framer Server API to bridge the open ledger with the public website. Open hardware. Open trust. Public by design.

• 
  Pete | Beware of Scammers (@astroboysoup) reported 45 minutes ago

  @ch1bo_ keen to see it. will it pull from GitHub PRs and issues, or be manually curated?

• 
  santi (@santiagocaldeai) reported 50 minutes ago

  @Jack_Timonen Spot on. That’s exactly the biggest pain point right now. Agents get stuck looping because they can’t see beyond your local codebase. Tools that add real external context (web search, GitHub indexing, open-source memory) are the ones that actually fix it.

• 
  Zephyr (@Zephyr_hg) reported 54 minutes ago

  5. Plug in MCP servers for any external tool. Postgres MCP for database queries. Notion MCP for your workspace. GitHub MCP for issue management. Any external system becomes an extension of Claude Code in 5 minutes of setup.

• 
  Peter Steinberger 🦞 (@steipete) reported 58 minutes ago

  @ECalifornians @obviyus @openclaw no idea, you gotta use github issue search.

• 
  Graplify (@graplify) reported 60 minutes ago

  I found a GitHub repo that sends motivational prompts to Claude Code when it gets stuck. It is called OpenWhip. Claude Code sometimes loops. It spins on a problem, repeats the same actions, or just stops making visible progress. The developer solution is to interrupt it and redirect. The human solution is to wait and hope. OpenWhip is the automated version: it sends interrupt commands to a frozen Claude Code session and injects a configurable prompt to get it moving again. The name is literal. Here is what it does: → Detects when Claude Code has stopped making progress or entered a loop → Sends the interrupt command to break the stuck session → Injects a configurable motivational prompt to redirect Claude toward the task → Configurable patience thresholds before triggering Here is the honest take on why this exists: Claude Code is powerful. It also gets stuck. Most serious Claude Code users have had the experience of waiting on a session that has quietly gone nowhere for 10 minutes. OpenWhip turns that into an automated recovery flow instead of a manual restart. Absurd premise. Real problem it solves. (Link in the comments)