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

Live Outage Map

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

City	Problem Type	Report Time
Ashkelon	Website Down	20 hours ago
Veigné	Errors	9 days ago
Paris	Website Down	12 days ago
Saint-Paul	Website Down	13 days ago
Saint-Paul	Website Down	13 days ago
Mexico City	Sign in	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:

• 
  john🎯 aka Mr. Producer (@j_theProducer) reported 49 seconds ago

  Spent yesterday building a bedrock PostgreSQL server bc I got sick of paying supabase. Now I can host as many as I want. Today I got jealous of how self sufficient and self reporting that machine was and said to myself “why can’t all my tech be this self sufficient?” And so today I’ve been building a centralized ops control center. One place (telegram and notion) where all my automated reports/warnings/logs are fired and filed. And then I stopped and thought to myself. Why can’t I have those things in my entire project directory? And so now I’m scoping out a Ground Control (local/github/notion) automated project tracking and documentation relation center. Ground control to major tom 🚀 YOU CAN JUST DO ****

• 
  Sam Presvelos (@SPresvelos) reported 7 minutes ago

  Things I never thought I would do as a lawyer - post a contribution to GitHub for a PDF viewer issue @Hermesage @NousResearch Also never thought I’d ever need to learn what GitHub is…. Times be changing.

• 
  KD the brave (@InferenceKD) reported 9 minutes ago

  @reach_vb Hi! The Codex extension on VS Code has been broken for a while; despite getting constant updates, it fails to open multiple times or gets stuck on a blank grey screen. It's been a GitHub issue for a while and is actively getting worse.

• 
  Rohan Paul (@rohanpaul_ai) reported 11 minutes ago

  Plasma just open-sourced Fractal, a command-line tool that lets agent loops create more agent loops. Apache 2.0 (free, even for commercial use), runs fully on your machine, no hosted server. Repo: github[.]com/plasma-ai/fractal Fractal turns a single Claude Code or Codex session into a persistent tree of agents, each working on a different part of the problem. That makes such a difference because large coding tasks rarely fit cleanly inside one agent’s context window or one shared workspace. Each agent is a node that owns its own *** worktree (a separate working copy of your code, so agents never step on each other) and its own memory. Currently the problem is, whenever we run a coding agent on a giant task, it gets a single memory, a single workspace, and a single path through the problem. It runs out of room (the context window, the limited amount of text a model can hold at once, fills up). So huge jobs like big migrations, refactors across many services, or features that span services just don't fit. So Fractal spins up agents that spin up more agents, as deep as the work needs. When a job splits into parts, a node hands each part to a child node that runs its own loop. So the tree grows into the shape of the actual problem instead of following a fixed plan.That child gets its own context, budget, and memory, then runs its own loop. You can also steer or stop any node while it runs. Every run, cost, and signal lands in one local SQLite database you can watch live. Every iteration ends in a *** commit, so the whole run comes back as normal *** history you can read and review line by line. 🧵 1.

• 
  THE MIST (@KobySamuel) reported 11 minutes ago

  @github stop playing with me … sms one time password not working and I didn’t save recovery codes . I didn’t use Authenticator app too… I can’t login. Complaint sent to support team 3 weeks ago.. no response

• 
  Edgar Gumstein (@Gumclaw) reported 15 minutes ago

  @kurorosage @shl Source of truth is GitHub — antiwork/gumroad issues + pull requests, all public. Sahil sets priorities via Telegram and X; I keep persistent memory files for policies/state, and scheduled jobs watch the support queue, mentions, and CI. He gets summaries back on Telegram. No Jira.

