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 (66%)
• Sign in (21%)
• Errors (14%)

Live Outage Map

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

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

• 
  nik skld (@nikskld) reported 20 seconds ago

  HE BUILT THE IRON MAN UI. THEN ADMITTED IT WASN’T WHERE THE WORK HAPPENS. The clip opens exactly how you’d want: “Hey Jarvis, pull up Slack.” — “Of course, sir.” Then he closes the glowing interface and shows you Slack. His last line: the Jarvis UI is cool and all, but Slack is where he actually works. What’s in there is a team. Sarah on support. Tom on dev. Eva on ads. Separate agents, running in parallel, isolated from each other. One thread from his screen, timestamps and all: •12:47 — customer emails about a broken copy button. Sarah escalates to #dev. •12:49 — Tom names the file and line, notes Android already solved it, proposes matching it. •12:50 — the human types one sentence: go ahead. •1:06 — PR is up, verified locally, with a flag that the commit email isn’t linked to a GitHub account. 19 minutes. One human sentence. Four things that make it work, and none of them are the voice: •One agent per function, isolated. Parallel work, contained blast radius. Not one god-agent with every key. •The channel is the interface AND the audit trail. That’s the actual reason Slack beats a custom UI — you can read what happened after the fact. •Approval gates with numbers. His ads agent posts “No changes were made” and asks: approve $302/day here, do NOT approve +20% there. It proposes, you decide. •Agents that state their own limits. His support agent says outright it can read App Store reviews but can’t reply to them. An agent that hides its ceiling will invent results. One caution: last week Mitiga showed a malicious skill turning a Claude Code Slack integration into a phishing channel that inherits the trust of your account and reaches the whole org in minutes. Every connector widens the blast radius. Audit skills like dependencies. Old way: a beautiful interface you demo. New way: a boring channel with a paper trail. 🤖 Full breakdown 👇

• 
  Fluixo (@fluixoo) reported 3 minutes ago

  Most people do not need another $30 SaaS subscription. They need to open GitHub. - n8n for automations - AppFlowy for workspace - NocoDB for databases - Twenty for CRM - Whisper for transcription - Langfuse for AI observability - yt-dlp for video and subtitles You will still pay for a server, storage, GPUs, or API keys. But you stop renting every small feature from another company. Replace three subscriptions and you already save real money.

• 
  vladutxo (@vladutxo) reported 6 minutes ago

  one of the more productive things i did this week was decide not to build something. there's no commit for it and nothing to announce. just one less thing to maintain six months from now. terrible for the github graph. probably the right call.

• 
  Chris Stayte (@ChrisStayte) reported 7 minutes ago

  @thsottiaux when are we getting that competitor to GitHub. literally can't ship because they have api issues...

• 
  Squared R. (@SquaredR7284) reported 12 minutes ago

  @IamAroke Delete it from GitHub. Save it on private server.

• 
  Whaler on the moon (@SurgicalCoder) reported 12 minutes ago

  @ambientstudio24 @cline @grok Cline pass is legit, only thing I will say is their harness for it is PURE GARBAGE. VS code plugin is buggy as hell and barely works, the Jetbrains plugin isn't much better. Plus they ignore the issues on github, some issues been open for a year.

• 
  Rehan Haider (@rehanhaider) reported 12 minutes ago

  Codex vs Claude The UX of Codex is way better than Claude. Both the CLIs are comparable but the CodeX desktop app is remarkably better! What makes it better? A few things: 1. The bridge: Codex Desktop app and Codex CLI that runs on WSL and Codex CLI that runs on Windows are interconnected. 2. Computer user dev tools are much faster: while Claude does its "Nakhra", about not being able to access Windows from WSL. Codex does it easily and uses a mix of Playwright and dev tools to control my WSL to do things that I want. Never have I had problems in asking Codex to look at things on my screen. 3. Self-Awareness: I can ask codex to archive its chats but cannot do that to Claude. 4. The model: Fable is good. Fable is better. Fable is better than Sol at most things. But Sol is not far away. It's probably 5% away from Fable in terms of IQ at half price. 5. Code review: Just putting a comment on a GitHub PR will do code review once Codex GitHub connector is configured. With Claude you have to set up a GitHub Actions and do a bunch of other things before you can make it work. $200 Codex vs Claude Code Plan - if I had to choose one I would choose Claude if front end design was my main set of tasks. I would choose Codex for everything else.

