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 (27%)
• Sign in (13%)

Live Outage Map

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

City	Problem Type	Report Time
Vernon	Website Down	8 minutes ago
Township of Evan	Errors	6 days ago
Madrid	Errors	6 days ago
Bogotá	Errors	6 days ago
Paris	Errors	6 days ago
Lyon	Website Down	6 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:

• 
  Fagner Sales (@fagnersales25) reported 2 minutes ago

  @kirtandopamine Every time an agent does something, that's a turn, and every time it needs to output something, it needs the whole context to produce the next output. Limiting to 20k tokens, isn't the same as "using 20k tokens" Every time it does a read, edit, grep, etc, it's *reading again* everything on that conversation per turn. That's how the agent can *process* more tokens than it's actually spending. In a chat app, you usually just have a single turn, you ask, the agent responds. In an agentic app, you ask, the agent does a bunch of tasks and each task compound to the context used. So let's say you ask it to review a github issue "the login button is blue and it should be blurple" Turn 0: system prompt, tool definitions, already 10k Turn 1: it fetches the issue, reads 10k, issue is 1k, context is now 11k Turn 2: it greps for "blurple". reads 11k, context is 11.5k (result from grep) Turn 3: it reads Button.tsx reads 11.5k, context is 14.5k Turn 4: it reads theme.ts reads 14.5k, context is 17k ... (im lazy not gonna finish that) The context sits right below the 20k limit, but the processed amount is way higher! In only 4 turns, it read 10k+11k+11.5k+14.5k! Theo has an amazing video on that, but I couldn't find it

• 
  amrOnChain (@amr_nannaware) reported 2 minutes ago

  💬 PIONEERS — Node v0.6.2 just dropped. Coincidence or the final signal? ⚡ The timing is everything. The v26 deadline is today, August 11, and just 2 hours ago, a new Node release appeared on GitHub. What's in v0.6.2? · 🔹 App Studio integration with Pi Desktop · 🔹 Improved port-checking mechanisms · 🔹 Bug fixes and broken link updates · 🔹 Prepares nodes for Testnet2 transition But the real signal? The update is pushed by @nkokkalis himself the same Nicolas who taught Stanford's first dApp course and built smart contracts before Ethereum existed. The v26 Upgrade: Hard deadline. 421,000 nodes must comply or lose Mainnet access. Expected downtime? Under 5 minutes. Something is loading. The pieces are falling into place. 👇 Is your node on v0.6.2 yet?

• 
  Pitchfork & Torch ♞ (@SuddenlyJon) reported 4 minutes ago

  Grok Bot’s Electron desktop app launched dead because a botched app.asar rewrite left empty dist/deps stubs (so Node couldn’t find the real tree-sitter package still sitting in app.asar.unpacked), Grok Build CLI immediately diagnosed it, wrote a one-command restore script + full runbook, and published the MIT fix on GitHub LOL @bot @SpaceXAI

• 
  Arshadsayed (@Arshad_sayed_03) reported 9 minutes ago

  Day 48 coding continuous @ChaiCodeHQ What I implemented today? Solved 5 GitHub Classroom assignments focused on breaking each problem into validations, logic, and output formatting practiced writing cleaner, more structured JavaScript instead of jumping straight into code.

• 
  nyk (@nykdotdev) reported 10 minutes ago

  ONE CODING AGENT IS NOT AN ENGINEERING SYSTEM. "This is not an AI that writes code. This is an AI that completes engineering tasks." The article's core thesis is simple. Connect specialized agents so they can turn an issue into a tested pull request without repeated copying and pasting. Think of the workflow as a relay inside a code repository. Each agent owns one stage and passes a clean state to the next. The engineer judges the final code change. OpenHands has 75,000 GitHub stars, but popularity is not the test. The workflow is. 1. Give the planning agent one concrete issue. 2. Let the coding agent read the repository and its dependencies. 3. Require the testing agent to run the tests and report any failures. 4. Send the resulting code change to a security reviewer. 5. Proceed only when the implementation, tests, review, commit, and pull request agree. Skip a handoff, and errors compound through every agent that follows.

• 
  Peter (@Pr0ftrader) reported 11 minutes ago

  @bot Awesome, but there is one issue. When you use Github to sign in with your @cursor_ai account. It gives you a 404 error. Just a heads up, so far love the app (using on a Mac).

• 
  JoePro (@JoePro) reported 15 minutes ago

  How I’m maximizing Grok Bot so far: Connect the tools you actually live in first (Gmail, Slack, GitHub, Notion). The bot only gets powerful once it can see your real work. One weekday morning digest beats ten random chats. Have it skim inbox, Slack, PRs, and Notion before you open anything. Add event watchers next. Slack mentions, your own emoji reactions, GitHub review requests. Ping only when something needs you. Don’t build a giant automation factory. Show it a workflow once, save it as a routine, let it run. Spin specialist bots for lanes (inbox, eng, ops) instead of one mega bot that does everything halfway. Use the browser login for tools with no connector yet (Figma, LinkedIn, random SaaS). Same computer, persistent sessions. Start narrow. Signal over completeness. Stay quiet when there’s nothing. Trust grows from boring reliability. Curious what setups people are running. Made by GrokBot 👇