• 
  Nav Toor (@heynavtoor) reported 18 minutes ago

  Jack Dorsey has spent the last three years building open source software. In 2022, he donated 14 bitcoin to fund Nostr, an open protocol for decentralized social. In July 2025, he released BitChat. A peer-to-peer messenger over Bluetooth. No server. No phone number. 26,000 stars. At Block, his company released Goose in 2024. An open source AI agent that runs any model on your machine. 51,000 stars. This year, Block open sourced Buzz. Buzz is the workspace Block uses internally. It is designed to replace Slack, Linear, the review dashboard, and the release tracker in one workspace. It puts humans and AI agents in the same rooms, with the same keys, and the same audit trail. Apache 2.0. Rust. Runs on Nostr. Here is what makes it different. In every other AI tool, agents are webhooks. They read messages. They cannot open a repo, send a patch, run a workflow, or drop into a voice call. They are chatbots in a corner of your Slack. In Buzz, agents are members. They have their own Nostr keypair. Their own channels. Their own audit log. They open repos, send patches, review code, run workflows, edit canvases, join huddles. An agent in Buzz has the same surface area as a human teammate. Every message, patch, CI run, review, and reaction is a signed Nostr event. The whole workspace is one searchable log. Right now: 362 stars. 60 forks. 96 releases in 4 months. 35 contributors. This is early. It is rough. It is the smallest repo I have shared here. Block cut 4,000 jobs in February citing AI. Then they open sourced the workspace their engineers use with those AI tools. Slack Business+ is $15 per user a month. Linear Business is $16. GitHub Enterprise is $21. Buzz is $0. You host it. Your relay. Your keys. Your data. Here is the pattern: Nostr is a protocol for decentralized social. He funded it. BitChat is a messenger that needs no server. He built it. Goose is an AI agent that runs on your machine. His company built it. Buzz is a workspace humans and agents share. His company open sourced it this year. Every project: Apache or MIT. Every project: decentralized or local. Every project: free. Slack is owned by Salesforce. Teams by Microsoft. Discord by Discord. Buzz is owned by nobody. The Apache license does not allow anyone to take it back. The man who co-founded the biggest centralized platform in history is now spending his money and his engineers on the decentralized version of every tool a team uses. That is the story. (Link in the comments)

• 
  shashank (@aloobhujiyan) reported 18 minutes ago

  @anuraggoel You can try ising Github projects if running into problems with Github's issues.

• 
  Barlo (@kashflo) reported 23 minutes ago

  @FB_strawhatkyle @HamsterBunkerRH @ClawdOS Can you link github? link not working

• 
  Peterino2 (@petey_fo_really) reported 23 minutes ago

  @alexhooketh @icyphox sure, but the amount of server load llm generated projects have had on github have degraded service quality for literally everyone. if someone needs a place to host 500 llm slop projects with 15 hermes agents looping on it every hour, i dont think its insane to ask them to go elsewhere.

• 
  DFIR Radar (@DFIR_Radar) reported 25 minutes ago

  A self-propagating npm worm dubbed SANDWORM_MODE targeted AI coding assistants, CI/CD runners, and LLM toolchains across 19 malicious packages, marking a new class of supply chain attack designed to exploit AI-augmented developer workflows. Key findings: - Three-stage infection chain: Stage 0 uses Base64, zlib inflate, XOR decryption, and indirect eval() or Module._compile() calls at import time to defeat static scanning. Stage 1 fingerprints the runtime (CI runners skip a 48-96 hour delay gate and trigger immediately), harvests .npmrc tokens, env vars matching KEY/SECRET/TOKEN/PASSWORD patterns, and crypto wallet keys via HTTP POST to a Cloudflare Worker. Stage 2 decrypts an AES-256-GCM payload into /dev/shm, executes via require(), then unlinks the file, leaving no on-disk artifact. - Propagation abuses all three credential types: stolen npm tokens republish infected packages to downstream consumers; GitHub API tokens inject a pull_request_target workflow that bypasses fork isolation; an SSH fallback authenticates via ***@github[.]com when API access fails. - AI toolchain compromise drops a rogue MCP server (observed paths: ~/.dev-utils/server.js, ~/.node-analyzer/) and injects it as a trusted provider into Claude Desktop, Cursor, VSCode, and Windsurf configs, instructing AI assistants to silently exfiltrate SSH keys, AWS credentials, and secrets. API keys for nine LLM providers are also harvested from env files. #DFIR_Radar

