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

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	15 days ago
Tlalpan	Sign in	21 days ago
Quilmes	Website Down	21 days ago
Bengaluru	Website Down	23 days ago
Yokohama	Sign in	23 days ago
Gustavo Adolfo Madero	Website Down	27 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:

• 
  • (@Weichaus) reported 8 minutes ago

  @RomanP918791 @clawdb0t @thsottiaux They can do that all they want, but at the end of the day, if they want to swim, rather than sink, then they need to drive down costs because (as we have seen with GitHub Copilot) it’s obscene If this continues people won’t be paying them for anything

• 
  Sam Thapa (@SThapa123456) reported 8 minutes ago

  i told claude to fix a github issue without reading the issue myself. it opened a pr. looked clean. now i'm sitting here trying to do three things at once. understand what the issue actually is. understand what the pr actually does. steer the architecture if it went the wrong way. all in the same head. in the same moment. with a slack notification from my ceo pending. something i'm realizing as i do more agentic engineering: skipping the plan doesn't save effort. it just defers all of it to the worst possible moment. @theo and @steipete aren't big fans of the talk-talk-plan-execute flow. the argument is roughly that modern agents are capable enough that the ceremony slows you down more than it helps. just let it cook. i get it. but what i'm finding for myself is that plan-first isn't ceremony, it's a cost-spreading strategy. you pay the "understand the issue" cost when it's cheap, before anything is built. you pay the "shape the solution" cost at the plan stage, when changes are one sentence instead of a re-implementation. by the time the pr exists, the model is already in your head and reviewing it is just verification. skip those stages and the cost doesn't disappear. it stacks up and lands on you all at once, after the code exists, when every decision is now expensive to change. the polished pr is the trap. it looks like progress. it's actually a bill coming due. (credits to CC for helping me articualte this idea)

• 
  XFutuRestyle (@RestyleFutu) reported 9 minutes ago

  Why are the plugins in the Codex app in Windows so poorly designed that they keep disappearing? People are even creating entire threads on GitHub about this issue. "Chrome plugin disappeared from Codex App marketplace after update; cached browser-client is not trusted"

• 
  AI Crave (@wecraveai) reported 9 minutes ago

  THIS ANDROID APP TRACKS YOUR LOCATION WITHOUT GPS. NO SATELLITE. NO CELL TOWER. NO INTERNET. Just your phone's accelerometer, compass, and gyro doing math in real time. It's called DeadReckoning. GPS has one fatal weakness nobody talks about: it dies the moment you go indoors. Underground tunnels. Hospitals. Malls. Warehouses. Parking garages. Anywhere with a roof or a wall or a building nearby that bounces the signal wrong. Google Maps just stops working. Apple Maps just stops working. Every $400/year enterprise indoor positioning SDK just stops working. This free Android app doesn't stop working. Because it never needed the satellite in the first place. Here's how dead reckoning actually works: → You start at a known point → The accelerometer detects every step you take → The gyroscope tracks every turn you make → The compass holds your heading → The app integrates all three in real time and draws your path → No signal required. No towers. No beacons. No WiFi. Nothing external. It's the same navigation technique ships used before GPS existed. Sailors in the 1600s crossed oceans with it. This brings it to your Android phone. Here's the wildest part: The entire indoor positioning industry is worth billions of dollars. Cisco sells hardware beacon networks for enterprise indoor tracking. Zebra Technologies charges six figures to map a single warehouse floor. Apple built a whole proprietary protocol called Indoor Maps that requires venues to submit data directly to them. This repo does the same core thing with sensors that are already in your phone. For free. In Java. On GitHub. 115 stars. 50 forks. 55 commits. No license restrictions. One honest note: dead reckoning accumulates drift over time. The longer you walk, the more the position estimate wanders from reality. It's a physics problem, not a code problem. For short to medium distances indoors, it works. For long sessions you need a correction source. But as a foundation for indoor nav, this is the whole idea. The billion-dollar indoor mapping industry doesn't want you to know your phone already has everything it needs. Repo in the first comment.

• 
  Pablo Pedrotti (@pablonpedrotti) reported 10 minutes ago

  @github Are you going to fix the extreme token usage, bugs and poor responses of Copilot? Even if you want to pay API prices it is a terrible idea to do so on Copilot. Tasks that used to take 5 to 10 minutes on Copilot now take me 30 seconds on Codex sub with Pi, with better results.