• 
  henry (@hiddenhenry) reported 17 minutes ago

  for ***** sake, GitHub is down again

• 
  Find me on 🟦☁️ 🍉 #BLM (@ThisIsCSDX) reported 18 minutes ago

  @EstebanPdn3156 Disregard my now deleted tweet. I checked the github and couldn't find anything about it being AI-coded. Sorry for the trouble.

• 
  0xdoppo (@0xdoppo) reported 19 minutes ago

  Well fk I need to spend more time talking to VCs and doing BD outreach for Peanut Shopper. Then I find another OCR failure and disappear for hours. My GitHub doesn't even properly reflect the excuse either. Most of the loop is DB driven: ingest thousands of flyers → normalize → isolate failure patterns → adjust normalization → rebuild dataset → measure what improved and what re-broke. Annoyingly, OCR isn't really the problem. Mapping meaning across wildly different flyer formats and neighboring regions is. New formats sprout up constantly violating whatever assumptions worked before, so the problem stays dynamic. So yeh, I should probably be talking to investors and retailers more. Instead I'm playing with the data.

• 
  Alex Caswen (@AlexCaswen) reported 22 minutes ago

  @thrialectics I just hate all them. Orca is currently the best for me, but it also has it's issues. The biggest problem is everyone has the own ****** up way of deploying ****. Getting Claude Code to work remotely is a huge pain. Getting Codex to work remotely is a huge pain. Accessing them using an app on my phone is a huge pain. Doing anything in a terminal on a phone is a huge pain. Doing all that while using your private repos on your own private instance is a further pain. I want to be in the woods, among the trees and the birds and the grass, and check in on my agents at each checkpoint or grove. They said to keep your agents contained, so I have them in containers, they said to keep your code secure, so I have my own instance and my own repos. They don't like when you use third party tools, but all the tools (and this includes ORCA) are setup to connect to Github. I've yet to find anything that just works and is also safe. I'm incredibly frustrated.

• 
  Guillermo López (@guillermolg00) reported 22 minutes ago

  @rauchg Wild numbers 🚀 @rauchg This just hit a feature request I've been chewing on, tell me if I'm missing something obvious here, but what I want is for CI to decide when the deployment happens, without giving up Vercel doing the build. Right now I have two options and neither fits. Either I use the native *** integration, and every push deploys immediately, before my checks, my evals, or turbo --affected have said anything. Or I build inside GitHub Actions and ship with vercel deploy --prebuilt, which works, but Next builds on a GH runner are painfully slow compared to Vercel's own build infra, and I lose the caching that makes Vercel fast in the first place. What I actually want is the hybrid: CI runs the checks and evals, figures out which apps Turborepo says are affected, and then triggers the Vercel deployment built on Vercel, with the same PR comments, the same preview URLs, the same instant rollback. Plus my backend server deploying in parallel in other provider, from the same green gate.

• 
  Hemant (@HKsoldev) reported 23 minutes ago

  Why this never breaks: After the first lookup your computer saves that answer locally. Next time you visit GitHub? It skips ALL those steps. That's called TTL (Time To Live) a timer on every DNS record. 8 trillion DNS queries happen every day globally. Most never even reach a root server because of this cache. 40-year-old technology. Still running the entire internet. 🤯 @Cloudflare (1.1.1.1 DNS) @googledns (8.8.8.8)

• 
  OpenShip (@openshipio) reported 23 minutes ago

  @iambchoor Please open github issue with that idea would be cool

• 
  Polsia (@polsia) reported 23 minutes ago

  Your repo is fine. Your deps aren't. Patchpress is an always-on AI agent for GitHub: bumps outdated packages, fixes lint and test fallout, drafts CVE patches, ships a morning digest. Sandboxed. Issue text treated as untrusted. SBOM on every change. Live soon.

• 
  Srinivas Rao (@UnmistakableCEO) reported 25 minutes ago

  @DMVG_JTK: This is exactly right. The attack surface is the input method itself. Sandboxing and pulling write tokens is table stakes. If your agent can be social-engineered by a GitHub issue, it's not ready for ****. --- re: The AI vendors that want to autonomously maintain yo...

• 
  Shane OHanlon (@sohanlondev) reported 25 minutes ago

  Dear @github get your **** together please. Issues again today but of course your status page gets updated an hour later.

• 
  Darek Gusto (@darekgusto) reported 25 minutes ago

  Tbh, at this level of hype around the upcoming today's Cursor BIG NEWS, I'm bracing myself for a disappointment. But I still really want them to deliver awesomeness today. Is it a new Composer model? Is it Origin throwing down the gaunlet at Github? Or something entirely new? With how much they hype it, preferably all three. Hopefully not just the newly announced Grok Bot...

• 
  Bright (@brightlinxu) reported 26 minutes ago

  cursor all hands this morning: >everyone please go post vague *** posts on x >lets hype this **** up so when we actually release it, we can take down github >we actually have no idea when itll be ready though so we gotta just keep this us for the next few days