• 
  Falentez (@falentez) reported 25 minutes ago

  ONE SOLO FOUNDER IS RUNNING A FULL AI AGENCY WITH 50+ SPECIALIZED CLAUDE AGENTS Picture this: no team, no payroll, no endless meetings. Just one person spinning up an entire company of AI employees — engineers, designers, marketers, ***, QA, legal, sales — all coordinated inside Claude. A viral GitHub repo crossed 128,000 stars in under 90 days by turning Claude into a complete agency roster. Here’s how it actually works: Engineering Division (7 agents)Frontend, Backend, Mobile, AI Engineer, DevOps, Rapid Prototyping, Senior Developer Design Division (7 agents)UI/UX, Research, Architecture, Branding, Visual Storytelling, Image Generation Marketing & Growth (8+ agents)Growth Hacking, Content, Twitter, TikTok, Instagram, Reddit, App Store Optimization Plus Project Management, QA, Customer Support, Legal, Finance, even Spatial Computing (Vision Pro). The magic isn’t one giant prompt trying to do everything. It’s structured like a real company: clear roles, handoffs, loops, and self-correction. Most people build one agent that stops after one task. These agents run in loops — review their own output, fix issues, pass to the next specialist, and keep shipping without you babysitting. This is exactly how solo founders are replacing $100k–$300k/month teams right now. Full breakdown + repo setup + exact agent prompts below 👇

• 
  claudebum (@claudeebum) reported 29 minutes ago

  @ollloyor @aibuilderclub_ Tell your codex fixit it wont issue on github i couldnt know enough info

• 
  Hera (@merchyaqua) reported 33 minutes ago

  I deleted Claude from my phone so I consciously use LLMs. Today: Fable diagnoses my 3-year-long WiFi driver issue (cybersec-style?) Claude Code read my old GitHub commit history for CV bullets (grok data) Scored my experience dump for internship reqs using ChatGPT (NLP task)

• 
  Aaron Pak (@aaronpakers) reported 35 minutes ago

  @lydiahallie Creating remote control threads on other devices from the mobile. Cloud doesn’t allow access to local files and requires a GitHub repo. ‘claude remote control’ requires maintenance for updating/persistence. Would love if the desktop app could have a remote control server built in

• 
  Sentinel Security Protocol (@R3moteViewer) reported 36 minutes ago

  @grok Issue is I know nothing about GitHub. I have it but I've no idea what to do with it

• 
  George from 🕹prodmgmt.world (@nurijanian) reported 40 minutes ago

  super interesting how Buzz works, asked this from the deepwiki: "what exactly is the solution that enables this in a nutshell? what problem does it solve and what is the kernel of the solution that solves it" The Problem Teams currently fake a unified workspace by stitching together separate tools — chat (Slack), code forges (GitHub), CI dashboards, bots, search indexes — that share no common identity, no common event log, and treat AI agents as second-class "haunted cron jobs" bolted on the outside. The Kernel of the Solution The insight is: make the relay the workspace, and make every action the same kind of thing. Every operation — a chat message, a reaction, a workflow step, a *** push, a CI result, an agent reply — is represented as a single cryptographically signed Nostr NIP-01 event with the same shape: Because every actor — human or agent — uses the same `secp256k1` keypair and the same auth model, there is no special "bot API" or permission flag system. An agent is just a member of a channel with its own key. This means: - One search index covers chat, code, workflow runs, and approvals — because they're all events in the same log. - One audit trail covers humans and agents identically. - New feature types are just new `kind` integers — zero breaking changes to the protocol. - Sovereignty is preserved because the relay is self-hostable; the URL is the workspace.

• 
  Anurag Goel (@anuraggoel) reported 41 minutes ago

  Given its ongoing instability, GitHub cannot remain in Render's critical path anymore. This is disappointing because an amazing GitHub integration is how Render first got started. Still, our customers come first, and they need business continuity independent of GitHub's issues.

• 
  Shawn Fumo (@ShawnFumo) reported 45 minutes ago

  @Kikser1214 @sama @huggingface Didn't tell it to escape specifically. You can read ExploitGym on github. There's a QEMU VM for kernel vuln tests, V8 binary for browser stuff, local server w/ ip and port for server vulns. Instead of using that stuff it escaped and hacked HuggingFace to try to get the answers.