• 
  Bipin Paul (@iAmBipinPaul) reported 10 minutes ago

  @lukehoban The only issue is that GitHub Copilot’s price is too high, so most users will not choose it.

• 
  Strata (@ChainZenit) reported 13 minutes ago

  A lot of "AI coding agents" are just people who can't code finding new ways to not code. everyone's building agent frameworks. ship it. celebrate. then Tuesday comes and the bug is in the architecture, not the prompt. here's the uncomfortable truth: the tool doesn't matter if the person using it can't think. Claude can write your code. cool. can it tell you you're solving the wrong problem? GitHub trending is 70% AI wrapper repos right now. half of them will be abandoned in 3 months. not because the tool failed. because the builder never learned to build. vibe-coding is multiplying by zero. the thing that compounds isn't the tool. it's the judgment you refuse to outsource.

• 
  Jesus (@codexJesus) reported 21 minutes ago

  @guinnesschen Prompt: Scan GitHub for bug reports, and then for the easy looking bugs, create new threads in worktrees to fix them. For the most important ones pin them as well

• 
  Lummox (@Lummox_eth) reported 21 minutes ago

  HERMES AGENT CROSSED 140,000 GITHUB STARS IN 3 MONTHS AND JUST BECAME THE MOST USED AGENT IN THE WORLD. Most AI agents forget everything between sessions. Hermes writes its own skills from experience. Next time it runs the skill, improves it, and gets faster. Independent benchmarks show agents with 20+ self-created skills complete similar tasks 40% faster than fresh instances. Qwen 3.6 where the 35B version outperforms last year's 120B models at one third the memory footprint. DGX Spark with 128GB unified memory running everything locally at $0 per month after hardware. The setup takes 30 minutes. LM Studio plus Qwen 3.6 27B for the model server. One install script for Hermes. One config connecting them. Set context window to 65,536 tokens or nothing works. After one month of daily use your skills directory has 20 to 50 learned workflows. Your Hermes is genuinely different from anyone else's.

• 
  riRoyal.Base.eth (@0xRiRoyal) reported 26 minutes ago

  hope everyone is doing well, ok im gonna say something most farmers wont. spent like 2 hours in quip's github last night and... most post quantum projects in crypto have nothing visible. roadmaps, a litepaper, maybe one demo. you cant actually read what they built. @quipnetwork has it all sitting there. wrapper contracts, mining design, testnet harness, the difficulty logic. just out in the open. idk, that matters more to me than i thought it would. you cant audit a roadmap. you can audit code. theres a whole class of crypto projects right now hiding behind stealth mode or selectively open or whatever the term is this week. usually because theres nothing real to show yet. if a team is willing to put their post quantum implementation in public, two things are probably true. they have something real, and they're inviting people to find problems before adversaries do. most projects say theyre serious about security this one lets you check

• 
  Ed Zynda (@what_the_func) reported 26 minutes ago

  I don't know if it's some kind of scam or not or what their angle is but I keep getting vuln reports for MCP Go, an OSS MCP package for Golang. Just file a ******* issue in Github bro, I ain't reading your long *** ******* email that's probably AI slop.

• 
  Paula Vazquez (@VampireGurlAI) reported 26 minutes ago

  @tekbog Prediction could be fatale with claw and I poked the bubble with some of the employees and they told me to read GitHub and would not answer system questions not even a few days later w/ users actively haven security issues von by passing hacking web scrapping still happening Microsoft put on a show performance and mask off not only 24/hrs later

• 
  Andres Eger (@EgerDev) reported 27 minutes ago

  @zuess05 When even Claude can’t fix a bug, I try it on Grok or Codex to see what they find. If that doesn’t work, I go back to the old days digging through GitHub or StackOverflow lol.