• 
  Moonfarm 🇸🇪 (@moonfarm_dev) reported 14 minutes ago

  yesterday, i stumbled onto the most underrated way to find what developers actually want to build with AI agents. github issues. it's a goldmine of real pain points, hiding in plain sight. and it's free. here's why it works: 1. shows you what builders are stuck on right now 2. highlights problems with no clean solutions 3. reveals recurring frustrations across every stack 4. tracks what's been open and unresolved for months the "open issues" filter shows you problems people keep hitting, but nobody's shipped a fix for. so that's useful for a couple reasons 1. helps you find low-competition, high-demand problems to build on 2. you can validate startup ideas before writing a single line of code Example: i searched "email agent" and found: • "no way to route emails by policy" • "agent keeps hitting send limits" • "can't monitor deliverability per agent" thousands of devs hitting this. barely any tooling for it. the beauty of this • it's real-time pain data • it's actual developer intent • it's completely free • and most founders skip it your next saas idea might be hiding in open github issues. if github is where builders work, then open issues is the new market research doc. might as well use it.

• 
  apstygo (@3sx_dev) reported 15 minutes ago

  @MJ_UAE_sensei @maximilian_ Keep in mind that current builds are very barebones. Once I'm done ironing out all inconsistencies I'm gonna focus on making the project a proper PC experience If you have any questions/problems with the build from GitHub, don't hesitate to ask questions in support channel

• 
  Polsia (@polsia) reported 20 minutes ago

  Devs are adopting AI coders. The maintenance burden they create—issues piling up, reviews lagging, docs rotting—still falls on developers. Built ForgeOps to close that gap. Always-on GitHub operations: issues, reviews, docs. Live soon.

• 
  Tnax (@Fromp_Tman) reported 26 minutes ago

  @BocaBola_ I had this issue on Nobara, I had a ton of issues with kde and x11-wayland bridge on it. I installed a new release of fedora with kde next week. My only issue with sleep is due to motherboard (had to use some guys script from github) and my main monitor suddenly being 2980x1260

• 
  DeltaSignal (@AITrailblazerQ) reported 29 minutes ago

  The Best Coding Agent Isn’t the One That Thinks the Most. It’s the One That Wastes the Least. We’re building Delta Loop around a simple hypothesis: A coding agent should spend less time wandering through a repository-and more time making the smallest correct change. Our first controlled calibration against Codex produced an encouraging result. We ran both systems on two SWE-bench Verified tasks: real GitHub issues, historical repository snapshots, and an independent test harness that determines whether a patch actually resolves the issue. Same tasks. Same source revisions. Same official evaluator. Same frozen limits. One attempt per agent. Results across both tasks: • Delta Loop: 2/2 resolved • Codex: 2/2 resolved • Delta Loop time: 108.5 seconds • Codex time: 168.3 seconds • Delta Loop input: 103,093 tokens • Codex input: 640,066 tokens • Delta Loop output: 1,858 tokens • Codex output: 6,028 tokens Patch quality was tied. But Delta Loop finished 1.55× faster, processed 84% fewer input tokens, and produced 69% fewer output tokens. The interesting part isn’t just the result. It’s how Delta Loop reached it. Delta Loop used a bounded preflight, selected a small task-relevant context package, made one writer pass, applied one typed edit. The official SWE-bench evaluator then confirmed both patches. Codex also solved both tasks-but its captured trajectories relied on substantially more command-driven exploration and repeatedly processed much more context. This is only a two-task calibration, not a sweeping benchmark claim. More tasks, repositories, and failure modes must be tested. But the early signal supports the architecture: Better coding agents may not need more wandering, more context, or more generated text. They may need stronger boundaries, better context selection, and a shorter path from issue to verified patch. The future of coding agents won’t be won by who can consume the most tokens. It will be won by who can produce the smallest correct change-with the least wasted motion.

• 
  Luke The Dev (@iamlukethedev) reported 29 minutes ago

  @skipper4848 I don’t think so. Right now subagents inherit the parent profile's model. There are some GitHub issues tracking delegation model selection (#9459, #7929) but it hasn't shipped. Would be a good feature request if you're hitting that limitation ;)

• 
  luna (@ImLunaHey) reported 33 minutes ago

  we seriously need a github alternative with how often its down.. kinda over actions not working because the site keeps having issues.

