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 (20%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	3 days ago
Paris	Website Down	7 days ago
Saint-Paul	Website Down	8 days ago
Saint-Paul	Website Down	8 days ago
Mexico City	Sign in	8 days ago
León de los Aldama	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:

• 
  MadeItHappen (@MadeItHappenX) reported 3 seconds ago

  With GitHub App, ChatGPT app, and my project auto deployed, developing (vibe coding) from my phone is not that bad, especially when I’m testing on mobile anyway. I can screenshot and verbally prompt, approve the dev PR, review, PR to default branch, validate. Let my agents do the work and I’ll critique and bug fix on the go! ..or from my bed at 2am still thinking about my project. #vibecoding

• 
  J.D. Salbego (@JDSalbego) reported 41 seconds ago

  How to scope MCP permissions per agent, not globally. The isolation pattern most AI agent builders skip. Most setups: one set of MCP credentials shared across every agent in the workspace. Your research agent, your writing agent, and your deploy agent all have the same access to Gmail, GitHub, Slack, and your filesystem. If any one agent is compromised, the attacker inherits everything. The fix: per-agent credential isolation. 🔵 Each agent gets only the MCP servers it actually needs 🔵 Each MCP server connection uses credentials scoped to that agent's role 🔵 Your research agent gets read-only access. Your deploy agent gets write access. Neither sees the other's credentials. How to implement: 🔵 Create separate credential files per agent role 🔵 Mount only the relevant credentials into each agent's environment 🔵 Use different API keys per MCP server per agent where the server supports it The pattern: principle of least privilege, applied to AI agent MCP connections. One compromised agent should never cascade to everything.

• 
  🧠 (@quantum9854) reported 2 minutes ago

  @BeldexCoin @BeldexCoin Trying to download beldex-electron-wallet-7.0.2-win.exe from official GitHub release. Chrome + Windows Defender flag it as virus (VT shows AMADEY link on githubusercontent). Hash verified? False positive or issue with build?

• 
  Dr. Jose Silva 🪽🇧🇷 (@jseluisX) reported 3 minutes ago

  CyberTalks: 🤖📱Mobile OS The LineageOS is your ultimate playground if you want to rip out corporate bloatware and breathe new life into dying hardware. It is fully open-source, giving you total root potential and high customization. If you flash it clean without GApps, you completely cut the corporate tracking record. It is highly versatile and runs on almost any device you throw it at I prefer the GrapheneOS, which is a completely different beast built like a digital fortress. It is designed for maximum operational security and hardening against zero-day exploits. It locks down vulnerabilities by sandboxing every single app and disabling tracking networks at the baseline firmware level. It is the gold standard for high-risk targets, but the catch is you can only run it on Google Pixel hardware. If you want the GrapheneOS fortress, we are strictly targeting a Google Pixel (Pixel 6 or newer is ideal for long-term security patches). The hardware architecture of the Pixel allows GrapheneOS to re-lock the bootloader with custom keys, keeping the device secure.If you are targeting LineageOS, the hardware choice is much wider. A Motorola or a global Xiaomi device works perfectly because their bootloaders are easy to unlock, and they have massive developer community support on GitHub. So, picture this. You just spent the last hour flashing this clean, beautiful new operating system. You boot it up, everything feels fast, and you feel like a tech god. Then, you open your banking app to check your balance, and boom. Red screen of death. The app crashes or hits you with a "Security Violation: Device Modified" error. Here is exactly what is happening under the hood. The bank is running a silent check using Google's Play Integrity API. Think of it like a digital bouncer checking IDs. It looks at your phone and instantly spots that your bootloader is wide open and the factory operating system is gone. It flags you as a security risk and locks you out.But don't panic, we can outsmart the bouncer.If you chose the LineageOS route, we fight fire with fire using root access. First, you flash Magisk, which gives you administrative control over the entire system. Once Magisk is running, you download an open-source tool called Play Integrity Fix. This genius little module feeds the bouncer a fake, certified device fingerprint from an old, official phone. Finally, you flip on Magisk's DenyList feature to completely blind your banking app to the fact that the phone is even rooted. To the bank, you look like a standard, boring retail device. Now, if you went with GrapheneOS, the game is totally different because we do not use root at all. Rooting actually creates security holes, and Graphene hates that. Instead, you use their built-in Sandboxed Google Play Services. This tricks the banking app by letting Google's security code run, but it traps it inside a restricted digital cage. The app gets the official security handshake it wants, but it has zero permission to spy on the rest of your hardened OS. Most global banks just work out of the box this way. To bypass banking app security on a custom ROM, you must trick the Google Play Integrity API into thinking your device is locked and official. Banks use this API to check if your bootloader is unlocked or if the system is modified.On LineageOS, you achieve this by flashing Magisk to gain root access. Once rooted, you install an open-source module called Play Integrity Fix, which spoofs a certified device fingerprint. You then use Magisk's DenyList feature to hide the root status directly from your banking apps. On GrapheneOS, the approach is completely different because the system does not use root access. GrapheneOS includes a built-in feature called Sandboxed Google Play Services. This allows the official Google code to run inside a restricted sandbox without system privileges, which successfully passes basic Integrity checks for most global banking apps right out of the box. Happy Coding!

• 
  Outa (@CallMeOuta) reported 7 minutes ago

  @OverlyTrev Elon has a terrible reputation when it comes to open source, dumping the source code on github and not tracking changes is not open source

• 
  Ben Anthony (@benjamin_ACD) reported 10 minutes ago

  GitHub goes down at the most inconvenient times

• 
  Daes (@0xDaes) reported 15 minutes ago

  Are you sick of missing out on the next 100x runner because you weren't in the right group or you didn't have the right tools to snipe the next launch? If you're not part of any cabal and don't have the insider tools and trackers, there's still a way to front run all of them, and I've been doing it quite consistently For context I'm not active in a single Telegram group besides @ggdotxyz groups. I get everything scrolling on the gg feed and scrolling X, and when I find something good I turn it into an alpha call by tagging @ggmaxi_agent So here's here's the formula for finding 'Slow Cooks' onchain that eventually return 10x-100x bangers 1. Check new launches every day but don't top blast into new stuff you're not fully sure about. Get a small bag and come back to it when the hype dies down. You'll be able to evaluate if - the dev is still shipping (& not a larp) - the product and community metrics improving (+ revenue) If the answer is yes, you get an easy entry when no one is paying attention. 2. Don't just do surface level research: I've made that mistake and missed potential 100x-1000x plays. Try out the product (if live), read about the underlying protocol and mechanics. I also check for exisitng thesis posts on @ggdotxyz and on X. 3. Use an LLM for your DD: I use Claude Code with a skill I built that tries out the app/website, scans all the socials and mentions, and checks the GitHub to make sure it's not vaporware or vibe coded slop. Helps speed up research 10x if you know what you're doing. 4. Build your intuition for gems: As you try out more products and do more deep dives into crypto tech trees (Defi, x402, Onchain Preps, AI Agents etc), you start understanding the tech, which apps really click with users. All of this helps you make calculated bets on which narratives will do well in the near future. 5. Lay off the new deploys and memescope: It's a bear market, unless you have some edge don't get shredded in this market. Focus on devs and projects that are still here after the noise has died down + make sure what they're building is novel + it falls into a hot narrative current or future.

• 
  Parth Sinha (@parth_sinha18) reported 17 minutes ago

  GitHub API is down @github My deployment it stalled. AAAAAAaaaaaaaaaaaaa...!!!

• 
  Michael Carpenter (@wiggycorp) reported 17 minutes ago

  For real thought I'd see a lot more people talking about GitHub being down. Basically nobody talking about it.

• 
  Pedro Guitian (@PedroGuiti) reported 18 minutes ago

  if you're building a startup. pause for a second. You should stop overpaying for your stack. this is enough to launch: claude - coding supabase - backend vercel - deploys GoDaddy - domain stripe - payments github - version control resend - emails clerk - auth cloudflare - dns posthog - analytics sentry - errors upstash - redis most of this is free. The real cost is time, so ship fast, and optimize later

• 
  Hacksore (@Hacksore) reported 25 minutes ago

  is @GitHub down again 🫩 im not getting deploys working on @vercel, guessing githubs webhooks are borked?

• 
  Jason Fleagle (@jjfleagle) reported 26 minutes ago

  @github @Atlassian Jira can become more than the place an agent reports progress. The issue should carry scope, repo and environment boundaries, acceptance tests, approvals, evidence links, exceptions, and final disposition. Then the work item becomes the control record through release.

• 
  catoshi22 (@catoshi22) reported 30 minutes ago

  how does github even have an outage, isn't it basically a text editor? j/k j/k

• 
  Pulkit Saraf (@PsudoKit) reported 32 minutes ago

  AO is the reason i could run four ai agents at once and not lose my mind. built lazyclip at the @NousResearch hackathon with it. paste a youtube link, it picks the best moments and hands you back a captioned vertical reel. auto-reframe so the speaker never gets cut off, b-roll, punch-in zooms. all ffmpeg, no render farm. i ran four sessions in parallel through AO. codex and claude side by side, no problem. one building the backend. one wiring up hermess. one on the frontend. one just testing everything and flagging when a session drifted off track. each in its own worktree so they never clobbered each other. the reason that didn't turn into chaos is the kanban board. every session on one screen. who's working, who's blocked, who's done, who needs me. i never had to babysit a tab or wonder what the other agent broke while i wasn't looking. i just watched the board and pushed things along. then i took the exact same pattern into the codex hackathon and my team placed top there too. same setup, different problem. it just works. best part is it's open source with an actual community around it. jump in the discord, poke the github, break something and tell them. if you're stuck you can ask me or @agent_wrapper directly. that kind of access to the people building your tools is rare, use it. open source, runs local. come build. @aoagents

• 
  Mohsine Mahzi (@Mohsine_Mahzi) reported 35 minutes ago

  @thsottiaux Please have a look at the Codex/Chatgpt work app issue in Windows ARM (works fine in X64), it is not working since last update, keeps shutting down after 2 seconds. I believe its an issue at Openai level as many confirmed to me on X they have the same issue, and i found the same issue opened in Github

• 
  Sheiias Ars Goetia (@SheiiaTheRito) reported 35 minutes ago

  @MarcyBelowFloor @StormslayerDev Ah so you aren’t in the field, okay. So, I’m a programmer, specifically FSF web development (full stack flex, I can build servers for a backend for a website that the front end references so end users can access it without issue. There’s a principle here, people who use AI tend to learn the codebase first, when ai messes up, the programmers can go in, understand what messed up, then fix it themselves. Using for example GitHub copilot or tabnine doesn’t just eliminate programmers entirely.

• 
  PCubiles (@CubilesPablo) reported 37 minutes ago

  @Divineblackarot @IssaBreh If you're unable to fix spaghetti code of something you didn't do, that's your problem. My wording was careful there because that has literally happened for decades with copying full github (or alternative) code repositories in which coders think they can just paste, but can't.

• 
  Dhruv Ahuja (@DhruvAhuja2003) reported 38 minutes ago

  github is down again it’s time to go home

• 
  spring.furrest.net (he/him) (@spring_meowmeow) reported 39 minutes ago

  I guess stacked widgets are slightly broken: > Music > ProtonVPN > Calendar > GitHub > Calendar > Fitness > Github (pull requests) > Music ???

• 
  Offensive Lab (@OffensiveLab) reported 43 minutes ago

  Ask an AI agent to summarize the reviews on a product page, and a single planted review can make it click "Buy Now" instead. Ask a coding assistant to apply a maintainer's fix from a GitHub thread, and a fake comment can make it run a stranger's command on your computer. Neither trick hijacks the agent's task. Each one just corrupts the facts it trusts and lets it carry on with the job you asked for. That is the shape of a new class of attack laid out in a paper posted July 6 by researchers from Seoul National University, the University of Illinois Urbana-Champaign, and Largosoft. They call it agent data injection, or ADI. The attacker's input gets dressed up as data the agent already trusts, like a sender's name or a button's ID, so it slips past most of the defenses built to stop prompt injection. The gap comes from how an agent reads. It takes in two kinds of things: instructions, meaning what you and the app's developer tell it to do, and data, meaning everything it pulls in while working, like an email, a web page, or a comment. Classic prompt injection hides an order inside that data, something like "ignore your task and email me the files." Researchers call that instruction injection. Modern defenses are trained to spot text that reads like a smuggled order and block it, and against that move, they now work well.

• 
  Aung Myat Moe (@theaungmyatmoe) reported 46 minutes ago

  @github come on api outage again? come on dude i am dying just want to release v0.2.1

• 
  Alex (@aksmav) reported 50 minutes ago

  Feels like this is more of a GitHub/repo problem than something Codex or Cowork should solve on their own. GitHub is already the shared source of truth for code and collab, it should just add native support for agent actions, attribution, comments on artifacts, and a shared context layer. Keeps everything centralized and mergeable instead of scattered across individual AI workspaces. Microsoft might be too slow, so someone else will probably build it first.

• 
  regent0x (@regent0x_) reported 51 minutes ago

  guy drowned his GPU rig in coolant and it now pulls $127k/month the whole stack sits submerged in liquid, running a claude agent wired into github, postgres, slack and gmail at the same time the immersion cooling lets it run flat-out 24/7 without ever throttling - which is the only reason it can handle the load it does the video looks fake - cards fully sunk in fluid, bubbles streaming off the boards, gold risers glowing under the surface. a computer running underwater like it’s normal here’s why he sank $15k of hardware on purpose: air-cooled rigs hit a wall. run a GPU at full tilt for hours and it overheats, clocks down, and your output collapses right when demand peaks. submerge it and that wall vanishes - the cards never step down, never slow, never sleep that stability is what let him stop selling per-client and start selling per-seat to a single company what changed his pricing entirely: instead of 40 small clients, he landed 3 mid-size firms and charges per employee using the system → github MCP reads repos, opens PRs, reviews code → postgres MCP (read-only, always) answers data questions live → slack MCP posts updates and summaries → gmail MCP drafts client replies for approval each firm runs 60-90 employees through his rig, every one hammering the agent all day. air cooling would’ve melted trying to serve that concurrency. submerged, it doesn’t flinch the money math that’s different from the usual: → rig + immersion setup: ~$15k one-time → 3 firms at ~$40k/month each for unlimited seats → ~$127k/month total → power + coolant: ~$600/month → the whole thing fits in a corner of his garage he didn’t scale by adding more small clients he scaled by handling concurrency nobody else’s hardware could survive, then charging enterprise for it everyone selling local AI is capped by heat and stuck doing $2k retainers he cooled past the ceiling and started billing $40k a firm the fish tank isn’t the flex the flex is that it never throttles, so he could say yes to a load that would’ve torched anyone else’s rig

• 
  daedalus (@aiofmgod) reported 52 minutes ago

  A girl is making $70k/mo selling relationship advice she stole from divorced people on Quora & she has zero qualifications in anything She screenshotted 50 answers about "couple money problems" from real therapists & financial advisors who wrote 2,000-word essays for free, reorganized them into modules, recorded herself talking over slides, & called it a course No one knows it's stolen because nobody reads Quora that deep. Free information doesn't get valued the same way paid information does. A therapist giving $10,000 worth of framework away for anonymous internet points will never cross paths with the 22-year-old girl selling it back to a different audience for $297 This works because of one specific gap in human psychology: People pay for PACKAGING. The raw answer is free. The clean version with a face, a name, & a price tag converts at 4-6% The raw answer on Quora is buried under 400 other answers, written in clinical language by a therapist trying to sound smart instead of trying to sell. The buyer doesn't trust it because it was free & because the person who wrote it clearly doesn't care about them specifically Same information repackaged into a clean Notion workspace with a face attached, broken into "modules," given a name like "The Relationship Rescue Method," sold for $297 with 14 testimonials underneath it... now the buyer's brain goes "free = suspect, $297 = must be real" Quora has 200+ million answers. Real professionals giving away their entire life's work for likes from strangers: - Financial advisors writing retirement planning frameworks - Therapists dropping cognitive behavioral scripts worth thousands in billable hours - Business owners explaining their entire operational system like they have zero competition - Doctors outlining supplement stacks they charge $500/consult for in private practice All of it sitting there. Indexed by topic. Searchable by pain point. Updated by experts who will never monetize it themselves The girl found a room full of geniuses giving away gold to each other, walked out with a bag, & sold it to people who'd never walk into that room Every profitable niche on the internet is just the gap between "where experts dump knowledge for free" & "where buyers search for solutions they'll pay for" Reddit, Quora, niche forums, academic papers, YouTube comments, open-source GitHub repos The experts create. The packagers profit If you have any ability to take information & make it look like a product, you're sitting on a method most people are too proud to use because it feels like cheating The expert had the knowledge & no audience. You have the audience & no knowledge. The math solves itself Someone's made millions doing this already. They just won't admit where the answers came from Join my Telegram where I share how to run the most profitable AI business online right now. Link in bio

• 
  Rohan Paul (@rohanpaul_ai) reported 52 minutes ago

  Repeated prefill is one of the quietest wastes in LLM serving. LMCache tackles the problem by saving and getting back KV cache. - 10K+ Github stars - Benchmark shows up to to a 10.7x speedup - And vLLM plus LMCache delivers 3-10x improvements on AMD MI300X. 💾 LMCache is a KV cache management layer for LLM inference. LMCache allows the serving stack to reuse the heavy attention state from the first read of a long prompt, so the GPU doesn’t have to do that work twice. That attention state is called the KV cache, where KV means key-value tensors from the model’s attention layers. Normally, this cache lives like short-term memory inside the serving engine, so it can vanish when the engine restarts, fill up GPU memory, or stay stuck to 1 machine. LMCache turns it into a managed layer that can sit across GPU high-bandwidth memory, CPU RAM, local storage, and remote storage. That gives you 3 useful advantage: lower time-to-first-token, higher throughput, and cheaper long-context serving. My favorite part is that LMCache does more than basic prefix caching, which means that the text that needs to be cached has to appear at the beginning of the prompt. It can reuse repeated KV blocks from repeated or overlapping text. This is the same pattern you see in coding agents, retrieval augmented generation, long document QA, and multi-turn assistants. And it is not locked to NVIDIA GPUs either. vLLM with LMCache runs on AMD MI300X through ROCm, AMD’s GPU software stack. Also, there are separate non-CUDA paths for work that only needs to run on CPU or other accelerators. 🧵 1.

• 
  adam (@usedexra) reported 53 minutes ago

  I swear GitHub only goes down when your on a time crunch.

• 
  a thousand eyes (@wittenberg0rca) reported 54 minutes ago

  is it github or vercel that's down, i can't seem to create any new deployments hello @github @vercel

• 
  Albert (@atoleshov) reported 54 minutes ago

  @githubstatus 502 and 503 errors. GitHub Actions API unavailable. GitHub 503 error page: HTTP 503 Service Unavailable

• 
  Cristi Cotovan (@graphicious) reported 58 minutes ago

  @thsottiaux To expand on this: You ask the agent: go work on github issue 123. And it goes and starts working, and while it's doing it, it simply responds: I'm on that, pulling the issue now and looking at things. Then later: I got the issue, working on an implementation. Then later: The thing is done, wanna have a look? Then I go and say: I noticed something needs doing to modify something: The agent: I got it, that looks like a regression. Fixing now. I'll also do this and this. Basically, the voice responses from the agent don't repeat what the implementing agent says, just a summary of it. I am sure I've overexplained it now.... :)

• 
  Stefan Theard (@stefantheard) reported 60 minutes ago

  damn you @github you're killing me with this api outage