• 
  Sam Thapa (@SThapa123456) reported 27 minutes ago

  i told claude to fix a github issue without reading the issue myself. it opened a pr. looked clean. now i'm sitting here trying to do three things at once. understand what the issue actually is. understand what the pr actually does. steer the architecture if it went the wrong way. all in the same head. in the same moment. with a slack notification from my ceo pending. something i'm realizing as i do more agentic engineering: skipping the plan doesn't save effort. it just defers all of it to the worst possible moment. @theo and @steipete aren't big fans of the talk-talk-plan-execute flow. the argument is roughly that modern agents are capable enough that the ceremony slows you down more than it helps. just let it cook. i get it. but what i'm finding for myself is that plan-first isn't ceremony, it's a cost-spreading strategy. you pay the "understand the issue" cost when it's cheap, before anything is built. you pay the "shape the solution" cost at the plan stage, when changes are one sentence instead of a re-implementation. by the time the pr exists, the model is already in your head and reviewing it is just verification. skip those stages and the cost doesn't disappear. it stacks up and lands on you all at once, after the code exists, when every decision is now expensive to change. the polished pr is the trap. it looks like progress. it's actually a bill coming due. (credits to CC for helping me articualte this idea)

• 
  Rowan Void (@rowanvoid) reported 29 minutes ago

  It's wild how many people in software would rather put a trigger warning about their terrible personalities on their GitHub profile than get medicated and go to therapy.

• 
  rehash3d (@r3hashed) reported 30 minutes ago

  @Polymarket JUST IN: Polymarket is down 15% of the time taking over GitHub in the leaderboard

• 
  Noman Gul (@NomanGulKhan) reported 31 minutes ago

  @gregpr07 I also made the switch but somehow it was draining battery. there are some related issues opened in their github repo.

• 
  Ziwen (@ziwenxu_) reported 32 minutes ago

  I think I finally figured out why I stopped enjoying OpenClaw. Not because it's bad. But because I was spending more time maintaining my AI workspace than actually using it. Every update meant checking dependencies, fixing broken workflows, reading GitHub issues, and rebuilding things that worked yesterday. At some point, the tool became another job. That's what surprised me about Hermes. It feels less like a framework and more like a finished system. The biggest difference? - When I open OpenClaw, I think about maintaining the system. - When I open Hermes, I think about what I want to build. If you've been feeling AI tool fatigue lately, you're definitely not alone. Read my full breakdown on why I changed my mind, then watch NetworkChuck's new guide if you want to get it set up in the cloud. It’s well worth the watch.

• 
  iris (@reporadars) reported 33 minutes ago

  I track GitHub trends daily. These stood out 6.2k ⭐ codeburn > See where your AI coding tokens go. Interactive TUI dashboard for Claude Code. 1.4k ⭐ mcp-brasil > MCP Server para 41 APIs públicas brasileiras 1.4k ⭐ hermes-hudui > Web UI consciousness monitor for Hermes — the AI agent with persistent memory Links below

• 
  Emile (@eledure) reported 34 minutes ago

  github down? @github

• 
  Patricio Lobos (@strandedinoslo) reported 34 minutes ago

  @dazfl @nickchapsas Still doing .NET in VScode, I've just downloaded OpenAI extension, working fine, no issues or timeouts like with Claude or paying for a new home with github copilot.

• 
  Maciej Soroczyński (@soroczynski_com) reported 38 minutes ago

  More about base64 that been use for hacking GitHub: Why do hackers use Base64? Przegląd od AI Hackers use Base64 primarily for obfuscation (hiding their tracks) and system compatibility rather than for encryption. Base64 is an encoding method that translates raw, unreadable binary data (like malware executables) into a safe, standard string of 64 printable text characters (A-Z, a-z, 0-9, +, and /).Here is exactly why threat actors rely on it:1. Evading Security Filters (Obfuscation)Naive security filters, firewalls, and antivirus solutions look for specific malicious text or keywords. By encoding malicious scripts (like PowerShell) into a Base64 string, hackers turn recognizable code into an innocuous block of text, allowing the payload to slip past these defenses undetected.2. Safely Transporting PayloadsBase64 was originally designed to transmit binary files (like images or attachments) over text-only protocols like email (SMTP) or web traffic (HTTP) without the data getting corrupted. Hackers use this exact same property to inject malicious files or commands directly into web requests, HTTP headers, or cookies.3. Hiding Command and Control (C2) TrafficWhen malware communicates with a hacker's server, it often needs to send stolen data or receive instructions. If the malware sends this data in plaintext, network defenders and Intrusion Detection Systems (IDS) will easily spot it. Encoding the traffic in Base64 hides the intent of the communication, making it look like standard web traffic.4. Bypassing Bad Character LimitsCertain communication channels—such as URLs or specific command-line arguments—will crash or misinterpret complex binary characters. Because Base64 strictly uses standard, keyboard-friendly ASCII characters, hackers can use it to safely pass their code through restrictive input fields without breaking the system.Important note: Base64 is not encryption. It is just a different format for representing data. Anyone (and any modern security tool) can decode a Base64 string back to its original form in seconds using freely available tools like CyberChef.