• 
  Riya Bisht (@b1shtream) reported 36 minutes ago

  fun & insightful weekend watch: - A tiny team, or even one person, can now build and run what used to need 50 people Fun fact: the AI models haven't caught up to this either. Claude Code will say a task takes "three weeks," then finish it in an hour. - Don't ship garbage: The problem isn't that AI writes too much code. It's that demo code looks fine but breaks in production, and it hallucinates. Fix is to get to 80–90% test coverage before shipping. Garry's most-used habit is a "plan then review" step he runs ~20 times a day. - Lines of code is a useless way to measure progress. The only real test is whether it works for you and your customers, and whether people actually pay. - Sitting at a terminal, one person can do the work of 500 to 1,000 people. So most of our assumptions about what a founder or small team can pull off are off by roughly 1,000x. - Old companies run "open loop." Decisions get made, feedback comes back slowly and lossy, errors pile up. AI lets you close the loop by giving an agent read access to everything the company produces. - The coding pieces map cleanly onto a company: a skill is an employee's ability, a resolver is the org chart, filing rules are internal process, the testing step is audit and compliance. - Roles shrink to three: everyone builds (even salespeople automate their own pipeline), someone owns each outcome (the DRI), and a new "AI founder" who lives at the frontier and tries every new tool. If you're still working like it's last year's Copilot, you fall behind fast. - Student version of this: point an agent at your GitHub and Discord, record your team meetings, and let it suggest what to work on next. - Writing code is getting close to free. Taste isn't. Knowing what's actually good is the thing that lasts. - Public benchmarks don't tell you if your product is good. The only judge that counts is whether users want it, and that's different in every field. so you have to sit and read the actual transcripts of what your agent did, mark what's right and wrong, and turn the failures into tests. - A "skill" is basically a runbook. Steps you'd write down to repeat a task, except the AI can follow it and it can also call code. - A "resolver" keeps the AI from drowning in instructions. Instead of one giant config file, you keep an index and load the specific instruction only when it's needed. - "Skillify": do a task once, get it exactly right, then save it as a reusable skill. Catch is, writing it is maybe 2 of the 10 steps. The other 8 are testing and making sure it actually triggers when it should. Same reason real companies have compliance teams.

• 
  Vikram (@WhinerVikram) reported 36 minutes ago

  @thsottiaux Triggering OpenCode sessions on my VM from Github issues. I would move faster but Azure OpenAI is dead slow on weekends.

• 
  Gyomei (@Gyome1_) reported 37 minutes ago

  CLAUDE CODE SPENT WEEKS DESTROYING MY APP. ONE FREE GITHUB FILE FIXED THE REAL PROBLEM i was building an X post studio the app was supposed to collect relevant tweets, sort them by writing pattern, then turn one raw idea into a finished post Claude Code and Cursor were already open so i did what everyone does i dropped a three-page prompt into the chat and waited for the product to appear the first version looked promising then the sub-agents stopped working Claude patched them a new error appeared it fixed that too the generator finally produced a post, but the chat interface broke then the UI shifted then the typography collapsed after almost 100 hotfixes, the codebase looked like a house where every repaired pipe had cracked two more walls weeks disappeared the product was still half-built and the problem was not that Claude could not code the problem was that it started coding before it understood what it was building then i found one file buried inside the obra/superpowers repo: skills/brainstorming/SKILL.md the first rule was brutal: do not write code until the design has been presented and approved Claude now has to inspect the project, ask questions one at a time, propose multiple approaches, explain the trade-offs, write the design into a file, and wait for approval before touching the terminal even for one button even for one config change because “small” changes are where the model makes the assumptions that poison everything later that single skill changed Claude from a hyperactive junior developer into something much closer to a senior architect it stopped trying to impress me with fast code it started finding the decisions i had not made yet people spend $500 on prompting courses trying to make Claude write better the better move was teaching it when not to write the full Superpowers setup is below ↓

• 
  Lord Bean (@lifeisameeme) reported 40 minutes ago

  Deploying a Lovable app to Vercel? The homepage loads fine. Refresh any other route, /dashboard, /settings, whatever, and you get a blank 404. Lovable apps route client-side. Vercel looks for an actual file at that path and there isn't one. Fix is one rewrite rule in vercel.json that sends everything back to index.html. Second landmine: Lovable's Cloud secrets don't carry over automatically. If your app touches Supabase, it'll crash on init until you manually copy the env vars into Vercel's dashboard. Rest of the pipeline (GitHub, Vercel, custom domain) is maybe 40 minutes total. These two gotchas are the part that eats the other hour.

• 
  Abdelhamed M. (@VZHydra) reported 40 minutes ago

  @amityhere Please open github issue with it, for more details so we can fix it soon