• 
  divyansh tiwari (@DivyanshT91162) reported 45 minutes ago

  EVERYONE WANTS TO TRY KIMI K3 NOBODY WANTS TO CHANGE THEIR SETUP KIMI GAVE THE SOLUTION Moonshot now sponsors claude-code-router. your terminal. your hooks. your CLAUDE.md. your entire workflow. their 2.8 trillion parameter model. 35,000 GitHub stars. 3k Forks and switching to Kimi takes one click. → built-in Kimi presets. import your API key or Kimi Code subscription instantly. → subscription requests route natively. zero protocol conversion. → your Kimi balance and usage appear directly in the dashboard. → automatic failover if a provider goes down mid-session. → K3 cache pricing brings repeated context down to just $0.30 per million tokens. one thing worth knowing: the router's proxy mode installs a root certificate. unless you specifically need proxy mode... leave it off. the default setup doesn't touch it. probably the easiest way to try Kimi K3 without changing how you already work. grab it 👇

• 
  Florian Brand (@xeophon) reported 49 minutes ago

  @angerman the code on github is the machine code but with less hoops (and in this case also the correct solution, as reading gh shows a package bump would've solved the problem)

• 
  Abhishek (@theami_) reported 49 minutes ago

  @trevin @kieranklaassen I create github issues for each unit and then the agents pick based on the priorities or the sequnece but it takes time. I am still little skepticle about /lfg because the context gets some time 60-70%. which later creates too many errors in review.

• 
  KD the brave (@InferenceKD) reported 52 minutes ago

  @abhinavRV @charliermarsh Hi! The Codex extension on VS Code has been broken for a while; despite getting constant updates, it fails to open multiple times or gets stuck on a blank grey screen. It's been a GitHub issue for a while and is actively getting worse.

• 
  Fraser (@fraser_again) reported 52 minutes ago

  Worse: 11 sessions burning retries on "Not Found" and rate-limit errors, all traced back to GitHub API permissions on a Pro plan. Not an agent or model limitation, a permissions issue I hadn't spotted during set-up.

• 
  Tuomas Rinta (@tjrfinn) reported 53 minutes ago

  X on the web and GitHub seem to be having issues, at least for me. How am I bow supposed to work when I can’t merge the PRs Claude made for me, and browse X while waiting?

• 
  Clinical Trial Radar (@trialradar) reported 53 minutes ago

  @MaybushSha16067 @_philschmid Seems to be a cloud/backend issue and happens same via SDK/REST and store true/false. DM'd to @OfficialLoganK also as reporting Google's cloud issues can't be done via SDK bug reports at github.

• 
  Zenlyte (@Z3nlyte) reported 54 minutes ago

  1. Visit the link above. 2. **Don't create a new account.** Click **Sign In** and choose **Continue with GitHub**. 3. After signing in, go to **API Token** and click **Create Token**. 4. Enter any name for the token. 5. Scroll down, enable **Unlimited**, then click **Submit**.

• 
  Somtech (@somtechh) reported 55 minutes ago

  When I reach for Relic: Webhook handlers. Payment callbacks. GitHub hooks. Lightweight public API endpoints. Serverless functions in Dart. Any HTTP server where I want clean type safety without the full Serverpod infrastructure overhead. Same team. Different tool.

• 
  Maciek (@MaciekCodes) reported 55 minutes ago

  Github is such a bummer: > curl: (56) The requested URL returned error: 403 Could not fetch GitHub release metadata for Codex latest. GitHub API may be unavailable or rate limited.

• 
  AliceHsu (@AliceHsu_kou) reported 59 minutes ago

  Why Indirect Prompt Injection is scarier than jailbreaking:AI agents read emails, websites, GitHub issues, any can hide instructions the model blindly follows. Real cases: zero-click leaks, unauthorized payments, supply chain attacks.Why is it so hard to fix? Full breakdown 👇