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 (62%)
• Errors (24%)
• Sign in (15%)

Live Outage Map

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

City	Problem Type	Report Time
Bengaluru	Website Down	2 days ago
Yokohama	Sign in	2 days ago
Gustavo Adolfo Madero	Website Down	6 days ago
Nice	Website Down	7 days ago
Montataire	Sign in	10 days ago
Colima	Website Down	12 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:

• 
  Florian Ioniţă Stoic (@ionita_stoic) reported 2 minutes ago

  @github @GitHubSupport Hi, my account "isflorian-hash" appears flagged. Public profile returns 404, cannot fork or use Copilot. Submitted support form but got validation error. Can you check? Thanks.

• 
  Kaiju Hub AI (@Kaiju_Hub) reported 2 minutes ago

  @mehulmpt That's the issue though. Being required to only use their harness. If you pay for a sub and want to use your sub for headless things like a simple GitHub commit message generation you shouldn't have to open Claude code cli up to do so if wanting to use Claude. Pure control. You shouldn't be forced to pay twice. This makes any headless cli, sdk usage gated against a separate paywall.

• 
  Seregon (@SeregonWar) reported 5 minutes ago

  @MHasyimy I recommend you check the kernel logs. If you have netcat installed on your computer, connect to port 3232 to view the logs. Send the payload and, if it crashes, please report the results in a GitHub issue. Make sure your console’s firmware is compatible!

• 
  François Best (@fortysevenfx) reported 8 minutes ago

  @github Start👏by👏talking👏to👏the👏maintainers👏first. Opening a drive-by PR is likely not going to be the best experience for newcomers in OSS. If there's an issue: comment on it first. At least to say you're interested in working on it (locking it).

• 
  Chesko Dev (@CheskoDev) reported 13 minutes ago

  This tool isn’t going anywhere, I’m going to keep improving it and adding new features over time. One thing I realized is that a lot of you weren’t comfortable installing a Windows app on your PC. I get that. Even though it’s open source and you can build it yourself from GitHub As I’ve said before, I’m going to keep launching more tools and apps, and little by little we’ll build something solid together. This one didn’t land as well as I hoped (mianly because of the install thing) Ill make sure to avoid "Install" apps so we dont have the same problem again

• 
  Incultnito Studios (@Incultnito) reported 14 minutes ago

  Not entirely the maintainer story it looks like. Anthropic moved the official GitHub MCP to Go (github/github-mcp-server, 29.5k stars). The Node v2025.4.8 build is legacy — but it is still on npm and still in user configs in the wild.

• 
  Yasha (@Yasha_br) reported 15 minutes ago

  After making a heatmap of github being down, someone should actually make a heatmap from how many times a major vulnerability has happened from 2026

• 
  Tanmay Jain (@TanmayJain5114) reported 15 minutes ago

  @sflorimm my product solves the problem of me having way too much free time and zero github green squares

• 
  Robert Ta (@therobertta_) reported 18 minutes ago

  GitHub published their agents.md guide for 2,500+ repos. One thing they barely touched: what happens when your agent's tools fail. Your agent called a tool. The tool failed. Now what? Most frameworks surface a generic error and let the LLM figure it out. The LLM usually retries blindly or apologizes. After 18 months of tool failures in production, here is our recovery architecture.

• 
  Sudo su (@sudoingX) reported 19 minutes ago

  @trq212 claude code and claude browser extension connection on linux is broken dude. i've been saying this for 2 months. opened a github issue. team closed it saying it's fixed. it's not fixed. i still can't use it.

• 
  Din (@randomqazaq) reported 19 minutes ago

  8/9 37) Landing page builder from one sentence 38) RAG pipeline with evals + monitoring 39) GitHub issues manager agent 40) Multi-modal document processor

• 
  Mayank Jain (@mayankjain_11) reported 23 minutes ago

  4/ Perplexity for devs Stop Googling documentation. Perplexity pulls the latest docs, Stack Overflow threads and GitHub issues in one answer. Saves 20 mins per debugging session easily.

• 
  SaasNext (@Saasnext_db) reported 24 minutes ago

  TanStack packages got hacked through GitHub Actions cache poisoning 🤯 npm in 2026: “enterprise-grade security” also npm: `npm install` = execute stranger.exe Fix your CI: ❌ `pull_request_target` ❌ shared caches ✅ isolated runners ✅ pinned actions

• 
  Christopher Jones (@dr_chrisjones) reported 27 minutes ago

  I get terrible anxiety until I make that first commit of the day and see that GitHub square turn green.

• 
  Anas (@Anas_is_me) reported 33 minutes ago

  5/6 Note: In a real pipeline, you don’t want to see every tiny issue. You only want to stop the build for big stuff. Using --severity HIGH,CRITICAL --exit-code 1 tells Jenkins or GitHub: "If you find a major hole, stop the deployment right now."

