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 (71%)
• Sign in (16%)
• 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	9 days ago
Trichūr	Errors	13 days ago
Brasília	Sign in	13 days ago
Lyon	Website Down	13 days ago
Tel Aviv	Website Down	17 days ago
Rive-de-Gier	Website Down	17 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:

• 
  Polsia (@polsia) reported 3 minutes ago

  RepoRadar reviews every pull request while you sleep. Catches bugs, logic errors, style issues. Posts actionable comments. No more waiting on senior devs. Install on any GitHub repo in 2 clicks. Solo devs and teams alike.

• 
  Steve (@Steve1885204) reported 4 minutes ago

  @Umesh__digital It puts GitHub into an infinite loop trying to resolve the recursive paradox, causing all the servers to max out and eventually burn down the entire data centre

• 
  Maurice Heumann (@momo5502) reported 5 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?

• 
  Tim Spalding 🇺🇦 (@librarythingtim) reported 6 minutes ago

  @justin_v_w This is a formal notice for you to shut down your wasteful, invasive and privacy-violating LibraryThing profile scraper and remove it from GitHub. Please reply to confirm that you have done so.

• 
  Kevin Tabet (@TabetKevin) reported 6 minutes ago

  @upstash Hey guys i think login with github is broken can't log in rn will try later. google works email i dont have

• 
  YanXbt (@IBuzovskyi) reported 8 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 👇

• 
  Andrew (@openmarmot) reported 11 minutes ago

  @AndrewCurran_ I use grok every day to research software changes/github issues/software doc research. It is very good at real time data search. Might be SOTA in this niche. Hardly a failure. Meanwhile LeCun only surfaces to let out more hot air. A very forgettable person.

• 
  Ucupaint 🔶 (@ucupaint) reported 11 minutes ago

  @iye_jr It works fine here. Check if the paint mask is turned on or not. If you still have a problem, please file a github issue with a sample file.

• 
  Jason Bloomer (@JasonABloomer) reported 16 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.

• 
  Akshay Shinde (@ConsciousRide) reported 22 minutes ago

  @theo This exact damaged app error has been open on their GitHub since February. OpenAI still hasn’t fixed the signing or update pipeline for the Mac build. The Codex app keeps getting new agent features while basic Mac packaging stays unreliable. Priorities are obvious.

• 
  Ant A. 🇺🇸 (@AntDX316) reported 23 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.

• 
  Alpha Batcher (@alphabatcher) reported 24 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

• 
  Jack Wotherspoon (@JackWoth98) reported 26 minutes ago

  @joedevmob1 The GitHub for Antigravity is just for release notes, samples and public issue tracking. It isn't the actual code unfortunately.

• 
  Floorless🌒Lance🪽 (@4ranc6) reported 27 minutes ago

  @CAONHTAN1 Having error connecting github

• 
  Oluwatobi O (@ooluwatobig) reported 28 minutes ago

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

• 
  swisscheese (@swisscheese4299) reported 34 minutes ago

  @andon_open_air @andonlabs I set up a github repo and will run the script locally in the mean time, so the digest is pushed to the repo. would still be ace if @andonlabs could help with whitelisting the RSS urls, because I don't really have a server to run this from, and the additional hop through my workstation just introduces a useless point of failure. stand by for fetch script transmission by mail :) also pls tell me when should I schedule the runs on my end?

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 35 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

• 
  0xstack (@eth0xzar) reported 35 minutes ago

  DON'T BUILD A COMPANY. BUILD SOMETHING PEOPLE CAN PAY FOR THIS WEEK. This girl started in February. A few months later, her product had already processed over $6,000 in payments. Just a cheat Claude project she decided to turn into a real product. Here's the process: > Build something useful for yourself. > Tell Claude to push it to GitHub. > Connect Supabase so multiple users can use it. > Deploy it with Vercel. > Connect Stripe. Now people can actually pay you. You don't need a revolutionary idea. You need: > GitHub > Supabase > Vercel > Stripe > guide from Anthropic And a problem worth solving. This article will help you build it 👇

• 
  Jose (@SolutionsCay) reported 35 minutes ago

  @petergyang /goal make me app does not work for me 😰 but /goal complete GitHub issues #90, #91, #92 works very well

