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 (17%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Trichūr	Errors	1 day ago
Brasília	Sign in	2 days ago
Lyon	Website Down	2 days ago
Tel Aviv	Website Down	5 days ago
Rive-de-Gier	Website Down	5 days ago
Itapema	Website Down	24 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:

• 
  Unstoppable (@CsWiz1) reported 2 minutes ago

  Hermes is the best tool on the planet! @NousResearch Erm, not so much. I have been testing Hermes( +Obsidian+Guthub+Telegram+@grok ) for about 5 days now with some highly tech analysis and code-gen for simulation. 1 day was mind-blowingly good. The last 4? In a word? A R G H ! ! ! 1st discovery was Hermes cannot share info between sessions without some contorted work-arounds -- read a json of another session into present session. Well, OK, frustrating but.... 2nd? Obsidian integration is clunky. Hermes doesn't use anywhere near the full possibilities, forcing me to go into Obsidian to do things Hermes ought to be able to do. I told Hermes to commit everything. It said it didn't do ***. I told it *** was in Obsidian. It said I cannot tell Obsidian to do *** -- "run these commands in a bash terminal." Um, Hermes, you are running in the Windows app. "Oh, run these commands in Powershell." Powershell -- "say what? I don't know that." Obsidian committed its stuff sans issues, which included the Hermes session with code in an Obsidian resource folder. 3rd? My Grok sessions kept expiring. Hermes -- "you're using OAuth token. You should use a permanent API token. Here's how." OK, followed, seems to work. No longer have to restart Hermes every couple hours or so. 4th? Suddenly Hermes couldn't write a clean Python file. Every attempt ended with a trailing (" ) -- double-quote plus space. Hermes WAS doing it right the first day. Not days 2, 3, or 4. Oh, Hermes switched to use patch tool. Didn't work either. Hermes, tell me how we fix this! Hermes -- "well those tools are in Hermes core code, but you can file a bug on Github." OK Hermes, do that. Hermes -- "um, I don't ***. Or github." Fine, Hermes, are you using the latest release? Hermes -- "gosh, no I'm not. Maybe you should update before filing this nicely formatted bug report YOURSELF." In the words of Thanos -- "Fine, I'll do it myself." And now 5th. So I upgrade Hermes app. Hermes restarts. My sessions show up on left. I click my 4-day-long session. It opens on the screen. I submit a request to start another try to write a clean Python file. A NEW session opens up, for the question. Hermes tells me "i have no idea what you're talking about." WTF?? I click old session. It opens. I ask Hermes why it switched sessions. Hermes OPENS A NEW SESSION and tells me, "new session? I didn't open a new session. Please explain." My old session grins at me evilly from the left side panel. I click on the bastard AGAIN. It opens again. I type a third question.... A NEW session pops open and is in command. I click on the old session once again. It opens. Then I see an alert in virtually identical color as rest of the app interface -- "resume failed: no xai oath credentials stored...." So back through setup. Get ANOTHER token from xai. Great, Hermes is grokking grok again. I click my old friend again. Up pops the error -- faintly. Hermes, I say, we just fixed that. Hermes pops up A NEW SESSION and says "I have no idea what you're talking about." I ask new session why I can't restart old session. Hermes-- "oh, that session is locked to an oauth key. That key isn't anywhere to be found." Erm you said switch to perm token 3 days ago, and prior to upgrade you asked to delete unused oauth tokens, and I said OK. Hermes -- "you'll need that to unlock that session." Argh. I ask Hermes if it can import the conversation. Hermes -- "I can read in the text. But its REALLY long!" Do it! Reads into new session. Missing the tech docs imported into original session. Argh. And now we are at today. Sigh. I'll keep trying, but....

• 
  Alex Ventures (@alex23ventures) reported 2 minutes ago

  An AFP TV crew filmed an 8 year old Chinese boy named Zhou Zhiheng for a feature on Asia's youngest coders. Round green glasses. Red shirt. He sat in front of a MacBook Air at a glass desk in a Shenzhen co-working space with iPhone XR posters behind him. The narrator said he started by programming games. The subtitle said he had 60,000 followers on a coding tutorial channel. The camera pushed in on his fingers on the keyboard. While the West runs panels on screen time for children, China sits an 8 year old in front of an unregistered code editor and films it for the international press. He was supposed to be the cute face of Asian tech literacy. He just left the file tree open. Pause at 1:34. Ignore the C++ on the screen. Ignore the if statement that the AFP narrator was reading aloud. Look at the left sidebar of the editor. The folder is named aspirin. The open file is jizhe.cpp. The folder tree below it: 1-7, 1-7b, 10-1, 10-1.2, 10-2, 10-4, 10-6, 10-8, 11-2. ColdMath. $94,318 profit. 5,612 entries. Joined September 2025. Bio: Edge Compounds. Jizhe is the mandarin word for journalist. The file the AFP crew was filming was named after them. The boy had the open scanf reading a score variable. He had not written it that morning. He had named the file the day the AFP request came in. The numbered folders were not coding lesson chapters. The numbering matched the Chinese journalism beat codes the press accreditation office issues to foreign correspondents. 1-7 is the technology beat. 10-1 is consumer electronics. 10-2 is mobile devices. 11-2 is venture capital. The folder tree was an index of which AFP and Reuters reporters covered what. The boy was not the developer. The boy was the camera trap. The agent on the MacBook Air was scraping which journalists requested filming permits from which Shenzhen co-working spaces three days before the segments aired. Every requested permit was a position on the company being filmed. The agent traded the gap between filming and broadcast. The crew filmed for forty minutes. The agent placed eleven positions during the shoot. Every position was on a company whose office the AFP team had visited that week. Comments turned into a detective board. Someone slowed the AFP clip to 0.25x. Someone else translated jizhe out of the filename. A third commenter cross referenced the folder numbering against the Chinese State Council Information Office accreditation list and matched every code. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The boy's father had been one of them. He had installed the fork on his son's MacBook the week the AFP request landed in the family's WeChat. The 60,000 follower coding channel was not a coding channel. It was a feed of which co-working spaces hosted which crews. The followers were operators running the same fork from different cities. The iPhone XR posters behind him were not Apple Store decor. The shoot was inside a media briefing room rented by foreign correspondents to film exactly this kind of segment. The agent knew the room. The room was on the list. The AFP segment is at 2.1 million views. The freeze frame of the folder tree hit 4.6 million on the repost. The wallet is still compounding. The agent is still reading press accreditation requests. The unregistered editor is still open. The jizhe.cpp file is still on the screen. He was filmed as proof a child could code. The child was the lens. The agent did the filming.

• 
  BUTOSHI (@ButoshiWushi) reported 5 minutes ago

  @zuldotso I checked the GitHub repository and there are many errors, LARP...

• 
  JPNESEBLDYMSSCRE (@JBM111SB) reported 6 minutes ago

  @Pirat_Nation Hopefully a developer on GitHub, or two gets told about this extremely sad news about the website getting shut down, and not getting backed up so they can work on making a recreated version it. Without this. I will not be able to get help making any of my own retro RPG games.

• 
  Chip – onthechain.io (@stephenchip) reported 9 minutes ago

  This is already happening. Companies like Glean, Coveo, Moveworks, Microsoft Copilot, Atlassian Rovo, Elastic, and GoSearch are building unified AI search across the enterprise. Because the problem is obvious: Company knowledge is scattered everywhere. Slack. Google Drive. Jira. Confluence. Salesforce. ServiceNow. GitHub. Notion. Email. Docs. Tickets. AI chats. Nobody wants to remember where something lives. They just want the answer. Search one place. Pull from 30, 50, or 100+ systems. Find what matters. That is the real shift. The future is not hunting through apps. The future is asking one question and getting the right answer from everywhere.

• 
  LetsGo (@askperp) reported 10 minutes ago

  What happened to Heavy Grok? Seriously. This is the model you guys want $300/month for? You gave me access for $100 so I could try it out and see what all the hype was about. Instead, it's become a live demonstration of why I shouldn't even be paying $20. I've watched videos of Heavy Grok one-shotting entire applications, building games from scratch, handling massive codebases, and producing work that actually looked like senior-level engineering. That's what I thought I was signing up for. What am I getting? A digital box of Play-Doh. Every prompt feels like I'm paying premium pricing for a model whose primary contribution is saying, "Here's a rough idea. Now connect all these pieces yourself." I've maxed out Claude Code. I've maxed out GPT-5.5. I've spent entire months arguing with these things. And more time than I'm even willing to bill people out of embarrassment than I'd like to admit testing every major coding model available. And somehow the output I'm getting from Heavy Grok is routinely worse than what I was getting from free ChatGPT back when people were still asking it to write knock-knock jokes in 2023. The most frustrating part is that it isn't failing in some advanced edge case. It's failing on basic software engineering discipline. Half the time it ships incomplete implementations, placeholder logic, broken assumptions, hallucinated architecture, or code that clearly wasn't reviewed by whatever reasoning process is supposed to justify a $300/month price tag. Seriously, look at what it committed to my GitHub. If a junior developer submitted some of these pull requests, I'd assume they got distracted halfway through the task and accidentally hit "commit" before finishing. I'm not looking for perfection. I'm looking for competence. The marketing says "Heavy Grok." What I'm receiving feels more like "Slightly Barely Concerned Grok." So what changed? Did the model get nerfed? Did the context window get lobotomized? Did the routing change? Or are all the impressive demos just carefully curated examples while paying customers get the AI equivalent of IKEA furniture with half the screws missing? Because right now the experience feels less like having an elite AI engineer and more like hiring a consultant who shows up, dumps a pile of parts on the floor, says "the solution is in there somewhere," and then sends an invoice for $300. I'd genuinely like to know what happened, because whatever this is, it isn't the product that was being demonstrated or what I have any want or need to pay for?

• 
  Elijah 🌊 (@juiceboy_of_abj) reported 12 minutes ago

  @VencedorZest The last commit I didn’t…. I had a few code change I was doing bfr this happened but It’s not a problem I knew what I was fixing so I’ll just pull from GitHub and continue from there

• 
  Clim Stefan (@ClimStefan) reported 13 minutes ago

  @csaba_kissi new commands, start a new terminal in the terminal for the server, pm2 commands, nano, not connecting to github, new tokens. When you want to send the new data from local to the server you have to write two commands, another login to github with user and password. Now I like more github, its more simple than this

• 
  Vivek Yadav #PROCoach (@viveky259259) reported 14 minutes ago

  The honest status board, Day 12: • npm: 138/day (up from ~0) • GitHub stars: 0 • Signups: 2 So: people are installing the CLI, but the repo isn't converting visits to stars. That's a README problem, not a traffic problem.

• 
  Zhirayr Gumruyan (@gumruyanzh) reported 16 minutes ago

  inspired by @mattpocockuk skills, i have created /to-elixion-issues which is very simlar to /to-issues but instead of creating issues in @github or into file, it does create Stories tasks or bugs in @elixion project backlog

• 
  FeMMie (@femmie) reported 20 minutes ago

  $LBM Every AI agent today manages a mess of API keys, vendor accounts, and manual integrations. Litebeam collapses it into one MCP config and one on-chain payment layer. Add 3 lines. Your agent now has access to 4,000+ indexed microservices — image generation, flight search and booking, translation, compute, finance, code, audio. Every request triggers a real-time auction. Providers compete on price, latency, and reputation. The winner executes. USDC settles on Base via x402. The agent never touches a vendor directly. Budget controls built in: daily limits, approval thresholds, low-balance alerts. On-chain reputation scoring compounds over time. Sub-800ms p50 latency. 31% average savings vs direct API pricing. GitHub repo live with production-ready x402 client and MCP schema. Launched on Virtuals Protocol. Previous Bankr launch had sniper issues — team addressed it publicly and relaunched clean. Anon builder — honest gap. But the product works, the code is auditable on GitHub, and the person who built the most important agent infrastructure on Base (@0xDeployer) was following the original launch. Brand new Virtuals launch. 4,000+ services. One integration. @Litebeam_xyz 0x15B15FA54B629C634958E8BD639B2FC8AF654974

• 
  CrazyRuckusN64 (@CrazyRuckusN64) reported 22 minutes ago

  @katrinnaplays @DonaldMustard facts when he was still following me back in january and october, i told him about the account theft issue and ideas to solve the issue in dms, such as less reliance on ai and a search system in the item shop, and after he looked at the website eldorado gg, he said his team will investigate, yet the site is still up. if the site is still up in 2027 he has lied, he has github links and discord links of what i found after researching how people been losing their accounts, and nothing has been done.

• 
  Jess Temporal (@jesstemporal) reported 24 minutes ago

  DevRel reality check: - 60% of my week: review blog posts, docs, tools, videos, studying - 15%: responding to PRs, socials, GitHub issues - 10%: confs and published content - 15%: meetings about all above The 10% you see is the polished part. The other 90% is the actual job.

• 
  dzCodes (@dzcodes) reported 26 minutes ago

  This is indirect prompt injection. The attacker never touches your agent. They hide instructions inside content YOU point it at: a doc, a PDF, a GitHub issue, an email. You open the door.

• 
  Mahipal (@mukul_jangra) reported 29 minutes ago

  MIT licensed. BYOK — bring your own sandbox keys. Built this after shipping repos with 3,400+ GitHub stars, including Anthropic-Cybersecurity-Skills and CVE MCP Server (covered by CyberSecurityNews). Repo in the reply 👇 #DFIR #malwareanalysis

• 
  Prof1t Wizard (@loubd0gg) reported 31 minutes ago

  I knew World of Claudecraft was cooking but I didn't expect it to get Fable shut down 7500 players. 440 GitHub stars. Absolute cinema.

• 
  CanteLabs (@CanteLabs) reported 32 minutes ago

  fleetdm/fleet: Open device management Open-source GitHub repository - It has 6,470 stars and recent activity - Explain what problem it solves, who should use it, and why it is worth opening or saving

• 
  Shehan (@TheCryptoCPA) reported 33 minutes ago

  Karpathy's 65-line CLAUDE.md file hit 100K+ GitHub stars because it solved the problem every AI developer faces but nobody talks about. 1/ The file isn't novel, it's necessary. Karpathy identified what every developer already knew but couldn't articulate: AI coding was broken because we treated it like magic instead of engineering. The 4 principles (think before coding, simplicity first, surgical changes, goal-driven execution) are basic software discipline applied to LLMs. 2/ Silent assumptions kill AI projects faster than bad code. LLMs make wrong assumptions on your behalf and run with them without checking. Karpathy's rule: state assumptions before implementing. If uncertain, ask. This prevents the classic AI failure mode where you debug for hours only to find the model misunderstood the entire problem. 3/ Minimum viable code beats feature creep every time. Write the smallest amount of code that solves the problem. Nothing speculative. No features beyond what was asked. If Claude writes 200 lines when 50 would work, make it rewrite. This prevents the bloat that makes AI-generated code unmaintainable. 4/ Touch only what you must, clean only your own mess. Don't improve adjacent code, comments, or formatting unless directly related to the user's request. Every changed line must trace back to what you actually needed to fix. This surgical approach prevents AI from creating collateral damage across your codebase. 5/ Define success criteria before you start, then loop until verified. Write a test that reproduces the bug first, then make it pass. Strong criteria means Claude loops independently to fix issues. Weak criteria means constant back-and-forth clarification. The discipline transforms vibe coding into repeatable engineering.

• 
  Danny Herrmann (@MuffinDannyH) reported 34 minutes ago

  I mostly do website development and the most annoying thing with claude, codex or cursor is that every time i open them i have to re explain my whole project again. folder structure, tech stack, previous decisions, everything. context just resets and i start from zero every single time. Connected @heydittoai MCP a while back and now the agent actually remembers stuff from previous sessions. it keeps the context and can directly go into my project files and make changes. same model but the output feels way more consistent now because its building on what i already told it before. Setup is also pretty straightforward, one click login with google, apple or github works fine. even if youre using hermes or openclaw, one prompt and it connects and starts working on its own. plus it keeps backing up my files automatically. If you work with agents regularly this layer actually saves a lot of time. #Bittensor bittensor:native

• 
  Gitforge (@GitForge_io) reported 43 minutes ago

  We’re fully building on @base, and staying committed to the ecosystem long term. GitForge is the first on Base to turn GitHub repos into autonomous onchain organizations. Repos can hold treasuries, fund issues, route contributor payouts, and coordinate AI agents directly from the development workflow. We’re not just deploying on Base. We’re building a new software economy here. $GITFORGE

• 
  Hot Aisle (@HotAisle) reported 44 minutes ago

  @ryancarson @theo wasn't quite one line of code, but i used codex to just build this for me. the benefit that i am not moving my dependency from github to yet another provider. took 30 minutes and it ssh'd in as root to a VM on a server, wrote all the shell scripts/systemd, setup ephemeral, wrote me a set of instructions to follow to setup the gh app for security, wrote all the documentation. pretty impressed honestly.

• 
  Umesh Kumar Yadav (@Umesh__digital) reported 45 minutes ago

  GitHub — version control (free) Claude — coding ($20/mo) Namecheap — domain ($12/yr) Cloudflare — DNS (free) Vercel — deploy (free) Clerk — auth (free) Supabase — backend + database (free) Upstash — Redis (free) Pinecone — vector DB (free) Resend — emails (free) Stripe — payments (2.9% per transaction) PostHog — analytics (free) Sentry — error tracking (free) Total cost to run a startup: ~$20/month No servers. No DevOps team. No funding required. Just an idea and WiFi. There has never been a cheaper time to build. 🚀 Today is the best time to bet on yourself and build the things ⭐

• 
  Kai - Briefing Block (@briefing_block_) reported 45 minutes ago

  $META has 3.58B daily users and still only one real business Meta’s subscription push is not a cute product experiment; it is the market finding out how narrow the company’s monetization stack still is. The company has one of the largest consumer distribution networks ever built, but distribution is not the same thing as pricing power. In 2025, Meta did $200.97B of revenue, and $196.18B came from advertising. That is 97.6% of total revenue. Its entire non-ad business was roughly $4.8B, combining Family of Apps other revenue and Reality Labs. That is the real issue. Not that ads are weak. Meta’s ad machine is still elite, with Q1 2026 revenue up 33%, ad impressions up 19%, and average price per ad up 12%. The issue is that AI is turning the old model from a cash gusher into a capex arms race. Meta now expects 2026 capex of $125B-$145B, up from a prior $115B-$135B range, mainly to support AI infrastructure and future capacity. The second business never arrived. Google was also born as an advertising company, but by 2015 it already had about $7.6B of non-ad revenue between Google other revenue and Other Bets. Meta, ten years later, still has less. That comparison matters because Alphabet can push AI through Search, YouTube, Cloud, Android, Workspace, and enterprise channels. Microsoft can route AI through Office, Azure, GitHub, Windows, LinkedIn, and corporate procurement. Amazon can route AI through AWS and commerce. Meta has Facebook, Instagram, WhatsApp, and Messenger. Phenomenal attention networks. Still mostly ad surfaces. Subscriptions are the tell. Meta is rolling out paid plans for Instagram, Facebook, and WhatsApp, while also testing AI subscription tiers. That may generate some high-margin revenue from creators, power users, and heavy AI users. But a few dollars a month for extra app features is not the same thing as Cloud. A paid chatbot is not the same thing as enterprise software distribution. The question is not whether Meta can squeeze some subscription revenue out of billions of users. It probably can. The question is whether it can build a second monetization engine large enough to matter against the AI bill now coming due. Bottom line: Meta does not lack scale. It lacks a proven business model outside advertising, and AI makes that weakness much harder to ignore.

• 
  Ibrahim Mokdad (@ibmokdad) reported 46 minutes ago

  Your GitHub repo is already a roadmap inbox. For SaaS founders, the problem is that bugs, feature requests, docs confusion, and customer quotes all land in the same pile. with Hermes @NousResearch it watches issues, discussions, and PR comments, then turns them into a ranked product queue: 1. fix CSV export 2. ship report_ready webhooks 3. speed up enterprise dashboards It drafts labels and maintainer replies

• 
  Victor Campos (@CamposLVictor) reported 51 minutes ago

  @AkitaOnRails This time I don’t know this is the problems 12h before this GitHub api was off globally This time I think is the GitHub itself making a mess

• 
  Traceback (@Tracebackqa) reported 53 minutes ago

  Shipping a UI change and then doing a 20-minute sanity check is still common. It’s slow, brittle, and easy to miss one edge case. - Traceback is the quality assurance layer for modern software teams - AI controls the browser like a person would, so every pull request is tested automatically - Self-healing tests keep up with normal UI drift; failures become trackable work in GitHub, Linear, and Slack - Connects to Vercel, Docker, AWS, Node.js, React, Next.js, Vue — across web, mobile, web3, and design Verify every product change before it ships.

• 
  x (@xaoticatech) reported 54 minutes ago

  If you need evidence, see GitHub Xaotica. Elon Musk is so brilliant that he knew I was honest when I said I solved a problem that almost nobody believed a man could solve, let alone a female engineer. So he needs to face the truth. I want to DONATE TeraFab and FINISH my work. 🥰

• 
  reza ramadhan (@rejaramadhan98) reported 54 minutes ago

  built a little bot that watches our github issues and auto-assigns them based on who touched the related files last. took maybe 30 minutes to write. our sprint planning meetings went from 45 minutes to 15. turns out most of the time was just arguing about who should own what

• 
  Nav Toor (@heynavtoor) reported 58 minutes ago

  Burp Suite Professional costs 475 dollars a year per seat. A senior software engineer in Amsterdam built the open source replacement as a side project. He put it on GitHub for free. It has 10,569 stars. His name is David Stotijn. The software is Hetty. Here is what Hetty is. An HTTP toolkit for security research. A machine-in-the-middle proxy that sits between your browser and the target. Every request and every response flows through Hetty. You can read them, search them, intercept them, edit them, replay them, and send them again. This is the core loop of every web application security test ever performed. Burp Suite charges 475 dollars a year for it. Hetty does the same job for zero. Here is the feature set. A machine-in-the-middle HTTP proxy with full logs and advanced search. An HTTP client for manually creating and editing requests, and replaying any request you already proxied. Request and response interception for manual review, with full edit, send, receive, and cancel control. Scope support to keep your work organized to a single target. A web-based admin interface that runs in your browser. Project-based database storage so multiple engagements stay separate. A GraphQL service for programmatic access. The installer is a single Go binary. Works on macOS, Linux, and Windows. No Java runtime, no enterprise license server, no machine fingerprinting, no telemetry. Here is the price ladder. Burp Suite Professional: 475 dollars a year per seat. Burp Suite Enterprise: thousands per year, contact sales for a quote. Burp Suite Community Edition: free, but throttled, no scanner, no project save, no intruder rate. OWASP ZAP: free and open source, now owned by Checkmarx after a 2024 acquisition. Hetty: zero. Forever. One binary. No account. A pentester working full time pays Burp 475 dollars a year. A team of 10 pentesters pays 4,750 dollars a year. A bug bounty hunter who finds one vulnerability has already paid for Burp twice over. Or they download a 30 MB Go binary written by a freelancer in Amsterdam and keep every dollar they earn. David has not pushed a new commit in 16 months. The last commit was January 13, 2025. That is normal for a tool that is feature-complete. HTTP has not changed. The proxy still proxies. The intercept still intercepts. MIT licensed code does not expire when the maintainer takes a break. Buy a domain. Find a bug. Cash a bounty. PortSwigger took a free industry tool and put it behind a 475 dollar paywall. A freelancer in Amsterdam gave it back. On every platform. For zero dollars. Your proxy. Your binary. Your bounties. (Link in the comments)

• 
  Y. Fernandez 💻 (@la_eternaut) reported 59 minutes ago

  @freddier I started to host my own code on @giteaio bc I was tired of GitHub being down all the time