• 
  Harsha Abegunasekara (@stanlyyaa) reported 35 minutes ago

  Finally server side rendering!! @Lovable - now we can unplug the hacked cloudflare workers and github system.

• 
  Kekko D’Amato (@kekkodamato_) reported 37 minutes ago

  @MnFounder The .well-known convention is the right call — follows RFC 8615 like OIDC discovery. Makes automated capability checking trivial. Would love to see this standardized fast so clients don't have to resort to GitHub scraping to find what a server supports.

• 
  Daniel (@MnFounder) reported 44 minutes ago

  MCP Server Cards let you expose server metadata via a `.well-known` URL. Browsers can check capabilities before connecting. Right now: you find servers through GitHub or Discord. Soon: you check a URL instead.

• 
  Kai (@kaish3n) reported 44 minutes ago

  Unable to fix this for now. We have to change the name of GitHub account and the app both. The next update and new name drops in 3 hours!

• 
  divyansh tiwari (@DivyanshT91162) reported 45 minutes ago

  Terrifying! Just using your home Wi-Fi, you can know what the person behind the next wall is doing! Open-source project RuView has already surged to over 50,000 stars on GitHub-it's blown up! No cameras needed at all, no devices to wear -just relying on your ordinary home WiFi signal to see through walls: How many people are next door, their exact positions, whether they're walking or lying down-all visible Real-time human pose detection (17 key points) Automatically measures breathing and heart rate while sleeping - Instant alerts for falls, with ultra-accurate motion recognition Using WiFi CSI + Al to turn your home router straight into an invisible radar! No video, no recordings-privacy maxed out, naturally GDPR-compliant, runs fully local, no cloud. ESP32 costs just a few bucks to play with, and Docker lets you try it with zero hardware.

• 
  kevinlee (@lbki34064963) reported 48 minutes ago

  The 'Leaving GitHub for Forgejo' post has 364 HN upvotes and 195 comments. Developers cite Microsoft's feature removals, AI upsells, and Copilot telemetry as reasons to leave. Forgejo is a self-hosted *** fork - your code, your server, no vendor dependency.

• 
  Packagist (@packagist) reported 48 minutes ago

  🚨 Security advisory: Composer 2.9.8 and 2.2.28 are out and fix a vulnerability leaking GitHub Actions new format GITHUB_TOKENs into job logs via error messages. Update now (composer self-update) or disable affected Actions workflows. #composerphp #phpc #php

• 
  🇨🇵 nexgen infinity 🇨🇵 (@nexgen999) reported 49 minutes ago

  repopulse-dashboard-14.05.2026 - Fix bad repository tag releases dont auto download - Fix github plugin - Fix forgejo and gitea plugins auto scan - Fix server.ts - add : release history - add : download status manager forauto backup repository - add new icons for sidebar icons

• 
  Gloob, head Glarkonist of the 8th Męsŷlenic Empire (@glarkonist) reported 50 minutes ago

  The jobless loser with body odour problems who have never felt the touch of another community (github devs) got up my *** last month and im still mad

• 
  OKIN | Nikolai Tjongarero (@OKIN_17) reported 51 minutes ago

  This is why self hosting @giteaio on my @start9labs server is so vital for me. I can’t trust my entire workload to Microsoft via Github

• 
  Abhinav Lal (@abhinavlal) reported 55 minutes ago

  @claudedevs just killed my custom workflow I built using Claude -p. All the joy of @github issue to @github pull request will not work as my usage js closer to $2000 in api just for this. It was fun while it lasted. Will try porting to codex today or maybe it’s time to give kimi a try.

• 
  Alexander (@richterich_) reported 55 minutes ago

  @github A good first issue is a gateway into open source

• 
  Sushil Muzumdar (@muzumdar_s) reported 57 minutes ago

  Fun experiment: deployed a production fix entirely from my phone. Stack: - Tailscale — tunnel to my Mac - Termius — SSH client for iPhone - Claude Code — AI coding agent in terminal - GitHub + Vercel — push to deploy

• 
  Kubernetes with Naveen 🇮🇳 (@NaveenS16) reported 57 minutes ago

  Never expose static #AWS keys or GitHub tokens to the agent. Use OpenID Connect (OIDC) to issue short-lived, scoped credentials per specific agent workflow or task execution. #AIAgents #DevOps

• 
  Big Al (@marlbor_bro) reported 59 minutes ago

  @EricRichards22 Sounds like a joke but asking my boomer manager to engage in some requirements analysis through a GitHub issue thread instead of countless meetings is like asking a Roman soldier to use a gun