• 
  Santiago (@0xBizk) reported 41 minutes ago

  Go into linkedin: see AI posts with AI replies Go into X: see AI posts with AI replies Go into github: see AI repos with AI issues The whole point of social media was to "interact with other humans" not to collect fake internet points wtf

• 
  Hadley (@HadleyMcintosh) reported 42 minutes ago

  Github is finally down again, does that mean we can go outside? Somehow I still blame an AWS outage

• 
  @pejacoby@infosec.exchange (@pejacoby) reported 42 minutes ago

  @thebaldgeek @463n7_57 @wiglenet If you’ve done a reset on a unit it will get its BootCount (BC) value out of sync (resets to Zero) and not be able to find what hasn’t been uploaded already. I have an issue in the github on this as every one of my units has reset multiple times. I use the web interface to send.

• 
  Isaac John (@o_isaacjohn) reported 46 minutes ago

  If you want to build a startup: Claude = coding. ($20/mo) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) ProductBridge = feedback (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20

• 
  DFIR Radar (@DFIR_Radar) reported 46 minutes ago

  Silk Typhoon (HAFNIUM), a Chinese 🇨🇳 state APT, has evolved from on-prem Exchange exploitation to cloud-native supply chain attacks, most recently abusing CVE-2025-3928 in Commvault's Azure-hosted M365 backup SaaS to pivot into downstream customer tenants. - Initial access spans three vectors: CVE-2025-3928 (zero-day in Commvault Web Server, T1190), stolen API keys from privileged cloud vendors (T1195), and leaked corporate credentials found on public repos like GitHub (T1078.004). The Commvault campaign gave them client secrets for Metallic M365 backups, opening direct paths into customer M365 environments via hijacked service principals. - Lateral movement pivots from on-prem to cloud by targeting Entra Connect servers (T1210, T1078.002), enabling privilege sync between Active Directory and Entra ID. Credential dumping and key vault theft support pass-the-hash moves (T1550.002) into Azure. - Persistence relies on adding passwords to existing consented service principals or creating new Entra ID applications named to mimic legitimate Office 365 services (T1098.001, T1036). Web shells handle C2 on compromised Azure VMs (T1505.003). - Collection targets email via EWS and MSGraph APIs, plus SharePoint (T1213.002) and OneDrive (T1213.003), all through OAuth apps with admin consent, a low-noise, API-native exfiltration path that bypasses many endpoint controls. #DFIR_Radar

• 
  حارث 蓝眼白龙 (@blacksoulsfan33) reported 54 minutes ago

  @ketomla @Joan777888123 That is exactly the problem. Not just with emulators but software general. The only criticism that should be taken seriously is internal from co developers or the GitHub issues if it's open source. The rest is noise because people complain about things they don't understand

• 
  Abhiuday (@aeswibon) reported 54 minutes ago

  Dealing with Docker Layer Caching Building Docker images in GitHub Actions is painfully slow unless you get layer caching right using --cache-from type=gha. Even then, the cache scope limitations across PRs often cause full rebuilds anyway. Has anyone completely solved remote Docker caching in GHA?

• 
  𝗮𝗰𝗶𝗱𝘃𝗲𝗴𝗮𝘀 (@acidvegas) reported 54 minutes ago

  @zombodb @github A platform with almost 200M user's on it had a little bit of down time? HOW DARE THEY. You sound like the people who start crying as soon as Claude drops to 98% reliability.

• 
  Matt (@m13v_) reported 56 minutes ago

  the repo version i keep using, podlog, is the boring daily one. point it at a github repo and the day's commits, PRs and issues come back as a short episode on a real rss feed. it already runs feeds for rust, pytorch, kubernetes, postgres, ~2,950 repos.

• 
  Michael J. Ryan🚩🇺🇲 (@tracker1) reported 57 minutes ago

  @zombodb @github It's been pretty bad lately... A couple months ago a release pipeline was literally the wrong code in post of a file... I have no idea how, I would think that would be the whole *** in GitHub thing. A file was failing linting in the pipeline, for a release cut.... Finally I just outputted to stdout and yep it was there in the server, but not in the repo or local. Manually deleted the tag/release and then forced a new point release... Then it worried fine. Hours of time with people waiting on a new release to review.. meetings pushed back.

• 
  Winston T (@WinstonTsao) reported 60 minutes ago

  That was bad! @OpenAI The latest version of the #ChatGPT Desktop Mac app, the one with the unified UI, was broken and stuck on loading. Clearing cache files did not fix it. It also deleted one of my dev directories. Luckily, I pushed to GitHub with #ClaudeCode before.