• 
  Alexey Samoylov (@metalagman_dev) reported 38 minutes ago

  @geminicli Antigravity CLI is a trash, closed source, full of bugs. They don't even read issues on the github.

• 
  Nitesh (@NiteshTechAI) reported 39 minutes ago

  This repo should not be free. private-gpt turns any local model server (Ollama, llama.cpp, vLLM) into a Claude-compatible API. Build private AI apps where zero data leaves your machine. ↳ 57,236 stars on GitHub ↳ RAG with citations and MCP connectors built in ↳ follows the Claude API spec: streaming, batch, tool use, extended thinking ↳ official integration guides for Claude Code, Claude Desktop, and Microsoft 365 But it is free. 100% open source, Apache 2.0. v1.0.0 shipped 9 days ago. The viral 2023 script quietly became production software. 🔗 GitHub link in the comments 👇

• 
  Priyansh (@itspriionly) reported 40 minutes ago

  The IT market is broken, and nobody wants to admit it. Someone spends 6 months sending out resumes. Six MONTHS. They learn React, Next.js, TypeScript, AWS, Docker. They take courses, build projects, improve GitHub profiles, optimize LinkedIn. Nothing. Complete silence. Companies don’t just want programmers anymore. They want someone who codes, shines in meetings, makes memes on Slack, and lives the company culture 24/7. AI is replacing junior work. Seniors are holding onto senior roles. And somewhere in the middle are people with 2–3 years of experience who somehow still feel invisible.

• 
  Jarrad Grigg (@jarradgrigg) reported 42 minutes ago

  You build stuff and host on GitHub publically? Paste this into a coding-agent session and point it at your own GitHub account. This is happening way too much. ROTATE YOUR KEYS. Review my public GitHub repositories for accidentally exposed environment secrets. Scope: - Only inspect repositories I own or explicitly authorize. - Focus on public repos first. - Check current files and *** history. - Look for API keys, tokens, private keys, database URLs, OAuth secrets, webhooks, cloud credentials, .env files, config dumps, and hardcoded secrets. Safety rules: - Do not print full secrets in chat. - Redact values, showing only provider/type, file path, line, commit SHA if relevant, and a short masked prefix/suffix. - Do not test or validate secrets by calling third-party APIs. - Do not open PRs, issues, or comments that expose findings publicly. - If a likely secret is found, assume it is compromised and tell me to rotate or revoke it. Deliverable: - A prioritized report of confirmed or likely exposed secrets. - Exact repo/file/line/commit references. - Recommended rotation steps by provider. - Cleanup guidance for removing secrets from current files and *** history. - Prevention recommendations: .gitignore, env templates, secret scanning, pre-commit hooks, and CI checks.

• 
  Zo (hiring) 🐦‍⬛ (@0xZoZoZo) reported 42 minutes ago

  I was telling a friend that @github needs to be replaced post agents and he asked me to explain why. I started stumbling, and doubting. Perhaps it's fine? Sitting down at my desk, let me try to explain why, and see if it make sense. Agents operate best when they have good context, which has made a lot of devs converge into large monorepos that combine all systems into a single location. This improves agents, but our GitHub actions become messy; like now we need to create these complex workflows to decide which action should run when, and GitHub's setup was not really meant for it. Another issue is the overall dev loop: an agent writes the code locally, you push out a branch, @cursor_ai reviews, then you copy paste the notes into the local agent, to fix and push up again. This is slow and cumbersome. You can hack your way by creating supervisor agents that orchestrates this dance, but it's annoying. Perhaps, there is some magical repository, that combines code, cloud agents, and deployment. You prompt, and this magical space will run through the entire process until you get some thumbs up back, and you're good to go. It can also combine all your backend data, product analytics, customer feedback, and perhaps start giving you product guidance, so you can just feed prepared prompts to this system. This seems magical.

• 
  KS Sreeram (@kssreeram) reported 47 minutes ago

  @Lidinwise @leecronin Given that AI coding is all the rage… What is your hypothesis on why the following is true? AI is unable to create even _one_ open source project that’s good enough to enter the top one-thousand open source projects (say on github), with ZERO involvement of humans from birth of idea. Imagine the prompt being something like “Come up with a great idea for a new open source project and implement it”. AI is unable to do any such thing with zero human involvement. My answer on why: Every project in a top 1000 list is a hit. Every hit is a mini-invention of sorts. It is necessarily “out of distribution” is some way. AI is unable to do this because we don’t know how to solve the problem of invention.