• 
  Pedro Albuquerque (@petersaints) reported 42 minutes ago

  The models I have been testing have been mostly Qwen 3.5 4B and 9B, and Gemma 4 E4B. One of the things I did was integrate the LM Studio local API Server into VS Code as an alternative to GitHub Copilot Pro.

• 
  Chelm's Deep (@ChelmsDeep) reported 44 minutes ago

  @plainionist @PaulGugAI This actually works ridiculously well. Was having problems with recurring errors and debug loops. I harvested information from some github repos built in the same stack, added a skill to read the knowledge base and search the repos, fixed 12 issues on the first turn.

• 
  AIDegen (@nrsvv11) reported 59 minutes ago

  A Chinese developer posted a 41 second video on Bilibili showing the dashboard for his one person company. 19 autonomous AI agents handled everything 30 human employees used to do. Electricity bill: around 600 dollars a month. He pointed at the grid of cards on his monitor. Researcher. Copywriter. Designer. Developer. Sales. Support. Checker. The system ran 24 hours a day. He approved decisions from his phone on the subway. A laid off mid level manager at a Shenzhen electronics factory recognized the cubicle in the wider shot. He sent one screenshot to a Bilibili tech forum: timestamp 0:23. Pause at 0:23. Ignore the dashboard. Ignore the Dell monitors. Look at the giant union sign on the shelf in the upper right corner of the frame. That sign is not a decoration. That is the entry sign of his old employer's union office. The cubicle in the video was not his apartment. The cubicle was the corner desk in the union office where laid off workers came every morning for free coffee and wifi. He had not built a one person company that replaced 30 employees. He had been one of the 30. The company had laid him off six months earlier when they bought a SaaS platform that did eighty percent of what his department used to do. The 19 AI agents were real. The agents were also a demo. He had been running the system for himself for six months. He had pitched it to his former employer twice. Both times they had passed. The Dell monitors were not his. They belonged to the union steward's desk. He used them every morning from 9 AM to 1 PM because the union office had air conditioning and his apartment did not. The 600 dollars a month electricity bill was real. The electricity was the union office's. The union steward had agreed to let him plug in his local server in exchange for him helping ten other laid off workers polish their resumes. 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 laid off manager had been one of them. He had built the 19 agent system on top of that fork as proof that the company that fired him had been wrong about him. He was not a founder demonstrating the future of one person companies. He was the first laid off middle manager in his city to figure out the only way to win the AI replacement argument was to present yourself as the one who pressed the button. The clip is at 2.1 million views. The zoom on the union sign got another 1.6 million. Chinese tech viewers are still sharing the video. Still nodding. Still asking how to license the system. The system is still running. The cubicle is still at the union office. He still has not heard back from his former employer. He told the internet he had replaced 30 employees. The 30 employees he claimed to have replaced included him.

• 
  Cameron G | Product Security Advisor (@camgrimsec) reported 59 minutes ago

  Attack Scenario: Attacker posts a "pre-trained CrewAI agent" on HuggingFace or GitHub. Tutorial title: "Skip the training, use my agents." User runs crewai train --trained-agents-file downloaded.pkl The pickle inside opens a reverse shell. The attacker is now inside the server No exploit code. Just a file

• 
  Sahil Bansal (@bansal_saahil) reported 1 hour ago

  @pamelafox @slicknet Does this BYOK custom end point config requires us to login to github?

• 
  Jongwon Park (@JongwonPar9958) reported 1 hour ago

  @jimmykoppel Yeap, Github issues / PRs related to benchmark defect.

• 
  François Best (@fortysevenfx) reported 1 hour ago

  I won’t be removing old tags obviously, and GitHub has immutable releases & tags, but you can never know from the outside if a repo has this turned on. That leaves the problem of discovery, the only immutable place with a modification record would be the README or a CHANGELOG file.

• 
  emeꕤ (@mixxariana) reported 1 hour ago

  @uwukko hi wukko, are there any news related to drm? i was reading the issue in github and there hasnt been any new comment