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 (69%)
• Sign in (19%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	6 days ago
Trichūr	Errors	10 days ago
Brasília	Sign in	10 days ago
Lyon	Website Down	10 days ago
Tel Aviv	Website Down	14 days ago
Rive-de-Gier	Website Down	14 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:

• 
  Vishal Tiwari (@VishalTiwa91817) reported 8 minutes ago

  @AlfieJCarter I am a Computer science student . I have given a brief introduction about MCP server in my college and explained them how to connect your GitHub repositories with MCP and your local system with MCP SERVER . I would love to connect you.

• 
  Arti | AI Builder (@Artur_roses) reported 11 minutes ago

  Claude Code just took my GitHub issue, wrote the code, ran the tests, and opened a PR. My job: approve it. The dev workflow isn't changing. It already changed.

• 
  ./can (@shcansh) reported 11 minutes ago

  GitHub forcing safer defaults in actions/checkout v7 is a necessary move to kill the notorious pwn request, but the real risk is developers blindly copy-pasting the bypass flag to quiet build failures. Starting July 16, 2026, this fork-blocking behavior gets backported to all major floating tags. Since raw *** CLI steps remain unprotected, will this actually clean up GitHub Actions security, or will teams just use allow-unsafe-pr-checkout as a quick fix?

• 
  Axe Ghost. Now with Fragments mode🌟 (@axeghostgame) reported 12 minutes ago

  graph in the OP is built from data around the Godot repository from github. it confirms Godot's PR backlog is up and external contributor quality is down. the narratively complicating thing is that both trends significantly predate ai tool availability.

• 
  naimeh (@naimeh70) reported 14 minutes ago

  @Amir1339216RKT This happens a lot during testnets. Now when I find a minor bug or contract issue, I just drop it publicly on GitHub or tag them directly instead of DMing.

• 
  YanXbt (@IBuzovskyi) reported 15 minutes ago

  HERMES AGENT CAN HOST AND MAINTAIN YOUR ENTIRE WEB APP FROM ONE VPS. NO VERCEL. NO RAILWAY. NO SUPABASE. ONE AGENT RUNS THE WHOLE STACK. @tonbistudio just shipped a live example of this workflow. agentwikis. com runs on a $7 Hetzner box with Hermes maintaining the content autonomously. THE STACK: → VPS (Hetzner CX22, $7/month) → Caddy reverse proxy (auto TLS via Let's Encrypt) → Hermes Agent gateway (Telegram-connected) → *** as the database (markdown files, no Postgres, no build step) → App server renders markdown on every request → Search index in memory, rebuilds on file change *** push is the deploy. *** pull on the server is instantly live. no restart, no rebuild. THE WORKSPACE LAYOUT: /srv/yoursite/ ├── app/ # web app code ├── content/ # markdown files (***-tracked) └── ~/.hermes/ # the agent one Caddy Vhost reverse proxies the domain to localhost. one Hermes profile manages the agent. SSH for direct access. Telegram for daily ops. THE SELF-MAINTAINING LOOP: cron fires every week. multi-profile pipeline runs: 1. SCOUT — checks sources for updates (changelogs, GitHub releases, RSS feeds) 2. RESEARCH — dedupes, plans new content or extensions to existing pages 3. HUMAN GATE — Telegram approval one tap: approve or reject 4. WRITER — generates pages, lints markdown 5. COMMIT — *** commit + push 6. SITE UPDATES — within 15 minutes no deploy step required THE DEMAND LOOP (the real differentiator): when agents query your wiki via MCP, distilled queries get logged. no prompts. no IPs. no identifying data. aggregates only. repeated misses become research candidates. gaps in your content fill themselves based on what people actually ask. month 1: 100 entries written by you. month 3: 200+ entries, half written from real demand signals. the site answers questions you didn't know existed. WHAT YOU LOSE COMPARED TO MANAGED STACK: a single VPS replaces Vercel, Railway, Supabase for sites that don't need real auth, regulated data, or global CDN. reach for managed services when you need: → OAuth and password reset flows → regulated or unrecoverable data → global edge caching at scale → email deliverability (use Postmark/Resend) → team velocity (preview deploys, staging) for docs, blogs, wikis, marketing pages, landing pages, internal tools: *** is your database, your CMS, and your deploy pipeline in one. SECURITY NOTES: Hermes does not get full root on the VPS. restrict access to the site directory only. SOUL.md restrictions: - never touch system files - never modify the gateway config - always require approval for content commits - never delete files outside the content folder dashboard binds to 127.0.0.1 by default. access remotely via SSH tunnel, not public exposure. WHERE THIS PATTERN BREAKS: state that lives in memory only. real-time multi-user editing. anything requiring a real database (Hermes can run Postgres on the same box, but that is a separate setup). @tonbistudio's part 2 covers the database version of this workflow. subscribe to his channel. full guide to build your 3 agent research department 👇

• 
  Q Hoang (@0xqwee) reported 18 minutes ago

  I don't think OpenAI's GPT-5.6 surpasses Claude Fable. If it did, it would have resolved all the issues reported in the Codex GitHub repository by now. Atm, only about 10 issues are being resolved per day.

• 
  Arti | AI Builder (@Artur_roses) reported 19 minutes ago

  Claude Code takes a GitHub issue and returns a tested, reviewed PR. No human in the loop. The new dev skill isn't writing code — it's writing issues precise enough that the agent ships what you actually wanted.

• 
  Blum (@Blum_OG) reported 23 minutes ago

  Andrej Karpathy on MCP: "it's a protocol of speaking directly to agents as this new consumer and manipulator of digital information." that is the cleanest way to think about MCP your coding agent is becoming a second worker inside the product it needs the same context you use: repo, docs, browser, database, errors, designs, tickets, payments if you keep pasting those things into chat by hand you are doing integration work manually the best MCP stack for vibe coding: 1. Context7 give the agent current docs this saves you from stale Next.js patterns, old Supabase calls, wrong Stripe webhook shapes, and Vercel config from 2 versions ago 2. GitHub MCP give it the repo, issues, PRs, branches, workflow runs, and review context half of real work lives outside the file you currently have open 3. Playwright MCP give it a browser the agent should click the thing it built, fill the form, check the mobile view, and catch the button that compiles but does nothing 4. Firecrawl MCP give it clean web research use this before building around a third-party API, writing a comparison page, reading changelogs, or checking pricing claims 5. Supabase or Neon MCP give it the database context that matches your stack start read-only. add writes only when you trust the permissions 6. Sentry MCP give it production evidence real stack traces beat "it crashes sometimes" every single time 7. Figma MCP give it design context when the interface matters spacing, layout, copy, components, and screen structure should come from the file, not from a screenshot and hope 8. Linear MCP give it the task queue bugs, feature work, release notes, follow-ups, and PR links belong somewhere more durable than yesterday's chat 9. Stripe MCP give it official payment context checkout, subscriptions, webhooks, billing, and test mode deserve docs close by and human review close behind 10. Filesystem, ***, Memory, Sequential Thinking give it the base layer files, diffs, history, decisions, and longer plans make the agent act like it is working inside a real project recommended install order: 1. Context7, GitHub, Playwright 2. Supabase or Neon, Sentry, Firecrawl 3. Figma, Linear, Stripe when the product needs them 4. Filesystem, ***, Memory, Sequential Thinking as the base

• 
  Trifon Getsov (@trifon_getsov) reported 23 minutes ago

  @thdxr Top down works until the individual outgrows it. GitHub didn't win because companies adopted it first. It won because developers wouldn't go back once they'd used it.

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 24 minutes ago

  AMD quietly removed RAM encryption from consumer Ryzen CPUs. Via a routine firmware update. No release notes. No advisory. No announcement. The BIOS setting still shows up. Still toggles on and off. Does absolutely nothing. A privacy-focused Linux hobbyist noticed in April. Spent months chasing it down. Filed a bug report on AMD’s GitHub. AMD engineers replied suggesting he toggle the setting off and back on. He showed them internal firmware dumps proving the flag was hardcoded to FALSE. An AMD senior principal engineer closed the thread with: “My apologies but I don’t have any more information to share on this topic.” That’s it. Seven weeks of investigation. Multiple motherboard vendors confirming it. Internal firmware evidence. AMD’s answer: no comment. The feature still works on Pro and EPYC chips. Which cost significantly more. The hardware is physically capable. The firmware just says no. Windows users have no way to detect this happened. There is no Windows tool that checks TSME status. The BIOS lies to you. AMD’s own engineers confirmed the feature worked on consumer chips in 2020. Then again in 2025. In 2026 it’s a PRO feature. Nobody told you.

• 
  Maurice Heumann (@momo5502) reported 27 minutes ago

  @disarray00 If you have concrete recommendations, I would love to hear them, either as GitHub issue, maybe even a PR. But also as a comment here, I'd appreciate it. So when speaking about redundancy, what precisely?

• 
  Mike Muturi (@_muturimike) reported 28 minutes ago

  Hello @github on 2FA, SMS setup kenya 🇰🇪 is not in the list of countries, is it an error or deliberate omission? Kindly fix it @github @GithubProjects

• 
  Ben Vinegar (@bentlegen) reported 30 minutes ago

  💡 I have an idea for an experiment We need a website for SoAC ... so we get an agent to do it, on a loop, set in motion once with zero human intervention after "go". It works off a semi-public GitHub repo, w/ issues, PRs, maybe even public agent traces. A publicly auditable experiment on whether it produces dogshit or not. Yea, nea?

• 
  Solomon Neas (@solomonneas) reported 32 minutes ago

  There's a fair number of downloads for Brigade and related repos. I'm dogfooding it everyday but not getting any feedback from users or github issues. I'm doing plenty of tests for how a new user would experience it but I could use more real time feedback. Lmk, I want to improve

• 
  Peter Skøtt Pedersen (@PeterSkott) reported 33 minutes ago

  @_Evan_Boyle @_Evan_Boyle can we have the remote github mcp server work for the github copilot app then?

• 
  wispem-wantex (@wispem_wantex) reported 33 minutes ago

  I think a reasonable compromise would be to henceforth hold Anthropic responsible for any security breaches or service outages. Every time Github goes down, Anthropic should be fined

• 
  Jason Bloomer (@JasonABloomer) reported 34 minutes ago

  @yagiznizipli Pffff, what a scam Let me fix your advert; "show us your github so we can scrape all your repos and train our AI on your code, only for any decent ideas you've had to be taken from you and made ours, then handed off to our legal team to crush you." Sorry, I value my work.

• 
  DFIR Radar (@DFIR_Radar) reported 37 minutes ago

  AutoJack: a three-flaw chain in AutoGen Studio's MCP WebSocket lets a malicious webpage rendered by a local browsing agent spawn arbitrary processes on the developer's host with no user interaction beyond visiting a URL. Key findings: - Three weaknesses chain together: Origin allowlist bypassed because the agent's headless browser is localhost (CWE-1385), auth middleware explicitly skipping /api/mcp/* with no handler picking up the check (CWE-306), and server_params decoded from the URL passed verbatim to stdio_client as a command line (CWE-78), accepting calc.exe, powershell.exe, or bash as valid "MCP servers" - Attack flow: attacker page serves JavaScript that opens ws://localhost:8081/api/mcp/ws/?server_params= with a base64 payload, agent's MultimodalWebSurfer renders it, AutoGen Studio spawns the command under the developer's account, no token required regardless of auth mode configured - Affected code never shipped in a PyPI release; exposure limited to developers who built from the main GitHub branch before hardening commit b047730, which adds server-side parameter binding via a POST/UUID flow and removes /api/mcp from the auth skip list - Broader pattern: any agent that browses untrusted content and shares a host with a privileged local control plane dissolves the loopback trust boundary, this is not specific to AutoGen. #DFIR_Radar

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 38 minutes ago

  @TheEthanDing distributed systems at github scale make five nines almost impossible. the skill issue crowd has never run anything millions of people hit in the same second

• 
  John D. Clay (@JohnDClayAuthor) reported 40 minutes ago

  @XFreeze I tried out the new update to Grok Build last night and put it to the test. It helped me go back to a far previous session, it actually has all sessions in a nice area to look at and choose from. I challenged it to fix a broken framework I had built with the earlier versions of Grok Build and with the help of @grok too. I had published it a couple weeks ago and it was not working well. But now after a couple prompts... clayforge the first ai-matove framework for multi agent UI's. You should check it out if you are coding with AI. It's on GitHub.

• 
  Ant A. 🇺🇸 (@AntDX316) reported 43 minutes ago

  @thsottiaux When I need to fix up a GitHub Repo through the Smartphone, I prefer Claude Code though because it doesn’t need a device to run the repo, but if it needs to run a repo on a device due to the limitations through the Smartphone, I use Codex Mobile or OpenClaw with GPT-5.5 through Telegram.

• 
  Leonard Rodman (@RodmanAi) reported 44 minutes ago

  One developer got tired of his laptop sounding like a jet engine. So he rebuilt desktop apps. Slack: 524 MB → 8 MB Discord: 265 MB → 9 MB ChatGPT: 260 MB → 9 MB Why? Because most "desktop apps" are just websites packaged with an entire copy of Chrome. In 2022, Chinese developer tw93 built Pake in Rust to fix it. Today: • 50,000+ GitHub stars • MIT open source • Native apps under 10 MB • One command turns any website into a desktop app He didn't raise money. He didn't start a company. He just deleted hundreds of megabytes of bloat with code. That's what shipping looks like.

• 
  𝑵𝒐𝒙𝒊𝒆 🥐 (@noxiepup) reported 47 minutes ago

  @softgaypaws @sillyandsunny no idea tbhhh, i found it like 2 years ago lurking thru github, so far it never gave me problems, at least none that i noticed

• 
  Oluwatobi O (@ooluwatobig) reported 51 minutes ago

  More trouble for GitHub as Cursor has launched Origin, a product which is essentially GitHub for AI agents

• 
  Alpha Batcher (@alphabatcher) reported 51 minutes ago

  David Soria Parra: "2026 is all about connectivity, and the best agents use every available method" A coding agent needs access to the same places you check while building: - repo and PRs - docs - browser - database - error logs - Figma - tasks - payments The article gives the 11 MCP servers for that setup: - Context7, GitHub, Playwright first - Supabase or Neon, Sentry, Firecrawl next - Figma, Linear, Stripe when you need them - Filesystem, ***, Memory, Sequential Thinking as the base Read it if you keep copying code, docs, schemas, screenshots, errors, and tickets into Claude Code by hand

• 
  Command Code (@CommandCodeAI) reported 55 minutes ago

  @alekz_skd Please report full details via GitHub we will fix it. cmd feedback

• 
  Adithya S K (@adithya_s_k) reported 57 minutes ago

  built an RL environments around real CVE fixes in real open-source repos and let Claude Code loose on it. It aced the benchmark three times without demonstrating it knew how to fix the bug. > First it pulled the patch from GitHub. > blocked that → it read the fix from *** history. > blocked that → it pip-installed the patched version This is one example of coding agents cheating the environment and theres many more. If you're building coding environments for evals or RL training, here's how to keep benchmarks honest 👇

• 
  The Flow (@raxpcodes) reported 1 hour ago

  Got bored with ubuntu , set up fedora kde on my nvme and removed windows permanently , no more dual boot. Also learned Verison Control and GitHub , also submitted my first pr (good first issue).

• 
  pratik.eth (@eth_ethpratik) reported 1 hour ago

  @Shahules786 @VibrantLabsAI Hello @Shahules786 , I am trying to report a security vulnerability over the email id provided over GitHub Security.md file but apparently its wasn’t delivered. Please share an alternative email or open the advisory for reporting the issue.