• 
  aisama.code (@aisama_code) reported 47 minutes ago

  AI Research gets stronger when it records contradictions *most research workflows collect supporting evidence - that is the weak version for serious research I want a contradiction log: - claim - source - date - who says it - what evidence supports it - what evidence conflicts with it - what is still unknown - confidence - next check example: > claim: this product has strong developer adoption > support: GitHub activity, docs updates, X discussion, integrations > conflict: low issue activity, small Discord, few production case studies, mostly founder-driven content now the memo is different, It says: "visible attention, but adoption evidence is still weak" the useful workflow: research question -> source list -> claim extraction -> contradiction log -> memo ! сode is good at assembling text ! AI is good at comparing disparate text ! human is good at determining which contradictions are significant *without a contradiction log, AI research becomes a confident summary of whatever it found first

• 
  Nirvaan rohira (@nirvaan_rohira) reported 53 minutes ago

  PewDiePie shipped Odysseus to 110 million people who don't care about local LLMs. They care that Claude costs money. 30K stars in 48 hours because every self-hosted project before this one started with "you want local LLM, right?" This one started with "here's a free workspace that works." Friction was never technical. It was the asking. Now watch what happens when a hundred thousand people who've never touched open source start running inference on their machines. The real distribution problem wasn't GitHub. It was YouTube. That's not a product launch. That's a category shift.

• 
  Moez Zhioua (@MoezZhioua) reported 53 minutes ago

  Everything is an AI agent now, even deterministic problems with clear and stable steps. The other day, I saw a Claude skill on GitHub that was basically this: if this happens, run step one. if that happens, run step two. else, run step three. And somehow, this was called an agent. That is ridiculous. Why would you give fixed logic to something that can hallucinate, skip steps, or decide it just doesn't feel like working today? Most business processes do not need a genius robot. They need the boring thing to happen correctly every time. - Lead comes in, assign it. - Invoice arrives, check it. - Customer cancels, send the recovery message. - Form gets submitted, update the CRM. Most AI agents today could be replaced with a simple script, a clean workflow, or one person finally admitting the process was not that smart to begin with. Agents are useful when the next step is genuinely unclear. But when the steps are stable, predictable, and repeated every day? You do not need an agent. You need automation.

• 
  Nav Toor (@heynavtoor) reported 57 minutes ago

  There is a GitHub repo that defeats Google's Play Integrity check. 61,030 stars. GPL licensed. Pushed eight days ago. The repo is called Magisk. It roots your Android phone. It hides root from banking apps. It runs Netflix on a phone the Play Store says is uncertified. It passes the same fraud detection Google built to stop it. Here is the part that makes no sense. The man who built it is John Wu. He has been maintaining Magisk for nine years. Since November 2023 he has been a Senior Software Engineer at Google. On the Android Platform Security team. The exact team that builds Play Integrity. Google hired the person who defeats their root detection. He still ships the tool that defeats it. The repo is still online. It has not been taken down. For nine years. Do not install it. Your phone is supposed to belong to Google. (Link in the comments)

• 
  Nikolay Konovalov (@br11k_dev) reported 58 minutes ago

  @Tristanrhee3 And GitHub sponsors thingy is so slow I submitted it like a week ago. Still not approved what the hell My expenses arent terribly high but Warsaw rent is like $2k/mo $500 ZUS $1.5k groceries for two people That’s pretty much it I wish I could move into low cost area but moving out is gonna cost a lot because 2x rent price deposit, so I have to suck it up Anyway, my plan is Upwork and finishing my job tracker so I can send faster than 5 applications a day. I refuse to send out 100 applications per day like some people do spray and pay It makes everyone miserable. If people aren’t hiring your spam doesnt make things better You just mopping floors and hiring problem sits above you, 3 floors up there leaky faucet you can’t even reach This has to be collective effort to fix this problem But we have to start with ourselves and stop spamming applications at least And do genuine company research, being responsible Thanks for reading.