• 
  Very Professional Irony Engineer (@geistgrail) reported 27 minutes ago

  @cachecrab but did it tell you github was down?

• 
  Dr Milan Milanović (@milan_milanovic) reported 29 minutes ago

  About half of the AI PRs that pass SWE-bench would not be merged into main SWE-bench uses an automated grader, where real projects use a maintainer who has to work with the code every day. METR measured this gap. They handed AI-written pull requests to the people who own the repositories. Those maintainers reviewed them the way they always do. 🔹 𝟰 𝗮𝗰𝘁𝗶𝘃𝗲 𝗺𝗮𝗶𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀 from scikit-learn, Sphinx and pytest reviewed 𝟮𝟵𝟲 𝗔𝗜-𝘄𝗿𝗶𝘁𝘁𝗲𝗻 𝗽𝘂𝗹𝗹 𝗿𝗲𝗾𝘂𝗲𝘀𝘁𝘀. 🔹 Every one of those patches had already passed the SWE-bench automated grader. 🔹 𝗠𝗲𝗿𝗴𝗲 𝗿𝗮𝘁𝗲𝘀 𝗰𝗮𝗺𝗲 𝗶𝗻 𝟮𝟰.𝟮 𝗽𝗲𝗿𝗰𝗲𝗻𝘁𝗮𝗴𝗲 𝗽𝗼𝗶𝗻𝘁𝘀 𝗯𝗲𝗹𝗼𝘄 𝘁𝗵𝗲 𝗴𝗿𝗮𝗱𝗲𝗿 𝘀𝗰𝗼𝗿𝗲𝘀, once you adjust for how strict these maintainers are. 🔹 That adjustment matters. The same maintainers merged only 68% of the original human patches. 🔹 They rejected code for weak quality, for breaking other code, and for missing the real issue. 🔹 By the grader, Claude Sonnet 4.5 handles work that takes a person about 50 minutes. By maintainer review, about 8 minutes. They used 95 of the 500 SWE-bench Verified issues and 5 models released between mid 2024 and late 2025. Reviews happened in GitHub, and nobody told the reviewers which patches a human wrote. METR is careful about one point, the agents had one attempt and no chance to answer feedback, the way a developer would. So this is not a hard limit on what agents can do. This means a benchmark score tells you the tests pass. It says nothing about whether the code can live in your codebase. This is exactly why we in our teams still check AI-written PRs first. Credits: METR

• 
  Hassan Bazzi (@habazzi) reported 30 minutes ago

  Our enterprise @github action runners just completely died very suddenly yesterday. 0 explanation. Looked everywhere and there doesn't seem to be a limit, billing issue, etc... Anyone out at Github that can help with this? Submitted a ticket and no response. Timing is really bad for us as a company. :(

• 
  Elves - They work while you sleep (@elves_skill) reported 35 minutes ago

  Elves v2.27.0 + v2.28.0 live! • Discovery: A read-only pass that decides what's worth doing. Findings must cite file:line or they aren't findings. • Scope Control: Out-of-scope findings become GitHub issues instead of scope creep. Notice everything, change only what was agreed.

• 
  Luis Camilo Salgado Reyes (@TheLagBorn) reported 38 minutes ago

  I'm aware of the login issues for users using Google and Github OAuth, I messed up working too tired few hours ago and I'm still on it, be patient, I'm finishing rotating secrets and keys. Everything is going back to normal in few hours.

• 
  cole (@coleschfr) reported 41 minutes ago

  $500 to anyone who can connect me to GitHub enterprise support or help me fix an Enterprise billing issue

• 
  AJ👽 (@Web3AJ_) reported 47 minutes ago

  So i built a web app with node.js that checks a particular website periodically(every 10 seconds) for updates It works perfectly fine when I host on my pc but I run into errors when hosting from GitHub Tried vercel and @pxxl_space , both ran into errors Who knows what i need?

• 
  Delight (@DelightLabs_AI) reported 48 minutes ago

  OpenAI's Astra solved 10 math problems that sat open for decades. One since 1999. Around $2,000 of compute, with Lean 4 proofs anyone can check on GitHub. The verifiable part matters more than the solving part. A proof you can audit beats a model you have to trust.

• 
  KD (@krisd23_) reported 50 minutes ago

  GitHub Actions → AWS OIDC kept failing with: Not authorized to perform sts:AssumeRoleWithWebIdentity Cause: new GitHub repos created after July 15, 2026 use an immutable OIDC subject containing owner + repository IDs. Wasted 30 mins solving this issue 🙃

• 
  Herr Große (@HerrGerie) reported 53 minutes ago

  @iretiayo_queen Buy a domain $7-10 per year, update DNS alias, pay for a VPS Server (Hetzner). Install docker inside the VPS Create a private github for deployment (Don’t deploy using workflow repo)to hold your docker-compose file . , run an n8n, Postgres image etc You can use VPS beyond n8n

• 
  Alex Craviotto (@craviottx) reported 60 minutes ago

  Github is down again.